Old wiki retention: OPNFV wiki is a dedicated confluence instance, and incurs monthly charges. There is a desire to sunset quickly. Content would be copied to a stable, long lasting site.
CNTT wiki will be moved to a separate space within wiki.lfnetworking.org and marked READ-ONLY
If you want subtrees copied from CNTT or OPNFV wiki, send email to Jim Baker, identifying the root of the subtree. Jim will create the associated tickets with LF. Look for an email from Jim.
Casey created a push button automation to help with creating notes-pages.
Please start to populate the wiki if you're the PTL of a project. Jim will notify folks via email.
Future topics: Alignment of groups/IDs across LF LDAP and Github. Issue tracking (Jira/Github?).
10,000ft view: Re-scope of the work needs to be done, incl. RA/RI.
If Pharos would be the home of PDF 2.0, the project definition, contributors, etc. would need to be redone - following an ack by the TSC.
In addition (separate from PDF 2.0) there is an upgrade required to existing lab definition. This can be separated from the PDF 2.0 definition. Al suggests that the long term focus on PHAROS would be the focus on lab infra and setup.
Could we consider having the installer teams (Airship, XCI) define what the PDF should look like?
Qiao Fu wasn't available for today's meeting. Discussion to be continued in the Tech Meeting on Thursday.
5 min
Continue Release process discussions, Goals and Management
Should specification and conformance streams operate independently or integrated?
What should the Release cadence be?
Artifacts to be included (#agree, hold-over from meld)
Jim will create a new mailing list for PTLs and WS leads.
Strong desire to migrate traffic to Anuket mailing lists (and off OPNFV lists). Note: Operating lists on group.io incurs a cost, hence parallel operation is not desired for a longer term.