-
Notifications
You must be signed in to change notification settings - Fork 216
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
Comments
@repoforge/packagers this is the main issue for the transition period |
Header file repoforge/repo-files@18e0423 |
vault is here http://repository.it4i.cz/mirrors/repoforge-vault/ |
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? |
@agrybas you can submit MRs, guidelines are more less OK. No need to wait for transfer period. |
There's a new server for Mirmon instance at http://rumcajs.fr.pudu.cz/. 24h check will be provided on both instances: A new branch has been created too at https://github.com/repoforge/mirrorlist/tree/gh-pages_new-site |
Everything's OK with the new mirmon server. So |
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 |
To-Do
The text was updated successfully, but these errors were encountered: