Summary: | New QA subproject: Devmanual | ||
---|---|---|---|
Product: | Documentation | Reporter: | Markos Chandras (RETIRED) <hwoarang> |
Component: | Devmanual | Assignee: | Gentoo Quality Assurance Team <qa> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | recruiters |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 439994 | ||
Bug Blocks: |
Description
Markos Chandras (RETIRED)
![]() Why not introduce a new devmanual alias? Would that justify a new QA subproject? Or a new project? Or just an alias? And who would be eligible to be in that alias as devmanual git access is a bit messy? I don't think all devs have access to it and I am not sure who does to be honest I'd say a new QA subproject. Definitely not recruiters. (In reply to comment #3) > I'd say a new QA subproject. Definitely not recruiters. Fine me by. How would you like to handle the permissions? Should all recruiters+qa be in the ACL? Who else? Having said that, I believe everyone should be (or can be) part of this project. Even users who want to improve it. What do you guys think? In this case it would make more sense to move it from git.gentoo.org to git.overlays.gentoo.org to make it more visible so potential contributors can follow the normal git contribution path for submitting patches. (In reply to comment #5) > Having said that, I believe everyone should be (or can be) part of this > project. Even users who want to improve it. What do you guys think? In this > case it would make more sense to move it from git.gentoo.org to > git.overlays.gentoo.org to make it more visible so potential contributors > can follow the normal git contribution path for submitting patches. Ignore that. it is already in git.overlays.gentoo.org I'd honestly keep it to "all devs" — we can easily check who's doing what. That's also why I don't want to have it on either qa@ or recruiters@. And hopefully somebody (Brian?) will get rid of the stupid guidexml hybrid (which is the main reason why I'm not touching it with a 10' pole. Ok everything is now in place. I will send the announcement for the revamped subproject soonish |