On Docs: https://readthedocs.org/projects/anuket/ already exists. There is a need for consolidated documentation (which was earlier driven in OPNFV by the docs project).
15 min
Assuming a successful Anuket recruiting program,
Anticipate new people in the specification WS and the Development Projects.
Thus developer on-boarding needs to be really easy, incl. a comprehensive set of documentation, wiki, etc.
We'll use spaces to avoid namespace conflicts. But use with care.
If you want sub-trees copied from CNTT or OPNFV wiki, send email to Jim Baker, identifying the root of the sub-tree. Jim will create the associated tickets with LF.
How did we do on this call for action?
Will we drop blank Wiki Pages from the Wiki? (#agree on this??)
Further topics:
Alignment of groups/IDs across LF LDAP and Github.
Anuket per project wiki: TSC AGREES to remove projects from the wiki that don't update their wiki by . Note that this does not include archiving the project (which might happen at a later stage).
15 min
Active Repo Migration
DockerHub Migration - no change to OPNFV Dockerhub
Contributor License Agreement → Only "DCO": Developer's Certificate of Origin
Other projects that Anuket Needs, but are not currently staffed???
PTLs/Co-Chairs
"Pharos":
Anuket needs a view of the available build/deploy/lab (incl. member labs) resources. TSC looks for volunteers to provide that overview - so that we can effectively use Anuket's budget in 2021 (before we spend money on new resources, the TSC needs a proper view on the current set of resources and their availability).
LFN lab resources: Linux Foundation Lab Projects are asked to move to "LaaS" resources (and off the existing UCS servers - so that they can be decommissioned).
