This message came from the CF Trac system. Do not reply. Instead, enter your comments in the CF Trac system at http://kitt.llnl.gov/trac/.
John, Thanks for taking the initiative on getting this rolling. Matt Harris (cc'd here, and @mattbenn on github) is the owner and should be able to create a CF-2.0 repository as well as appropriate teams for the repo -- perhaps one small team with commit writes, and another larger team of contributors that can write to the wiki? He would just need a list of github usernames (e.g. mine is @rsignell-usgs). So maybe if folks agree we can then either e-mail Matt and ask to be included to the contributor list or raise an issue on the new repo Matt creates. ... Thanks, Rich On Mon, Oct 6, 2014 at 7:19 PM, John Caron <ca...@ucar.edu> wrote: > Thanks to John and Chris for summarizing. I think we are almost ready to go. > Heres my summary: > > > Charter/Scope > > (1) What use-cases cannot be met with the classic model, or could be met > much more easily with the extended model? > > (2) Possible things to deprecate (because there is a better way to do it) > > (3) Backwards compatibility is desirable, but not required if there is a > substantial advantage in simplicity and clarity. So respect precedent and > dont constrain important innovation. There has to be a strong advantage for > making incompatible changes. > > (4) If we introduce a new way to do something, we should carefully consider > removing the old way, because it is easier for users of the convention if > there is only one way to do something. > > > Process: > > We will try out using github for the discussion and the "discussion summary" > document. > > 1) We will use the CF github account if possible. > > 2) We will create a new repo under https://github.com/cf-convention, say, > https://github.com/cf-convention/CF-2. > > 3) We will use the "Issues" feature to discuss. Essentially this allows > threaded discussion, and new issues are created as needed to keep things > on-topic. > > 4) We will use the wiki to create a "discussion summary" document. It looks > adequate in that we can create various pages and link them together. It will > be a collaborative document where anyone can write (add your name to your > edits perhaps?) At some point we will probably transition to a collection of > documents in the repo. > > Anyway, we can get started and refine this set of guidelines as we go. > > Questions: > > - Who has admin rights to the CF github account? > - How do people get permission to write? > - Any other ground rules needed? > - Any changes to the above? > > -- Dr. Richard P. Signell (508) 457-2229 USGS, 384 Woods Hole Rd. Woods Hole, MA 02543-1598 This message came from the CF Trac system. To unsubscribe, without unsubscribing to the regular cf-metadata list, send a message to "majord...@lists.llnl.gov" with "unsubscribe cf-metadata" in the body of your message.