[CF-metadata] Discussion of technical CF issues as GitHub issues?

Chris Barker chris.barker at noaa.gov
Mon Feb 27 18:17:39 MST 2017


On Mon, Feb 27, 2017 at 10:08 AM, Jonathan Gregory <
j.m.gregory at reading.ac.uk> wrote:

> With some technical effort, the trac system was set up so that all ticket
> updates are sent to everyone on the CF email list. I believe this is an
> important requirement, since we want the trac discussions to be inclusive,
> and
> people won't join in if they don't know they're going on. Can that be
> arranged
> with GitHub?


yes -- gitHub issues integrate very well with email.


> What advantages would GitHub offer over trac? I don't think we
> should have any more channels for discussion; we could agree to replace
> trac
> with GitHub, but it wouldn't be a good idea to maintain both at once.
>

gitHub has a nicer, more featureful interface and API, and is now more
widely used and thus more familiar to more people. Also, once someone has a
single gitHub identity, they can use that for everything on gitHub -- I
know I'm not that only one that has WAY too many passwords!

So I think we'd get better / more participation.

There was also talk of managing the doc itself on gitHub at some point --
that would be great.

-CHB



-- 

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

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20170227/05809e5f/attachment-0001.html>


More information about the CF-metadata mailing list