Breakout conversation: CiviCRM and the Drupal Community
notes started partway into the conversation
- How does a person contribute in bite-sized chunks to a code base that is monolithic?
- You can write Drupal modules for CiviCRM - that's the best way to extend CiviCRM and is a recent development with added hook support
- Drupal has Form API, CiviCRM has Quick Form - you have to be willing to make that leap and learn something new
- there's a big gap between the users and the developers
- there seems to be a Drupal/CiviCRM PR problem
- CiviCRM can either be broken down into smaller modules are not; just have to make a strong decision and stand behind it.
- Need to put projects out there that's well defined for people to work on. Give people more concrete ways to get involved. Give specific points of contact for the work.
- CiviCRM is changing. In recent years the concepts of components have appeared, making things more modular; the API and hooks are better developed
- The thoughts that are going on internal to CiviCRM developers that might please Drupal folks need to be publicized better
- Thoughts about having Minimal and Standard installations (maybe Custom too) similar to Drupal 7 installation
- Could have a packged up Drupal/CiviCRM installation to make things easier
- more training videos and materials
- aesthetic differences between Drupal and CiviCRM can also be challenging when going from the former to the latter
- Large CSS and templates cleanup is underway for CiviCRM
- idea to develop a guide to CiviCRM for Drupal developers to ease transition, point out parallels
- modularize WYSIWYG so that people can choose to either use CiviCRM-bundled WYSIWYG or Drupal WYSIWYG API module