#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 jonathan):
In commenting on Dave's geometries proposal (https://github.com/cf-
convention/cf-conventions/pull/109) it turned out that I had a lot of
suggestions to make. It didn't seem possible to do this with !GitHub
comments so instead I edited Dave's !AsciiDoc text. !AsciiDoc is not the
same as !MarkDown, so !GitHub can't render it correctly, but it's not
''very'' different. Having gone through this exercise, I wonder whether in
future it would be best to develop conventions changes on !GitHub issues
in !MarkDown format, and convert it to !AsciiDoc after agreement. There is
at least one program (`pandoc`) which is said to be able to do this. Or
could we store the conventions document in !MarkDown rather than
!AsciiDoc? I assume that !MarkDown doesn't have all the required
facilities, since !AsciiDoc appears to be more powerful.
Jonathan
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/160#comment:23>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
