-
Notifications
You must be signed in to change notification settings - Fork 9.1k
TOB members 2019 #1922
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TOB members 2019 #1922
Conversation
@OAI/tsc could you please review my pull request? |
@ncaidin I may well be too pedantic here, but when I read
I worry that someone might interpret this as being the governing body, vs the BGB. Changing the charter, for example, is a cross-project high-level issue, but should not be done by the TOB. So should we somehow constrain this language? |
Thanks @usarid . I simply did a copy/paste from the Charter to make sure it was consistent. Please bear in mind that the TOB has been invoked zero times since OAI has been formed. I think the part where it says "in the TSC" makes it clear. The TOB is intended to resolve conflicts that the TSC can not in order to avoid having to go to the BGB. What if I change it to this: Personally I would be okay keeping the language as is or changing to this. Also open to other suggestions, but suggest we KIS (keep it simple). What do you think? |
The new language sounds great to me. Thanks!
…________________________________
From: Neal Caidin <notifications@github.com>
Sent: Friday, May 31, 2019 5:26 AM
To: OAI/OpenAPI-Specification
Cc: Uri Sarid; Mention
Subject: Re: [OAI/OpenAPI-Specification] Ncaidin patch 1 (#1922)
Thanks @usarid<https://github.com/usarid> .
I simply did a copy/paste from the Charter to make sure it was consistent. Please bear in mind that the TOB has been invoked zero times since OAI has been formed. I think the part where it says "in the TSC" makes it clear. The TOB is intended to resolve conflicts that the TSC can not in order to avoid having to go to the BGB.
What if I change it to this:
"The TOB is responsible for managing conflicts, violations of procedures or guidelines or other issues that cannot be resolved in the TSC for the OAS. For further details please consult the OpenAPI Project Charter."
Personally I would be okay keeping the language as is or changing to this. Also open to other suggestions, but suggest we KIS (keep it simple).
What do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1922?email_source=notifications&email_token=AAAJXW5EFXVLFQ2YFVRPW2TPYEKQVA5CNFSM4HL2BIVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWVCPKI#issuecomment-497690537>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAAJXW5247PZXDI6VZ2MRVLPYEKQVANCNFSM4HL2BIVA>.
|
@usarid text updated. Thanks for your review. |
@usarid , is there anything else I need to do to get this PR approved and merged? |
@OAI/tsc is there anything more that needs to be done with the request to get it approved and merged? Thanks. |
To reflect the latest TOB elections.