CLAs relating to TAB GitHub repo ( tab-documentation )

I've started work on data prep for creating the requested GitHub "open" repo (tab-documentation), per the request form Chet sent through on Friday [1]

Since you've requested "Open source license: Apache License v 2.0" in this program, I assume we would expect Individual CLAs from the Maintainers, including from the two Invited Experts, if they are to be considered authors/editors of the two Handbooks.

But I can spin up the repo (today) without the additional CLAs if you want.   Chet?

Just now we have Individual CLAs on file for Trey, Jacques, and Stefan, but not for Patrick, Paul, or Ashok.  [2]   Chet, I'm guessing that you're also serving as a repo author/editor making substantive contributions, and would want to file a CLA also (up to you)

I'll create (per default spinup) a "master" branch with protection [3], and you all can take it from there, including further adjustments to README and CONTRIBUTING file boilerplate text.

- Robin

TL;DR::

=================== refs

[1]  Request for "

tab-documentation" repo

ACK:  https://issues.oasis-open.org/browse/TCADMIN-2868?focusedCommentId=69459&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-69459

Request an OASIS Open Repository project be created: tab-documentation

https://issues.oasis-open.org/browse/TCADMIN-2868

[TC] name: Technical Advisory Board (TAB)

[TC] email address: 

GitHub repository name: tab-documentation

Purpose statement: The Technical Advisory Board documentation

project will enable a broader community to provide input

on the materials developed by the TAB for the benefit of

the OASIS community.

Description: Supporting the development of best practice and

guideline documents by the TAB for the benefit of the

OASIS technical community.

Open source license: Apache License v 2.0

Maintainer(s): Please make all TAB members Maintainers

[2] CLAs on file ("x")

Members

[ ] Chet Ensign

[x] Trey Darley

[x] Jacques Durand

[ ] Patrick Durusau

[x] Stefan Hagen

Invited Experts

[ ]  Paul Knight [Editor's Handbook]

[ ]  Ashok Malhotra [Chair's Handbook]

[3]  protecting "master" branch initially (protection can be revoked)

Branch protection will disable a force-push to the named branch and prevent it from being deleted.

See: https://git-scm.com/docs/git-push#git-push--f

-f | --force

--[no-]force-with-lease

--force-with-lease=<refname>

--force-with-lease=<refname>:<expect> 

-- 

Robin Cover
OASIS, Director of Information Services