On 04/19/2012 05:38 PM, Russ Allbery wrote:
Bernd Zeimetz be...@bzed.de writes:
That would require that the tech-ctte's decisions do not take months or
years. They are fast if they really need to be, but in such general
cases the time a descision takes is imho way too long and frustrating
On 04/18/2012 09:29 PM, Tollef Fog Heen wrote:
]] Colin Watson
alioth is just a Debian-specific hosting site, not a general gateway to
package maintenance. We're not set up for them to be dispute resolution
for the whole of Debian, and they have no constitutional authority to do
that
Bernd Zeimetz be...@bzed.de writes:
That would require that the tech-ctte's decisions do not take months or
years. They are fast if they really need to be, but in such general
cases the time a descision takes is imho way too long and frustrating
for all involved people. I would prefer a
Hi,
I would like to throw out an idea for constructively combating low
activity in strongly maintained packages.
Across the Debian package ecosystem team maintainership has been seen
as the strongest antidote for package stagnation. This process just
works because as one team member becomes
On Wed, 2012-04-18 at 13:10 -0400, Michael Gilbert wrote:
So anyway, enough explanation, on to my proposed solution. Seeing as
team spirit has been a quite effective antidote to stagnation, lets go
ahead and use that again.
I agree with the general intention, but not with the details of the
On Wed, Apr 18, 2012 at 2:12 PM, Moray Allan wrote:
On Wed, 2012-04-18 at 13:10 -0400, Michael Gilbert wrote:
So anyway, enough explanation, on to my proposed solution. Seeing as
team spirit has been a quite effective antidote to stagnation, lets go
ahead and use that again.
I agree with
On Wed, Apr 18, 2012 at 01:10:42PM -0400, Michael Gilbert wrote:
So anyway, enough explanation, on to my proposed solution. Seeing as
team spirit has been a quite effective antidote to stagnation, lets go
ahead and use that again. Here is my suggested process:
Nowhere in this process seems
On Wed, Apr 18, 2012 at 2:51 PM, Colin Watson wrote:
Nowhere in this process seems to be the notion that you should
contribute actual effort first before adding yourself as an uploader. I
think that's important, particularly in the many situations where it's
not lack of packaging of a new
]] Colin Watson
alioth is just a Debian-specific hosting site, not a general gateway to
package maintenance. We're not set up for them to be dispute resolution
for the whole of Debian, and they have no constitutional authority to do
that anyway. De-emphasising the role of alioth
Michael Gilbert wrote:
Plus I don't have to find hosting for my work elsewhere,
which is kind of a pain and unwanted.
This at least is easy to address. Alioth automatically notices
per-user git repositories under ~/public_git[1]. Something similar
works for other version
10 matches
Mail list logo
