Hi Jonathan, all,
Jonathan Gregory wrote:
> The trac system is evidently being used for detailed discussion as well as
> proposals, and it has advantages for that. If that is done, however, it might
> be best to close the discussion ticket and open a new one when a definite
> proposal is made. That's just my opinion; we don't have any rules about this.
>
All the change proposals I've followed have required several versions
before being accepted. And editing the actual proposal text has been
painful. So, I would like to ask: Are we using the wrong tool for
writing and editing CF change proposals?
The trac tickets are great for tracking issues and discussions. However,
you can't edit existing text. Which makes modifying the text of a
proposal difficult. Closing a ticket and opening a new one when changes
need to be made could work but would cause discussions to be somewhat
disjointed. (Does trac support closing tickets due to a new ticket? Or
would those links have to be made by hand?)
Wikis on the other hand were made for distributed editing. The CF wiki
tracks changes to each document and allows viewing and linking to
specific versions.
So, rather than figure out a way to support editing/versioning in the
trac tickets, I would like to suggest that we consider using the trac
tickets for discussion of issues/proposals and use the wiki for the
actual change proposal text. This would greatly simplify the editing
process and would allow for the discussion to be held in a single ticket.
Ethan
--
Ethan R. Davis Telephone: (303) 497-8155
Software Engineer Fax: (303) 497-8690
UCAR Unidata Program Center E-mail: edavis at ucar.edu
P.O. Box 3000
Boulder, CO 80307-3000 http://www.unidata.ucar.edu/
---------------------------------------------------------------------------
Received on Fri Jun 27 2008 - 12:00:24 BST
