@dblodgett-usgs wrote: > I hope that in the future, we have a nice interface for diffing, commenting, > and evolving text for this kind of application, but right now we just don't. > So we need to kick out to google docs or fork repositories in small groups to > evolve the text of major contributions and look to the future for better > solutions.
Frankly, gitHub PRs are a pretty darn good interface for "diffing, commenting, and evolving text" it does fall down a bit on a having a good way to comment on an existing doc, rather than just the diff, but not too bad. "kick out to google docs" (or anything else) is a bad idea -- the whole point of git is to preserve the history, that's the part we really want to keep. However, key is that we need to start with a policy, and then see how it goes -- frankly, we can't nail down an exact policy anyway, and people wouldn't exactly follow it if we did. But in short, my suggestion is: - Use gitHub issues for managing general discussion - Use gitHub PRs for proposing and discusing changes to the text of the document. - Use branches when there is a large change, particularly if it effects multiple parts of the doc. - Use whatever the heck you want to develop the first draft of a major addition. -- 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-393207022
