From owner-cvs-doc@FreeBSD.ORG Tue Jun 24 01:13:37 2008 Return-Path: Delivered-To: cvs-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 213A3106564A for ; Tue, 24 Jun 2008 01:13:37 +0000 (UTC) (envelope-from murray@stokely.org) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id A227F8FC26 for ; Tue, 24 Jun 2008 01:13:36 +0000 (UTC) (envelope-from murray@stokely.org) Received: by ug-out-1314.google.com with SMTP id q2so541239uge.37 for ; Mon, 23 Jun 2008 18:13:35 -0700 (PDT) Received: by 10.66.249.20 with SMTP id w20mr2785201ugh.22.1214270014971; Mon, 23 Jun 2008 18:13:34 -0700 (PDT) Received: by 10.67.101.19 with HTTP; Mon, 23 Jun 2008 18:13:34 -0700 (PDT) Message-ID: <2a7894eb0806231813l47b76243h599d3421ca97fc2d@mail.gmail.com> Date: Mon, 23 Jun 2008 18:13:34 -0700 From: "Murray Stokely" To: "Simon L. Nielsen" In-Reply-To: <20080621203158.GE1079@zaphod.nitro.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200806202003.m5KK3TkH072678@repoman.freebsd.org> <2a7894eb0806201416v2b1df3a5k8e07268df5883ecf@mail.gmail.com> <485C2C91.5000508@freebsd.org> <87ve03647m.fsf@kobe.laptop> <20080621203158.GE1079@zaphod.nitro.dk> Cc: cvs-doc@freebsd.org, cvs-all@freebsd.org, Daniel Gerzo , Colin Percival , Giorgos Keramidas , doc-committers@freebsd.org Subject: Re: cvs commit: www/en index.xsl www/en/security Makefile errata-rss.xsl errata.rss www/share/sgml libcommon.xsl X-BeenThere: cvs-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the doc and www trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 01:13:37 -0000 Yea I think having just a subset of the content and a link to the full advisories would be the way to go. The titles alone aren't that useful, and I could see the entire advisories as kind of wasteful. I wonder if security team would be amenable to releasing security advisories in a very simple XML schema which is then output as plain text, RSS feeds, or pretty html? - Murray On Sat, Jun 21, 2008 at 1:31 PM, Simon L. Nielsen wrote: > On 2008.06.21 03:07:09 +0300, Giorgos Keramidas wrote: >> On Fri, 20 Jun 2008 15:17:53 -0700, Colin Percival wrote: >> >Murray Stokely wrote: >> >> Thanks for adding this. It would be even more useful if this and the >> >> security advisory RSS feed included the text of those advisories >> >> rather than just the title. Right now they are stored as text files >> >> on another host, but it would be great if we could work with security >> >> team to store these in a format more amenable to syndication by our >> >> RSS feeds. CCing Colin in case he has any thoughts on this, and >> >> assuming he doesn't read www commit messages. =) >> > >> > What would we get by putting the complete advisory text into the RSS >> > feeds except a waste of bandwidth? I can understand adding some more >> > information (say, the Topic), but throwing in everything seems a bit >> > extreme. >> >> It's about as extreme as adding the full text of blog posts in RSS feeds >> all over the world. Some people may find it useful, others may find it >> a waste of bandwidth. >> >> How about adding *two* RSS feeds: a 'short' one, with the titles and a >> link to the real advisory, and a 'long' one with the full text? > > Note that including this is not as easy as it may sound. You need to > somehow automatically get the advisory text and include the > appropriate parts. Copy/paste of anything but the title is not an > option. The advisories are not available to the doc build on > www.FreeBSD.org... this may change at some point but there are no > current plans to do so. > > Some years ago I made a parser to convert advisories into XML so you > can extract parts (different sections etc) as needed. It works but > it's not pretty... > > -- > Simon L. Nielsen >