[cad-linux] Re: Proposed task list for linuxCad group

Comments below.

On Sun, 2003-01-19 at 14:23, alvin@xxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:
> hi ya kim
> 
> i think the "task list" is always ongoing...

True.  It is dynamic.  It will change as we go.

> - though you're right that one does need to assign homework
>   to some so that we can get the ball rolling

We have to work as a team. 

> - as people see that contributers are doign work regularly,
>   that others will pick up things that are falling  behind...

Yep.  And so that people aren't repeating work and so that all the bases
get covered. 

> - am curious...
>       - why can't we use  "http://cad.freelists.org"; for starters
>       and worry about domain names later

Sure.  I didn't mean to imply that we couldn't.

>       - everybody can use their own domain names fo their choice
>       as a mirror  ( should not be an issue ? )

Not initially. 

> - since not everybody is in the ml... i assume there is a
>   searchable mailserver archive with all the past emails 
>       - if its NOT searchable... readig thru xxx,000 of emails is
>       sorta counterproductive

I don't know a thing about what you are discussing.  I can't comment. 

> - getting google/yahoo hits is important too for "keywork searches"
>       - i went poking around for varkon sources and struck out

I agree. Actually, if we want publicity, all we have to do is compose an
article for desktoplinux and slashdot and we'll get lots of it. 
However, I think we should get some things more or less figured out
before we get barraged. Maybe not though ?  I'd like to see what sort of
commitment people in this group are willing to give.  Too many cooks
spoil the stew.  If we can get a few of the organizational decisions
ironed out before "going public", that would be great.  

> c ya
> alvin
> 
> 
> On 19 Jan 2003, Kim Lux wrote:
> 
> > 
> > Hi people.  
> > 
> > I'd like to propose some structure/organization on what we are about to
> > attempt.  I don't mean to be forward and I'm not calling myself the
> > leader of the group or anything, I'd just like to put some things into
> > motion.
> > 
> > Here is how I think we should proceed:
> > 
> > 1) Develop a list of who is and isn't going to be involved with the
> > project and what everyone thinks they can contribute.  This will tell us
> > what sort of resources we have available, right now anyway.  
> > 
> > 2) Develop a list of all the currently available Linux CAD packages. 
> > Assign them to people to review and report back to the group.  To make
> > decisions on how to proceed, we need to know the basics of what is
> > available: code layout, code stability, base format, what it does, etc. 
> > Maybe we need to work in teams to do this so that each part gets
> > covered. 
> > 
> > 3) Develop a statement of product functionality in various stages.  Ie
> > stage 1: basic 2D CAD app.  Stage 2: add these functions... Stage 3:
> > integrate with this... etc. That sort of thing.
> > 
> > 4) Come up with a product name, if needed / applicable.     
> > 
> > 5) Put infrastructure in place to support a project being worked on by
> > our team.  We need a revision control system, a website, a bugsite,
> > etc.  
> > 
> > 6) Somewhere along the line, announce that the linux cad group exists. 
> > Tell them what our mandate is and that we are looking for people to
> > contribute. 
> > 
> > 7) Delegate the various tasks to people and get people working on them:
> > coding, testing, documentation, marketing, etc. etc. etc. Here is where
> > we start working on the actual product !  
> > 
> > 7a) code, develop, design, document, etc.  Move the product forward one
> > step.
> > 
> > 8) beta rollout of stage1. ADVERTISING.  If this project is going to
> > grow and flourish, it needs to become THE Linux CAD system, period.  If
> > it is clearly the market leader, then it will get the developer
> > resources to continue to grow. If it is another unknown basement
> > project, it will die like all the rest. 
> > 
> > Your thoughts and feedback are welcome. 
> > 
> > Kim Lux  
> > 
> > 
> > 
-- 
Kim Lux <lux@xxxxxxxxxxxxxxxxxxx>

Other related posts: