search

opengeospatial / CoverageJSON

Public repo for CoverageJSON project
Apache License 2.0
10 stars 8 forks source link

How to update the proposed Community Standard #10

Closed chris-little closed 2 years ago

chris-little commented 2 years ago

There is a full copy of the specification in this GitHub repository. When should we insist on PRs from branches and forks, and when should we do updates in-place on the master branch?

chris-little commented 2 years ago

I propose that full PRs are done for significant edits, then we have slightly formal, but still ad hoc, meetings to record the group decisions on each PR. We shold only do trivial edits in place, such as typos, formatting and grammar, but we should not have a succession of lots of little/small edits, as it makes life fiddly for those following the repo. Thoughts?

jonblower commented 2 years ago

I think typos/grammatical edits that don't change the meaning or structure could be done in-place

chris-little commented 2 years ago

Agreed 2021-11-10 PRs for substantive changes, and a few in-place edits for typos (to be kept to a minimum, to avoid too many notifications. At least 2 reviewers for PRs.