Goals for CiviCamp
Please add a few things we can accomplish as a group at CiviCamp. All attendees are expected to be fairly savvy with CiviCRM (from a user/admin perspective) and have a good idea of the CiviCRM schema. Understanding CiviCRM internals would be nice but not essential.
I'd also like to avoid getting into discussions about why CiviCRM does not do things the Drupal way etc . Here are a few things on my mind. I've taken the liberty to add a few controversial topics
Drupal Modules to integrate with
- Organic Groups Sync
- Fix bugs in og_civicrm_synch for trunk and get 2-way synch working
- Make the linkage between an OG and CiviCRM group conditional when the synch module is enabled
- Consider enhancing the CiviCRM buildForm hook so that it can also inject fields into standard form templates (use injecting OG synch prompts into Group Settings form as a test-case for this)
- Consider Rob Thoren's model for runtime synch - CiviCRM maintains group membership and passes that info to OG.
- CCK? (take a look at CiviNode?)
- CiviMember_Roles (http://drupal.org/project/civimember_roles). Pull this into CiviCRM core
- Quickform module (by David Strauss) and/or general better integration with Drupal Theming layer ?
- Goals and future of API
- How can we get developer community to help lead/participate in development/documentation/testing of this
- How should we structure things going forward so we are not duplicating a lot of code (and hence neglecting the ones the core team does not use)
Get YOUR Issue(s) Coded for 2.2
Some (all?) of you have client-requested enhancements / fixes "in the queue". We can do code sprints on these issues to make sure they get included in the next release (2.2). Examples include:
- No obvious way for the user to edit a profile at /user
- Usability Improvement: organizing dropdown select boxes that list fields
- Visibility control for event participant statuses
- allow admins to specify maxlength for text fields (built-in and custom fields)
- Drupal Calendar <-> CiviEvent and/or CiviCRM Activities integration
CiviCRM Unit Testing
- How do we get the community to help build unit tests.
- How do we "force" the core team to be more "religious" with regard to this
3rd party components being used
- Should we migrate to jQuery, if so why?
- Should 3.0 switch to using the Zend Framework
Performance of large sites and DB schema changes
- Any major schema changes needed to improve performance?
- Things we can / should do to make CiviCRM more extensible