1. Do not fork Drupal (agreed)
2. Forgo Glory. Instead make Drupal better. Where you can, involve and empower the existing Drupal Development Community.
3. Sure, creating an easier technical install (the ftp-way) is important, but also create a wordpress.org / .com ecology. The easiest install is a one click install. (I volunteer, just say the word).
4. One of the greatest barriers for a nice Drupal site is not the availability of modules or even installing them. It is the integration of different modules though css/dhtml/javascript/ajaxy wizardy (which completely eludes me too). We need to create great looking cool themes - NOT for a standard empty drupal install - but for completely configured and installed applied community concepts. A nice font, some colors and a sexy image header will NOT do.
5. Understand that any code you create needs to be maintained. New modules should be kept to a minimum, kept as granular as possible (to enable yet newer, as yet unenvisioned possibilities) and pushed into their own maintenance projects.
6. Google is also a big fan of Drupal. Can we do something with Google’s summer of code
7. Find other sponsors, big and small.
8. On the project site it is currently stated that ‘The hope is to integrate OpenSocial, OAuth, and OpenID.’ It is my opinion that these things are absolutely essential for a futureproof Community project. It could finally lead to being completely in charge of your own community profile through our project / Drupal. Let’s be ambitious here.
Reply to Message
Posted today about the project (slow news day)
http://hansacross.wordpress.com/2008/03/28/large-scale-community-cms-project-started-caveats-explored/
Main points:
1. Do not fork Drupal (agreed)
2. Forgo Glory. Instead make Drupal better. Where you can, involve and empower the existing Drupal Development Community.
3. Sure, creating an easier technical install (the ftp-way) is important, but also create a wordpress.org / .com ecology. The easiest install is a one click install. (I volunteer, just say the word).
4. One of the greatest barriers for a nice Drupal site is not the availability of modules or even installing them. It is the integration of different modules though css/dhtml/javascript/ajaxy wizardy (which completely eludes me too). We need to create great looking cool themes - NOT for a standard empty drupal install - but for completely configured and installed applied community concepts. A nice font, some colors and a sexy image header will NOT do.
5. Understand that any code you create needs to be maintained. New modules should be kept to a minimum, kept as granular as possible (to enable yet newer, as yet unenvisioned possibilities) and pushed into their own maintenance projects.
6. Google is also a big fan of Drupal. Can we do something with Google’s summer of code
7. Find other sponsors, big and small.
8. On the project site it is currently stated that ‘The hope is to integrate OpenSocial, OAuth, and OpenID.’ It is my opinion that these things are absolutely essential for a futureproof Community project. It could finally lead to being completely in charge of your own community profile through our project / Drupal. Let’s be ambitious here.