... | ... | @@ -5,6 +5,10 @@ Participants indicated that the market felt flat and that CiviCRM did not seem t |
|
|
## Key Takeaways
|
|
|
|
|
|
1. Spark
|
|
|
1. The core team discussed the current # members (30) as well as the passive marketing approach to date.
|
|
|
2. CiviCRM partners are able to register for their own spark account (https://civicrm.org/civicrm/contribute/transact?reset=1&id=100) and are free to build services around Spark.
|
|
|
3. One Spark user as of this writing as transferred to a CiviCRM partner and another is expected to do so per KarinG
|
|
|
4. The core team will work up plans to more actively promote 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.
|
... | ... | @@ -13,7 +17,9 @@ Participants indicated that the market felt flat and that CiviCRM did not seem t |
|
|
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.
|
|
|
4. Elected board
|
|
|
4. Establishment Committee - Participants agreed to elect a team of individuals tasked with formalizing a governing body/process whereby the community can shape the priorities and direction of CiviCRM. The summit attendees empowered Pete D, Jon G, Peter P and Josh to drive this initiative and work up an outcome that is in the best interest of the project.
|
|
|
1. [Outline of objectives, decisions and format](https://lab.civicrm.org/community/governance-summit-dev-camp/wikis/governance-summit/Governance-summit-decisions)
|
|
|
2. [Call for establishment committee elections](https://lab.civicrm.org/community/governance-summit-dev-camp/wikis/governance-summit/Call-for-Establishment-Committee-Nominations)
|
|
|
5. Product management
|
|
|
|
|
|
## Core Team led initiatives
|
... | ... | @@ -29,6 +35,7 @@ The core team presented a YTD P&L and balance sheet, and summarized it's current |
|
|
3. CT members earn $50 an hour w/o benefits, and will float their pay in order to keep the project 'sustainable'. Using quotes here, but that isn't really sustainable.
|
|
|
4. Visibility on income has historically been difficult because both donations and earned income are tough to budget. Consulting projects are not typically known in advance and fundraising efforts vary.
|
|
|
5. Karin Gerristen provided a breakdown of 2017 budgets and demonstrated how partner dues could be changed to cover a portion of the gap.
|
|
|
6. Though no formal commitment was made, the core team will provide periodic updates about its financial position to the community at large.
|
|
|
|
|
|
|
|
|
## Community Summit 2019
|
... | ... | |