Dear all, I have taken a look at ?ONAP TSC Charter DRAFT 6 6 Clean ? XXJ? document (I do not know if it is the latest version)
Here are some first comments: ? There are additional non-functional areas i.e. Operational requirements (monitoring tools, disaster recovery, alarm/event catalog, backup/restore strategy etc.) that we should consider. ? Will the Performance Coordinator also focus on KPIS/Telemetry, Scalability, dimensioning tool based on performance results etc.? Many thanks & regards Catherine From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Ed Warnicke Sent: Thursday, April 06, 2017 11:10 PM To: SPATSCHECK, OLIVER <spatsch at research.att.com> Cc: onap-tsc <onap-tsc at lists.onap.org> Subject: Re: [onap-tsc] DRAFT Technical Community Charter Oliver, I suspect we may have to prune at some point. I like getting the ideas out on the table to increase our available selections :) Ed On Thu, Apr 6, 2017 at 1:59 PM SPATSCHECK, OLIVER (OLIVER) <spatsch at research.att.com<mailto:spatsch at research.att.com>> wrote: Ed, as I like the idea of ?usability? (we actually have a metric in AT&T our OPS guys use to tell us how usable ECOMP is?) I am starting to worry how one coordinates all the coordinators to ensure we still end up writing code rather then just coordinate it. Maybe I am overly pessimistic but figured I point it out. Oliver On Apr 6, 2017, at 4:44 PM, Ed Warnicke <hagbard at gmail.com<mailto:hagbard at gmail.com>> wrote: On Thu, Apr 6, 2017 at 11:19 AM, Haiby, Ranny (Nokia - US/San Jose USA) <ranny.haiby at nokia.com<mailto:ranny.haiby at nokia.com>> wrote: Thanks Ed, Steve, Alla, Lingli, Phil, and Chris. I suggest adding another coordinator - a "usability coordinator". The inherent complexity of each of the merged projects, the complex task of the merge and a community led by engineers may result in severe usability issues. We may end up with an amazingly architected software that may not be usable for mere mortals. Usability of course is beyond the scope of any GUI, and touches all interfaces of the system. The role of such coordinator will be to ensure any developed functionality meets certain usability rules and guidelines and does not break the overall end user experience. This is an excellent idea :) It actually sparks another idea :) You seem to be focusing here on what might be termed "Runtime usability"... how easy is it to use the various interfaces of the system including GUI, I presume APIs, etc. One situations I have often seen trip projects up is "Deployability"... basically... how easy (or hard) it is to 'deploy' the thing. Some projects are insanely hard to deploy, some are easy. My experience has been its has less to do with the complexity of the underlying problem than it does with the care the projects take in being easily deployable... might be another good one to add to the list :) Ed Regards, Ranny. _____________________________ From: Danny Lin <lind at vmware.com<mailto:l...@vmware.com>> Sent: Thursday, April 6, 2017 9:56 AM Subject: Re: [onap-tsc] DRAFT Technical Community Charter To: <roberto.kung at orange.com<mailto:roberto.kung at orange.com>> Cc: onap-tsc <onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>>, <xiexj.gd at chinatelecom.cn<mailto:xiexj.gd at chinatelecom.cn>> Related to what is brought up below on project, I thought it would be great to hear the inputs regarding the charter of Architecture committee , the role of Architecture committee, where does it play in the lifecycle of the project, and how does it drive the architecture of ONAP in general (influence, or decide, or arbitration, etc) Danny Sent from my iPhone On Apr 6, 2017, at 9:35 AM, "roberto.kung at orange.com<mailto:roberto.kung at orange.com>" <roberto.kung at orange.com<mailto:roberto.kung at orange.com>> wrote: It is not clear for me how we create project with its resource. I assume the creation of projects will be the conclusion of the work of requirements on the architecture, based on the 11 modules that have been identified up to know. One project per module? Once we have a list of tentative project, I assume that the TSC will ask for resources. As we don?t know yet who merits to be commiters, How are we going to choose them at the beginning? And consequently the PTL? May be at the beginning some interim organization base on volunteering. I also find coordinators a good idea. May be it is redundant with commitees. As for the subject of coordinations, it should be decided by the TSC. They may not last forever. For me the first subject of coordination is the architectural framework. RK De :onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:onap-tsc-bounces at lists.onap.org]De la part de xiexj.gd at chinatelecom.cn<mailto:xiexj.gd at chinatelecom.cn> Envoy? : jeudi 6 avril 2017 10:57 ? : Christopher.Donley; onap-tsc Objet : Re: [onap-tsc] DRAFT Technical Community Charter Thanks to Ed, Steve, Alla, Lingli, Phil, and Chris. It's comprehensive. I've attached the document with some notes, and I hope these could help. Regards, ________________________________ Xiaojun XIE Technical Director of IT R&D Center, Guangzhou Research Institute of China Telecom. (O) 86-20-38639130 (M) 86-13316090153 xiexj.gd at chinatelecom.cn<mailto:xiexj.gd at chinatelecom.cn> From: Jason Hunt<mailto:djh...@us.ibm.com> Date: 2017-04-06 11:11 To: Christopher.Donley<mailto:Christopher.Donley at huawei.com> CC: onap-tsc<mailto:onap-tsc at lists.onap.org> Subject: Re: [onap-tsc] DRAFT Technical Community Charter Thank you to Ed, Steve, Alla, Lingli, Phil, and Chris for pulling this together! It looks great! I've attached a marked up version with some comments -- none major, but just looking for clarifications. I would welcome hearing from others on the perceived differences of "coordinators" vs "subcommittees" and in what other projects these structures have been used. Whichever we choose, I would tend toward not specifying in the charter which topics would be covered (just like we don't specify the actual projects in the charter). Thanks! Regards, Jason Hunt Executive Software Architect, IBM Phone: +1-314-749-7422<tel:(314)%20749-7422> Email: djhunt at us.ibm.com<mailto:djhunt at us.ibm.com> Twitter: @DJHunt ----- Original message ----- From: "Christopher Donley (Chris)" <Christopher.Donley at huawei.com<mailto:christopher.don...@huawei.com>> Sent by: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> To: "onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>" <onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>> Cc: Subject: [onap-tsc] DRAFT Technical Community Charter Date: Wed, Apr 5, 2017 1:14 PM Dear TSC, Ed, Steve, Alla, Lingli, Phil, and I have put together the attached DRAFT technical community charter. It is largely based on similar documents from ODL, OPNFV, FD.IO<https://urldefense.proofpoint.com/v2/url?u=http-3A__FD.IO&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=drPvJRzj_tQhCVms8mbsInYM-od7Ltrw2kU8KwaGlPw&s=26r7aZsEAv0ymANQk-oFXIXhMDJyrqVWa2BbuaM4UgU&e=>, and OPEN-O. There are a number of open issues in the draft, and we are looking for your feedback. To highlight a few areas and some of our questions: ? TSC Vice Chair: should we have one, and if so, did we describe the role correctly? ? Coordinators (leadership roles focused on various technical topics that we may want to address as a community): Is this the right approach? Did we call out the right examples? ? Subcommittees: we describe rules for establishing subcommittees under the TSC. This is a slightly different approach than coordinators to ensuring critical topics are addressed. Do we want to use both? Did we capture the distinction clearly enough? ? Architecture Committee: we specifically call it out in this draft. Do we want an Architecture Committee? Should it be included in the Charter? We?d like to request a 30-minute slot during this week?s TSC meeting to present the existing draft and start to collect feedback. Thanks, Chris _______________________________________________ ONAP-TSC mailing list ONAP-TSC at lists.onap.org<mailto:ONAP-TSC at lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-tsc<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwMGaQ&c=uilaK90D4TOVoH58JNXRgQ&r=3nVF4lkCrih5WqBdByLDuw&m=RvJlYI9cm03wE-WbtCO-MfsXo6p72C8ZccnF-7d5vlA&s=bLmUMQ4Wex6MOBiQ_CwZAPE08kIFtkuVMOELsHzTf04&e=> _________________________________________________________________________________________________________________________Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent doncpas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signalera 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 ONAP-TSC at lists.onap.org<mailto:ONAP-TSC at lists.onap.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=3nVF4lkCrih5WqBdByLDuw&m=RvJlYI9cm03wE-WbtCO-MfsXo6p72C8ZccnF-7d5vlA&s=bLmUMQ4Wex6MOBiQ_CwZAPE08kIFtkuVMOELsHzTf04&e= _______________________________________________ ONAP-TSC mailing list ONAP-TSC at lists.onap.org<mailto:ONAP-TSC at lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-tsc<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=drPvJRzj_tQhCVms8mbsInYM-od7Ltrw2kU8KwaGlPw&s=hFHfYeYmtMwKfK7SnKR71RqlCScVCHcaiXKibCYaeDo&e=> _______________________________________________ ONAP-TSC mailing list ONAP-TSC at lists.onap.org<mailto:ONAP-TSC at lists.onap.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=drPvJRzj_tQhCVms8mbsInYM-od7Ltrw2kU8KwaGlPw&s=hFHfYeYmtMwKfK7SnKR71RqlCScVCHcaiXKibCYaeDo&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170410/3959e6ab/attachment-0001.html>
