... | ... | @@ -7,12 +7,12 @@ Participants indicated that the market felt flat and that CiviCRM did not seem t |
|
|
1. Spark
|
|
|
2. [Extended Support](https://lab.civicrm.org/core-team/civicrm-extended-support)
|
|
|
1. The core team presented a 4 month extended support release focusing on security updates and critical bug fixes for discussion.
|
|
|
2. Though there was broad support for a paid ES version, most felt that 6 months or greater was necessary to provide meaningful value to partners using ES.
|
|
|
2. Though there was broad support for a paid ES version, most felt that 6 months or greater was necessary to provide meaningful value to Partners using ES.
|
|
|
3. Attendees stressed that the real market for ES was in the partner community, and a paid release to end users would fall flat.
|
|
|
4. The core team agreed to digest the feedback and follow up within the next week with proposed revisions to ES.
|
|
|
3. [Stats](https://lab.civicrm.org/infrastructure/stats-collection)
|
|
|
1. Attendees agreed that improving our collection of stats and user information was a priority in order to more effectively market to our community.
|
|
|
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.
|
|
|
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
|
... | ... | |