Concept draft for a Bugzilla-based system to report help-needing projects ------------------------------------------------------------------------- Author: Tobias Klauser Last changed: $Date: 2004/06/07 13:34:00 $ 1. Introduce a new Product called "Help needed" (proposals for other names are welcome) 2. Introduce the following Components, belonging to the mentioned Product * Orphaned package (Packages which need a new maintainer) * Developers needed (Herds who seek new members) * Documentation (Need help with documentation) * Help with package (Help on packaging a new software) * General (Need help in general) * Other Maybe I forgot some points. I don't know the exact struture of the Gentoo Project and all its subprojects etc so I perhaps mixed up something. So it would be nice if an insider could check and complete the above list? 3. Now, if a developer, a herd or even users (no I need help installing software XY or configuring device ABC! Such request belong in the forums) need help, they can fill in a bug report. They should add some points to the report, so that a potential candidate for help can easily see if he/she is able to do that job. I imagine something like: * Which project/package is concerned (Should go into the Summary) * Description of the job * Needed skills * Reason for seeking help Example: Product: Help needed Component: Orphaned package Summary: Package xy needs a new maintainer Description: I seek a new maintainer for package xy because I don't have enough time anymore for maintaining it. The job involves: * Checking for new versions of the package * Writing ebuilds for the new versions * Test the ebuilds * Add them to CVS * Mark the ebuilds stable, if they are well tested by the community * etc. Skills you should bring: * Good skills in Shell-/Bash-Scripting * Good understanding of Portage and Gentoo in general * etc. 4. When the reports are submitted, other developers or interested/advanced users can seek through these easily, because it's all Bugzilla-based. If someone wants to help, he or she can add a comment which should include a short introduction of him-/herself with skills, experience etc. 5. The developeri(s) who submitted the request, can now contact the potential candidates and maybe quiz them, perform other steps. 6. The bug can be closed, when one or more skilled persons were found. ---