This issue is for discussion, potentially at the upcoming CF Community Meeting, on how to take care of the source codes for the Conventions, and taking care of some technical debt therein.
All of the suggestions below are my own and some people may disagree with them, I'm just collecting for now. 1. We have a lot of broken links and could fix them. 1. It would be a good idea to use aliases for hyperlinks rather than embedding the URLs in the text, so that it's easier to move the links if needed. 1. Putting single sentences on a line of their own would improve readability of diffs and help us track changes better - restricting lines by character length isn't really necessary for a document of this type. 1. Eliminating trailing whitespace would also be good. In terms of helping issues move along our pipeline, a few ideas: 1. Use project boards 1. Eliminate the "question" template, instead directing users to the "discuss" repo 1. Adding checks to the PR template - are authors included in author list? Is the change recorded in the changelog, so that we don't have to do archaeology at the end before a release? -- 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/267 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
