... | ... | @@ -17,9 +17,9 @@ Participants indicated that the market felt flat and that CiviCRM did not seem t |
|
|
5. Product management
|
|
|
|
|
|
## Core Team led initiatives
|
|
|
1. Tutorial Extension
|
|
|
1. CiviTutorial Extension - Based on feedback from participants (specifically around making CiviCRM more 'evaluator friendly'), the CT has begun work on an extension that allows for custom tutorials. UK participants discussed possibly working on the content at the upcoming sprint in the UK.
|
|
|
2. Feature Request - The CT consolidated existing projects on the a [form gitlab project for feature requests](https://lab.civicrm.org/community/feature-request). The purpose of this space is to create a forum where stakeholders may add, discuss and up/down vote improvements to CiviCRM.
|
|
|
3. Partner group communications on Gitlab
|
|
|
3. Partner group communications on Gitlab - DevCamp attendees proposed consolidating the partner and dev lists (currently google groups) on to Gitlab. Discussion on doing so for partner list [is happening here](https://lab.civicrm.org/community/partner-meetings/issues/3).
|
|
|
|
|
|
## Financial Position
|
|
|
The core team presented a YTD P&L and balance sheet, and summarized it's current financial position as:
|
... | ... | |