CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • Future roadmap thoughts
Pages: [1]

Author Topic: Future roadmap thoughts  (Read 781 times)

jsherk

  • I post occasionally
  • **
  • Posts: 82
  • Karma: 0
Future roadmap thoughts
April 21, 2010, 02:44:51 pm
As a long term roadmap goal, I have suggestion to think about...

I understand that the standalone version is being phased out in favor of the Drupal and Joomla integrated versions. As a long range possible goal of maintaining only one code base (instead of two separate versions), maybe all core features could start to be "pulled back" into a single standalone type version that does not require Drupal or Joomla, and then there would be separate modules that would add Drupal and Joomla functionality.

I am not saying you should maintain the current standalone version, but instead look at features that are duplicated (done differently) in Drupal and Joomla and start to pull them back into CiviCRM... for example, are users and roles handled differently in Drupal and Joomla? Then have CiviCRM take over that particular option fully, and then have a Drupal crossover module and a Joomla crossover module that will integrate the CMS with civi.

Just a thought.

Thanks

jsherk

  • I post occasionally
  • **
  • Posts: 82
  • Karma: 0
Re: Future roadmap thoughts
May 02, 2010, 05:59:12 am
OK,and now a counter-point to my own suggestions...

When I first found CiviCRM I tried (unsuccesfully) to install the standalone version and then found out standalone was being discontinued anyways, so I reluctantly installed Drupal, got it working and then installed Civi and got it working.

Its been about 2 weeks now that I have been using civi, and I think I better understand the concept of "don't reinvent the wheel" ... in Drupal it is VERY EASY to create modules that can then be used by civi, which makes adding functionality much easier than trying to hack the civi code! Civi is not a content management system and drupal is not a crm, but the using drupal as a base for things like permissions and custom modules is a time saver and means more time to develop new features instead of re-inventing what has already been done!

For those of you that were like me, saying "I don't want to install Drupal, and I just want a standalone version because that's what I want" I suggest you give Drupal and Civi chance!
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • Future roadmap thoughts

This forum was archived on 2017-11-26.