|Hey, I wouldn't mind if you restricted commit access to CVS to only core
|JBOSS team members as long as the core team religiously reviewed and
|commited patch submittals.  Although I do enjoy having rw access,
|this would
|keep some of the "purity" you're talking about.

I wasn't clear and the "purity" is the wrong word... let me explain

the LOWER the purity the HIGHER the success of the OPEN SOURCE project see?

If we have 99% purity it means we have FAILED as an open source group since
NO-ONE contributes and helps? (btw this is the problem with JOnAS and to a
lesser degree Tomcat, NOBODY really helps besides the "paid corporate"
people (IBM, SUN, EVIDIAN), and that is **failure** from an open source
standpoint).

So I must use another word since in fact I WANT a lot of contributions (->
low purity).

Sue me! I am a physics PhD not an english major.

Managing the flow is another issue, right now i am pretty lax with RW, I
give them like they were candy and see who flies and who craps out.  So far
this has worked pretty good, you being the latest example ('=) but it will
bite me up the ass sooner or later.  So far so good.

So NO, I am NOT interested AT ALL in restricting RW to the tree and
controlling the input... no way!

just be good and remember to practice safe coding... and talk about your AID
right here...

regards

marcf

|
|Bill
|
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development



_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to