From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [Gentoo Phoenix] recruitment process
Date: Tue, 06 Apr 2010 02:16:52 +0000 [thread overview]
Message-ID: <4BBA9994.1020301@gentoo.org> (raw)
In-Reply-To: <20100405182552.GE2156@Caemlyn.Fullrate>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05-04-2010 18:26, Zeerak Mustafa Waseem wrote:
> On Mon, Apr 05, 2010 at 04:07:01PM +0000, Jon Portnoy wrote:
> There should be a process of weeding out developers that bitch and/or whine, but if most of the teams are understaffed then there has to be done something about it.
> The way I see it there are two options:
> a) Scale down the size of the operation, reduce packages offered, and if there are more packages wanted, let the users maintain them.
> b) Look at an effective way of making the process of become a developer (and being a developer for that matter) more attractive.
>
> The first option could be somewhat simple, we already have overlays so those could simply be used. The second option (which would be the best IMO) is a fair bit harder. The first thing that needs to be done is find out why people don't want to become developers. I've heard a few users mention the quiz, but it seems that the thing keeping most people away from becoming developers are all the flame wars that have occured, and the fact that it (to us users) seems like the council isn't doing much of anything about it.
> So while I believe that improving (and/or updating) the recruitment process is important, I think there would be more success if it seemed like a nice place to be a part of, and that bad behaviour is dealt with.
The Council has a very important role in Gentoo, but if everyone keeps
turning to them to do everything, nothing will get done and they'll get
swamped trying to do anything.
Bad behaviour in the mailing lists is something that all of us have an
obligation to prevent and help fix - including every developer and all
interested community members. If and when someone violates Gentoo's Code
of Conduct[1] and or exhibits a repetitive abrasive behaviour, please
contact either the User Relations[2] or the Developer Relations[3] teams
in case of an user or a developer.
As Petteri already replied, developers who chose to focus in their
"corner" are free to ignore most of the mailing lists and have no
requirement to participate or even read the flames. In other words, if
you'd like to become a developer but have kept away because of the
flames, don't worry as you don't have to get involved on them.
However and despite all the recent complaints about flames in the
mailing lists, as someone that has been following the mailing lists for
a while, the amount and level of flames has been substantially reduced
in the last 2 years or so. We still have flames, but nothing like we
used to have before. Also noteworthy, the number of people involved in
the flames is very small and the majority is well known.
[1] - http://www.gentoo.org/proj/en/council/coc.xml
[2] - http://www.gentoo.org/proj/en/userrel/
[3] - http://www.gentoo.org/proj/en/devrel/
- --
Regards,
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJLupmUAAoJEC8ZTXQF1qEPXzgQAISLb1K8s4Fa2ORYK4+Lef/Y
YeAYiM5xzNPl6kTi6rJF1IoQwDuaS0G/YfRRtzDYeibcYBE0GLVQL0cAyQDTF371
EvgQblvMpTpay8hiNmtdNAb0X6Bm5WUhZoTeY+ayrh6Yih+cniGP5K+zP70550vQ
vvI0y9AdebwZzWrjedeEkUutaxNoBrED7IOfdixDpgD2110NuRcBHpdiBqen0exr
Q2iBdG2ynfdEzYyYAgGHvHcjibtlboLe9DWkQ/APW5uOJHCt0M5QW8HtF7eaPvNf
DS27KNwzoV1VLKxSD5I6cLFz5+NTikI7htZrxqvqjJx0zdk3X+whDOZBXT+7Amv3
2Jaiym4VCsmVXu2hWtZTlbhh0hp07ybx3NmLqNiRkNXX2636A5dCg6fwAUy/CC/g
bmCIMtkTe7oXj+m23AVB1tU5zQuaBMhuV6BucRl3on2bAkSr53Hg0dFbGwwCdiMc
FDULTNrXI1c1P5AKrqFWY6wHj6HW+m6rOVPowXHkuMEmde+T152jci0XYVOCj4v4
YjwKvDyQphk2rzb4S7hLTHpiMIzmM3cbt2/u0zfeviRkMueeT+zfIl8PMi3IN+5W
fvwbTPEq3Eh1JfEaTDDhcYXeIZjrLFx1Es2MYgBKOVzRXCZm9z1Lm15A0LgjpP9O
e09KPDVHG33o/pVc/pqA
=AdOw
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-04-06 2:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 1:33 [gentoo-dev] [Gentoo Phoenix] recruitment process Tobias Heinlein
2010-04-05 5:50 ` Eray Aslan
2010-04-05 16:07 ` Jon Portnoy
2010-04-05 16:50 ` George Prowse
2010-04-05 17:57 ` Jon Portnoy
2010-04-05 18:28 ` Denis Dupeyron
2010-04-05 18:26 ` Zeerak Mustafa Waseem
2010-04-05 17:35 ` Petteri Räty
2010-04-06 2:16 ` Jorge Manuel B. S. Vicetto [this message]
2010-04-06 13:28 ` [gentoo-dev] " Duncan
2010-04-06 16:16 ` Denis Dupeyron
2010-04-05 18:51 ` [gentoo-dev] " Nathan Zachary
2010-04-05 18:59 ` Denis Dupeyron
2010-04-07 17:35 ` Markos Chandras
2010-04-05 7:48 ` Ciaran McCreesh
2010-04-05 8:19 ` Brian Harring
2010-04-05 13:38 ` Richard Freeman
-- strict thread matches above, loose matches on Subject: below --
2010-04-03 13:40 Ben de Groot
2010-04-03 13:53 ` "Paweł Hajdan, Jr."
2010-04-05 2:36 ` Alistair Bush
2010-04-05 8:23 ` Petteri Räty
2010-04-03 13:53 ` George Prowse
2010-04-03 14:05 ` Petteri Räty
2010-04-03 14:22 ` George Prowse
2010-04-03 21:39 ` Sebastian Pipping
2010-04-03 14:03 ` Petteri Räty
2010-04-03 19:00 ` Jesus Rivero (Neurogeek)
2010-04-03 21:48 ` Sebastian Pipping
2010-04-04 9:43 ` Petteri Räty
2010-04-04 16:24 ` Ben de Groot
2010-04-04 15:16 ` basile
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=4BBA9994.1020301@gentoo.org \
--to=jmbsvicetto@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