More than 420 hours contributed back to CiviCRM in 2018!

Cividesk strongly advocates for community participation and collaboration to work on maintaining continued progress and improvement of CiviCRM. We pride ourselves on being involved in several aspects of ongoing projects and needs. 2018 has been an eventful year and we are happy to report that we have contributed to CiviCRM in a variety of ways:

1. Report and fix bugs
At Cividesk, we have a wide range of customers who use different parts of the software for their specific needs. It also means we get to work with a vast range of functionality that the CRM provides. Reporting bugs is a way to help developers and make it easier for them to repair the issue. Developers need to know step by step what we did before encountering the bug, how the malfunction exactly happened, what other extensions/plugins run at the same time, etc. Discovering and fixing bugs regularly contributes to the continued improvement of the software.

2. Contribute new features
New or customized features that are requested by Cividesk customers and that qualify to be generic enough to benefit other organizations are contributed back to CiviCRM to then be implemented for all users. We also like to hear from other developers and incorporate their feedback so that the best possible generic solution is pushed back into the software. Some of the features are provided as patches to the core code base and others are contributed as extensions.

3. Review patches
CiviCRM continues to thrive and improve thanks to the generosity of its users and the organizations that employ them. When someone opens a pull request (PR) on CiviCRM Core, it must be reviewed before we can merge it. Cividesk engages in reviewing core PRs and provides feedback which is a useful and much needed way of contributing to CiviCRM.

4. Code clean up
Cleaning up the code can be seen as paying down technical debt. Regular clean up reduces the risk of bugs and redundancy in future iterations. We have also contributed to this process because it is important in maintaining sustainabilty of the software.

5. Improve extensions
In 2018 we have ontributed to patches/bug fixes and improvements to various extensions. Most recently this includes CiviCase, Extended Reports and CiviVolunteer which benefit all CiviCRM users.

6. Contribute to translation
CiviCRM can be operated in many different languages! Cividesk continues to work on ensuring that the strings in the CRM are translated and make sense for users who are using CiviCRM in a different language than English.

7. Provide case studies
On civicrm.org you can find a large variety of case studies that present the success (and sometimes the challenges) of organizations who have been successful with the implementation of CiviCRM. Cividesk has published many case studies that can be a very helpful resource for organizations looking to learn more about CiviCRM and how it has been implemented by other organizations.

8. Forums
Cividesk continues to be very active on CiviCRM StackExchange forum which is a thriving place to ask and answer questions related to CiviCRM. We are very happy to help users from non-customer organizations to troubleshoot their issues or simply answer questions. Being active on StackExchange helps us learn about problems from various users and listen to other ideas as well.

9. Trainings
We provide monthly CiviCRM online trainings to users who need to learn how to use all the functionality of CiviCRM, refresh skills, train new staff or expand their use of CiviCRM.

Every month, the Cividesk team makes a dedicated effort to contribute back to CiviCRM in one way or the other. In 2018, Cividesk is proud to have contributed 420+ hours to CiviCRM's open source initiatives!

Category: