On 8/21/06, Werner Punz <[EMAIL PROTECTED]> wrote:
In every large open source project, it's natural that certain developers tend to focus on certain parts of the code. However, assigning "formal" ownership or responsibility -- or even implying that there is such a thing -- is not the way Apache projects work. We are all corporately responsible for all of the code, and have freedom to get involved with any of it.
Need to coordinate, or ask who might be affected by a change you want to make? That's what the dev list is for.
Craig
Jurgen Lust schrieb:
> Op ma, 21-08-2006 te 11:14 -0400, schreef Mike Kienenberger:
>> Do we want to list out who's responsible for components on the wiki?
>> It seems like ththis would encourage having people send email directly
>> an individual committer rather than the MyFaces community.
>
> Hmm, good point.
>> Once things are checked into the repository, we should all be
>> collectively responsible for the code. There are going to be people
>> who have a lot more invested into a component, but does that require a
>> tracking page? SVN logs will show who has been committing changes
>> to a particular component.
>
> Personally I favour the way they do things at Gentoo Linux: instead of
> everyone being collectively responsible for the code, they have divided
> their committer community into groups, each with a project lead. For
> example, they have a Java group, an Apache group, etc.
>
> Jurgen
>
>
Actually I just started the page to document which components
are dojoized and which are not,
the maintainers are not really mandatory on this,
it just makes things easier...
I like the idea with the groups btw...
In every large open source project, it's natural that certain developers tend to focus on certain parts of the code. However, assigning "formal" ownership or responsibility -- or even implying that there is such a thing -- is not the way Apache projects work. We are all corporately responsible for all of the code, and have freedom to get involved with any of it.
Need to coordinate, or ask who might be affected by a change you want to make? That's what the dev list is for.
Craig
