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/[email protected]/
Updates to RIPE-500: Policy Development in RIPE
- Previous message (by thread): Updates to RIPE-500: Policy Development in RIPE
- Next message (by thread): Updates to RIPE-500: Policy Development in RIPE
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Thu May 8 19:32:28 CEST 2014
Hey Jim, > This text is unchanged from RIPE500 and nobody seemed to notice or care about that. Until now. Presumably that wording was OK when RIPE500 was developed and discussed at great length. Does it *really* need fixing? And fixing right now? This specific case is not a very complicated one, just a case of bad language mostly. I don't see why we should publish a document with a known language bug in it. May I suggest fixing it by replacing "Individual proposals may choose to vary these" with e.g. "These may be varied for individual proposals" (or whatever is proper English). No change in meaning, just a cosmetic change so we don't need a cosmetic surgery project later :) I wouldn't have a problem with a native English speaker fixing these little things when publishing the new version as a RIPE document. As long as it is just language fixes we shouldn't waste any time on them. Cheers, Sander
- Previous message (by thread): Updates to RIPE-500: Policy Development in RIPE
- Next message (by thread): Updates to RIPE-500: Policy Development in RIPE
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]