Dear Jonathan, On 05/04/2019 14:16, Jonathan Gregory wrote: > Dear Mike and Klaus > > Thanks for your emails. I understand your points, but it seems to me that what > we have proposed will not make life significantly more difficult. > Specifically, > > (1) We propose to have one discuss repository taking over all the functions > of the current email list, which is for everything except proposals to amend > the convention. Those are made in a different repository, which is taking over > from trac. So this is no change of organisation, just of platform. Up to now > we have not needed to split general queries from standard name proposals. We > could do that if there is a need, but since there hasn't been a need up to now > it is simplest to migrate to a new platform with no change of organisation. > Anyone with a query can start a GitHub issue to ask their question, and we > will > make it clear that this is an expected use. +1. I think it's really important to make it clear that this is the expected use case.
> > (2) We presently have two email lists, which is complicated, and neither of > them is a satisfactory arrangement for the future. The one I'm writing on now > (the UCAR email list) is taking significant effort to maintain (from Brian > Eaton - our thanks to him), so we need to move it, at least. The other one > (at LLNL) is OK for distributing GitHub postings but its archives cannot be > made public, so it would not be appropriate as a replacement for the UCAR > email list. Thus, if we want to retain an email list, we will need to start a > new one. It seems simpler not to do that, but to move to GitHub instead, since > the functionality is available. > > This may not be your first choice, but is it satisfactory? Fine, let's give it a go :+1: > > Is there anyone who is interested in CF but would not be willing or able to > use GitHub in future to raise questions that at present they would ask on this > email list? > > Best wishes > > Jonathan > > ----- Forwarded message from Klaus Zimmermann <klaus.zimmerm...@smhi.se> ----- > >> Date: Fri, 5 Apr 2019 13:31:50 +0200 >> From: Klaus Zimmermann <klaus.zimmerm...@smhi.se> >> To: cf-metadata@cgd.ucar.edu >> Subject: Re: [CF-metadata] proposed migration of these discussions to GitHub >> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 >> Thunderbird/60.6.1 >> >> Dear Jonathan, >> >> for what it's worth, I am with Chris on this one. >> >> Imho a mailing list is the right format to shoot a question when you >> don't yet know exactly the approach (is it a feature request? a bug? >> just a clarification?) and who exactly you should ask. This way you >> reach all interested parties by the standard means of communication. >> >> An issue on github is great to preserve history and progress of, well, >> issues, such as bug reports and feature requests, typically with a >> rather small subset of interested people. > > ----- Forwarded message from Mike Grant <michael.gr...@eumetsat.int> ----- > >> Date: Fri, 5 Apr 2019 11:43:35 +0000 >> From: Mike Grant <michael.gr...@eumetsat.int> >> To: "cf-metadata@cgd.ucar.edu" <cf-metadata@cgd.ucar.edu> >> Subject: Re: [CF-metadata] proposed migration of these discussions to GitHub >> >> [I'm personally happy with Github, but count as an interested person / long >> time lurker!] >> >> A lot of open source projects resolve this problem by splitting the >> conversation into two mailing lists. One is typically "-devel" for >> developers (in this case, anyone working on the standard or proposing >> changes) and one "-users" for people seeking help or wanting to report an >> issue, but not wanting to get involved in the details. Typically some/many >> of the dev people sit on both lists and redirect misplaced conversations to >> the correct list. >> >> Perhaps a possible compromise here would be to move all the -devel >> conversation onto Github in an organised fashion as proposed and create a >> -users mailing list explicitly just for queries? >> >> Cheers, >> >> Mike. >> >> -----Original Message----- >>>> From: Chris Barker - NOAA Federal <chris.bar...@noaa.gov> >>>> This list is also used to ask questions about how to best use the CF >>>> conventions, not just changes to CF. >>>> And a list IS a good way to facilitate those conversations. >>>> >>>> I also think it might bd good to have a list that recurved >>>> notifications of new discussion — though not every post! >>>> >>>> Still a listserve fan, >>>> >>>> -Chris >>>> >>>> >>>>>> which is an administrative >>>>>> complexity, especially as we currently have two different lists >>>>>> (for trac and email), which have to be kept consistent manually. >>>>>> Anyone can join GitHub for themselves and watch the CF repositories. >>>>>> >>>>>> Best wishes and thanks for your interest in CF >>>>>> >>>>>> Jonathan >>>>>> >>>>>> >>>>>> To get a username on GitHub, go to https://github.com/ and sign up. >>>>>> This is free! Once you have a username, you can sign in. >>>>>> >>>>>> The issues on the CF conventions repository are at >>>>>> https://github.com/cf-convention/cf-conventions/issues >>>>>> This shows the list of changes to 1.7 which are being discussed. >> >> Any email message from EUMETSAT is sent in good faith but shall neither be >> binding nor construed as constituting a commitment by EUMETSAT, except where >> provided for in a written agreement or contract or if explicitly stated in >> the email. Please note that any views or opinions presented in this email >> are solely those of the sender and do not necessarily represent those of >> EUMETSAT. This message and any attachments are intended for the sole use of >> the addressee(s) and may contain confidential and privileged information. >> Any unauthorised use, disclosure, dissemination or distribution (in whole or >> in part) of its contents is not permitted. If you received this message in >> error, please notify the sender and delete it from your system. >> _______________________________________________ >> CF-metadata mailing list >> CF-metadata@cgd.ucar.edu >> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata > > ----- End forwarded message ----- > _______________________________________________ > CF-metadata mailing list > CF-metadata@cgd.ucar.edu > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata > _______________________________________________ CF-metadata mailing list CF-metadata@cgd.ucar.edu http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
