CiviCRM Community Forums (archive)

Hi all,

Reading the work about the TaxReceipt extension / add-on for CiviCRM today on the blog, I was surprised to see it being advertised as Drupal only. Considering that CiviCRM is now supposedly compatible across three platforms, and that we have a shiny new extensions interface, it seems right that extension development be done in a platform-agnostic way from now on. A simple solution from my side would be to only offer 'official' status through blog/forum etc to extensions made for the in-built platform, but that seems a bit draconian for a volunteer effort. Does anyone have good suggestions to move away from the status quo more quickly ?

Anthony

I think these are valid points, and there are multiple ways all of us should approach this:

1. Work with people and get them to do CMS agnostic modules as much as possible. However there are already quite a few existing drupal modules that will need to be ported (e.g. canadian tax receipts, yearly tax receipts etc)

2. Get more developers from joomla and wordpress involved (our biggest bottle-neck, IMO) and get them to help port some of the above existing modules to be CMS agnostic

3. Continue improving the project to use standard PHP frameworks (aka symfony etc) so its a lot easier to do a CMS agnostic module

Bottom line, i think all contributions are great and help improve the platform. They need to be acknowledged and respected. We should remove barriers and make things easier for folks to contribute back in their preferred mode

lobo