search

opengeospatial / Bounding-Box-Abstract-Specification

Other
0 stars 0 forks source link

Management of changes #3

Open chris-little opened 2 years ago

chris-little commented 2 years ago

@ghobona There is no protection on the main branch. I suggest this is tightened up to only allow merges of Pull Requests after at least two approving reviews. I suggest @samadammeek agree a list of 3 or more potential reviewers from the Conceptual SG of the Architecture DWG. In other repos, 'in place' editting has been allowed for typos, grammatical and other non-substantial changes, but this has a knock-on effect on people who have taken a fork/clone and then have to re-base. I suggest all editting should be via PRs, and typos should be accumulated and a PR created.

ghobona commented 2 years ago

@chris-little I agree.

I suggest the reviews are you, @samadammeek , and @KathiSchleidt.

ghobona commented 2 years ago

I've set up a GitHub Team at https://github.com/orgs/opengeospatial/teams/bounding-box-abstract-specification_project-team/members

Members of the team have 'Write' access to the repo.

I have also set up branch protection on the main branch for 3 approvals to be required before changes are merged. The 3 approvals will also apply to members of the GitHub team.

ghobona commented 2 years ago

Please note that GitHub does not offer an option, through its User Interface, for stating where those approvals have to come from.