Hello Phil
I am interested to be part of a workgroup.
Best
Jamil
Le 14 déc. 2017 à 01:03, Phil Robb
<[email protected]<mailto:[email protected]>> a écrit :
Hello ONAP TSC Members:
As documented in the ONAP Project Charter, the TSC is tasked with figuring out
how to populate the TSC in a meritocratic manner beginning 12 months after the
project launch, which was March 2017. Hence it is time to start planning this
transition. To kick this process off, I have the following suggestions:
- Given that March 2018 is in the middle of the Beijing release cycle, I
suggest we postpone the TSC election until directly after the Beijing release
in late May. We should discuss and approve our method of populating the TSC by
the end of March, but not actually execute it until late May or early June.
Please let me know if you think this is a good or bad idea.
- I suggest we form a small workgroup to create an initial proposal for
discussion with the broader TSC. Some topics to consider when architecting the
TSC makeup include:
- Constituencies. Are there different constituencies that need
representation on the TSC?
- PTLs. Having an election of PTLs to populate the TSC one possible way to
do it. These PTLs may be from different constituencies, or just At-Large.
- Committers-At-Large (CALs). Some seats can come from the committer
community at large.
- Particular Roles. Possibly have the PTL from the Integration Team, or
the Release Manager as voting members of the TSC as an example of "special"
roles that should have TSC representation.
- Company Caps - To ensure that a single company does not have too much
voting power within the TSC, a limit (usually defined as a percentage) is
imposed on how many TSC members can come from the same organization (or
affiliated organization).
- TSC size. Common guidance is to keep the TSC size somewhere between 7
and 19. 11,13, and 15 are common sizes. Depending on how the TSC is populated
the size may vary or may be static.
Please let me know your thoughts. If you think a workgroup to put an initial
proposal together is a good idea, please indicate that. If you think we should
have a few open discussions to set an initial direction please indicate that.
If a workgroup seems reasonable, and you would like to participate in that
group please indicate that as well.
I look forward to the discussion.
Thanks,
Phil.
--
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
_______________________________________________
ONAP-TSC mailing list
[email protected]<mailto:[email protected]>
https://lists.onap.org/mailman/listinfo/onap-tsc
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc
