Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repoforge Transition #377

Open
10 of 16 tasks
davidhrbac opened this issue Aug 11, 2016 · 9 comments
Open
10 of 16 tasks

Repoforge Transition #377

davidhrbac opened this issue Aug 11, 2016 · 9 comments
Assignees

Comments

@davidhrbac
Copy link
Member

davidhrbac commented Aug 11, 2016

To-Do

  • Mirror infra
    • new master mirror
    • send email to mirror admins
    • recheck mirror status after 96h
    • modify header
    • create new mirror status server
  • Clean-Up
    • create vault (out of rsync tree)
    • move obsolete trees to vault
    • vote?!? on obsoletes
    • README.md
  • Resign
    • create testing GPG key
    • create signing GPG key
    • test resign
    • rebuild release package (a lot of subtasks here)
  • TLD
    • transfer ownership
    • lists site?!?
  • notify CentOS wiki - not dead yet
@davidhrbac davidhrbac self-assigned this Aug 11, 2016
@davidhrbac
Copy link
Member Author

@repoforge/packagers this is the main issue for the transition period

@davidhrbac
Copy link
Member Author

Header file repoforge/repo-files@18e0423

@davidhrbac
Copy link
Member Author

@davidhrbac
Copy link
Member Author

@agrybas
Copy link

agrybas commented Oct 22, 2016

Hi @davidhrbac - if we have new packages to contribute, should we follow guidelines as outlined at http://repoforge.org/package/? Or better wait until the transfer period is over and potentially new procedures are put in place?

@davidhrbac
Copy link
Member Author

@agrybas you can submit MRs, guidelines are more less OK. No need to wait for transfer period.

krallin added a commit to krallin/aptible-omnibus-builder that referenced this issue Dec 8, 2016
@davidhrbac
Copy link
Member Author

There's a new server for Mirmon instance at http://rumcajs.fr.pudu.cz/.

24h check will be provided on both instances:
http://rumcajs.fr.pudu.cz/
http://mirror-status.repoforge.org/

A new branch has been created too at https://github.com/repoforge/mirrorlist/tree/gh-pages_new-site

@davidhrbac
Copy link
Member Author

Everything's OK with the new mirmon server. So mirror-status.repoforge.org CNAME ... CNAME rumcajs.fr.pudu.cz should be available within 600 secs.

@davidhrbac
Copy link
Member Author

RepoForge used to be one of the important repositories for CentOS/RHEL. I know that RepoForge is considered to be clinically dead nowadays. On the other hand RepoForge is still physically alive.

We would like to harness community opinion on RepoForge status and future. In case that you use or used to use the RepoForge I kindly ask you to fill up this form to help us with the decision.

The form is here: https://goo.gl/forms/4SLFnD16K4yJeitt2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants