- Meeting times
- TSC not technical enough. Solve technical problems across projects when teams have trouble passing milestones.
- Projects spending too much time on architecture/modeling, and not enough on code
- Digest news from wiki, mailing lists on a weekly/monthly basis (newsletter?)
- Prioritize TSC agenda/time to focus on high-priority
- JIRA for TSC decisions to make sure we follow up
- wiki internal organization (hard to find things under current structure)
- Streamline ONAP - core projects + "add-ons"
- Community still behaving in startup mode - development done inside companies, and dumped as seed code into projects, rather than transparent development in the projects
- ONAP should behave more like a meritocracy. Projects added based on value to companies. Incubation area? Approval criteria: significant commits from 3+ companies?
- TSC membership - lose membership if you miss more than a certain number of meetings?
- Too many private email exchanges. Use public forums.
- Message board, especially close to the release. Reminders on upcoming milestones/project issues.
- TSC members shepherd projects?
- #1 issue is ease of joining ONAP for a newbie
- documentation
- be willing to close things. Too many subcommittees/tiger teams?
- action register for TSC
- prioritize/differentiate threads, triage and delegate threads, dashboard for status
Overview
Content Tools