On 01/06/2015 04:25 AM, Liam O'Toole wrote:> On 2015-01-06, Somers-Harris, David | David | OPS > <david.somers-harris at mail.rakuten.com> wrote: >>> 1. Blatant screen scraping is a violation of the terms of service >>> for RHN .. so where is a SOURCE of information for something like >>> this: >>> >>> https://rhn.redhat.com/errata/RHSA-2014-2024.html >>> >>> If you read this: https://access.redhat.com/help/terms/ >>> >>> then, one can not just grab all the info on that errata page and >>> distribute it .. which is why we LINK to it and not distribute it >>> currently. >>> >>> So, the first issue is that one must find a source for the >>> information that would go into the 'updateinfo.xml' file that is >>> always maintained and is available to read and to redistribute. >>> >>> 2. If someone comes up with a place to get said data, THEN we could >>> properly publish that data in some way. >>> >>> Thanks, Johnny Hughes >> >> Can't we just ask Red Hat if it's OK for CentOS to use the data for >> its updateinfo.xml? Is there some official communication channel >> between the CentOS Project and Red Hat? > > Maybe you missed the big announcement: > > http://lists.centos.org/pipermail/centos-announce/2014-January/020100.html >Sure, but they aren't likely to let us. The purpose of CentOS within the Red Hat ecosystem is explained here: http://community.redhat.com/centos-faq/ CentOS is open source, so you can use it however you want and for what ever you are comfortable using it for .. however, giving special dispensation to violate terms of service of RHN to make CentOS more usable than it already is in the enterprise is not high on their priority list. They are not taking any action to make it in any way less usable, but they are also not going to do anything to make it easier either. What we need is a way to get that info from another place. Maybe the oval data, if it has all the required information and if the Terms of Service allow for that. Someone in the Community needs to research that and see if it is usable or if there is some other source for the information that can then be modified to create the updateinfo.xml file. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20150106/d4b6b55d/attachment-0001.sig>
On 2015-01-06, Johnny Hughes <johnny at centos.org> wrote:> This is an OpenPGP/MIME signed message (RFC 4880 and 3156) > --===============4697670779706124595== Content-Type: multipart/signed; > micalg=pgp-sha1; protocol="application/pgp-signature"; > boundary="MBFscW2dH0g022mxj8O937qiaWFFIRB5O" > > This is an OpenPGP/MIME signed message (RFC 4880 and 3156) > --MBFscW2dH0g022mxj8O937qiaWFFIRB5O Content-Type: text/plain; > charset=windows-1252 Content-Transfer-Encoding: quoted-printable > > On 01/06/2015 04:25 AM, Liam O'Toole wrote: >> On 2015-01-06, Somers-Harris, David | David | OPS >> <david.somers-harris at mail.rakuten.com> wrote: >>>> 1. Blatant screen scraping is a violation of the terms of service >>>> for RHN .. so where is a SOURCE of information for something like >>>> this: >>>> >>>> https://rhn.redhat.com/errata/RHSA-2014-2024.html >>>> >>>> If you read this: https://access.redhat.com/help/terms/ >>>> >>>> then, one can not just grab all the info on that errata page and >>>> distribute it .. which is why we LINK to it and not distribute it >>>> currently. >>>> >>>> So, the first issue is that one must find a source for the >>>> information that would go into the 'updateinfo.xml' file that is >>>> always maintained and is available to read and to redistribute. >>>> >>>> 2. If someone comes up with a place to get said data, THEN we >>>> could properly publish that data in some way. >>>> >>>> Thanks, Johnny Hughes >>> >>> Can't we just ask Red Hat if it's OK for CentOS to use the data for >>> its updateinfo.xml? Is there some official communication channel >>> between the CentOS Project and Red Hat? >>=20 Maybe you missed the big announcement: =20 >>http://lists.centos.org/pipermail/centos-announce/2014-January/020100.h> tml >>=20 > > Sure, but they aren't likely to let us. > > The purpose of CentOS within the Red Hat ecosystem is explained here: > > http://community.redhat.com/centos-faq/ > > CentOS is open source, so you can use it however you want and for what > ever you are comfortable using it for .. however, giving special > dispensation to violate terms of service of RHN to make CentOS more > usable than it already is in the enterprise is not high on their > priority list. > > They are not taking any action to make it in any way less usable, but > they are also not going to do anything to make it easier either. > > What we need is a way to get that info from another place. > > Maybe the oval data, if it has all the required information and if the > Terms of Service allow for that. > > Someone in the Community needs to research that and see if it is > usable or if there is some other source for the information that can > then be modified to create the updateinfo.xml file. >Thanks for all that. My contribution was in response to the question "Is there some official communication channel between the CentOS Project and Red Hat?" I should have trimmed more carefully and saved you some keystrokes. -- Liam
On 01/06/2015 12:03 PM, Liam O'Toole wrote:> Thanks for all that. My contribution was in response to the question "Is > there some official communication channel between the CentOS Project and > Red Hat?" I should have trimmed more carefully and saved you some > keystrokes.Nope. We're still air-gapped from the RHEL business units. We have lines of communication to other RH community projects, but nothing that would line up with this thread. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77