Today at the Bristol Code sprint a few of us made a concerted effort on getting making Giftaid 'plug and play' for Civi.
Our starting point is code written by Millertech and our aim is to get it into a state that we can package it as a Drupal module. Once we've done that, we're hopeful that we'll be able to package it for Joomla also.
CiviCRM Trainings / Code Sprint:
- Configuring, Customizing and Extending CiviCRM - New York: Sep 16, 2010 8:30 AM - Sep 17, 2010 5:30 PM
- CiviCRM User and Administrator Training - New York : Sep 16, 2010 8:30 AM - Sep 17, 2010 5:30 PM
- CiviCRM Code and Test Sprint - New York : Sep 18, 2010 9:00 AM Sep 19, 2010 5:30 PM
Over the first three days of the code sprint, we got through most of the tasks to be done. So, on the last day it was decided that some time could be allocated to something different, taking advantage of developpers from different continents being together. Three of us spent a few hours working on coding a way to deploy CiviCRM site with Aegir.
The past 8 days have been an amazing period for the CiviCRM community and core team members. Its been incredibly intense, extremely fulfilling and mind-blowing. A huge thank you and tip of the hat to the members of the community who participated in the event and came together from various parts of the world (asia, europe, north america) to push the project to greater heights, from a usability, documentation and localization viewpoint.
- Transifex allows teams of people to collaborate on translations – this is not an issue when you have a single person working on a translation, but as soon as you have two or more contributors working remotely, it’s crucial to use a tool that streamlines the process and allows for easy and centralised communication,
- the user hierarchy is simple, clean and seems to be efficient: project maintainers accept language maintainers who, in turn, accept language team members and coordinate given language’s development,
- project maintainers can announce localisation-oriented things on the project’s page,
- teams can have discussions on the per-language discussion boards,
- the user interface for translations is better and easier to work with, and has the (dubious for some languages, but useful for others) ability to fetch Google Translate suggestions on-the-fly,
- PO files can be locked for work in offline tools (like Poedit, Virtaal or others) and the locking is visible to other contributors.
Well, it's been done, we chose the translation platform: Transifex. We're fully aware that we did not actually choose a platform that fully supports the ideal situation, but such a platform does not exists. This is more the choice of a promising back-end which we hope we can eventually develop into the ideal situation.
The interesting part in the discussion was finding a balance between the technical and functional interests.