> > Without getting into the products itself except for MMBob, that will be > made opensource soon as promised. Im not sure what this mail is > about. It seems you are asking the makers to 'backup' their claims of > opensource and i think that is a good thing. Would it not be better > to create a guideline on what we as developers/users of mmbase feel > makes a correct/nice mmbase related project ? Why not give us > a few 'guidelines' you feel are important. > > Let me give you a few of my own (what i would like to see) : > > A 'mmbase' approved application has : > > 1) A clear way of distribution > 2) A clear license model (opensource or not) > 3) if opensource, sources must be provided > 4) A clear maintainer (person or company) > 5) Following a technical set of demands per version (say 1.7, most use > bridge vs core, taglib vs jsp etc etc) > > in return mmbase comminity could give a stamp and rating for example > and provide 'space' on their machines for cvs, questions, bugtracker > etc etc. > > I for one would be a big supporter that we as a community start > developing these guidelines and have a way to enforce them when needed. > If you or someone else would like to have a project/meeting/whatever on > this topic could me in for taking part.
I think we are on the same track (only you say it a lot nicer). maybe also a "freshness" to the project to show the activity word!
