Project RoadMap

ewanpmclean's picture

This is the project's overall roadmap, as started by Ewan on 02/03/2008.

Copied from assembla:

"Roadmap

As this is an open source project, we should probably let go of some of the more mundane project principles :-), so:

1. No one should let the absence of a Roadmap right now hinder them in any way from starting to build or develop stuff they would really like to build or develop. Just don't hack drupal core, is all I'm saying.
2. No one should let the presence of a Roadmap hinder them in any way from building or developing stuff they would really like to build or develop. Just don't hack drupal core, is all I'm saying.

In making the roadmap we should consider

* Which features are most important to us
* Which features are most attainable (link to gap)
* Which features need to be worked on by core team, in what order
* Which features need to be coordinated by core team, worked on by others, in what order
* Which features can be published as 'needed, who will work on it?' (Now I'm making it up as I go along)
* What kind of quality control we like to implement through development and testing principles (e.g. no core hacking, use cck+views when possible, helping others build modules is always better than building them)
* Which features are new to Drupal 6. Depending on how far in the future our own switch to v6 is planned, these features should probably not be built separately for Gnomepal. If we do incorporate such a feature, we should see if a module was incorporated into core and use that module to ensure a manageable upgrade path for us and for our users

The Roadmap should very concretely describe

* A first build
* What functionalities
* What modules
* What configuration
* What manuals
* (also: what specifically not to invest core team time in for the first build)

(My instinct is to take make this first one distinctly manageable and attainable)
The Roadmap should very vaguely describe

Second, Third, Fourth builds. A moment for switching to another version of Drupal."

Mission Statement: "To empower community administrators to provide a ready-to-go toolset to its users, to allow them to communicate and interact with the community."

Project Description:

Building on a Drupal base, the project will use existing open source modules combined with customised open source code to create a less 'barebones' Drupal package that can be distributed as an integrated community experience.

Short-term Objectives:

-Develop this roadmap
-Solidify developer base
-Complete developer 'registration/profiles'
-Clean up modules and strip back to more basic setup to avoid unnecessary complications

Long-term objectives:

-Complete Gnomepal
-?

Timeline:

Base of GnomePal (V1.0 release): Approx 3 months from completion of roadmap

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Josh's picture

One of the things that struck me most about this idea is that it would account for different use cases, meaning feature sets. Right now I see a laundry list of great features, that n doubt could create a great out of the box tool set for community builders. But it seems to me that if want this to be a quality tool, created sometime in the next decade, we might want to define several feature scopes.
I envision the same several great themes available for all. And perhaps, all the modules could be included in the Big Tar. But I think it might be wise to limit which are turned on and mashed up for several "types of sites."
Bloat, and unrealistic expectations might follow a toolbox we create thats aimed for a Flickr, Myspace, Facebook, LinkedIn, Drupal.org, Bebo, Purevolue, Threadless, Pounce, with portable widgets!

Post new comment

The content of this field is kept private and will not be shown publicly.