Re: How to set up the libwww contributors

A core team sounds like a good idea. 
For it to work, we need a group of people
who are intimately familiar with libwww's
source code. 

I've only used libwww as part of building
Amaya. Unfortunately, I haven't even looked
at the source code. :-(

However, what I will do is to use libwww
to make a very very very simple browser --
so that I can become familiar with libwww's
usage. 

I can also help out by building libwww/Amaya
for Linux to test patched versions of libwww. 

But it will be a long time before I have the
expertise to evaluate source code patches by
examining the source. 

I hope that there are other people who are 
familiar with the source who can be a part of
the core team also. 

--- jose.kahan@w3.org wrote:
> Hello,
> 
> In our previous episode, Fox One said:
> 
> > Perhaps the W3C can create an alternate/
> > experimental CVS directory that allows
> > users to update it with their changes. 
> 
> I think that we need a core team responsible for
> handling the patches.
> If a patch is troublesome, the core team can discuss
> it between themselves.
> And this core team should be the only ones that have
> write access to
> the CVS base. Otherwise, we may have a big lose of
> time.
> 
> What do we need for applying patches?
> 
> What I do myself is that I try to generalize the
> patches I do to Amaya before
> moving them to the current libwww CVS branch. 
> 
> I also try to test them as far as possible, with
> amaya and seeing if some
> of the other libwww applications still work
> correctly. These are targeted
> tests.
> 
> But, I do have to say, libwww is _big_ and sometimes
> one fix can break
> something else. So, when I feel ok with my patch, I
> commit it, mail
> a message to the list,  and keep an eye open for
> eventual bug reports from 
> the list.
> 
> I'd really like to have some kind of core team here.
> I'm currently slowly
> applying patches, but I'll have to stop soon to do
> other things and who
> can continue doing this? I know some essential
> things about libwww and
> other people know other things. We can all gain time
> and continue making
> libwww live with a core team. Without it.. the
> perspectives aren't too
> bright.
> 
> To be honest, my main interest in libwww is that I
> use it in Amaya.
> So, I have the obligation of fixing bugs that we
> find. If we can't find
> a core team, should we stop libwww? I could continue
> just fixing the
> bugs I find in Amaya and that would be about it. 
> 
> As I said in other postings, libwww belongs to its
> user community, so it's
> up to us to keep it alive and make it go ahead.
> 
> What do you think? :)
> 
> Cheers,
> 
> -Jose


__________________________________________________
Do You Yahoo!?
Send instant messages with Yahoo! Messenger.
http://im.yahoo.com/

Received on Monday, 19 June 2000 11:03:39 UTC