#160: Proposal to use GitHub instead of trac
-----------------------------+------------------------------
Reporter: jonathan | Owner: cf-conventions@…
Type: task | Status: new
Priority: medium | Milestone:
Component: cf-conventions | Version:
Resolution: | Keywords:
-----------------------------+------------------------------
Comment (by davidhassell):
Thank you, Tanya, for the work you are putting in to CF-1.7.
I'm in favour of moving the trac discussions of changes/defects/etc. to
git hub issues, especially in the light of the forthcoming move of the
definitive conventions document to github. I would have thought that the
current CF-metadata email list should carry on as is, unchanged - many
readers and participants do not want or need to contribute to changes, and
so would not then need a github account.
To contribute to an issue, would you need your github account to be
registered, in some way, with the cf-conventions repository? There would
need to be some access restrictions to protect the master repository
which, I think (?), might preclude the creation of ''banches'' by anyone.
Anyone can always ''fork'' the repository, though. (Do correct me if my
git know-how is wrong!)
I think that keeping the iterations to changes within the issue is
important as there they can be wrapped up with explanations and examples
more easily than as edits directly to a fork. Perhaps a guideline could be
that new changes are described in the issue's intial statement and
accompanied by a fork of the document which contains the proposed changes.
The changes would then be iterated in the issue discussion with updates to
the fork only happening by agreement, and certainly at the discussion's
successful conclusion. Just a thought.
Thanks, David
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/160#comment:7>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
