Heather mentions that current assumption on event planning was 4 events per year. Heather asks: Given that the overall outlook on the progression of the pandemic is still unclear, do we want 4? There could be a potential for hybrid events in the 2nd part of the year.
Beth suggests that long term we might want to consider alternating purely virtual with purely physical events (different definition of what is commonly understood as "hybrid" where some folks are local and some are virtual/remote).
Understanding is that "classic hybrid" is challenging for remote attendees.
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.
Future topics: Alignment of groups/IDs across LF LDAP and Github. Issue tracking (Jira/Github?).
We'll use spaces to avoid namespace conflicts. But use with care. Current spaces (Virtualized Environment is for RA/RC1; Containerized Environments is for RA/RC2; for "everything Anuket", we'd use the Anuket space moving forward):
Please send feedback about pages to be moved to wiki.anuket.io to Jim by no later than Friday (Feb/12) this week.
Discussion on the need of having wiki pages for projects. Cedric makes the case for Functest to only work on github now (i.e. documentation only in git). Heather suggests that for a vibrant community, there is a need for a wiki to keep meeting notes etc. Cedric suggests to start with a simple link from the wiki to the functest documentation in git. Cedric underlines that he'd like to keep documentation (in git) separated from "wiki type" documents. End users should be guided to documentation first because wikis are often outdated.
15 min
Run CNTT RC2 by yourself via Katacoda (20 minutes, 10 clicks)
Heather mentions that the charter is a legal document and should be seen as such. It is mostly there to get Anuket incorporated as an LLC. We might rather focus on the operational guidelines - to document our processes and best practices.
Feeling by the group is that the charter might be overloaded with content that could also live somewhere else and does not need to be in a legal document.
Heather will invite Mike Dolan to one of the next TSC meetings to provide detail/guidance of what is required in a charter document.
Other projects that Anuket Needs, but are not currently staffed???
PTLs/Co-Chairs
Docs: Sofia has mostly been running the docs project single handed with help from Trevor and Aric. Thus we need to re-energize the docs project - there is a need for new blood. It was always part of the plan to have docs as part of the release process - to some extend this has been done, but there were always lose ends to pick up. David McBride echos that there is a need for a dedicated docs project. Near term, there is a need to merge CNTT and OPNFV documentation. David suggests to start with the CNTT documentation as a baseline and expand the scope to include elements from OPNFV. Someone needs to drive this task. This "someone" would be the docs project. An alternative could be a "docs working group". Any volunteers? Note: Projects write the documentation - the docs project is mostly about organizing and structuring the content.
Pharos: Similar to Docs: We need a volunteer to drive Pharos.
Heather mentions that recruiting new contributors to Anuket is the #1 prio for 2021 from marketing and overall LFN. Thus developer onboarding needs to be really easy, incl. a comprehensive set of documentation, wiki, etc. To be considered as a dedicated discussion topic for a future TSC meeting.
Future topics:
How do we figure out who is a WS stream leads AND PTLs in an automated way.
Docs project: PTL Step down - re-org.
Leverage dynamic shared runners for containers ??
Assuming a successful Anuket recruiting program, we need to make it Easy-to-join the specification WS and the Development Projects. What are the activities to accomplish this?
Action Items
Type your task here, using "@" to assign to a user and "//" to select a due date
