Since a few weeks ago project pages can contain a new
section to list open positions within the project that require fresh
blood (thanks to neysx for implementing this). Historically those were
only listed centrally
http://www.gentoo.org/proj/en/devrel/staffing-needs/index.xml, which
had a number
On Wednesday, 02. April 2008 22:46:16 Petteri Räty wrote:
> How does having the average time between commits be at most a week
> sound and if it goes under that, undertakers will get a notification?
It sounds like you're trying to get rid of someone.
--
Best regards, Wulf
signature.asc
Descrip
Mike Frysinger kirjoitti:
This is your monthly friendly reminder ! Same bat time (typically
the 2nd Thursday at 2000 UTC / 1600 EST), same bat channel
(#gentoo-council @ irc.freenode.net) !
If you have something you'd wish for us to chat about, maybe even
vote on, let us know ! Simply reply to
Wulf C. Krueger wrote:
On Wednesday, 02. April 2008 22:46:16 Petteri Räty wrote:
> How does having the average time between commits be at most a week
> sound and if it goes under that, undertakers will get a notification?
It sounds like you're trying to get rid of someone.
-
Petteri Räty wrote:
Defining required amount of activity for ebuild devs. I would like us to
raise the required amount of activity for ebuild devs.
Given that the low number of developers is ranked as our number one
problem in Donnie's informal survey[1], taking any kind of action
against inf
Mike Auty kirjoitti:
Petteri Räty wrote:
Defining required amount of activity for ebuild devs. I would like us
to raise the required amount of activity for ebuild devs.
Given that the low number of developers is ranked as our number one
problem in Donnie's informal survey[1], taking any kind
Petteri Räty wrote:
If you can't manage weekly commits, you can't respond to security issues
either. This means that you should have devaway on.
That assumption is false. If there was a need to do weekly commits and
the dev in question couldn't manage it, it would be wise to expect that
he ca
Petteri Räty wrote:
If you can't manage weekly commits, you can't respond to security issues
either.
I can see your point, I was more thinking about developers who have
maybe one or two small packages that don't have many version bumps or
bugs. They may be entirely able to respond to securit
Wulf C. Krueger kirjoitti:
On Wednesday, 02. April 2008 22:46:16 Petteri Räty wrote:
How does having the average time between commits be at most a week
sound and if it goes under that, undertakers will get a notification?
It sounds like you're trying to get rid of someone.
I don't have numb
On Wed, Apr 2, 2008 at 10:26 PM, Petteri Räty <[EMAIL PROTECTED]> wrote:
> If you can't manage weekly commits, you can't respond to security issues
> either. This means that you should have devaway on.
So if you don't maintain enough packages to commit on average once a
week, you're not worth hav
Mike Auty kirjoitti:
Petteri Räty wrote:
If you can't manage weekly commits, you can't respond to security
issues either.
I can see your point, I was more thinking about developers who have
maybe one or two small packages that don't have many version bumps or
bugs. They may be entirely able
It will be removed at the end of the month.
03 Apr 2008; Mark Loeser <[EMAIL PROTECTED]> package.mask:
mask dev-libs/swl due to dead upstream and not working properly; bug
#206163
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web
On Wed, 2008-04-02 at 22:19 +0100, Mike Auty wrote:
> Petteri Räty wrote:
> > Defining required amount of activity for ebuild devs. I would like us to
> > raise the required amount of activity for ebuild devs.
>
> Given that the low number of developers is ranked as our number one
> problem in
Jan Kundrát wrote:
Petteri Räty wrote:
If you can't manage weekly commits, you can't respond to security
issues either. This means that you should have devaway on.
That assumption is false. If there was a need to do weekly commits and
the dev in question couldn't manage it, it would be wise t
Petteri Räty wrote:
Mike Auty kirjoitti:
Petteri Räty wrote:
Defining required amount of activity for ebuild devs. I would like us
to raise the required amount of activity for ebuild devs.
Given that the low number of developers is ranked as our number one
problem in Donnie's informal survey
Hi,
"Jorge Manuel B. S. Vicetto" <[EMAIL PROTECTED]>:
> As others have commented, I don't agree with this point. Also, you're
> forgetting we have quite a few people working on this project and
> that we have many different roles.
And just remember Diego's post, where he by accident accused a
d
On 02-04-2008 21:21:25 -0400, Richard Freeman wrote:
> Would it make more sense to just make a policy that failure to maintain
> packages that you're maintainer on will result in getting removed as the
> maintainer, with said packages going up for grabs? Devs who keep claiming
> packages only t
17 matches
Mail list logo
