public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Help offered - Portage tree
Date: Fri, 14 Mar 2008 01:10:23 +0200	[thread overview]
Message-ID: <47D9B45F.5090600@gentoo.org> (raw)
In-Reply-To: <1205445795.30618.1242298155@webmail.messagingengine.com>

[-- Attachment #1: Type: text/plain, Size: 3277 bytes --]

davecode@nospammail.net kirjoitti:
> Well I'm a newcomer to Gentoo and never heard of Sabayon (great project
> btw).  Knowing no one here or there, nor any history:

Never heard of and you say it's a great project?

> 
> This conversation reminds me of Human Resources.  They always have
> 'procedures' and 'career tracks.'  Gentoo's chitchat about earning gold
> stars and brownie points is giving me HR sickness.  You're asking
> Michael Jordan to prove himself on the high school team.
 >

You don't know Sabayon and can evaluate the skills of lxnay?

> 
> I've read Gentoo's new dev announcements about monkeys and paper
> weights.  People with a couple of small open-source projects.  The
> monkeys and paper weights get CVS rights.  Then the chief architect of
> Sabayon is scotched over bugzilla output?  Please.  That smells like bad
> fish.

The new dev announcements are traditionally written in a funky way.

> 
> Bugzillas are mostly good for non-devs to report bugs.  I know zero
> developers who first think to themselves, "ok, I need a project
> bugzilla...then I can begin writing code."  That isn't how development
> works.
 >

But I don't know any major project not having a bug reporting tool.

> 
> "So you don't have time to file bugs but you would have time to fix
> them" is rhetoric.  The issue is ROI.  Why file bugzillas that some
> "dev" authority figure may or may not fix in two years, when you can fix
> the code yourself?
 >

The perception of things rottening in bugzilla hasn't been proven. Here 
are the response times to bug filed by lxnay in 2007 and 2008:

https://bugs.gentoo.org/show_bug.cgi?id=160333
  * first response in two days (and marked as WONTFIX but later reopened)
  * interactions could be better on either sides

https://bugs.gentoo.org/show_bug.cgi?id=188024
  * Fixed in two days

https://bugs.gentoo.org/show_bug.cgi?id=192786
  * Fixed in 7 hours after patch submission

https://bugs.gentoo.org/show_bug.cgi?id=193337
  * Your "expert" is missing basic ebuild knowledge --> WORKSFORME
  * 9 minutes

https://bugs.gentoo.org/show_bug.cgi?id=199886
  * little under two months (yes this is too long)

https://bugs.gentoo.org/show_bug.cgi?id=211324
  * Been open a couple of weeks waiting for other changes (borderline)

We do have lots of stuff that rot in bugzilla in many cases they are 
requests for new ebuilds and not problems with existing ebuilds.

> 
> If you want to call him a Gentoo developer, then do so ASAP, and give
> him CVS.  He knows what he is doing and filing bugzillas is a waste of
> talent.  If you let him fix his own bugzillas he might go for that.
> 

There is nothing stopping him from taking the quizzes as any other new 
dev. If he is as good say you he is, answering the quizzes won't take long.

> 
> You need to attract people like this and if bugzilla isn't working,
> think up something new.
> 

Bugzilla isn't the only way new people come in.

 >
> If you dislike his CVS mods you can always revert, take votes, etc.  But
> I say +1 let him have at it.
> 

Very useful after it has already been synced to tons of machines and 
users are hitting our IRC channels with torches.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  parent reply	other threads:[~2008-03-13 23:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 22:03 [gentoo-dev] Re: Help offered - Portage tree davecode
2008-03-13 22:10 ` Diego 'Flameeyes' Pettenò
2008-03-13 22:33 ` Anant Narayanan
2008-03-13 23:10 ` Petteri Räty [this message]
2008-03-13 23:29 ` Pierre-Yves Rofes
2008-03-13 22:43   ` Fabio Erculiani
2008-03-20  4:06   ` davecode
2008-03-14 16:30 ` Christian Faulhammer
2008-03-14 17:16   ` Fabio Erculiani
2008-03-14 18:08     ` Bo Ørsted Andresen
2008-03-15  9:37     ` Jakub Moc
2008-03-16  7:41 ` Luca Barbato
  -- strict thread matches above, loose matches on Subject: below --
2008-03-12 23:35 [gentoo-dev] " Fabio Erculiani
2008-03-12 23:46 ` Jan Kundrát
2008-03-12 23:57   ` Fabio Erculiani
2008-03-13  7:33     ` Thilo Bangert
2008-03-13  9:24       ` Fabio Erculiani
2008-03-13 10:27         ` Robin H. Johnson
2008-03-13 12:53           ` Fabio Erculiani
2008-03-13 13:10             ` Fabio Erculiani
2008-03-13 13:27               ` [gentoo-dev] " Ryan Hill
2008-03-13 16:22                 ` Fabio Erculiani
2008-03-13 16:43                   ` Fabio Erculiani
2008-03-13 17:42                     ` Rémi Cardona
2008-03-13 19:59                     ` Robin H. Johnson
2008-03-14 12:47                     ` Gilles Dartiguelongue
2008-03-13 16:52                   ` Chris Gianelloni
2008-03-13 17:00                     ` Fabio Erculiani
2008-03-13 19:20 ` [gentoo-dev] " René 'Necoro' Neumann
2008-03-13 19:37   ` [gentoo-dev] " Markus Ullmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47D9B45F.5090600@gentoo.org \
    --to=betelgeuse@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox