Date: Fri, 29 Mar 2024 06:49:09 +0000 (UTC) Message-ID: <822103300.29781.1711694949947@aws-us-west-2-lfn-confluence-1.web.codeaurora.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_29780_986581345.1711694949947" ------=_Part_29780_986581345.1711694949947 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Agenda:
Attendees:
Brandon Wick Heather Kirksey Bob Monkman= a> Anjali Goyal Jill Lovato Jim Baker William Diego Maza
Notes:
The LF CS Team is working on an initial round of concepts / logos that w= ill presented on next week's call
There was some good feedback received on the Mission / Scope from the co= mmunity. Beth made tweaks to the Mission/Scope on these final versions that= Heather will clear with LF Legal
######################################
Mission Statement: Empower the global communications community by creating reference cl= oud infrastructure models, architectures, tools, and programs to deliver ne= twork services faster, more reliably, and securely.
Project Scope: An= uket develops open reference infrastructure models, architectures, tools, a= nd programs. Open source software developed within the project will leverag= e OSI-approved licenses, while documentation, including specifications, wil= l leverage open licenses. The scope of the project includes but is not limi= ted to:
(a) Enabling member communities to align on model, architec= ture and implementation requirements and specifications for cloud-based com= munications infrastructure and workloads
(b) Supporting open source and ope= n standards communities in the ecosystem,
(c) Developing an integrated, tested, an= d validated open software reference infrastructure (including int= erfaces to hardware), with tools of its own design and from upstream t= esting projects,
(d) Helping design a conformance fr= amework and validation programs,
(e) Contributing to and influencing upst= ream projects leveraging the reference infrastructure,
(f) Creating new open source compon= ents within the reference infrastructure where needed,
(g) Supporting ongoing strategic ac= tivities and evaluating emerging technologies to foster continued deploymen= t success.
######################################= em>
Brandon reviewed a draft Positioning and Messaging framework with the te= am and received real time feedback. Meld marketing committee members are as= ked to help fill in the framework before next Thursday's meeting.
There was a discussion around Anuket marketing vis-a-vis with OVP Market= ing / Badging / Cloud Native Testing and collaboration with CNCF. The = default of course would be to replace the "O" in OCP with an "A" =3D AVP an= d leverage Anuket with new brand. But we also want to ensure we get this ri= ght for cloud native, and include the CNF tests. Jim pointed out that the c= loud native folks are thinking about different levels for badges: Ed. gold,= silver, and/or CNCF badging + Telco badging, etc. Heather pointed out= how layered conformance could work (e.g. using K8s test from CNTT) + Addin= g Telco tests from CNTT, etc. to create a badge. Downsides of this app= roach, however, are extra complexity, asking the ecosystem to participate i= n 2 separate badging programs, and tying a badge to the work of multiple pr= ojects / development teams. There was consensus that the approach/bala= nce CNTT has created in its relationships between party was working well an= d should be applied to Anuket.
By the Anuket launch (scheduled for Jan 13), we should have talking poin= ts in hand about OVP/CVC etc. About a month later, we can announce the new-= look verification program (new name, new brand, new messaging, co-marketing= with CNCF, etc). A key point will be how we market the artifacts coming ou= t of Anuket. Once this has been further refined by the Operations Working G= roup, we can discuss this on the Marketing Working Group.
Topics for next week's call are to review the initial brand concepts, fu= rther refine the messaging doc, and discuss the preliminary comms plan. Ide= as for launch include a mini-summit or webinar.