Good daytime! I don't understand how to say clearly... In example: Should I past something like <maintainer type="project"> <email>guru@gentoo.org</email> <name>GURU project</name> </maintainer> in metadata.xml or usual Proxy maintainer project should be enought? <maintainer type="project"> <email>proxy-maint@gentoo.org</email> <name>Proxy Maintainers</name> </maintainer> Reproducible: Always I also don't understand what category should fit bug...
Please don't mention the proxy maintainers. The proxy maintainers project is not related to GURU. Just setting yourself as maintainer like: <maintainer type="person"> <email>denis7774@gmail.com</email> <name>Denis Reva</name> </maintainer> is perfectly fine. You might also want to join #gentoo-guru on freenode where you can get further support. -M
However, if we'll maintain ebuilds to mainline Gentoo tree then we should have something like to know that ebuild is prepared from GURU project: <maintainer type="project"> <email>guru@gentoo.org</email> <name>GURU project</name> </maintainer>
Thanks for reply Max Magorsch
I don't think we currently want to do so. As (per GURU regulations) a package should be removed from GURU, as soon as the package is moved to ::gentoo. So the package is not related to GURU anymore, once it gets moved to ::gentoo.
(In reply to Max Magorsch from comment #4) > So the package is not related to GURU anymore, once it gets moved to > ::gentoo. Ok. So If I develop ebuild in ::guru, then it moved to ::gentoo, should I become something like proxy developer when ebuild is should been fixed? Or will I become usual Gentoo developer?
In other words, how can I fix those ebuilds that's mainlined to ::gentoo?
(In reply to Reva Denis from comment #6) > In other words, how can I fix those ebuilds that's mainlined to ::gentoo? If you don't become a full-fledged Gentoo Developer, you can still submit pull request for those ebuilds to the Gentoo git repo. For example, you can open a PR on the Gentoo repo mirror on Github: https://github.com/gentoo/gentoo/
(In reply to William Breathitt Gray from comment #7) Ok. Next question: Who is responsible for supporting ebuilds that have mainlined from ::guru to ::gentoo?
GURU can't maintain projects in Gentoo. Also, strictly speaking 'GURU project in metadata.xml' would mean devs overseeing the project and not members. If someone decides to move the package from GURU to Gentoo, that person is responsible for maintaining it forward. If you want to co-maintain it, you can do that with the person in question or via proxy-maint. If you want to move it yourself, you can try via proxy-maint but we're overburdened at the moment, so can't promise you it'll happen.
(In reply to Michał Górny from comment #9) > we're overburdened at the > moment, so can't promise you it'll happen. It's visible at number of GitHub pull request that becomes larger and larger :) Some of my pull requests even haven't reviewed yet. Your overburdened conditions has something to do with the quarantine due to the COVID-19 epidemic, doesn't it? May be we should create annonce about GURU project with eselect news? Not much users know about it… So I thought much users will want to get their loving packages faster. Ok, I mark resolved its. GURU is seems like official Gentoo user overlay with following official policing :)
