Hi All,
I have read the "Technical Charter". What I understood that was explained at
the developers conference is that ONAP will have a "Technical charter" and we
retain the "TSC Charter" that we have.
With this in mind, and in general, I have a few comments for this.
* I also understood that the "Technical Charter" should refer to the "TSC
charter", however I couldn't find this. For this I suggest add the following:
* In section 2: add a clause stating. "The operations of the TSC are
described in the TSC charter which is found on https://wiki.onap.org. In case
of descriprency between the this technical charter and the TSC charter, the
TSC charter takes precedence."
* Clause 2d of the technical chapter - This discusses that the
contributor maybe a committer by majority approval. The TSC charter however
describes the committer lifecycle more completely, however it also adds that a
committer promotion is "subject to TSC approval as well".
* I propose to replace clause 2.i. ii. Iii. With a new clause 2.d.i
"The role of the contributors and committers and the committer lifecycle is
described in the TSC Charter, which can be found on https://wiki.onap.org";
* Clause 2.g.viii indicates that the TSC policies are on
www.onap.org<http://www.onap.org>, but they are on wiki.onap.org.
* Clause 3 describes the TSC voting. This text is quite good and more
elaborate than the TSC Charter. I just note this for now, but later I think we
should lift this into the TSC charter as well.
* Clause 2bii the steady state startup period should be documented with a
Technical charter and TSC charter update (not the onap website in any manner).
Hence, I propose updating Clause 2.b.ii to read
* "Steady State": After the Startup Period, the size, makeup and
procedures for determining voting members of the TSC will be determined by the
TSC and documented in the TSC charter.
*
In addition, I have the following proposed additions (in addition to the
alignment comments above)
* Clause 1: There is the opportunity to also including in the scope an
aspect of driving industry adoption. To address this, we could add the
following clause. "The project scope of the project also includes activities
that promote and support industry adoption of ONAP as well as support actions
that promote industry alignment."
* Clause 1: I assume that this is for vendors as well. We could update
the first sentence as follows: The mission of the Project is to create a model
and meta-data driven reference open platform for service providers and vendors
to support/provide ......" ("and vendors" was added. It is in red in this
email, however just incase the color is removed).
* Clause 2e: add that it should also sign the contributor license
agreement. We could add at the end of Clause 2e: "Technical contributors are
required to sign the contributor licence agreement"
* Clause 8 describes "Amendments", and this says it is subject to approval
by LF projects. Can we be specific about what LF projects is (is that an SSL,
or what??).
Then I had a question. Clause 3d defines a "series manager". The term series
manager is not defined in this charter, that could be clarified.
Best Regards,
Steve.
From: [email protected] [mailto:[email protected]]
On Behalf Of Kenny Paul
Sent: 13 December 2017 17:01
To: [email protected]
Subject: [onap-tsc] LFN Technical Charter Changes for ONAP
All
Please find attached is a copy of the ONAP charter with the modifications to
align ONAP as a Serries LLC project within the LF Networking umbrella.
-kenny
Kenny Paul, Technical Program Manager
[email protected]<mailto:[email protected]>
510.766.5945
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc
