From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1EY4D6-000215-GC for garchives@archives.gentoo.org; Fri, 04 Nov 2005 16:14:36 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jA4GDlEM025836; Fri, 4 Nov 2005 16:13:47 GMT Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jA4GAmMa009777 for ; Fri, 4 Nov 2005 16:10:49 GMT Received: from [67.191.242.121] (c-67-191-242-121.hsd1.ga.comcast.net[67.191.242.121]) by comcast.net (rwcrmhc12) with ESMTP id <20051104161044014006bmo7e>; Fri, 4 Nov 2005 16:10:45 +0000 Message-ID: <436B877C.9080306@ieee.org> Date: Fri, 04 Nov 2005 11:08:28 -0500 From: "Nathan L. Adams" User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050722) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] GLEP ??: Critical News Reporting References: <20051101015125.1cc45eb4@snowdrop.home> <436AF548.8070406@ieee.org> <200511040032.25592.electronerd@monolith3d.com> <200511041033.06340.pauldv@gentoo.org> <436B34BD.7040509@gentoo.org> <436B6FC3.2000203@gentoo.org> In-Reply-To: <436B6FC3.2000203@gentoo.org> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: b90e3915-dd9d-42ca-9a11-59a6c2f78edb X-Archives-Hash: 321fac64ea16c99ade94f5e0f3ebbc57 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xavier Neys wrote: > Thierry Carrez wrote: > >> Paul de Vrieze wrote: >> >> >>> Oh god help. This also points to another reason why this is not such >>> a good idea. Writing guideXML is a lot more work than writing an >>> e-mail format file (ciaran's proposed format for those who didn't >>> recognize it). >>> >>> Also having double files containing the same information is broken by >>> design. >> >> >> >> OK so there is two options : >> >> 1- every "news" requires a GuideXML/RST/whatever errata at a central web >> location >> Pros: >> - non-portage user can easily browse errata >> - consistency in documentation >> Cons: >> - work overhead for errata-writing dev >> >> 2- every "news" requires just a short text-based item, extra doc is >> optional >> Pros: >> - flexibility: short news don't require writing extra doc >> - external doc reuse: the documentation referenced in the news item can >> be some upstream upgrade doc when sufficient >> Cons: >> - lack of consistency and difficulty for non-portage users to browse >> >> We can have the best of both worlds if we find a way to reduce the work >> overhead to 0 (using some kind of news2errataXml translator ?). If we >> can't, I tend to favor the second solution... > > > Both can be done. > Posting news items on our front page can be done today, publishing > upgrade notes can be done today, grouping all upgrade documents in an > upgrade category on the main doc index (docs.gentoo.org) can be done > today, having upgrade.gentoo.org point to it can be done one hour later. > All of the above does not require a single line of code. > > I suppose the news snippets could also be integrated in > packages.gentoo.org, hopefully without requiring too much work. > Great, then I hope that the scope of the GLEP gets expanded to include: - - central website (ugrade.g.o or errata.g.o or whatever) - - external docs follow existing doc policy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDa4d82QTTR4CNEQARApNQAJ9RzRxl1y/KRd/5xhVh0gQuwU4OEQCdFofK pC5D+BbzmgOcSDdW3IookUs= =J44D -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list