Hi TSC,
First of all, thanks Bin for the description. I personally did not know how
this meeting got created.
I think we can all agree that currently the only way for new projects to get
the stamp "you have community consensus" is through the decision of the weekly
technical discussion. Therefore, projects must go to the weekly technical
discussion and get the approval from it to reach the next level, the TSC. I see
some potential improvements in this process because there are some problems
that I personally see:
* We have a geographically widespread community. The time for this meeting
is never good for everyone and most of the times not even half of the TSC
participates, thus I don't think this meeting is a good way to measure the
"community consensus" because we are indirectly excluding TSC members and other
community members and we would like to hear their opinions too, right?
* Even if the project has been up for review in the wiki for 2 weeks, most
of the opinions, feedback, reviews are first time raised in that meeting and
not in the comments of the wiki. Therefore, most of the times, there is not
time to confront the points raised thus delaying everything
* Things can only move once a week, when this meeting takes place. This
adds an extra delay which could be avoided, or?. Let alone holidays, etc.
* Non native speakers might have difficulties to respond to feedback,
especially when comments are not raised before the meeting
* How the meeting decides if a project gets the approval is not clearly
settled. Currently, we don't vote and if there are no further questions, the
moderator of the meeting decides that the project is good to go to the TSC.
I'd like to suggest a new way for this which I think servers better the purpose
of "foster community review and fulfill the metric of “Proposal has been
socialized with potentially interested or affected projects and/or parties”".
Actually I have two similar alternatives, just the tool changes:
## Alternative 1 ## (preferred)
Upload the proposal to github (or gerrit or gitlab) and then allow TSC members
to comment on this and do the reviews online. Same procedure that CNTT is
following for its documents and a very common procedure in other open source
communities. We give 2 weeks and during that time TSC members must write their
concerns, questions, feedback, etc in the comments. Our PM or the person
proposing the project should actively take care of reminding it to the TSC
members, this way we will hopefully get reviews from the whole TSC. Things
could be of course delayed in case of need, e.g. a TSC person is on vacation,
comments were not addressed, etc... but in general, after 2 weeks, the project
is voted in the TSC and everyone had a chance to review it and raise concerns.
## Alternative 2 ##
Same as alternative 1 but uploading it to the wiki instead of github and review
the proposal in the comments.
The benefits I see:
* Everyone in the TSC can participate in the review 24h a day, 7 days a week
* We get opinions and comments from most of the TSC thus reaching what we
want: "community consensus"
* The person proposing the project will have space to think about the
concerns and reviews that were raised
* This eases a lot the participation of non-native speakers
* The project could still go and present in the weekly technical discussion
and of course clarify comments that were raised. However, the decision that it
has community consensus will be made by checking that TSC members reviewed it
and are fine with it
* From process perspective, I think this is clearer and it scales better
What you guys think? Any feedback is welcome!
Regards,
Manuel
From: opnfv-...@lists.opnfv.org on behalf of HU,
BIN
Sent: Sunday, August 25, 2019 6:54 AM
To: opnfv-tech-discuss@lists.opnfv.org ;
opnfv-...@lists.opnfv.org
Subject: [opnfv-tsc] Process Overview - How to Bring a Project into OPNFV
Hello community,
Fresh blood is joining us. New project proposals are coming. I want to take
this opportunity to give an overview of the process of bringing a project to
OPNFV.
1. History of Process
General Project Lifecycle is documented in [1]. Project promotion, and
demotion, across states can only be done by TSC review and voting. During the
reviews, the candidate projects are evaluated based on predefined metrics and
KPIs. The target numbers may vary for the different levels. In order for
creation review in TSC, proposals need to be emailed to TSC mailing list, and
posted for two weeks. Various review criteria are available in [1].
In practice, after OPNFV was founded, we started to discuss new project
proposals in TSC meeting on 10/21/2014 [1]. TSC spent 2 hours to discuss
several projects. None could be agreed. TSC realized that a separate community
discussion was needed to discuss project proposals, help proposals get
