| Review of Propose FOLIO Governance Model | Team | Discussion and notes: The following points we're raised: - The organizational structure presented may have a negative affect on attracting developers as it diminishes the role of Technology (TC "reports" to CC). It reinforces the concept that FOLIO is more about community and features than technology
- Terms of 1,2 years may impede continuity - consider longer terms
- Unclear how the TC and PC should communicate - do decisions need to go through and/or be approved by CC? Consider the case where TC recommends the project put resources on a Tech Debt Item. Does PC decide where resources are applied or does CC, or does CC have to 'approve' PC's decisions? The decision processes should be fleshed out.
- This doesn't seem to address what many feel is the largest issue for sustainability - where will the development resources come from as we build and maintain more and more functionality
- The doc should state that all meetings will be open (it's implied but better to be specific)
- Would like to discuss again next week.
|