Hi all, I have created a google doc here: https://docs.google.com/document/d/188rzOJF2i6-WOOqJOHCaSy9DOGyPiCoLHIFTBSWaDnA proposing some answers to my questions.
The members of the TSC WG and those who asked me to participate should have in their calendar an invitation for a call to go through this document and have a discussion. If anyone else wants to attend let me know and I will send you an invitation. Thanks! Joseph From: Dev [mailto:dev-boun...@lists.opencontrail.org] On Behalf Of Gasparakis, Joseph Sent: Monday, July 10, 2017 1:06 AM To: dev@lists.opencontrail.org Cc: ashbhal...@gmail.com; adapt...@juniper.net Subject: [opencontrail-dev] [TCS] Proposed technical governance structure including model Hi all, These are the items for this topic: - Model and rationale for it - Diagram/workflow (this is important) - Process for revising technical processes (3-4 weeks) Trying to kick off the discussion, here are some (scattered) thoughts I have, please add your thoughts: Model and rationale for it - This needs to be in accordance with the foundation that OpenContrail will get under - We need to consider the following: o How will the decisions in the TSC be decided? Will there be cases where a unanimous decision is needed, and when? Will most of the decision require majority or a specific percentage of the votes? o Only one representative in the TSC from each organization? o What are the focus areas of the TSC? ? Make architectural proposal and decisions for OpenContrail? ? Make contact with other Open Source projects (and their perspective TSCs) that OpenContrail will need to interface with? (like OpenStack) ? Prioritize and define usacases? Where do these usecases come from? Do we need something like "marketing committee"? ? Election of committers and new TSC members? What is the process for something like this? ? Review of operations? Does CI/CD systems do what they are supposed to do? Opens? ? What else? Diagram/workflow - When we have some more clarity on the model and rationale we can start putting some diagrams in place and we can continue the discussions based on these diagrams - What is the repository for these diagrams? What format should be used? Process for revising technical processes I supposed the technical processes need to be defined first so here is an attempt to start the list (some already discussed in Model and rationale for it) - Decision on election of committers, contributors and TSC members - Decisions on networking and hardware technologies to be supported in contrail and making sure they are abstracted in a way that most hardware vendors are covered. - CD/CI - Additions, updates, removal of unnecessary processes. Does CD/CI caters for the above networking and hardware technologies? - What else? Thanks Joseph -- Joseph Gasparakis Intel Corporation NPG Architecture & Systems Engineering
_______________________________________________ Dev mailing list Dev@lists.opencontrail.org http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
