dubuntu-team team mailing list archive

["Jay I." <jay.27182818@xxxxxxxxx>]

hi. i'll be busy till the next week and most probably will be
unavailable for this time. so here's my plan. i've created a basic
database layout and started development of a simple cli-based client
that will be working with the local database. on the next week i'll post
here the database layout and if everyone agrees we will create a
blueprint for it. and your charl should prepare our bzr repo. i think we
should start with a single cli app and when we all agree on the api
we'll separate it into a client and library. what about your php app (or
library, don't know what you mean saying 'architecture') i'd like to see
it. maybe it's worthwhile to push it into bzr as well?

ps. the link to your demo site seems to be broken.

regards,
jay

On Thu, 2009-07-02 at 20:58 +0200, Charl Wentzel wrote: 
> Hi Guys
> 
> Thanks Jay.  Please start with a database design, that will be great.
> You're welcome to use the Launchpad site to create a blueprint for the
> database design.  (https://launchpad.net/~dubuntu-team) That way we
> could all edit it.
> 
> As far as the webpage is concerned, that is something I could manage
> very quickly.  I'm already hosting a few demo sites.  This should work
> well while we are in the trail stages.  We could move it to a proper
> hosting service when we start getting traffic.
> 
> As far as the web page design, I could manage that very easily too.
> I've developed a php architecture specifically for ultra thin web client
> for database applications.  For something like this it would take me no
> more than a day to put it together.  It's not polished yet but I'm
> working on it now.  It would a great way to test and improve my
> architecture.  All I need is the database design. 
> 
> You can have a look at one such demo site here:
> http://recosys.no-ip.biz/sawaste 
> Username: admin or engineer
> Password: same as username
> The different users have different access rights, to feel free to try
> both.
> 
> However, I have no gui (gtk+ or qt) or python experience.  So this is
> where you guys could take the lead. How does that sound?
> 
> I would stick to the  Linux approach:
> step 1: command line tool that gets the job done.  The idea is that we
> would create a re-usable library with a clearly defined API.  The
> command line tool simply give a plain text front-end
> step 2: build a gtk+ front-end for the library that replaces the command
> line front-end (as an alternative)
> step 3: build the ncurses and qt front-ends.
> 
> If each of us take charge of some part of the project and the others
> test and comment then we should show much faster progress. Which brings
> me to the schedule.  This approach means we could do things in parallel,
> which would shorten the schedule significantly.
> 
> I think we need to create a separate page on the wiki site to manage the
> schedule.  We could add all the things that need addressing and propose
> dates, e.g. here's a few things we could add...
> 
> 1. Finalise blueprint
> 2. Database design - web page knowledge base
> 3. Web page - First draft
> 4. Logo design
> 5. Package manager blueprint - database choice, database structure,
> functional specification, choice of gui libraries, etc, etc...
> 6. Package manager alpha release
> 
> What do you think?
> 
> Charl