[Ltrace-devel] ltrace still being maintained?

[Zach Welch]

On 10/05/2010 11:07 PM, Juan Céspedes wrote:
> On Tue, Oct 5, 2010 at 7:16 PM, Zach Welch <zwelch at codesourcery.com> wrote:
> 
>> I think it is safe to say that Juan has dropped the ball.
>>
> 
> I am sorry to hear that, but I understand that that's what it seems :(

My statement derived from the lack of your participating in discussion
or patch management for close to a year. I am glad this discussion
caused you to resurface and start to pick up the ball again.

>> To this end, is there a public git tree that contains all of the changes
>> that should go into the next release?
> 
> 
> Ltrace main git tree is at ssh://git.debian.org/git/collab-maint/ltrace.git
> 
> Right now, there are 5 develeopers who can edit it, but I will be more than
> happy to add you two, or whoever could have more time than me to work with
> ltrace.

Is there a list of these folks? It'd be nice to know who could be called
upon in a pinch, but Joe seems like a good bet as the maintainer du jour.

> git.debian.org is accessed using an account in "alioth.debian.org"; you can
> create one online if you don't have one yet, and then tell me your user name
> to add you as a member.

I just registered as zwelch-guest, though I do not have a strong desire
to commit changes myself. That said, I think it's important to have
several active maintainers who can keep up with inflowing patches, and
I'm willing to keep an eye on things (to a very limited extent).

> However, if you don't mind, I would like to stay being the "admin" of the
> project.

I have no objections, so long as this does not pose a barrier to getting
a new release out the door with the changes that have accumulated over
the past year. If other maintainers update and tag the tree, it sounds
like that won't be a problem.

> I wish I had more time to work with this... and I still hope this will
> change soon (that is why I didn't reply before; I wanted to have time to
> apply some patches...)

I think it's important to at least keep the community updated;
otherwise, folks like me will start making assumptions about your
ongoing involvement. ;) Sorry if my presumption upset you.

-- 
Zach Welch
CodeSourcery
zwelch at codesourcery.com
(650) 331-3385 x743