<div dir="ltr">Scott: navigate to the FAQ page I linked, and search for some of the text I included. You'll find it.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 8, 2014 at 1:58 PM, Scott McCarty <span dir="ltr"><<a href="mailto:scott.mccarty@gmail.com" target="_blank">scott.mccarty@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Where is this documented, I am still trying to find this stated clearly in the announcements?<br>
<div class="im HOEnZb"><br>
<br>
----- Original Message -----<br>
> From: "Joshua Kramer" <<a href="mailto:joskra42.list@gmail.com">joskra42.list@gmail.com</a>><br>
> To: "Central OH Linux User Group - 432xx" <<a href="mailto:colug-432@colug.net">colug-432@colug.net</a>><br>
</div><div class="HOEnZb"><div class="h5">> Sent: Wednesday, January 8, 2014 1:51:52 PM<br>
> Subject: Re: [colug-432] RedHat and CentOS buddy-up<br>
><br>
><br>
><br>
> Strange... the CentOS mailing list and RedHat's official statements<br>
> appear to differ.<br>
><br>
> <a href="http://community.redhat.com/centos-faq/" target="_blank">http://community.redhat.com/centos-faq/</a><br>
> Will this new relationship change the way CentOS obtains Red Hat<br>
> Enterprise Linux source code?<br>
> Yes. Going forward, the source code repository at <a href="http://git.centos.org" target="_blank">git.centos.org</a> will<br>
> replace and obsolete the Red Hat Enterprise Linux source rpms on<br>
> <a href="http://ftp.redhat.com" target="_blank">ftp.redhat.com</a> .<br>
><br>
><br>
><br>
><br>
> On Wed, Jan 8, 2014 at 1:03 PM, Scott McCarty <<br>
> <a href="mailto:scott.mccarty@gmail.com">scott.mccarty@gmail.com</a> > wrote:<br>
><br>
><br>
> inline comments...<br>
><br>
><br>
> ----- Original Message -----<br>
> > From: "Joshua Kramer" < <a href="mailto:joskra42.list@gmail.com">joskra42.list@gmail.com</a> ><br>
> > To: "Central OH Linux User Group - 432xx" < <a href="mailto:colug-432@colug.net">colug-432@colug.net</a> ><br>
> > Sent: Wednesday, January 8, 2014 12:25:45 PM<br>
> > Subject: [colug-432] RedHat and CentOS buddy-up<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > After reading this Wired article, I had to check my calendar to<br>
> > make<br>
> > sure it wasn't April 1st, or that I was mistakenly reading The<br>
> > Register.<br>
> ><br>
> > <a href="http://www.wired.com/wiredenterprise/2014/01/redhat-centos/" target="_blank">http://www.wired.com/wiredenterprise/2014/01/redhat-centos/</a><br>
> ><br>
> > Highlights:<br>
> ><br>
> > 1. Redhat is hiring CentOS developers to work on CentOS<br>
> > 2. The official source for source code used in RHEL will be<br>
> > <a href="http://git.centos.org" target="_blank">git.centos.org</a><br>
><br>
> This is the downstream code, not the upstream code.<br>
><br>
> from:<br>
> <a href="http://lists.centos.org/pipermail/centos-announce/2014-January/020100.html" target="_blank">http://lists.centos.org/pipermail/centos-announce/2014-January/020100.html</a><br>
><br>
> =============================================<br>
> - - Sources that we consume, in the platform, in the addons, or the<br>
> parallel stacks such as Xen4CentOS will become easier to consume with<br>
> a <a href="http://git.centos.org" target="_blank">git.centos.org</a> being setup, with the scripts and rpm metadata<br>
> needed<br>
> to create binaries being published there. The Board also aims to put<br>
> together a plan to allow groups to come together within the CentOS<br>
> ecosystem as a Special Interest Group (SIG) and build CentOS Variants<br>
> on our resources, as officially endorsed. You can read about the<br>
> proposal at <a href="http://www.centos.org/variants/" target="_blank">http://www.centos.org/variants/</a><br>
> =============================================<br>
><br>
><br>
><br>
> > 3. They are handing the CentOS trademark over to Redhat for<br>
> > protection and stewardship.<br>
><br>
> Agreed<br>
><br>
><br>
> ><br>
> > I see good things ahead for CentOS!<br>
> ><br>
> > _______________________________________________<br>
> > colug-432 mailing list<br>
> > <a href="mailto:colug-432@colug.net">colug-432@colug.net</a><br>
> > <a href="http://lists.colug.net/mailman/listinfo/colug-432" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
> ><br>
> _______________________________________________<br>
> colug-432 mailing list<br>
> <a href="mailto:colug-432@colug.net">colug-432@colug.net</a><br>
> <a href="http://lists.colug.net/mailman/listinfo/colug-432" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
><br>
><br>
> _______________________________________________<br>
> colug-432 mailing list<br>
> <a href="mailto:colug-432@colug.net">colug-432@colug.net</a><br>
> <a href="http://lists.colug.net/mailman/listinfo/colug-432" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
><br>
_______________________________________________<br>
colug-432 mailing list<br>
<a href="mailto:colug-432@colug.net">colug-432@colug.net</a><br>
<a href="http://lists.colug.net/mailman/listinfo/colug-432" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
</div></div></blockquote></div><br></div>