Skip to content

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

Merged
merged 9 commits into from
Jul 8, 2019
Merged

TOB members 2019 #1922

merged 9 commits into from
Jul 8, 2019

Conversation

ncaidin
Copy link
Contributor

@ncaidin ncaidin commented May 9, 2019

To reflect the latest TOB elections.

@ncaidin
Copy link
Contributor Author

ncaidin commented May 30, 2019

@OAI/tsc could you please review my pull request?

@usarid
Copy link
Contributor

usarid commented May 30, 2019

@ncaidin I may well be too pedantic here, but when I read

and any cross-project or high-level issues that cannot be resolved in the TSC for the OAS

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?

@ncaidin
Copy link
Contributor Author

ncaidin commented May 31, 2019

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:
"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?

@usarid
Copy link
Contributor

usarid commented May 31, 2019 via email

@ncaidin
Copy link
Contributor Author

ncaidin commented Jun 3, 2019

@usarid text updated. Thanks for your review.

@ncaidin
Copy link
Contributor Author

ncaidin commented Jun 7, 2019

@usarid , is there anything else I need to do to get this PR approved and merged?

@ncaidin
Copy link
Contributor Author

ncaidin commented Jun 13, 2019

@OAI/tsc is there anything more that needs to be done with the request to get it approved and merged?

Thanks.

@ncaidin ncaidin changed the title Ncaidin patch 1 TOB members 2019 Jul 8, 2019
@webron webron merged commit 04f659a into master Jul 8, 2019
@webron webron deleted the ncaidin-patch-1 branch July 8, 2019 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants