Opened 12 years ago

Closed 12 years ago

#13 closed enhancement (fixed)

Procedure for correcting errors in the CF documents

Reported by: jonathan Owned by: cf-conventions@…
Priority: medium Milestone:
Component: cf-conventions Version:
Keywords: Cc:

Description

Rich Signell has pointed out an error in the CF standard document by raising a trac ticket. I think we need rules for deciding to make corrections, or there's a danger they might not be implemented. I propose the following:

  1. These rules apply to the CF conventions document, the conformance document, the standard name table and its guidelines.
  1. Errors in these documents can be corrected under these rules if it is clear that the text as it stands isn't what was agreed, because of a typographical or some other error. These rules can't be followed for making substantive changes. Errors in the standard names can alternatively be pointed out on the CF email list, and implemented by the manager of CF standard names (Alison) as part of a regular update.
  1. If someone thinks there is an error in a document, they should open a Trac ticket of type "defect" to point it out and to state what should be done to the text in order to correct the error.
  1. The correction is held to have been agreed if three weeks pass without anyone disagreeing with it. After that period, the ticket should be closed by the manager of the CF conventions (Kyle) or the manager of CF standard names (Alison), who will make the change. No moderator is needed because there cannot be any substantive discussion under these rules.
  1. If anyone disagrees that the correction should be made, because they think the document does have the intended meaning, then a correction cannot be made by these rules, the ticket should be closed, and the change should be proposed as an enhancement instead, following the rules for making changes to the CF standard, if the proposer wants to pursue the issue.

It feels a bit bureaucratic to have rules, but I think it may be necessary because experience shows that without rules we find it hard to reach conclusions. Please post your comments to this ticket.

Jonathan

Change History (2)

comment:1 Changed 12 years ago by caron

I agree, having a rule like this clarifies how to correct minor errors. thanks, jonathan.

John Caron

comment:2 Changed 12 years ago by jonathan

  • Resolution set to fixed
  • Status changed from new to closed
  • Type changed from task to enhancement

As there have been no comments on this ticket for three weeks and there is no disagreement, I think we can safely say that this procedure for correcting flaws in the CF documents is now agreed.

Note: See TracTickets for help on using tickets.