Gentoo Archives: gentoo-project

From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@g.o>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] Hiding problems, breach of Gentoo Social Contract
Date: Sat, 03 Dec 2016 21:34:11
Message-Id: alpine.LNX.2.00.1612032122260.24920@woodpecker.gentoo.org
In Reply to: Re: [gentoo-project] Hiding problems, breach of Gentoo Social Contract by Raymond Jennings
1 On Fri, 2 Dec 2016, Raymond Jennings wrote:
2
3 > On Fri, Dec 2, 2016 at 2:13 PM, Michał Górny <mgorny@g.o> wrote:
4 >
5 >> On Fri, 2 Dec 2016 21:52:57 +0000
6 >> "M. J. Everitt" <m.j.everitt@×××.org> wrote:
7
8 <snip>
9
10 >>> It may come to some surprise to you (and others) that Craig is not the
11 >>> only prospective dev who was somewhat perplexed with the attitude
12 >>> towards select Gentoo Devs, who seemed, on the face of it, to be
13 >>> actively contributing to the Gentoo project. There were at least six of
14 >>> us (if not seven, possibly more) who were actively considering and
15 >>> pursuing becoming a Gentoo developer, who all felt that we felt uneasy
16 >>> about progression, not helped by the problems of a lack of active
17 >>> recruiters and other issues within the Recruiters project, which have
18 >>> hopefully now been resolved. There is a mild concern that the only
19 >>> remaining recruiter, may have a bias against some of the prospective
20 >>> recruits, as having been "tainted" by the former Gentoo Dev who was
21 >>> ousted from the Proxy Maintenance project. As non-devs, we have no
22 >>> recourse to council to ask for this to be investigated, and we don't
23 >>> consider ourselves to have a 'voice' to express our opinions and
24 >>> frustrations with the Gentoo 'system' as we observe it. It seems ironic
25 >>> that we are unable to influence the procedures that would help us be
26 >>> represented, and hence the only outlets we have are the mailing lists
27 >>> and third-party platforms. If anyone can suggest the correct course of
28 >>> action that any prospective non-dev contributor might have, I'm sure
29 >>> there are a few ears who would be interested in the response.
30 >>
31 >> The first and most important person for a prospective developer is
32 >> his/her mentor. If you have a mentor, then by all means talk to him/her
33 >> first and he/she'll represent your case to the Council or any
34 >> appropriate community members.
35 >>
36 >
37 > This actually does bring up a side point I've been curious about.
38 >
39 > Do you need to be a current, or even potential/former developer to have a
40 > mentor?
41 >
42 > Can you have a mentor if you're a mere user?
43
44 The "mentor" figure is meant as the developer(s) that help someone being
45 recruited. However, the role of "mentor" is something that we can have
46 anywhere. So if there's any developer you respect and you're able to
47 create a connection to, then by all means please establish / foster that
48 connection and "use it" to improve your knowlege and presence on Gentoo.
49
50
51 About the point raised by "M. J. Everitt" and Craig, if you were trying to
52 join Gentoo, we aren't going to reject you just because of who was your
53 mentor. We do evaluate everyone for their own, not for who was their
54 mentor. Part of that evaluation is related to "social skills".
55 Despite all the recent discussion here, we do need to take into
56 consideration "social skills". Even if we do technical work, we need to
57 do it as part of a community, so it's essential that people are able to
58 work with others and reach compromises. At times, it seems some forget
59 that it's easier to improve technical skills and to get more knowledge,
60 than it is to improve our interaction with others. Recent Gentoo history,
61 imho, only proves that some people are even resistant to that (learning
62 "social skills").
63
64
65 Regards,
66
67 Jorge Manuel B. S. Vicetto
68 Gentoo Developer

Replies

Subject Author
Re: [gentoo-project] Hiding problems, breach of Gentoo Social Contract "William L. Thomson Jr." <wlt-ml@××××××.com>