A:Gergely Csatari to write a mail about TSC requires to add the TSC co-chairs as the administrators of the anuket-project GitHub organisation, so the community can manage the repo access.
My plan is to create a cross LFN wiki site to collect information, suggestions, feedback from the projects, as well as to convey the Board related and appropriate information to the project committers.
My suggestion would be to have a regular (say once in a quarter or at least 6 months) an open Board meeting (like we did for AI).
I think, we will need to raise a proposal for the Board to assist in seeking more resources and other (what?) support for the LFN activities.
In my view, Board could influence LFN bodies to help in better marketing the projects and the committers’ efforts. Any good ideas how?
Perhaps IT support issues if we think that they should be improved.
A:Sandra Jackson to run a report on Anuket contributors and commit report
Thoth was mentioned as a project that should move over
CNF task force
There will be a presentation/proposal to the TAC on
The idea is to create a standalone initiative for CNF gncertification
The CNF working group would work independently of RA2 and RI2
The reasoning is to not have to worry about the Anuket platform and the complications of having to incorporate Anuket into the solution. They want to use what they created already, which is different from Anuket
Focusing on the Cloud Native aspects of the project, rather than the functionality of working workloads.
5 min
Build server situation
The Orange build server is permanent and it is the build server for functest, barometer, NFV bench, vineperf opnvdocs and the anuket-specs
The LFN build server is still needed to provide redundancy for critical jobsA:Fabio Palumbo to share the document describing about responsibilities and scope of use with the build servers