... | ... | @@ -15,7 +15,11 @@ Participants indicated that the market felt flat and that CiviCRM did not seem t |
|
|
2. Likewise, attendees agreed that various pages on c.o should be revised to emphasize spark, ES, and Partners, and to de-emphasize the download of the latest stable.
|
|
|
4. Elected board
|
|
|
5. Product management
|
|
|
6. Tutorial Extension
|
|
|
|
|
|
## Core Team led initiatives
|
|
|
1. Tutorial Extension
|
|
|
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
|
|
|
|
|
|
## Financial Position
|
|
|
The core team presented a YTD P&L and balance sheet, and summarized it's current financial position as:
|
... | ... | |