Replaced the LC with the TSC.#51
Conversation
dblock
force-pushed
the
tsc
branch
3 times, most recently
from
4c0613b to
90b056f
Compare
Signed-off-by: dblock <dblock@amazon.com>
|
thank you @dblock - one comment - completely erasing the records of the LC feels inappropriate for transparency - I'd say we should likely note that it is super-ceded by TSC at least for a set time-period |
Signed-off-by: dblock <dblock@amazon.com>
I replaced MEMBERS.md in the LC folder by a note with a link to the last working version with the list of people and added a README with the same to access meeting notes. Does that work? |
andrross
left a comment
andrross
left a comment
There was a problem hiding this comment.
Looks like a .DS_Store file slipped in here
Signed-off-by: dblock <dblock@amazon.com>
KarstenSchnitter
left a comment
KarstenSchnitter
left a comment
There was a problem hiding this comment.
Good work. Only minor remarks.
Signed-off-by: dblock <dblock@amazon.com>
|
|
||
| b. Startup Period. | ||
|
|
||
| 1. The initial voting members ("Initial Members") of the TSC at the inception of the Project (the "Start Date") are those individuals identified as voting members in the "STEERING.md" file within the Project’s .github repository. Initial Members will consist of Initial Members serving one-year terms and Initial Members serving two-year terms, as indicated in the STEERING.md file. |
There was a problem hiding this comment.
I believe we set on TSC to be one year term?
There was a problem hiding this comment.
We always need some continuity, so it's 2 years to create overlap. At start LC members are 1 year so we can re-elect half after year 1, and the rest 2 years so we can re-elect the other half and then it's business as usual.
|
Thank you @dblock ! |
|
@krisfreedain Can this be merged? |
|
|
||
| 8. discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and | ||
|
|
||
| 9. coordinating any marketing, events, or communications regarding the Project. |
There was a problem hiding this comment.
This seems wrong. That's definitely not the job of the TSC. Point 9 is the job description of the community manager, and would be a significant distraction from the TSC's correct focus - on the steering the technical direction of the project.
There was a problem hiding this comment.
Thanks @rbowen.
I think this item came from the template we used and is present in other charters under LF, here and here.
Removing that paragraph would be an amendment to the Technical Charter that was reviewed by the members before we announced the foundation, which requires a 2/3 vote of the entire TSC and approval by LF. I opened https://github.com/opensearch-project/community/issues/53, please add your comments.
|
We had a discussion on whether this content belongs in the community repo and decided to create a new steering one. @krisfreedain is taking care of it. I'll split this PR in two then. |
…echnical-steering. Signed-off-by: dblock <dblock@amazon.com>
|
I've moved the TSC parts to https://github.com/opensearch-project/technical-steering (members merged as part of opensearch-project/technical-steering#4). @krisfreedain take a look again? |
8 participants
Description
The OpenSearch Project is supported by The OpenSearch Software Foundation, a project of The Linux Foundation. You can read the launch announcement here and learn more about joining the foundation here.
The project has a Governing Board and a Technical Steering Committee.
This PR adds the initial TSC charter and creates a placeholder for the GB.
Closes #48.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.