I echo greggles' concerns and recommendations around forking. It does seem that the UI goals of the Drupal crew are the same as the Gnomepal goals.
I also see some challenge in keeping things coordinated with the current Drupal efforts. Not only did Drupal 6 add lots of improved admin and web 2.0 fudge topping, but Drupal 7 is bringing even more. Same for installation process.
greggles mentioned the Drupal project* module which is now nearly overshadowed by Actions, Workflow ng, and the latest CCK and Views. These are super-powerful modules that can produce web apps fast and functional. Meaning, I can build a better project management system using those modules faster than we can code up improvements to the project* module.
Which leads me to think that another angle to accomplishing Gnomepal goals is figuring out how to package how-to's, recipes, admin education, and exportable & importable packs containing CCK/Views/Actions/Workflow records sets. This would make for "loadable apps" for Drupal.
Because of these kinds of factors, I'm wondering if perhaps a good 30%-50% of the Gnomepal energy and efforts should be committed to tracking, coordinating and supporting the current Drupal module dev teams (specifically, the installer and key modules). And maybe more to producing educational & how-to materials?
I echo greggles' concerns and recommendations around forking. It does seem that the UI goals of the Drupal crew are the same as the Gnomepal goals.
I also see some challenge in keeping things coordinated with the current Drupal efforts. Not only did Drupal 6 add lots of improved admin and web 2.0 fudge topping, but Drupal 7 is bringing even more. Same for installation process.
greggles mentioned the Drupal project* module which is now nearly overshadowed by Actions, Workflow ng, and the latest CCK and Views. These are super-powerful modules that can produce web apps fast and functional. Meaning, I can build a better project management system using those modules faster than we can code up improvements to the project* module.
Which leads me to think that another angle to accomplishing Gnomepal goals is figuring out how to package how-to's, recipes, admin education, and exportable & importable packs containing CCK/Views/Actions/Workflow records sets. This would make for "loadable apps" for Drupal.
Because of these kinds of factors, I'm wondering if perhaps a good 30%-50% of the Gnomepal energy and efforts should be committed to tracking, coordinating and supporting the current Drupal module dev teams (specifically, the installer and key modules). And maybe more to producing educational & how-to materials?
Whatcha think?