Licensing/Structure

Jesse Tie Ten Quee highos at highos.com
Tue Sep 5 12:58:52 PDT 2000


Yo,

On Tue, Sep 05, 2000 at 03:38:16PM -0500, David D.W. Downey wrote:
> > CVS? Who gets write access? Why? How are bug
> > reports submitted? Who is responsible for them?
> > Who wants to do more than just test the system,
> > and develop the profiler, our main frontend,
> > backend? How can we divide work between us, while
> > still maintaining some sense of order? Who wants
> > to do the website? After we get something
> > built/working, should anyone from our group
> > publicize our efforts? I mean what if some
> > reporter wants to talk to someone? Who can write
> > the documentation for alfs? What other questions
> > should we be asking?
> > 
> 
> At this point I suggest that we use Sourceforge since they already have
> all of these things covered quite well. Take a look at the KiXO Linux
> project and you'll see al the things that are available.

Hrm... no i would have to say, SourceForget has alot to offer, but something i don't think that would benifit LFS anymore.

LFS allready has it's own server with plenty of bandwith and resourses adding a CVS server isn't all that much work, imho

> They have quite a nice setup!

Agreed they do.

-
Jesse Tie Ten Quee - highos at highos dot com





More information about the alfs-discuss mailing list