Date and Time: UTC 13:00, Thursday March 12, 2015
Convenor: Bin Hu (AT&T)
Chris Price was absent, and Bin introduced this project proposal in wiki.
Yuriy (ZTE) asked if we should have one documentation sub-project for each project we are working on, because all projects will produce documentation more or less. Bin explained that this proposal is targeted for release documents of OPNFV, such as Release Notes, Install Guides, User Guides etc. Of course, many contents will be from each project that participate in certain release. Bin also showed how OpenStack is structuring their documentation (Installation, API, Operations and Administration, User Guides etc.). And the intention of this project is an equivalent set of documentation for OPNFV.
Ryota (NEC) indicated that there is a project category called “Documentation”, which is supposed to cover a set of projects related to documentation. So the name of this project “OPNFV Documentation” seems confusing, because it overlaps with the category of a set of (future) documentation projects.
Bryan (AT&T) suggested to rename it "Readme", because from the project description, it focuses on the documentation of Release Notes, Install Guide, User Guide and possibly API Reference and Interface Specification. The name "Readme" seems more appropriate.
Uli (Huawei) said that it should be subject to 2-week’s review period, because there may be more comments during that 2 weeks. So we should wait until March 24 as the earliest date for TSC creation review.
Iben (Spirent) indicated that there was a discussion yesterday about training document. One suggestion was to include the training documents within the scope of this project. The question is whether or not the proposal should be revised to include training document.
Because of the priority and importance of this project (i.e. for Release One release documents), the consensus is that it should be ready for TSC creation review once those above 3 points are addressed, i.e.:
- Renaming it to "Readme" to avoid confusion with the project category "Documentation"
- 2 weeks public review period should be satisfied
- Clarify whether or not to include training document
No one presents it. Postponed
No one presents it. Postponed
Iben introduced the progress since last discussion on Feb 26. Bryan helped Iben create a new #4 column in BGS Installer Approach Table to document the SaltStack installer approach, namely "SlapStick". The information includes the choice of component at each level of the stack. It is the great first step, and more information will be added with the progress of the experiment.
Narinder (Canonical) indicated that they are interested in experimenting Juju installer approach, and will add more information there.
Uli (Huawei) indicated that they are also considering another installer "Compass". Uli will share more information with the community to discuss it in a few weeks.
The conclusion is that this Salt Stack OPNFV Builder proposal will further pursue its experiment and community support in BGS. It's no longer needed to be discussed in this meeting.
Howard (Huawei) described that according to the comments last week, the wiki was updated with a diagram and some revision in an attempt to address the comments.
Because of time constraint, the discussion was postponed to next week.