Re: [JBoss-user] Re: Recent CVS removals

[Scott M Stark]

Its simply. We are not about to work with developers who we now feel have to be 
watched for every checkin because we don't know what their motives are. There 
was a decision to leave, fine, no action taken. There was a decision to fork, 
fine, you are removed as a developer. Any expection to retain developer status 
is simply absurd, especially given the fact that there was no discussion on any 
public or private JBoss channel. Simple project management 101.

--
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
Dan Christopherson wrote:

Frankly Bill, I don't see what good removing their CVS commit priviledge 
is going to do: now if they want to maintain anything, they must do so 
in a fork. It's LGPL'ed, so the only real restriction is that any 
modifications be publicly available.

As far as trust goes, what about the ability of the user community to 
trust the JBoss project admins? Regardless of the nobility of your 
motivation in taking this action, if you look at it through the eyes of 
a user, it simply looks like the JBoss Group, LLC. got pissed off 
because some people left and started abusing their position as JBoss 
project admins to mess with them. This doesn't help anybody.

Just my observations...

-danch




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user