Last week a number of community members worked on a digital sprint to improve the Developer Guide. The sprint was organised by CiviCooP (https://civicoop.org).
Blog posts by ErikHommel
Keep up-to-date with blogs from the core team, working groups, developers, users and champions worldwide. Subscribe to our newsletter to receive regular updates by email. We also have an RSS feed.
I would like to organize a digital sprint in the week of 12 April 2021 to update the Developer Guide!
The Developer Guide is a really important information source for new contributors to our community, but also to experienced contributors when information changes. For newbies it is important that they can find information quickly, the documentation is understandable, there are some FAQ's or how-to guides.....I am sure most of us can think of some kind of improvement.
In my previous blogpost on the Community Council and Sociocracy 3.0 (S3) I told you that we are studying and applying S3 to our community processes. In today’s little story I will focus on two important concepts in S3: driver and domain. And we are dying to get your feedback!
First of all, let me explain one aspect of our growing appreciation of S3 for our community:
Since April 2020, the first elected CiviCRM Community Council is a fact and I am proud to be a part of it! We have had our first two digital meetings across a few continents. The first meeting was basically just getting to know each other and have an initial chat about what we think our role should be. And accepting that we are never going to make everyone happy, do whatever everyone thinks the Council should do and meet the diverse expectations across the community.
We are about to start the election process for the Community Council of CiviCRM and we would like to invite you to register as a voter or nominate yourself as a candidate.
The Community Council of CiviCRM has been tasked at the Barcelona Civi Summit:
In october 2019 I spend a few days with the community at the Summit in Barcelona, and it was inspiring as usual! On the way back out of all the things we discussed two themes kept going around in my head. The first was the need for more marketing material that was felt by all present, and the second one was that in my opinion CiviCRM = software + community.
I have just published a new extension Former Communication Data.
The extension simply saves emailaddresses, phone numbers and address details in a separate tab on the contact summary when they are deleted as you can see in the attached screen print.
I have just published the CiviCRM native extension Contact Specific API Defaults which allows you to specify specific defaults for API fields for a contact.
The extension was funded by Mediwe and developed by CiviCooP based on this use case:
On Tuesday 11 September 2018 we had quite an enjoyable and interesting CiviCRM meetup in Antwerp.
A total of 32 participants gathered at the University of Antwerp Middelheim campus to share their stories around CiviCRM.
Diet Civi is a new "working" group within the CiviCRM community.
Our main objectives are to
improve CiviCRM’s ability to support a variety of different workflows on the common core data model.
define, coordinate, foster, and fund projects to achieve this.
