Version 4, last updated by jcbozonier at Jul 24 07:56 2008 UTC

Decrease font size Decrease font size

Increase font size Increase font size

Print this page Print this page

InitialPlanOfAction


  1. Firmly establish a concept.
    1. We need to have a good enough idea of what we're building that we can incite interest and enthusiasm. We need a user scenario that will show people how this project will solve a need of theirs.
    2. UI mock ups. They shouldn't be anything more than wireframes so that no one thinks we're too far done, also we don't want to waste time overdesigning. We just need to make sure we're all roughly on the same page.
      1. I have started creating the UI mock ups. They will help me get a good idea of the required featureset. [jcbozonier]
  2. Identify the technologies involved.
    1. Once we have our concept in place we can start to break it down and begin imagining how we will implement the system.
    2. All technology decisions will be driven by a core set of values that we need to agree upon. My core values (which we can add or subtract from as we feel is necessary) is to look for technology that: enables short feature oriented cycles; doesn't get in the way of maintainability; makes simple things easy and complex things possible (i.e. flexibility).
  3. Identify solutions to enable the technology.
    1. Since this is an open source project we will not use any commercial software.
    2. Google like mad.
    3. If an appropriate solution for a given technology can not be found we will mark it as one we must create ourselves.
This is a lot of research but I don't plan for this to take much time (perhaps a month). I think one of the benefits to doing a project like this is the ability to get things done. Honestly, step 3 is probably where we could begin to go off and do our own thing.