> I echo Jonathan's sentiments here. I have a GitHub account and followed > Dave's URL and was confronted by the attached screen shot. After scratching > my head for 10 minutes about what to do next I gave up and logged out. >
If you had started with a direct link to an issue, it would have been a lot more clear :-) And TRAC was also a tool for developers, and had an even harder to figure out interface .... Which I think is actually the source of the "problem" here -- due to account access or usability, we're simply getting more action on gitHub -- which means we'll have to handle the Issue/mailing list bridge differently. I am not a developer. But you ARE a technologist, and you ARE helping "develop" CF :-) I suppose gitHubs docs are confusing, but it is, in fact, a good platform for what we are doing. Not ideal, of course, but the best one out there at this point. And once someone told you to click on the "Issues" tab, I think you'd be off and running... That being said, I am a fan of mailing lists -- I like how they integrate with my daily workflow. I would not participate in CF, or hardly any other project nearly as much if I had to go to a separate forum, website, whatever, gitHub or any other. Which is why the gitHub/email bridge is so effective. But it is not a good idea to have an email list as a gitHub user watching issues -- There must be a technical solution to that. I would suggest that the goal should be: - The mailing list gets a message each time a new Issue or PR is created. - The mailing list is never watching any Issue or PR I would regard my role in CF primarily as an oceanographic domain expert > providing input to oceanographic Standard Names. I believe that there are > other domain experts who find Github an alien environment. Whilst many > aspects of CF fall into the 'techie domain' I feel Standard Name > discussions need to engage as many domain scientists as possible, which is > helped by making barriers to participation as low as possible. I think there are Three (at least) broad topics covered on this list: 1) Use of CF -- how do I save my data correctly? how do I interpret this data? etc. 2) Extension of CF: what new features/etc should CF have? what should they look like? etc. 3) Standard Names: new names, better definitions of existing names. We need not handle all these discussion the same way. A lot of software projects have a "something" list, and a "something-dev" list. And we could manage standard names differently as well. I'm not sure that's necessary here if we can "fix" the gitHub-mailing list connection, but maybe it is worth it. And I do think that standard name discussion should probably stay on this list. -CHB > > Cheers, Roy. > > > I have now retired but will continue to be active through an Emeritus > Fellowship using this e-mail address. > > > ------------------------------ > *From:* [email protected] <owner-cf-metadata@listserv. > llnl.gov> on behalf of Jonathan Gregory <[email protected]> > *Sent:* 08 November 2018 18:30 > *To:* David Hoese > *Cc:* Chris Barker - NOAA Federal; Little, Chris; Martin Juckes - UKRI > STFC; Jim Biard; Erik Quaeghebeur; [email protected] > *Subject:* Re: Please stop sending Github messages to the ML > > Dear Dave > > > As for the limiting yourselves, sounds like you are > > slowing down progress so people don't get too many emails? Sounds > > fishy. > > No, I think it means considering more of other people's remarks for longer > before expressing a new opinion of your own. > > Best wishes > > Jonathan > ------------------------------ > This message (and any attachments) is for the recipient only. NERC is > subject to the Freedom of Information Act 2000 and the contents of this > email and any reply you make may be disclosed by NERC unless it is exempt > from release under the Act. Any material supplied to NERC may be stored in > an electronic records management system. > ------------------------------ > -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [email protected]
