Re: [emergency-have] OASIS policy on Subversion and Git rep[ositories

[Robin Cover <robin@oasis-open.org>]

Hi Rex (and all)

Some additional documentation is available online for the use of GitHub repositories by TC members (for official TC work).  We also support "OASIS Open Repositories" for public participation in work loosely associated with a TC (but not under TC control). 

Doc: "GitHub Repositories for OASIS TC Members' Chartered Work"

https://www.oasis-open.org/resources/tcadmin/github-repositories-for-oasis-tc-members-chartered-work

Request Form: https://www.oasis-open.org/resources/tc-admin-requests/request-a-tc-github-version-control-instance-be-created

In particular, note

a) The GitHub repositories for TCs are considered venues for spinup by TCs (not by individual Subcommittees), but a TC can write a Description and Purpose Statement that matches the scope for a particular Subcommitee, and/or subset of Subcommittee work

b) We endeavor to provide write access for those who want and need to make commits to these GitHub repositories, but there's a special role for Maintainers (designated persons) that works better than giving blanket write privs to everyone in a TC.  See excerpt below.

Please feel free to contact me with questions on any details that may arise in your discussions

- Robin Cover

Maintainers. When a TC makes request for creation of a GitHub repository, one or more TC Members must be designated to serve as initial Maintainer(s) — sometimes also called "Committer(s)". Additional or substitute Maintainers may be designated at any time from among qualified TC Members.

All TC members may "contribute" substantive content, as well as provide input via GitHub Issues, comments, GitHub conversations, Wiki edits (etc), but they do not have full Maintainer responsibilities, described below. A regular TC Member can be a "contributor" in the GitHub defined sense: "contributor is someone who has contributed to a project by having a pull request merged but does not have collaborator [ viz, direct write] access."

A Maintainer, much like a prose specification editor, holds the pen and has direct write access to the GitHub "code" repository. A Maintainer accepts input from all TC members, evaluating it for incorporation into revised content. TC member input is expected in the form of GitHub Issues/Comments, GitHub conversations, pull requests, but might also be taken from the TC discussion list, or from TC meetings.

A Maintainer thus serves in an editorial capacity by having responsibility for assigning and closing issues, creating and associating milestones, creating releases, designating a default branch, creating and applying labels, initiating conversations on pull requests, merging and closing pull requests, assigning evaluation of a pull request, resolving merge conflicts, etc. The Maintainers may also monitor repository activity to help ensure that substantive contributions are made only by TC Members or by parties who agree to the terms of the OASIS Feedback License, as explained in the repository's CONTRIBUTING file.

On Mon, Mar 27, 2017 at 11:06 AM, rexbroo <rexb@starbourne.com> wrote:

Since we can use both/either Subversion/GitHub, I have no preference, except that we haven't set up an emergency repository on GitHub yet and we might want to establish TC policy before we do, since all OASIS TC members will have write privileges. We would, of course, be on an honor system, but it might be worthwhile to just have the TC on record for Requesting that only active SC members write to the SC's documents, or even that only approved editors write to the SC's documents. That would, at least, give us some legitimacy if we ever need to roll back someone's purposely unauthorized or accidental submissions.

Just a thought.

Cheers,
Rex

On 3/27/2017 8:50 AM, rexbroo wrote:

Hi Guys,

I went looking for OASIS policy for Subversion and Git repositories and found it it at https://www.oasis-open.org/resources/tools

I thought you might want to take a look at it,too.

Rex

-- 
Rex Brooks
Starbourne Communications Design
Email: rexb@starbourne.com
GeoAddress:
1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670 

-- 
Rex Brooks
Starbourne Communications Design
Email: rexb@starbourne.com
GeoAddress:
1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670 

--

Robin Cover
OASIS, Director of Information Services