At 11:41 on 03/01/2002 EST, Drew Northup <[EMAIL PROTECTED]> wrote:

> The _wonderful_ US of A has some messy laws when it comes to software. 

Could you be specific?  Thousands of other open-source projects seem to 
manage.

> Don't worry too much about the details of how I'll pull this off--that's
> my problem ;-).

So you propose to keep a private cvs tree and rsync it over?

>  For now I'm the only one doing _any_ cvs committing
> anyway.  That clears up some problems there.

Let me say that I don't think this is a good idea.  But do what you wish.

[snip] 

> > Getting more people able to commit, check out, and test is really
> > important to getting a project like this moving.
> 
> I agree about the checking out (and having it work.....).  But really
> for something like this we don't want too many people with CVS write
> permissions yet.  To solve this issue I'd like to try to set up
> different sub-projects on Savannah (maybe on Sunday...).

They don't necessarily have to have cvs write access.  What I really mean 
is that getting patches in FAST is one of the most important things i've 
observed in a number of projects i've been involved with.  

People tend to stop while they wait, and if they wait more than a day or 
too, they lose momentum.  It's certainly happened to me.

You can see it when you look at plex86's history- there are bursts of 
activity.  Whenever kevin slowed down, so did everyone else.

The bottom line is that there's a lot of pressure on the project lead to 
keep things moving.  More than might be apparent initially..  It's a hard 
job, and you have my sympathy.

> > The only thing which comes close is importance is documenting the design
> > goals, plans, and (perhaps most importantly) current design and
> > architecture.
> 
> So get started.  There is plenty of info in the source files to be
> extracted and organized.  So have fun.

I lack the interest or motivation to do so at this time.  But hopefully 
someone will.

I was also referring to past emails which were particularly good... if 
anyone knows of any, by all means send em in.  Better to have all the raw 
info in the cvs tree than to have get lost.. doesn't need to be polished, 
just available.

--Josh


> > Keeping up momentum is really important.  When people see things
> > happening, they feel more motivated to contribute.
> > 
> > --Josh
> > 
> > At 9:44 on 03/01/2002 EST, Drew Northup <[EMAIL PROTECTED]> wrote:
> > 
> > > I needed to fix the installation of CVS on my development machine (in
> > > between classes).  I think that it is ok now.  I also now think that I
> > > have the space I need to download the entire CVS and put up a copy at
> > > Savannah.  I will note that I'm not going to make Savannah the main site
> > > though (just a mirror) because of some crappy software patent laws here
> > > in the US.  This makes it easier to deal with problems should they
> > > arise.
> > >
> > > Jeroen Dekkers wrote:
> > > >
> > > > What is the status of plex86 at the moment? The savannah project is
> > > > created, but the CVS is empty. Is the CVS tree going to be imported
> > > > anytime sone? Is there anybody who is going to maintain the
> > > > repository? AFAICS nothing happened for the past months.
> > > >
> > > > Jeroen Dekkers
> > > > --
> > > > Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED]
> > > > Debian GNU supporter - http://www.debian.org http://www.gnu.org
> > > > IRC: jeroen@openprojects
> > >
> > > --
> > > |^^^ |  | |^^| |^^^  Drew Northup, N1XIM  |^^| |    |^^^ \  / /^^\ /^^~
> > > |__  |  | |  | |                          |__| |    |___  \/  |__| |__
> > >    | |  | |  | |           www.plex86.org |    |    |     /\  |  | |  \
> > > ___| |__| |__| |___ web.syr.edu/~suoc/    |    |___ |___ /  \ \__/ \__/
> > >
> 
> -- 
> |^^^ |  | |^^| |^^^  Drew Northup, N1XIM  |^^| |    |^^^ \  / /^^\ /^^~
> |__  |  | |  | |                          |__| |    |___  \/  |__| |__
>    | |  | |  | |           www.plex86.org |    |    |     /\  |  | |  \
> ___| |__| |__| |___ web.syr.edu/~suoc/    |    |___ |___ /  \ \__/ \__/
> 



Reply via email to