The first meeting of the newly constituted CiviCRM Community Council was held July, 13, 2023.
Blog posts by JoeMurray
JMA Consulting is pleased to welcome Jon Goldberg as our new Director of Operations effective today.
Some contributions to your organization might be sensitive if widely known. For example, a planned bequest might need to be kept quite confidential since the donor wants to keep its existence private from other possible inheritors or to remain anonymous about their large donation. Or you might want to restrict viewing of membership contributions to the Membership staff, and events registration contributions to your Events organizer.
Many organizations use MailChimp, SendGrid or SocketLabs email integrations to ensure their emails are delivered with whitelisting and lower load on their servers. Switching to Mandrill can dramatically reduce the cost of these services.
https://civicrm.stackexchange.com/ is launched in beta and thriving as a place to ask and answer questions about CiviCRM. The benefit of the Q&A format is that good questions and good answers can get voted up, and better serve as an expert repository of our community's experience. Search rankings will soon be able to find good relevant answers to everyone's beginner and expert support and development questions.
Don't ask for your privacy. Take it back.
Reset the Net is a campaign to improve individual and organizational privacy against mass government surveillance. I think we as CiviCRM community members should step up and act. In particular, hosting providers, implementors, and organizations using CiviCRM should up their game to implement SSL, HSTS, and PFS.
I'm writing to ask you to download and test 4.3.alpha2 that came out earlier today (http://civicrm.org/blogs/yashodha/civicrm-43-alpha2-out), especially anything to do with money. If you don't have the time and / or resources and / or skills to create your own test installation, please try a Drupal, Joomla!
Extensions are a growing part of the CiviCRM way of doing things. We need to develop a process and toolset to facilitate getting them translated and making those translations easily installable. This post is intended to lay out some issues and a potential approach in order to generate discussion.
Here are some assumptions and suggestions I have:
Notice to non-developers: This post is about how some functionality in 4.2 will be implemented in code and in the database, with very minor changes to anything visible through a browser. If you're not a developer, it probably won't interest you.