On Thu, Nov 8, 2018 at 11:47 AM Lowry, Roy K. <[email protected]> wrote:

> Dear All,
>
>
> 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. I
> then got a message describing Github as a tool for developers.
>
>
> I am not a developer. 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.
>
>
> Cheers, Roy.
>
>
> I have now retired but will continue to be active through an Emeritus
> Fellowship using this e-mail address.
>
>
> ------------------------------
> *From:* [email protected] <
> [email protected]> 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.
> ------------------------------
>

Reply via email to