Ciaran McCreesh wrote: > News Item Source > ---------------- > > News items are to be made available via the Portage tree. This removes any > need for polling of a remote source. > > A new directory, ``news/``, will be created in the main tree. Commit access > to this directory will be handled in the same way as for the rest of the > tree. This directory will contain further subdirectories named > ``yyyy-mm/``, where ``yyyy`` is the current year and ``mm`` is the current > month number (01 for January through 12 for December) -- this extra level > of separation will help keep news items more manageable.
Could we possibly use a system thats a mix of how GLSA's and GLEP's are handled currently? The main point here being that we can move the actual cvs location outside of gentoo-x86 and put it in somewhere more appropriate for translators. The example here is, all the GLSA's are currently not in the gentoo-x86 module. The regeneration script on our master mirror syncs with the gentoo module location for GLSA's and copies those files in its current location in the tree. Perhaps we could do the same for the news item where they actually reside in the documentation module and the 'plain text' versions of the files get copied into the tree at regen time. Correct me if I'm wrong, but I think GLEPs are currently created as RST files then you use a converter script to make it in guidexml. Then you actually commit both the rst and xml file to cvs. Could we possibly do the same here to make it simple? Automation is great where it fits best. I'd rather not deal with conversion on the server end, I'd prefer the conversion be handled by the developer/translator as they can double check the conversion script better than the script itself can. Poke at that :-) Cheers- -- Lance Albertson <[EMAIL PROTECTED]> Gentoo Infrastructure | Operations Manager --- GPG Public Key: <http://www.ramereth.net/lance.asc> Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742 ramereth/irc.freenode.net
signature.asc
Description: OpenPGP digital signature