Re: [Libbt-devel] Coordinating development

[Alien <ali...@us...>]

Op donderdag 21 april 2005 03:39, schreef Emil Sit:
> On Wed, 20 April 2005 at 17:48 (-0700), Dakidd wrote:
> > No, Alien, you're not the "only one active"... I've just been effective=
ly
> > silent, quietly banging away at adding stuff to make the thing truly
>
> I don't have the time to contribute to libbt unfortunately.
> However, I am worried that there are currently many developers
> proceeding on essentially independent paths with very little
> coordination.

This is a little where you're wrong: kevin said he was only busy with 1.03=
=20
branch, and that noone else was busy with CVS. and at the time, he was righ=
t.=20

In the time i just got here, I've been the only one changing CVS. ( and i=20
don't touch the stable branch ).

and since I'm the one doing the heavy coding, I expect my say to carry=20
somewhat far.

> This could be improved probably in several ways ---
>
>   * Updating the libbt website on sf to indicate the current
>     status and future plans, perhaps adding a registration-required
>     wiki.

can't help you there

>   * Automatic e-mails after commits to CVS.

don't think it's necessary

>   * Hanging out on the IRC channel (#libbt on irc.freenode.net)

i'm already there ;-)

>   * Having someone actually be in charge: Kevin, could you clarify
>     what role you want to play in libbt?

yes, actually in charge, this is the major problem I have been having, i=20
cannot seem to contact kevin...

> In addition to these logistic items (which don't require any one to
> write any code), it might be nice if there were some sort of
> consensus on these items before people continue hacking:
>
>   * Release goals/plan
>   * API definition
>     - Model for integration with applications (separate process or
>       linked in library with appropriate I/O multiplexing)

more or less finished ( libbt/include/bt/bt.h ) + see also libbt/TODO

>   * Implementation decisions:
>     - code style
>     - portable string/binary library
>     - portable network I/O

can be usefull to agree upon.

The big problem is that there is no active maintainer, therefor I repectful=
ly=20
ask of kevin or Pandora that I be given maintainer priviledges. I will not=
=20
act without consulting the mailing list, but I can be there _every_ day to=
=20
"maintain" libbt.

I have a buddy who wanted to help me coding on libbt HEAD CVS, and he still=
=20
(more or less a month) waits for ext CVS access or for kevin to contact him=
=2E=20
I just hope he wants to help now...


As a side note, I have mostly rewrote the existing code (at least i copy pa=
ste=20
some stuff, and some stuff I leave; but there isn't a file that's been=20
changed; and some are now obsolete ).