Graduation check list
I have written up a guide for new project to oVirt. http://www.ovirt.org/wiki/Graduation_check_list Take a look and fire any edits / comments regards Carl.
----- Original Message -----
I have written up a guide for new project to oVirt.
http://www.ovirt.org/wiki/Graduation_check_list
Take a look and fire any edits / comments
Only thing that I don't feel is clear is maintainer commitment (we will have very little use of dead projects).
regards Carl. _______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
----- Original Message -----
On 10/25/2011 05:24 AM, Ayal Baron wrote:
Only thing that I don't feel is clear is maintainer commitment (we will have very little use of dead projects).
Can you please provide more detail around what you mean.
A project which is not actively maintained (e.g. one patch every couple of months) who's maintainer does the bare minimum to integrate with oVirt but nothing else or when approached does not interact with the community should not be graduated. To graduate, a project should be active (a stable flow of patches), probably with contributions from more than one person, maybe even have more than one maintainer.
thx Carl.
On 10/25/2011 08:44 PM, Ayal Baron wrote:
----- Original Message -----
On 10/25/2011 05:24 AM, Ayal Baron wrote:
Only thing that I don't feel is clear is maintainer commitment (we will have very little use of dead projects). Can you please provide more detail around what you mean. A project which is not actively maintained (e.g. one patch every couple of months) who's maintainer does the bare minimum to integrate with oVirt but nothing else or when approached does not interact with the community should not be graduated. To graduate, a project should be active (a stable flow of patches), probably with contributions from more than one person, maybe even have more than one maintainer.
That is pretty well covered in project maturity etc. Carl.
----- Original Message -----
On 10/25/2011 08:44 PM, Ayal Baron wrote:
On 10/25/2011 05:24 AM, Ayal Baron wrote:
Only thing that I don't feel is clear is maintainer commitment (we will have very little use of dead projects). Can you please provide more detail around what you mean. A project which is not actively maintained (e.g. one patch every couple of months) who's maintainer does the bare minimum to integrate with oVirt but nothing else or when approached does not interact with the community should not be graduated. To graduate, a project should be active (a stable flow of patches),
----- Original Message ----- probably with contributions from more than one person, maybe even have more than one maintainer.
That is pretty well covered in project maturity etc.
Ok.
Carl.
participants (2)
-
Ayal Baron -
Carl Trieloff