This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ncc-services-wg@ripe.net/
[ncc-services-wg] Update regarding the proposals to improve the technical infrastructure supporting the RIPE Policy Development Process
- Previous message (by thread): [ncc-services-wg] Update regarding the proposals to improve the technical infrastructure supporting the RIPE Policy Development Process
- Next message (by thread): [ncc-services-wg] Update regarding the proposals to improve the technical infrastructure supporting the RIPE Policy Development Process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Wed Sep 25 20:53:59 CEST 2013
Hi, On Wed, Sep 25, 2013 at 06:12:08PM +0200, Mihnea-Costin Grigore wrote: > Problem Statement > -------------------- > The RIPE PDP process is too complicated for everyone: outsiders, new > members, experienced members, authors, and the RIPE NCC. Therefore, > participation should be made easier, especially for new-comers. > > Main scope: > - The initial focus and effort are on the RIPE PDP -- proposals, drafts > and policy documents; if any progress is made here, then we can think of > applying the same or similar solutions to other areas of RIPE documentation > - Any solutions discussed should also work for non-techies > > Details of the problem: > > a) The meta-data provided is incomplete: > - RIPE Policy Documents and Policy Proposals don't have unique and > clearly identified global names/identifiers > - There is no clear version and date for publication > - There is no track of who and when requested and approved a certain change > - There is no clear up to date succession and obsolescence information > within documents > - There is no canonical way to get an overview of all currently active > documents > > b) There is no systematic access to all versions of a document: > - There is no directly available history > - There are no easy to use tools to correlate between versions > - There are no tools for authors to submit new/corrected versions of a > document as it evolves through the PDP > > c) There is no plain-text version of each document and version thereof > in ASCII format > > [------------8<------------] I find this a fairly impressive piece of work - it follows the rule "a document is perfect if there is no longer something to take away", which is much harder than writing a 50 page document. And I agree with the problem statement :-) Gert -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 306 bytes Desc: not available URL: </ripe/mail/archives/ncc-services-wg/attachments/20130925/b3f03c87/attachment.sig>
- Previous message (by thread): [ncc-services-wg] Update regarding the proposals to improve the technical infrastructure supporting the RIPE Policy Development Process
- Next message (by thread): [ncc-services-wg] Update regarding the proposals to improve the technical infrastructure supporting the RIPE Policy Development Process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]