Commit 4d0a1e8f authored by xavier's avatar xavier


parent cdfe5e13
#Project Ideas
PROJECT IDEA, PLEASE ADD IT HERE. IF YOU ARE A STUDENT PLEASE DISCUSS POTENTIAL IDEAS by submitting them as issue in this dedicated repo**
These are ideas for projects suggested by potential mentors or members of the CiviCRM community. Potential
GSoC students are free to propose projects that are not on this list, but will need to work with the community to
find a qualified mentor for the project.
##Improve multi-lingual scalability
Themes: Translation, Internationalisation, Database architecture
Potential Mentor: Mathieu Lutfy (primary), Xavier Dutoit (for client testing)
When organisations operate in multiple languages and have public-facing forms available in multiple languages,
CiviCRM has to be switched to "multi-lingual mode". This makes it possible to translate custom field labels,
contribution page titles, etc, into more than one language. However, the current database model is made in a
way that only makes it possible to use up to 3 languages. We are looking to change the database model to a
more scalable one.
Technically, the current database model uses one big table per entity, with an extra column for each language
(ex: civicrm_contribute.title_en_US). A MySQL "view" is then created to simplify database queries
(civicrm_contribute_en_US.title). The model needs to be flipped around: an extra table for each language. We
also need to provide an upgrade mechanism for existing sites.
#Mosaico for responsive layout for emails
Themes: UI, responsive html5
Potential Mentors :
Organization Feedback :
The system messages (eg confirmation for an event registration, donation receipt, opt-in email...) look..., well,
let's just say it has room for improvement
They are lots of framework and templates that are easy to customise and allow to produce nice looking emails,
no matter if you look at it on your desktop or with your smartphone.
It might be needed to extend the template system for automated emails (eg. being able to insert "layout" token,
header, footer...), have a publication workflow to use less and make it easy to customise these layout on a perorganisation basis, have a cssinliner, move away from smarty....
Improving the extension system
Themes: community, extension
Potential Mentors : Someone from compucorp (jamie?)
##Organization Feedback
There is more and more extensions added around civicrm, and it's awesome, but now we are hitting the
limitations of the infrastructure. Some changes are needed within civicrm (eg being able to define dependencies
when an extension needs another one). Some other changes are needed around how we promote and distribute
these extensions, eg. making it easier to know what extensions support the latest versions, and for those that
don't support them, what's the issue (simply a matter of updating the documentation, some sponsoring needed,
very complex changes, obsoleted and feature added in the core...).
##Social Media Integration
Themes: Online Marketing, Social Media, Social Graph Analysis
Potential Mentors: kurund (Primary) , Joe Murray (JMA Consulting), Xavier
Organization Feedback :
CiviCRM provides a way for non-profits to engage their constituents through multiple media – email, phone,
walk-lists, etc. Its support for social media is currently quite limited. Possible projects to improve it include:
Integrate with social media logins (likely best to start with Facebook, then Twitter and Instagram) for quick
and easy petition signing, event registration, etc. and to get authorized access to petition-signers' social
graphs ( )
Pull in contacts from social media & match to CiviCRM contacts based on available information
Import into CiviCRM data about who is re-tweeting, sharing, writing on your wall
Establish ways to determine highly active users based on their social media activity
Add social media feed dashlet to see 'what's going on right now'
Add ability to automatically publish/ tweet about events, certain types of activities, possibly progress
towards fundraising goals
## API v4
Potential Mentors: Eileen, Coleman, Xavier
Theme: api, integration
The existing api v3 needs to be improved. The core has committed and prepared a solid version for v4, but it would need further imrpovement, adding tests, documentation and security testing.
## Open Supporter Data Interface (OSDI) API Implementation
Themes: Integration, Usability, Extension
Potential Mentor: Joe McLaughlin (Primary), and potentially Eileen McNaughton, Jason Rosenbaum (OSDI
org mentor), Josh Cohen (OSDI org mentor) - Joe McLaughlin will determine the possibility of any or all of these
folks being available
This project will continue work towards a beta CiviCRM extension that will allow CiviCRM to implement the Open
Supporter Data Interface (OSDI) API. See .
## Linking CiviCRM with LibreOffice / Collabora Office
Themes: Usability, Extension
It would be very user-friendly if CiviCRM would provide an action to write a Letter to a contact with LibreOffice /Collabora Office instead of using PDF-Letter. CiviCRM should pass Tokens to LibreOffice / Collabora Office .
LibreOffice / Collabora Office should run in the web (like in Owncloud) It should be possible to design a open
document template which includes tokens like display_name, address and so on. The action-menu of the
search-builder or a contact overview page should contain a button to start Libreoffice in the web. In the next step
the user should select a deposited template. If the action has been started from a search-builder, Libreoffice /
Collabora Office should print a serial letter, otherwise a single letter. The document should be saved as an
activity of the contact.
##Mailing list functionality
Themes: Usability, Mail, Extension
This goes in the same direction as the social media integration: Many NGO's make extensive use of mailing lists
for discussions between certain groups. Typical software, which is used by many organisations is "mailman".
Much of the needed functionality of such a mailing list software is already included in CiviCRM (such as
subscribe, unsubscribe, bounce management, ...). There "simply" has to be a new function, that allows
authorized e-mail-addresses sending bulk mails to their discussion groups.
In the past, there had been a quite complex solution using drupal organic groups and synchronize them with
CiviCRM. However, we would like to avoid the complexity and the dependencies that are coming with that
##CiviPhone Interactive Voice Response (IVR)
Themes: Integration, Usability, Extension
Potential Mentor: Joe Murray (Primary)
This project will create an extension that will allow CiviCRM to conduct automated phone interviews with contacts
selected from within CiviCRM. It will build on previous work done with CiviSurvey, and an extension that sends
voice blasts (robocalls) to contacts using Plivo's API. CiviSurvey question types will be limited to those that are
easy to collect responses for over the phone.
## Docker, cloud/Virtual Machine Templates (Appliances/Boxes)
Themes: Systems Engineering, Virtualization
Potential Mentor: totten (Primary) , nganivet (maybe bgm, ergonlogic?)
Organizational Feedback :
As with many open-source web applications, installing CiviCRM can be difficult – it requires installing/configuring
a series of related services (Linux, MySQL, Apache, an email service, and a CMS). A popular solution to this
problem is to distribute pre-built virtual machine templates ("appliances" or "boxes").
Unfortunately, there are many competing virtualization systems – such as Amazon EC2, OpenStack,
DigitalOcean, VMWare, VirtualBox, Vagrant, and Docker.
##SMS Tracking Survey
Themes: Extension, Usability, Data enhancing
Potential Mentor: JohnFF (Primary) , Joe Murray
Organizational Feedback :
Future First has an SMS Tracking Survey, originally made by Third Sector Design. Since then it's been tweaked
and cleaning/evaluating tools have been added. But it's still ropey, with deadlocking issues and a lot of FF
customisations. The parts that translate a response into a field should be made to be generic and settable
through an interface.
The objective here is to make it possible to release this extension as a standalone product.
An option would be to refactor current extension so that the UI for creating the survey, selecting recipients and
associating the activities with the recipients is done mostly through the existing CiviSurvey component. Thiswould improve the usability of CiviCRM overall, and reduce the code maintenance effort. Major tasks would then
be: 1) hooking in the use of SMS, 2) generalizing the method used to semi-automatically convert 'dirty' data
responses from free text entry into clean data for the Activity fields (called translating the response in current
implementation), and 3) support branching to next question based on response received for current question.
##RTL Languages Support
Themes: Translation, i18n.
Potential Mentors: Luciano Spiegel (Primary) , Ariel Kogan
Wiki: Localising for RTL languages (i.e. Hebrew, Arabic, etc.)
CiviCRM has been successfully translated to several languages. However, some issues still remain when trying
to run it on right to left (RTL) languages. The project aims to tackle two main lines of work: 1) Overcome the
technical challenges that are keeping CivCRM difficult for RTL languages translations (e.g. Editor for e-mail
sending, wizard-type progress bars) and 2) Make progress with the translation to Hebrew and use it as a proof of
concept to ensure goals with the first task are achieved.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment