Al, I would encourage us to stop mentioning "Debt" everywhere. It's quite disrespectful from the main (past and present) contributors and their companies. Even more when it may come from external people (see FMO) who don't contribute code to the project and who somehow are unaware of the open source principle and workflows.
Then I would appreciate us to quickly draw the contour of all CNTT FMO and OPNFV TSC actions. It's simply becoming impossible to contribute to OPNFV (and I would add CNTT too) due to: - the huge amounts of meetings (and you're forced to follow all of them as they are no public review, no mailing list thread, the feedbacks are hardly taken into account) - many planning decisions fully disconnected from the constraints (holidays, releases, etc.) - external companies are now allowed to interfere with activities decided by the contributors and their companies (see new OPNFV release management and the traceability) - the demotivation created by them and an unclear future I would ask the companies who suggest disruptive changes to OPNFV to commit human resources contributing code to OPNFV. I can't support a kind of subcontracting model when you're deciding for others thanks to "special roles and votes". We are rather losing the last developers very soon. And lots of disruptive changes may not help here (Gerrit/Jenking migration to GitlabCI, hardware resources are moving out to LFN, etc.) Hoping this email will be treated as opposed to all Functest announcements. Allowing developer to work back is more than an urgency. Cédric -----Message d'origine----- De : opnfv-...@lists.opnfv.org [mailto:opnfv-...@lists.opnfv.org] De la part de Al Morton Envoyé : lundi 24 août 2020 01:57 À : MORTON, ALFRED C (AL) <a...@research.att.com> Cc : STEELE, SCOT <ss8...@att.com> Objet : Re: [opnfv-tsc] LFN Governing Board outcome on the OPNFV-CNTT Merger OPNFV, Following the initial organizational meeting on Friday, I now ask for volunteers to serve on one of two new teams: 1. Organization/Governance - Definition of org structure, Interactions with OVP, cvc, TSC composition, Voting eligibility, Etc. 2. Technical/Debt/TSC - Operational aspects Since the tasks for each team and their Scope have not yet been fully defined [0], please let me know (directly by e-mail) if you are willing to serve on one or both of these teams. I think we will need more sessions to clarify the scope of these two teams, so please bring your questions to the meeting next week, schedule to be announced. thanks, Al TSC chair [0] https://wiki.lfnetworking.org/x/SApoAg > -----Original Message----- > From: MORTON, ALFRED C (AL) > Sent: Thursday, August 20, 2020 9:24 AM > To: opnfv-...@lists.opnfv.org; opnfv-tech-discuss <opnfv-tech- > disc...@lists.opnfv.org> > Cc: STEELE, SCOT <ss8...@att.com> > Subject: LFN Governing Board outcome on the OPNFV-CNTT Merger > > OPNFV, > > The LFN Governing Board expressed strong support for the Merger of > OPNFV and CNTT at their meeting on August 19th. This is good news for > OPNFV; it is the option many of us preferred from the start of Future > Mode of Operations (FMO) discussions. A special shout-out to Scot > Steele, who led the CNTT FMO team for several months. > > As the CNTT FMO committee concludes its work, there will be a new > transition team formed to complete the merger. There is plenty of work > to do. Folks who are interested should continue to attend the "last" > CNTT FMO meeting in the Friday time slot to learn more. (I don't know > more than this now, sorry for that.) The board has asked for a smooth > transition as much as possible, and as short time frame as possible > (re-use of the best rules, charter aspects, etc.). > > Meanwhile, our development efforts in all our projects continue, > including the work toward the OPNFV JERMA Release. > > THANKS for your continued participation in OPNFV, and the new > organization in 2021! > Al > TSC Chair _________________________________________________________________________________________________________________________ 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.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#24335): https://lists.opnfv.org/g/opnfv-tech-discuss/message/24335 Mute This Topic: https://lists.opnfv.org/mt/76381620/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
