TL;DR: A migration project is underway to bring wiki content into the Developer Guide.
Blogues
Restez à l'affut des dernières nouvelles de CiviCRM avec les billets de blogue de développeurs et d'utilisateurs de partout dans le monde.
Civdesk is excited to announce our newest training opportunity - Effective Email Marketing with CiviMail. During this session you will learn how to best leverage CiviMail to get your emailing into your constituents Inbox and have your content read.
During this two-hour training, you will learn about:
Hello world, I would like to introduce the idea of of CiviCRM "Community Fridays". Let's coalesce our ongoing community efforts improving Civi around a certain day of the week: every Friday.
JMA Consulting is pleased to welcome Jon Goldberg as our new Director of Operations effective today.
Last week we had a fourth sprint to improve CiviCRM performance at the socialist party.
LYRIC is a small non-profit that is entirely managed by volunteer attorneys. Our mission is to teach youth how to safely exercise their Constitutional rights, and we do so by connecting with schools and community organizations and training volunteer attorneys to teach our curriculum to high schools students.
First CiviCRM release this year has happened: CiviCRM v. 4.7.15 and 4.6.25 are now released.
RELEASE NOTES:
Big thanks to Andrew Hunt from AGH Strategies for putting up together release notes for this version.
The release notes for 4.7.15 can be accessed here
cv (https://github.com/civicrm/cv) and civix (https://github.com/totten/civix) are Unix/CLI tools for developers. cv provides access to your Civi site on the command line, and civix generates skeletal code for new extensions.
Over at the Extensions Working Group, we’re making careful progress toward improvements to the extension ecosystem, aiming to make it easier for all of us to do what we want with extensions: End users and site admins: easier to find, select, and install the right extension; Extension developers: easier to publish extensions and set clearer expectations for support and maintenance, and easier to avoid duplicating existing extensions; Community volunteers: easier to conduct extension reviews and help them get qualified for automated distribution.
As an early step in those improvements, I’d like to point you to the relatively new Extensions Lifecycle documentation, which describes the process of publishing extensions through the CiviCRM ecosystem, along with clear definitions of concepts like stewardship (who’s managing this extension?), project maturity (exactly what is meant by saying an extension is “experimental” or “stable”?), and more.It's a time of year when machines and people get stressed, particularly in countries where tax laws and custom favour end-of-year donations. And if you've ever managed a CiviCRM installation, the last thing you probably want is to interrupt your end-of-year festivities with an issue of someone being unable to make a donation.
