I was reading comments on Slashdot and the guy has been AWOL for almost a
year now.  Apparently, the developers have access to the web site, but not
the domain control.  They also should have access to all the build scripts
and what not.  So, they could fork if all else failed, but, it would still
be messy as they would have to find another domain name (to be safe).
Very unfortunate situation to be sure.  I use CentOS a lot and it has
served me very well.  No doubt it will continue somehow, but, it will also
be harder to trust in it when recommending it to a customer given all
this.  Sure it can happen to a closed-source product/project as well, but,
it seems with FOSS there is a stigma of an added need to prove it can be
trusted.  People will tend to see only the risk of it coming apart at the
seams as opposed to the reality that the FOSS nature of it is really
insurance of just the opposite.  Will be interesting to see how all this
unfolds.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Kevin Eldridge
Sent: Thursday, July 30, 2009 09:36
To: [email protected]
Subject: [nlug] Re: Unhappiness at CentOS


Wow. Hopefully the group can obtain some form of proper leadership for
CentOS for now and many years to come. CentOS has a strong following.

Kevin E.

Sent via BlackBerry by AT&T

-----Original Message-----
From: Curt Lundgren <[email protected]>

Date: Thu, 30 Jul 2009 07:29:16 
To: NLUG<[email protected]>
Subject: [nlug] Unhappiness at CentOS



For those interested, there's some trouble at CentOS - bad news for
me, as it's my favorite distro for servers:

http://www.centos.org

Curt





--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nlug-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to