From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo as a team effort
Date: Sat, 15 Jun 2013 21:20:46 -0700 [thread overview]
Message-ID: <51BD3D1E.9080901@gentoo.org> (raw)
In-Reply-To: <201306151415.01134.dilfridge@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2282 bytes --]
On 6/15/13 5:15 AM, Andreas K. Huettel wrote:
> Well, we have debated about everything to death, and independent of the
> technical details and of the issue at hand it always boils down to the same
> non-technical points:
Thanks for raising this topic. I think this worthwhile, and I see Gentoo
(and any other distro or even FOSS project) as collaborative team effort.
Things you can do alone as an individual are rather limited IMHO.
> * Do you see yourself as "maintainer of package X", or do you see yourself as
> "maintainer of package X which is a part of Gentoo"?
co-maintainer of package X which is a part of Gentoo. I'd like to thank
here my team-mates from the Gentoo Chromium team and every other Gentoo
developer who has contributed to the packages I maintain.
> * How many compromises are you willing to accept to provide the best user
> experience?
I would not compromise 95% users' experience for a vocal minority users'
experience, or at a risk of the package becoming significantly harder to
test or maintain.
Other than that, I'm trying to be accommodating and flexible when
receiving feedback about packages I maintain.
> * How many compromises are you willing to accept to help your colleague
> developers?
Similar thing here. I'm willing to respect decisions made according to
agreed-upon process even if I don't like them (except for really severe
cases), of course providing feedback as I see appropriate. I'm willing
to sacrifice my personal convenience if I know this is good for the
project as a whole.
> In my personal opinion, it's worthwhile to cooperate and put effort into
> Gentoo to improve the distribution as a whole. It is NOT worthwhile to focus
> on isolated solutions, refuse to cooperate with others, and waste energy on
> turf wars.
+1
I also believe there will always be situations where goals or
requirements of various people clash, and we need to learn to deal with
them. Forks and other kinds of "isolated solutions" have their place,
but it's a last resort rather than the first reflex.
Refusing to cooperate or turf wars is actively hostile and harmful to
the project, and it is important for the health of our community not to
allow these behaviors.
Paweł
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next prev parent reply other threads:[~2013-06-16 4:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-15 11:50 [gentoo-project] Gentoo as a team effort Andreas K. Huettel
2013-06-15 11:54 ` Fabian Groffen
2013-06-15 12:15 ` Andreas K. Huettel
2013-06-15 21:43 ` Michael Weber
2013-06-16 4:20 ` "Paweł Hajdan, Jr." [this message]
2013-06-16 6:31 ` Sergey Popov
2013-06-16 9:33 ` Douglas Dunn
2013-06-15 12:08 ` Rich Freeman
2013-06-15 12:42 ` Johannes Huber
2013-06-15 13:44 ` Tom Wijsman
2013-06-15 14:19 ` Johannes Huber
2013-06-15 16:08 ` Tom Wijsman
2013-06-15 13:30 ` Markos Chandras
2013-06-15 16:08 ` Roy Bamford
2013-06-15 20:00 ` William Hubbs
2013-06-15 20:14 ` Rich Freeman
2013-06-17 16:15 ` Chí-Thanh Christopher Nguyễn
2013-06-17 17:02 ` Rick "Zero_Chaos" Farina
2013-06-17 18:24 ` Chí-Thanh Christopher Nguyễn
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=51BD3D1E.9080901@gentoo.org \
--to=phajdan.jr@gentoo.org \
--cc=gentoo-project@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