<div dir="ltr"><div>It's amazing how quickly people trot out conspiracy theories when the stuff they're getting for free might be free but slightly different.<br></div><div><div><br></div><div>I haven't weighed in on this thread-o'-doom yet, and I was hoping not to, but it has simply jumped the fucking shark. If you're really that concerned about our new Red Hat overlords, I'd like to make two suggestions:</div>
</div><div><br></div><div>1. Fedora is coming up on its 21st release, which, at one every six months (roughly), comes out to over a decade of free, community Linux. During that entire time Fedora has been in bed, to a substantial degree, with Red Hat. (Note that I use the non-legal metaphor "in bed" instead of risking some petty bullshit semantic quibble over whether they're "led by" or "owned by" or whatever. They're sleeping together, okay?) And during that entire time, great bearded prophets of doom have emerged from the desert to proclaim that Fedora N-1 was surely the last free and open Fedora because the crushing hand of Genghis Red Hat is squeezing everything good out of it. I'd wager a beer (and this is a serious offer) that every single Fedora release after Fedora Core 1 has had at least one such Chicken Little. Take a browse through their various mailing lists.</div>
<div><br></div><div>Luckily, CentOS will have its Sandy Hook deniers right from its first release after knocking boots with Red Hat.</div><div><br></div><div>Maybe Red Hat is just completely fucking incompetent at corporate takeovers of community projects. Maybe they aren't even trying to take over Fedora or CentOS. Maybe they already have and we're all living in The Matrix brought to you by Red Hat and we don't even know it. Draw your own conclusions.</div>
<div><br></div><div>2. Absolutely nothing is stopping anyone -- including experienced rebuilders like the SL folks -- from building their own OMG MOAR OPEN rebuild. Nothing. In fact, <a href="http://git.centos.org">git.centos.org</a> makes it *easier*, because we have changelogs and historical sources and shit like that, not just a bunch of SRPMs that represent the current state of the repo. If RH really wanted to undermine community rebuilds and prevent them from challenging their market supremacy, they sure as hell would. For instance, I bet a clever lawyer could make a compelling case that RH only needs to release the sources, not the specfiles. And they don't have to release their source modifications at all for many of the more permissive FOSS licenses. They could royally fuck everyone who runs a free clone if that was their schtick.</div>
<div><br></div><div>Again, draw your own conclusions. Maybe RH is just incompetent.</div><div><br></div><div>Then again, maybe we've got a zillion-post thread with an SNR that's indistinguishable from zero because:</div>
<div><br></div><div>1. CentOS is now *more* open than ever, and rather than just making this change they're soliciting community involvement. Which is good. (And they seem to be listening to the need to reflect the RH minor version in the CentOS release version, too.)</div>
<div><br></div><div>2. Some people can't cope with change. When I was in .edu we used to tell this joke:</div><div><br></div><div>Q: How many professors does it take to change a lightbulb?</div><div><br></div><div>A: *CHANGE*?!?!?</div>
<div><br></div><div>Oh noes, RH decided to change the way they give away mountains of work that they're not required to!</div><div><br></div><div>Oh noes, several the CentOS core devs (who had employers before -- you know that, right? and those employers surely expected value from their investment then -- you know that, too, right?) now work for RH!</div>
<div><br></div><div>Oh noes, there's occasionally a point of disagreement between people who use CentOS for a living and those who build it for a living! (Maybe they're two very different constituencies with different goals? Nah, that's absurd!)</div>
<div><br></div><div>3. Any sufficiently large community is bound to have a few of the kind of screw-loose types who think the moon landing happened on a Hollywood sound stage. I mean, the CentOS folks have gone to great lengths at several points to belabor the fact that they really don't have a very special relationship with RHEL. (That's RHEL, not RH.) They pull their sources from <a href="http://git.centos.org">git.centos.org</a> one leg at a time, just like the rest of us, for instance. That certainly doesn't bespeak much of a vast Red conspiracy to overthrow the world. But I guess belief in this conspiracy already hinges upon the absolute incompetence of most of the players.</div>
<div><br></div><div>Ultimately, we as community members have three options. I'll spare you another numbered list, because they're short: We can just flow like seaweed in the tide and take whatever comes our way, which is pretty unlikely given that most us are antisocial nerds; we can continue to contribute *productively* and try to guide CentOS in the direction we want it to go, while recognizing the limitations of any volunteer-run product that depends on the good graces of a public corporation for its raw material; or we can take our ball and go home in a huff to rage against the machine while running Slackware or whatever.</div>
<div><br></div><div>So for the love of all that is holy, and particularly out of respect for the time it takes to hit delete on all of the shitty replies to this terrible thread, please let's can the bullshit conspiracy theories and personal attacks and screaming and crying and throwing our rattle across the room.</div>
<div><br></div><div>Note, if you must, that I do not have a <a href="http://redhat.com">redhat.com</a> email address, nor have I ever. I'm just a dude who deleted a lot of profanity from this email before sending it, I promise. I've spoken my piece, and do not intend to dignify this horrible thread with any further replies (or readings), so now's your chance to call me all sorts of horrible names without the risk that I might see it.<br>
<div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jun 22, 2014 at 3:20 PM, Ljubomir Ljubojevic <span dir="ltr"><<a href="mailto:centos@plnet.rs" target="_blank">centos@plnet.rs</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 06/22/2014 05:53 PM, Johnny Hughes wrote:<br>
> On 06/21/2014 01:31 PM, Ljubomir Ljubojevic wrote:<br>
>> On 06/21/2014 06:56 PM, Johnny Hughes wrote:<br>
>>>> Just to emphasize, people want COMPATIBILITY with RHEL, that is why we<br>
>>>> use it. If there will be no PERCEIVED compatibility, people will start<br>
>>>> waling away from CentOS. As simple as that.<br>
>>> And the CentOS goal is full functional compatibility.<br>
>>><br>
>>> We do now have and will continue to have that.<br>
>>><br>
>>> Changing a number in the name does not impact that at all ... it just<br>
>>> means we are trying to better describe what CentOS is.<br>
>>><br>
>> That IS the point over board and users are arguing about. Just like<br>
>> "Beauty is in the eye of the beholder", so is the "truth" what something<br>
>> is or isn't. All of users are trying to PRESERVE what was established.<br>
>> We do not think CentOS should be redefined just because of minority that<br>
>> uses apps that are meant for certain point-in-time.<br>
>><br>
>> So if you choose to keep with this PR nightmare, be ready to have<br>
>> diminishing membership, instead of increasing it. That is at least what<br>
>> vast majority of us, majority of community, on this list think. If you<br>
>> were to conduct referendum on this issue, I think 99% of CentOS users<br>
>> would vote against.<br>
>><br>
>> And then, to the all that follow this, it would look like selected few,<br>
>> now on the payroll of company that has vested interest in future of<br>
>> CentOS distro/project will go against will of vast majority of projects<br>
>> community, and play in the hand of that same company and it's profits.<br>
>><br>
>> While we are at it, why is Red Hat owner of "<a href="http://centos.org" target="_blank">centos.org</a>" domain name?<br>
>> And why is the Red Hat owner of CentOS trademark? "The CentOS Project is<br>
>> a community project. The CentOS Project leadership has transferred the<br>
>> CentOS trademark to Red Hat for protection and stewardship. The CentOS<br>
>> Governing Board will be responsible for policing use of the mark."<br>
>><br>
>> Who voted on it? Larger Community hasn't.<br>
>><br>
>> In fact, up to this point I thought CentOS is just joining forces with<br>
>> Red Hat. But text of the announcement says "The new initiative is going<br>
>> to be overseen by the new CentOS Governing Board." So this is actually<br>
>> NEW project that will claim CentOS name, but will not continue as<br>
>> CentOS, but in fat will be OpenRHEL. Only when I put together 2 and 2,<br>
>> Boards intention to remove OpenRHEL from CentOS that existed until<br>
>> January did I understood that my arbitrary story about what might happen<br>
>> is actually right.<br>
>><br>
>> Whois on <a href="http://centos.org" target="_blank">centos.org</a>:<br>
>><br>
>> Registrant Contact Information:<br>
>> Name: Red Hat, Inc.<br>
>> Organization: Red Hat, Inc.<br>
>> Address 1: 100 East Davie Street<br>
>> City: Raleigh<br>
>> State: NC<br>
>> Zip: 27601<br>
>> Country: US<br>
>> Phone: <a href="tel:%2B1.9197543700" value="+19197543700">+1.9197543700</a><br>
>> Fax: <a href="tel:%2B1.9197543704" value="+19197543704">+1.9197543704</a><br>
>> Email: Email Masking <a href="mailto:Image@redhat.com">Image@redhat.com</a><br>
>><br>
>> Administrative Contact Information:<br>
>> Name: Domain Admin<br>
>> Organization: Red Hat, Inc.<br>
>> Address 1: 1801 Varsity Drive<br>
>> City: Raleigh<br>
>> State: NC<br>
>> Zip: 27606<br>
>> Country: US<br>
>> Phone: <a href="tel:%2B1.9197543700" value="+19197543700">+1.9197543700</a><br>
>> Fax: <a href="tel:%2B1.9197543704" value="+19197543704">+1.9197543704</a><br>
>> Email: Email Masking <a href="mailto:Image@redhat.com">Image@redhat.com</a><br>
>><br>
>> Technical Contact Information:<br>
>> Name: Domain Admin<br>
>> Organization: Red Hat, Inc.<br>
>> Address 1: 100 East Davie Street<br>
>> City: Raleigh<br>
>> State: NC<br>
>> Zip: 27601<br>
>> Country: US<br>
>> Phone: <a href="tel:%2B1.9197543700" value="+19197543700">+1.9197543700</a><br>
>> Fax: <a href="tel:%2B1.9197543704" value="+19197543704">+1.9197543704</a><br>
>> Email: Email Masking <a href="mailto:Image@redhat.com">Image@redhat.com</a><br>
>><br>
>><br>
>> In light of this new revelation, if you go on with the change, count me<br>
>> out of any further contributing. I will continue to use it, but will<br>
>> welcome any attempt to restore old CentOS even under some other name.<br>
>><br>
>><br>
><br>
> What revelation ... Red Hat is now paying for the domain registration.<br>
> We (the Project) don't have any money, we never have. Stuff costs<br>
> money. We either get someone to sponsor our domain registrations,<br>
> servers we build on, servers we mirror on ... or we pay for it out of<br>
> our own pockets. That is the way it has been since the beginning. Not<br>
> only have I spent the time I mentioned before in this thread, I have<br>
> personally spent several thousand dollars of my own money over the last<br>
> 10 years to purchase hardware or go to conferences to promote CentOS,<br>
> etc. Karanbir has spent even more time and money than I have. All this<br>
> stuff you get for free has cost me dearly over the years in both time<br>
> and money. At one point it almost coast me my marriage.<br>
><br>
> We have opened up the entire process for the 7 distro to the community.<br>
> We have the git repo completely open for public consumption at<br>
> <a href="http://git.centos.org" target="_blank">git.centos.org</a>.<br>
><br>
> Every build log, built RPM, built SRPM (for those who would rather use<br>
> those) is available here:<br>
><br>
> <a href="http://buildlogs.centos.org/" target="_blank">http://buildlogs.centos.org/</a><br>
><br>
> You can look at the packages in our build root for every build, see the<br>
> result of every test that the RPM did while it built, etc. We have<br>
> never been more open or forthcoming.<br>
><br>
> Not only that, but every mock config used is published here for the build:<br>
><br>
> <a href="https://git.centos.org/summary/sig-core!bld-seven.git" target="_blank">https://git.centos.org/summary/sig-core!bld-seven.git</a><br>
><br>
> Every script we are using to do things with the git tree is here:<br>
><br>
> <a href="https://git.centos.org/summary/centos-git-common.git" target="_blank">https://git.centos.org/summary/centos-git-common.git</a><br>
><br>
> We could not possibly be more open ... you have never been able to see<br>
> so much about the distro before or how compatible it is or is not.<br>
><br>
> There is nothing to hide here, absolutely everything is out in the<br>
> open. No one else in the EL space is even close to this level of<br>
> openness. That doesn't even include the discussions on the lists.<br>
><br>
> Then we did all the QA completely open, the branding search was<br>
> completely open.<br>
><br>
> The process we use to build has not changed ... but now you can<br>
> absolutely see every part of it.<br>
><br>
> How we build docker images ... open, right here:<br>
><br>
> <a href="https://git.centos.org/summary/sig-cloud-instance!build-instance.git" target="_blank">https://git.centos.org/summary/sig-cloud-instance!build-instance.git</a><br>
><br>
> How do we do our comps.xml or live media, open and right here:<br>
><br>
> <a href="https://git.centos.org/project/sig-core" target="_blank">https://git.centos.org/project/sig-core</a><br>
><br>
> We are being completely open with everything and as such we think we<br>
> should also be completely open about things like binary compatibility<br>
> and the name. Giving something the exact same name implies certain<br>
> things, not all of which are true. Saying something is binary (or bit<br>
> for bit) compatible also implies certain things.<br>
><br>
> All we are trying to do here is be completely honest and complete open<br>
> about the distro as a whole and the process to get it as a whole. So<br>
> now everything is open, you can see everything about it all, and a<br>
> number after the decimal point in the name and/or the difference in the<br>
> word Binary and Functional is enough to make you mistrust something that<br>
> you have been using for free for ten years?<br>
><br>
><br>
<br>
<br>
</div></div>There are too many thing going on simultaneously. This text bellow I<br>
wrote on-the-go, developing the story as I wrote.<br>
<br>
1. I have a problem where I am not sure where I stand on who owns this<br>
project. Is it of the entire community, or just of the people on the<br>
board? I was definitely out of these talks, and since I was not<br>
consulted (just like other 99,9% of users) that means CentOS Project was<br>
not mine, I do not own even the tiny peace of it. Since several of you<br>
guys poured your hart and soul into this project it kinda is OK, but<br>
that fact robes me of my own "ownership", even 0.00000001% of it. I was<br>
just helping out you guys from Board/core devs.<br>
<br>
As I said, it is OK, you earned it, but that entails other things.<br>
<br>
Inner circle, the board, true owners of the project decided to abandon<br>
the project and start a new one, CentOS 2.0, totally not consulting<br>
anyone from the rest of Community. There was no vote, no one even warned<br>
us something like this is possible.<br>
<br>
All that happened is that you decided, worked on it for few? months and<br>
then announced that old cloning project is over, and that you will be<br>
using CentOS project trademark for a CentOS 2.0, while abandoning CentOS<br>
1.0.<br>
<br>
<br>
In CentOS 2.0 Red Hat has a lot of influence. They are your employers,<br>
they own the trademark (if they didn't they would just donated money for<br>
you to register domains under your CentOS), they are giving most of the<br>
hardware, there are moving THEIR source base directly to <a href="http://git.centos.org" target="_blank">git.centos.org</a>.<br>
<br>
Red Hat is going to work developing their basically for-profit projects<br>
via their subsidiary CentOS Project. Part of that process is that they<br>
want to create a greater mental distance between RHEL and CentOS, so<br>
people stop identifying those two as same thing, paid-for and unpaid-for<br>
versions. I know CentOS was kind of necessary evil, bringing them new<br>
customers and producing expert admins, enlarging user base, but at the<br>
same time you were cutting in their profit. When economy was good, it<br>
was fine balance. But in few last years Oracle and SL cut in,<br>
subscriptions started to drop and investors started to ask for more profits.<br>
<br>
Since trick with making 6.0 build complicated hurt both CentOS and<br>
turned out to be PR nightmare for friendly neighborhood Red Hat, they<br>
needed better approach. They need open source behind RHEL, but they need<br>
more mental distance so that using free-distro is available, but also<br>
further away from CentOS = free RHEL. So they gave you everything you<br>
needed/wanted, improving CentOS Project in the process, but there "few<br>
legal problems that need ironing out". I do not know how that idea was<br>
introduced, changing minor number to date of release, but I do know that<br>
effect is JUST what Red Hat needs for increased profits in the future.<br>
Not in new 1-2 years maybe, but when perception of CentOS != RHEL takes<br>
hold, more managers will choose to buy RHEL instead of keeping CentOS<br>
servers.<br>
<br>
We users of old CentOS 1.0 liked our independence from Red Hat, were<br>
more the Fedora, we were independent. At least until problems with 6.0<br>
were solved by secret help from Red Hat. Maybe this idea is<br>
preposterous, but at the time 6.0 building was problematic, at least few<br>
of users suspected Red Hat gave away some of the secrets to help stalled<br>
CentOS to reach "100% binary compatibility" goal. In hind perspective,<br>
this also looks like plausible scenario. It is all in mailing list<br>
archive of that period, questions how you guys managed to solve some of<br>
the problems, and you refused to give out secret sauce. No one was<br>
offended, we all were happy things picked up. But this troublesome build<br>
might indicated also problems with future builds, so that also might<br>
affected your decision to accept Red Hat's offer. Red Hat would get<br>
control over the build process, it would be recognized as leader, but<br>
would also solve them the their biggest process, having almost 100%<br>
clone for free.<br>
<br>
Now there is CentOS 2.0, brand new, drawing on old brand name, and you<br>
are waiting for storm to blow over to implement point-in-time date as<br>
planed. Since all of the board members of CentOS 2.0 are in agreement to<br>
proceed as planed, only thing that MIGHT avert you is loud revolt of the<br>
users. And since this was brought only on CentOS-devel mailing list,<br>
there will not be much more people revolting. We will just woke up in<br>
brand new world where another Company won over Community, the 99%.<br>
<br>
So I will try to prevent this voicing my concerns. I do not think I will<br>
achieve anything, but at least I will know I did my best.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
--<br>
Ljubomir Ljubojevic<br>
(Love is in the Air)<br>
PL Computers<br>
Serbia, Europe<br>
<br>
StarOS, Mikrotik and CentOS/RHEL/Linux consultant<br>
_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos-devel" target="_blank">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Chris St. Pierre
</div>