Sustainability

In late January, the CiviCRM Core Team published its 2019 annual report which laid out its objectives for 2020. While we’ve managed the occasional update somewhat randomly in the past, we’d like to stick to a cadence of quarterly updates going forward in order to communicate progress on our priorities. This update provides an overview of the first quarter of 2020 as well as reflects on what we see happening for the remainder of the year.

Let’s start with priorities that we cited where we’ve made some headway.

On 15 August 2019, we switched the contributor log (previously a webform/civicrm) over to Gitlab. Details on how to track time can be found here. We did this because more and more of the project management was taking place in Gitlab and because of weaknesses in the contributor log, specifically it was clunky and it was difficult to assess the legitimacy of contributions reported.

It’s been a long time coming, but we finally managed to post the Core Team’s financials online in a format that not only shows where we’re at but also breaks down our income and expenses over the past 12 months. We’ve maintained project stats online for some time at https://stats.civicrm.org so it made sense to just add a new tab there. Check it out here. The financials are currently updated each month, and we’ll continue to expand on them as we have capacity.

Contributor Elections

Of the 261 voters in this election, 199 cast ballots.

Those elected are:

• Allen Shaw, US

• Claire Williams, UK

• Erika Bjune, US

• Kathryn Carruthers, Canada

• Rose Lanigan, UK

Partner Elections

Of the 62 voters in this election, 49 cast ballots.

Those elected are:

The CiviCRM Core Team is pleased to announce what we hope will become an annual event; a combined governance summit and code sprint. This year’s event will begin on September 25th, immediately following CiviCamp Hartford, and will be located in West Milford, New Jersey (within an hour from major airports). Full event details including agenda and discussion are online (or will be soon) here: https://lab.civicrm.org/community-team/governance-summit-code-sprint/wikis/home

Earlier this year, we did a community wide survey to better understand the CiviCRM user base as well as help refine our priorities as a Core Team. While there were a few surprises in the results, one item that we expected to stand out was a need for ongoing training. Let’s face it… CiviCRM can be complicated, at least for those that leverage its full potential and adapt it to their own business processes.

Last week, I wrote about the CiviCRM community and tried to boil it down to a very simple venn diagram. Not only does 'community' play a huge role in producing the software through new features, bug fixes, etc., it also is invaluable for helping promote and raise awareness about CiviCRM the software.

The Core Team has spent the past six months assessing its capacity, managing a cultural transition, and overseeing the CiviCRM project in a post-founder environment that requires a different approach to economic sustainability. The challenges and opportunities presented by this transition can’t be overstated. We’re confident that, with strong community support, we can evolve CiviCRM into a model open source project.