[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#750135: Status of #750135 (Maintainer of aptitude package)

(Dropping a bunch of addresses, I believe that those that I removed
are subscribed to the bug report, the mailing list, MIA or not


2015-03-27 21:29 GMT+00:00 Don Armstrong <don@debian.org>:
> On Fri, 27 Mar 2015, Javier Barroso wrote:
>> Sincerely I would expect this bug to be solved in less than a year. It
>> has to been frustrating to be at Manuel circunstances. I know CTTE has
>> been very very very busy , I'm understand this is not the biggest
>> issue, but 8 month of not activities on git should be sufficient to
>> give the power to Manuel and tell to Daniel to have a collaborative
>> aptitude
> The CTTE certainly has not been very active on this issue. That's
> definitely our problem, but as near as I can tell, none of the parties
> have been very active either.

I didn't want to insist on this in the mailing list or IRC meetings
because of all of the discussions about systemd and so on -- they were
more important, and all what happened kept the committee very busy for
months.  And after that because of the burnt-out of people and other
urgent questions for the freeze.

In the meantime, I was doing other more interesting and rewarding
things in Debian anyway... if nobody cared about aptitude enough to
keep an active development, so be it.

Overall I was not very active in aptitude after that, yes, I sent only
a few e-mails since then (in Oct/Nov) to the mailing list to reply to
some security questions of some user, possibly affecting apt (or
similar reports at the time in apt's mailing list); and others
discussing a bit with the apt team (David) about API/ABI breakages
that would affect aptitude.

If with not being active you mean that I have not been active at all
in the development of aptitude, other people already explained that it
was because I was effectively expelled from the development group (==
no commit rights).  The only thing that I can do is to send e-mails to
the mailing lists or bug reports, but why to reply to bugs if I cannot
fix anything in the repository, my contributions are blocked, and
otherwise there is nobody integrating the patches proposed by other
people for months or years?

I could have created a fork, or could have uploaded a new revision
package setting the repository to collab-maint, but I thought that
doing those kind of things would only create more confusion for
aptitude/Debian users and would not have helped the situation in

> Currently unresolved questions from me are the following:
> 1) Is there still a conflict here? What precisely is it?
> 2) What would a resolution of this conflict look like to the parties?

The reply to both questions above is in my original request, specially
in the 4 paragraphs towards the end, between "Over the history of the
projects [...]" and "[...] to start with".

I think that all what I explained in the original request to the
committee applies now, because nothing changed, the last year only
added up in the same pattern.  I was expelled more than 1 year ago,
and sent the request to the committee 10 months ago, but the
development ceased again since then, mirroring what had happened in
previous years/cycles.

A quick glance to the development log [1] in 2013-2015 should explain
quite clearly the status of the project. (The commits in early January
authored by other people were added by me, picking from patches in BTS
or development branches -- it does not mean that those people were
active at that time).

[1] http://anonscm.debian.org/cgit/aptitude/aptitude.git/log/

The request to the CTTE was sent after consulting in private with
several people who know better about the procedures than I do, so I
think that it will be useful to come to a clear decision, and would
also be useful for similar cases that could arise around central tools
of the project in the future.

Manuel A. Fernandez Montecelo <manuel.montezelo@gmail.com>

Reply to: