I think you summarized most of the things we talked about at the meeting. The only thing I like to know is which subjects from the previous meeting will be discussed in more detail in the upcoming meetings. I am not (yet?) in the MMC, but I would make an agenda like this:
First meeting - What are the roles and tasks in the community and which belong to the MMC? - What is Mmbase? - What belongs in the source repository and what not? - Everything under the bridge? What about Modules, Builders and Observers? - Above the bridge? Small features (editors, editwizards, taglib, templates)? Full applications? Second meeting - Which communication channels should we use? - Infrastructure for contributions? How can people find sources related to MMBase? Nico PS. This weekend, I added the hacking guide to cvs head. A lot of the coding standards are added to the style guide. The rest of the guide is in /documentation/contribute.xml. I left a lot of chapters empty and they should be filled in later. I will add those when we have discussed them in the upcoming meetings. > -----Oorspronkelijk bericht----- > Van: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Namens Kees Jongenburger > Verzonden: dinsdag 22 februari 2005 13:39 > Aan: developers@lists.mmbase.org > Onderwerp: [Developers] shout > > > Hi > > it's been a while since the last SHOUT contest. I did not see any > posts about this yet. If there is not discussion about it we might as > well skip the next meeting. > > I don't feel totaly free to say everything here > > This is what I remebered (a least it's more the nothing). I did not > put names in the shouts > > SHOUT (What I remember of it) > > Ernst -> Will changing the licence(to GLP) help in making parties > contribute? > SHOUTS: > -> We will not change the licence (we know some people that will > object) > -> We don't want the code that is throwed over the wall > -> Some problems encountered are not solved by any party , they just > code around it. A good example of such a never solved bug is the > behaviour of the cache (that gets deleted when a commit occurs). Did > anybody even bother to file a bugreport? > > Andre -> furure goals and roadmap, we need that roadmap!!! > SHOUTS: > -> We already know what we want in the roadmap wha't the point > -> having a roadmap will help finding funds/resources > -> creating a detailed roadmap (containing information about how we > expect the stuff to be implemented will help in the sense that > companies wanting of help will also know what we expect) > -> creating a roadmap costs time / effort. Who will invest in that? > -> Why a roadmap, only things that programmers will implement will > get implemented. It is enough that a programmers want's to implement > something to put it on the roadmap. > -> We want somebody to go and fetch resources > > RvM: explained AGAIN :) why he left the MMC and thinks the MMC as we > know it can't work. In a few words : MMC / Developers are not an > official instance and can't therefore make decisions. > SHOUTS > ->We agree that there is a problem > ->We want to keep the MMC as is > ->We want to drop the MMC as we know it > ->We want to create an instance that can support the > developers(beweging/vereniging) > ->We want the foundation to support the developers > > > Scb2: Do we need somebody that can go shopping with a roadma. > To free resources to implement functionality in an > open-source fashoin SHOUTS > -> actually this is what Scb2 shouted for every topic > anybody called > > Nico: (don't remeber) but.. > SHOUTS: > ->hacking MMBase is not a hacking guide (to long) > ->hacking MMBase have overlap with other documentation > ->hacking MMBase is a read idea and should be a first > read for somebody who want's to commit code to the mmbase community > > Flax: It's very hard to get started using MMBase when you are > used to programming struts/ using an IDE. Flax sees MMBase as > one of the components that is used in a system. If the > component fails it should be possible to directly jump into > the source / debugger > SHOUTS: > -> We don't want newbies that don't know cvs > -> Why isn't there a netbeans / eclipse project file in CVS? > -> we want to go HOME , we are not talking for 4 ours > > keesj: What to to with 3rd party apps > SHOUTS > -> lets VOTE! > -> lets go HOME. > _______________________________________________ > Developers mailing list > Developers@lists.mmbase.org > http://lists.mmbase.org/mailman/listinfo/developers > _______________________________________________ Developers mailing list Developers@lists.mmbase.org http://lists.mmbase.org/mailman/listinfo/developers
