...
- We don't use all of the TSC members in the community. A few are involved with sub-committees etc, and some in projects. We could look at also assigning project support of some TSC members to groups of projects so that they have a TSC member to be a point of contact to represent their concerns, questions, etc and to lead the related discussion in the meetings.
- Missing f/b from the board meetings and related discussions about what it means for ONAP.
- Document placement on wiki should be much better organized. The proposal is to have a single storage place for ALL submitted documents by tagging where specific document belongs to
- We may need to have agreed requirements' terminology e.g. "shall", "should", "may" across a different architecture, use cases, modelling, security etc. activities
- A special folder with release's approved documents should be created (for easier reference by another committees/orgs)
- PTL's should be allowed to vote on process changes that affect the way they deliver their components
Agreed action plan
4/12/18 Recording: audio_only.m4a