Mark & CF community, I agree that it would be great to allow a larger group of folks with time and interest to help out and get CF-1.7 out of the gates.
I wonder if we might also take this opportunity to consider more radical options to increase participation, like setting up a CF-Conventions organization on Github and moving the conventions there. The git model and the tools that github provides would make it much easier for other folks to contribute changes and for those changes to be reviewed, discussed and merged. Recently we moved the UGRID conventions from a Confluence wiki <http://publicwiki.deltares.nl/display/NETCDF/Deltares+CF+proposal+for+Unstructured+Grid+data+model> to github <https://github.com/ugrid-conventions/ugrid-conventions/blob/master/README.md> and I was surprised at how easy it was. I haven't moved trac tickets to github but it looks like many other projects have and there are tools to do it (e.g. http://stackoverflow.com/questions/6671584/how-to-export-trac-to-github-issues) What do folks think about this? Thanks -Rich On Fri, Sep 27, 2013 at 12:11 PM, Hedley, Mark <[email protected]> wrote: > I think the need for CF 1.7 is clear. There are a lot of agreed tickets to > process. > > I am particularly concerned by the comment: > "Making a new version of CF depends on Jeff Painter or a colleague at PCMDI > having time to do it, I presume." > > I am worried that this factor is a barrier to publishing the updated > conventions document. > > The source for the conventions document is under source control and published > here: > https://cf-pcmdi.llnl.gov/trac/browser/cf-conventions > https://cf-pcmdi.llnl.gov/trac/browser/cf-conventions/trunk > > I would think that a number of community members would be happy to take a > ticket and a branch and input the required changes. This can then be > reviewed and approved as part of closing the ticket. > > All that would be required to make a start on this would be for people to > volunteer and be given access to the source control system with the ability > to make branches. Access should be easy as I guess all interested parties > already have a Trac account. A smaller group with merge rights to the trunk > would be needed to review and merge changes. > > I am happy to put myself forward to do a bit of this work; if a number of us > muck in, I think we should be able to get 1.7 up to scratch in a fairly short > amount of time. > > Are there others in the community who could offer a little of their time to > contribute to such an effort? > > mark > > ________________________________________ > From: CF-metadata [[email protected]] on behalf of Jonathan > Gregory [[email protected]] > Sent: 13 September 2013 10:35 > To: [email protected] > Subject: [CF-metadata] Can we please close ticket 93 and modify the latest CF > document accordingly? > > Dear Rich > > There are a lot of tickets which have been agreed and should therefore be in > the next version of the CF standard. They are all the ones shown in green in > http://www.met.reading.ac.uk/~david/cf_trac_summary.html, including ticket 93. > > Making a new version of CF depends on Jeff Painter or a colleague at PCMDI > having time to do it, I presume. I agree we need a new one, because there are > a lot of concluded tickets, and it's two years since CF 1.6 was published. We > do not close the tickets until the new version of CF is published which > includes them, because the process isn't finished until then. In CF 1.7, the > history will be updated to list all the tickets which were enacted in it. > > However, even without a new version of CF, it can be assumed that ticket 93 > (and all the other concluded ones) will be part of CF 1.7. Software developers > can act on that assumption. > > Cheers > > Jonathan > > ----- Forwarded message from "Signell, Richard" <[email protected]> ----- > >> Date: Thu, 12 Sep 2013 13:59:39 -0400 >> From: "Signell, Richard" <[email protected]> >> To: CF metadata <[email protected]> >> Subject: [CF-metadata] Can we please close ticket 93 and modify the latest CF >> document accordingly? >> >> CF Folks, >> >> The Iris project would like to add support for the >> "ocean_s_coordinate_g1" and "ocean_s_coordinate_g2" coordinate that >> was described in this enhancement ticket for CF 1.7: >> >> https://cf-pcmdi.llnl.gov/trac/ticket/93 >> >> The last comment in this ticket is 11 months ago by Jonathan Gregory >> saying that these enhancements should be added to the next release of >> CF. Can these please be added to the CF 1.7 draft document and the >> ticket closed? >> >> (I see the "latest CF document" is 2011-12-05 16:44 , so that's >> perhaps why this change didn't get added? >> >> Thanks, >> Rich >> >> -- >> Dr. Richard P. Signell (508) 457-2229 >> USGS, 384 Woods Hole Rd. >> Woods Hole, MA 02543-1598 >> _______________________________________________ >> CF-metadata mailing list >> [email protected] >> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata > > ----- End forwarded message ----- > _______________________________________________ > CF-metadata mailing list > [email protected] > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata > _______________________________________________ > CF-metadata mailing list > [email protected] > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata -- Dr. Richard P. Signell (508) 457-2229 USGS, 384 Woods Hole Rd. Woods Hole, MA 02543-1598 _______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
