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

Define 'Path to Maintainership' and 'List Maintainers' #11

Open
GeorgLink opened this issue Feb 12, 2018 · 5 comments
Open

Define 'Path to Maintainership' and 'List Maintainers' #11

GeorgLink opened this issue Feb 12, 2018 · 5 comments

Comments

@GeorgLink
Copy link
Member

Per proposal in chaoss/community#5 :

The README.md of the repository contains a list of who is maintainer. Each CHAOSS repositry brings together different people and they document in the repository specific CONTRIBUTING.md how somone becomes a maintainer on their repository.

TODO:

  • Specify 'path to maintainership' for this repo in CONTRIBUTING.md file
  • List current maintainers in README.md file
@Polaris000
Copy link
Contributor

Is there a reason this hasn't been looked into?

@Polaris000
Copy link
Contributor

Suggest closing this issue if the matter has internally been resolved.

@GeorgLink
Copy link
Member Author

Hi @Polaris000,

I appreciate that you review old issues and try to clean up.
This request is to improve the value of README's across CHAOSS projects. I don't see it done yet in this repository, which is why I would like the issue to remain open.

@Polaris000
Copy link
Contributor

Thanks for the reply! Yes, I had noticed that the requested changes had not been made. In fact, only a few repos have closed this issue. Since its been over a year, I thought that it had been decided to scrap the idea in a weekly meet and someone forgot to close the issue. That's all.

@GeorgLink
Copy link
Member Author

That's understandable. Thanks!

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