Look, I'm not trying to be rude here, but it isn't as easy as it seems to
just up and move  CVS reposity from one place to another sometimes (and NO
the people over at savannah can't do it for me..... they don't OWN
fastxs.net!!).  As soon as I get the CVS copied, this is what I'd like to
do:

1) Set up a distribution's tree--only stuff that we know WORKS gets to be
there.  I plan on being tough about this after what happened this past
August.  This will be the starting point for each next patch set (in
between distribution tree updates)

2) Set up a patches tree, by distribution release version.  This means
that code changes and patches get to be haggled over and tested separate
from the CVS tree until we can be damn sure that the patches are ready for
the big time.

Patches will be voted upon, and will only be included once an agreed upon
amount of testing has been done (on both CVS updates, and clean installs
to avoid past problems).  The details of this are up for argument as of
now.  I want to hear some good arguing on this one.  No holds barred--no
flaming permitted.  Standard ground rules apply otherwise.  I think that
y'all get the point.

I want to get this project moving as much as the next guy.  Don't get me
wrong here, but we need to stop for a second and take a good look at
ourselves and our objectives.  That is what the beginging of a new year is
for.  We need to get this thing organized more than it was before.  People
are starting to take us seriously--and to cope we re going to have to
manage this project in a serious manner.  I got permission to bear the
flag because I was the only on from the original crew of about 30 some
people whom was still answering user questions on the mailing list after
the big job thing this past summer.  I want to get this thing off the
ground in such a way that it stays off te ground--and for the moment that
means a little micro-management.  Eric has my endorsement to post patches
on Savannah for the time being, and for my part I hope to get the last
working CVS there for download.  I'm also going to sort through Colin's
CVS-dump tarballs and possibly post a couple of them before I disconnect
on Friday for a much deserved and anticipated Spring Break trip out into
the wilds of West Virginia with our local outing club.  I'll be back (I'm
not planning on doing anything dumb) online on about the 18th after break
and will be back to work ASAP after that.

So, that's the news from Lake Woebegone.......

On Fri, 1 Mar 2002, Bryce Denney wrote:

> On Fri, 1 Mar 2002, Drew Northup wrote:
> > The _wonderful_ US of A has some messy laws when it comes to software. 
> > Don't worry too much about the details of how I'll pull this off--that's
> > my problem ;-).  For now I'm the only one doing _any_ cvs committing
> > anyway.  That clears up some problems there.  And yes, I do know who to
> > talk to about setting up a new non-US hosted site--so that is already
> > being worked on.
> 
> 
> Especially for a project which is done in one's spare time, I strongly
> recommend giving cvs write access to a number of interested and competent
> people.  Then progress can continue even when the primary developer(s) are
> unable to find the time.
> 
> It's got to be a balance between two extremes
>   (a) one person controls the cvs and publishes a readonly copy, and
>   (b) so many people are contributing without adequate communication that
>      code quality goes down.
> 
> IMHO, plex86 has tended toward one extreme, and that's why the project
> came to such an abrupt stop when Kevin was not able to continue on it.
> 
> Regards,
> Bryce
> 
> 

|^^^ |  | |^^| |^^^  Drew Northup, N1XIM  |^^| |    |^^^ \  / /^^\ /^^~
|__  |  | |  | |                          |__| |    |___  \/  |__| |__
   | |  | |  | |           www.plex86.org |    |    |     /\  |  | |  \
___| |__| |__| |___ web.syr.edu/~suoc/    |    |___ |___ /  \ __/ __/



Reply via email to