Dear Dave Thanks for your contributions. I could be moderator of this, and thank you for asking, but if David Hassell has time to do so that might be better since I'm rather short of time at present. Would you, David?
I agree with you that a googledoc is a good medium for editing large amounts of text (in the mode where edits are suggestions). Maybe some comments could be added about this possibility. There is a need to keep intermediate versions, I would say, as the issue proceeds to discuss them. If there is only one evolving doc it's not so easy to compare successive or alternative versions. We should preserve the distinction between enhancements and defects that we currently have with the trac tickets. Perhaps pure typos could be identified as a separate category from these. CF doesn't currently have a code of conduct but I agree it's a good idea to adopt one. That's a governance issue, I think. I wonder what Karl feels. Best wishes Jonathan On Mon, May 21, 2018 at 12:35:43PM -0700, David Blodgett wrote: > Date: Mon, 21 May 2018 12:35:43 -0700 > From: David Blodgett <[email protected]> > To: cf-convention/cf-conventions <[email protected]> > Cc: JonathanGregory <[email protected]>, Mention > <[email protected]> > Subject: Re: [cf-convention/cf-conventions] GitHub Contribution Guidelines > (#130) > > Dear CF community, > > I've started work on #130. It can be seen in pull request form between > branches in my fork > [here](https://github.com/dblodgett-usgs/cf-conventions/pull/10/files) or in > rendered markdown form > [here](https://github.com/dblodgett-usgs/cf-conventions/blob/CONTRIBUTING/.github/CONTRIBUTING.md) > > > @ChrisBarker-NOAA -- I did not get all your ideas implemented. If you want to > leave comments with proposed additional details or ideas for an additional > section, I'm happy to copy/paste/rewrite, I just didn't really know how to > fit your thoughts into the doc at the first pass. > > Others, please don't hesitate to leave in-line comments on the pull request > version, but please do also summarize your comments in line in this issue so > they make it to the email list. > > Note that I also added the [Contributors > Covenant](https://github.com/dblodgett-usgs/cf-conventions/blob/CONTRIBUTING/CODE_OF_CONDUCT.md) > as a placeholder for a code of conduct. Is there a pre-existing CF code of > conduct written down some where? > > @JonathanGregory -- do you want to act as moderator of this discussion? I > think it would be in our interest to move it to near conclusion prior to the > meeting in June. > > Best regards, > > Dave > > p.s. apologies for the push of a couple commits to #115 that came over the > email list a moment ago -- Those commits were promptly reverted and moved to > another branch. > > -- > You are receiving this because you were mentioned. > Reply to this email directly or view it on GitHub: > https://github.com/cf-convention/cf-conventions/issues/130#issuecomment-390758888 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/130#issuecomment-392906937
