Patch Manager ------------- The Patch Manager watches the developers mailing list and make sure that no patches "slip through the cracks".
This means watching every thread containing "PATCH" mails, and taking appropriate action based on the progress of the thread. If the thread resolves on its own (because the patch gets committed, or because there is consensus that the patch doesn't need to be applied, or whatever) then no further action need be taken. But if the thread fades out without any clear decision, then the patch needs to be saved in the issue tracker. This means that a summary of any discussion threads around that patch, and links to relevant mailing list archives, will be added to some issue in the tracker. For a patch which addresses an existing issue tracker item, the patch is saved to that item. Otherwise, a new issue of type 'PATCH' is filed, and the patch is saved to that new issue.
The Patch Manager needs a basic technical understanding of MMBase, and the ability to skim a thread and get a rough understanding of whether consensus has been reached, and if so, of what kind. It does *not* require actual MMBase development experience or commit access.
CVS ---------------------- Only one type of user exists in the CVS world: committer. However, three roles exists in my CVS world: committer, module owner and admin.
Committer A committer is a user who has access to commit changes to files that are under CVS control. Committer carry the responsibility to check in quality code. Committers almost never need system level access to the CVS machine.
CVS module A module is any number of source files that form a meaningful package. Submodules may exist within top-level modules.
Module owner A module owner is a committer who has been assigned to monitor or co-ordinate a file or a number of files under CVS control. Module owners would be responsible for solving bug reports, enhancement and change requests, patch submissions, and so on. A module owner would also be responsible for fixing your tree breakages if you are not around to fix them. Module owners rarely need system level access to the CVS server.
CVS administrator The CVS administrator is a committer who has commit access to the $CVSROOT/CVSROOT directory; Administrator access within the repository is controlled by putting the user in the UNIX group that has write access to the CVSROOT in questions. An admin will have command line access to the CVS machine.
The MMbase "CVS" task is a synonym for Community-maintained Module owner. The current community-maintained modules are linked in the "all" module (mmbase all src config html documentation tests applications). CVS administration is done by the hosting task.
Nico Klasens
_______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
