> > Andr� van Toly wrote: > > At 08:27 +0100 15-02-2005, Pierre van Rooden wrote: > > > >> Nico Klasens wrote: > >> > >>> To get this thread going, I have put together a hacker's guide to > >>> mmbase with a lot of help of some other excellent guides > on the net. > >> > > I think it's a good start for a hacker's guide. A few remarks, > > > Participating in the community > > ============================== > > I think a hacker's guide must mention #mmbase even though not > all developers are participating in this channel.
I will add this to the contribute.xml in the docs. > > Directory layout > > ================ > > > > A rough guide to the source tree: > > is this complete enough for a hacker's guide? The readme.txt > inside the distro contains a more complete directory tree, > maybe put a reference to this one in the hackers guide? The only directory lisitngs I could find were from the source and binary distribution which are different from the CVS 'all' module. I expect that someone who is going to develop will checkout the HEAD from cvs. > > The "Patch Manager" Role: > > ------------------------- > > > > MMBase usually has a Patch Manager, whose job is to watch the > > developers mailing list and make sure that no patches "slip > through the cracks". > > > > Although it's everybody's responsibility to watch the > patches, I think it's a good idea to assign a patch manager. > I also think it's a good idea to create a way to add patches > to the bugs in the bugtracker. True, it is the patch manager's responsibility that all patches are picked up by someone. > > Commit access > > ============= > > > > @@TODO@@ This is what I prefer. This is different from how > it is now > > in MMBase. > > > > I think we must have a discussion about this separately from > this hackers guide. This is or must be an issue in the whole > 3rd party discussion also. That is why I left this out of the contribute.xml. If we all agree on it then I (or someone else) should add it to the file. Nico _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
