-
Notifications
You must be signed in to change notification settings - Fork 91
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
README: Add PSC's in charge #140
Comments
@OCA/core-maintainers |
Makes sense to me. |
The information is in the OCA instance. Dont know how to recover it to générate readme... |
Yes that's a point I don't have answer. |
isn't https://github.com/OCA/maintainer-tools/blob/master/tools/oca_projects.py where the info about PSCs/repos lives? |
I suggested to keep it simple, and make it a copier question. |
It can be done by a controller in https://odoo-community.org, where all that information is already stored. For example, Copier could just put a link to https://odoo-community.org/psc-teams/find-by-repo?repo=OCA/project in the readme which just makes a 302 redirection towards https://odoo-community.org/psc-teams/project-service-28. |
There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
Not sure it's simple if we duplicate the information in two places. (in odoo-community + in copier answers file). There will be harder to maintain, don't you think ? |
Good news: we are going to manage repos via github actions. I'm sure we can handle this too. |
Why having a different organization for such repo? |
It's temporary. We needed a sandbox to play with. We'll move what's needed to OCA when ready. |
Provide a more ergonomic way for OCA#140 (comment) to fix OCA#140.
I don't know if it's possible, but this could be a help for contributors to have PSC's name and links (to odoo-community.org) in repos README.
The text was updated successfully, but these errors were encountered: