From: Peter Stuge <peter@stuge.se>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] repo/gentoo.git, or how committing is challenging
Date: Tue, 15 Dec 2015 01:31:59 +0100 [thread overview]
Message-ID: <20151215003159.10996.qmail@stuge.se> (raw)
In-Reply-To: <566EA40F.5090806@gentoo.org>
Patrick,
Patrick Lauer wrote:
> Like seriously, every time I try to approach this set of problems I
> run into enough stupidity
Stop the silly complaining and help work on solving the problem instead.
If you can contribute then do so. If not, your options are to hire
someone who is, or await the day when a fix to your problem magically
appears. :) It really is that simple.
You mentioned that you use Gentoo professionally. This means that you
have already invested in Gentoo and have probably planned to
contribute to Gentoo. It seems that you have come across an
area where you could contribute.
If you choose not to that's perfectly fine, but since there is no
warranty you really do not get to complain that it's broken if you're
not helping fix it, and the tone you are using is certainly not
acceptable.
> why do we have documentation then when it's not adequate
Because you haven't helped make it adequate for your needs.
> why do we have a helper tool when it doesn't work?
Because you haven't helped make it work the way you need.
> ... and now I walk away for another week, in the hope that things
> maybe are saner then.
In my opinion that is the very last thing you should be doing.
Open source only works when you take ownership of the problems you have.
You are on the contrary saying that you refuse to own your problems,
that you only want to consume perfect solutions that someone else has
provided you.
It sounds like something a spoiled teenager might say, and it is
really not acceptable behavior in any open source project.
Help fix the problem instead - as you initially offered to do. That's
the very best approach! Everyone will be thankful and the world will
be a happier place.
You need to work on communication. Nobody will want anything to do
with you as long as you continue to sound like a spoiled teenager,
and once you change your communication style plenty will still
remember you for how you used to be, but you have to start somewhere.
It's simple. Stop complaining, be concrete and specific, and send
patches.
Thanks for your contributions to Gentoo, past and future!
//Peter
next prev parent reply other threads:[~2015-12-15 0:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 17:36 [gentoo-dev] repo/gentoo.git, or how committing is challenging Patrick Lauer
2015-12-13 17:38 ` Patrick Lauer
2015-12-13 18:50 ` Andrew Savchenko
2015-12-13 19:05 ` Patrick Lauer
2015-12-13 19:20 ` Andrew Savchenko
2015-12-13 21:30 ` Mike Gilbert
2015-12-13 21:53 ` Andrew Savchenko
2015-12-14 3:00 ` Brian Dolbec
2015-12-14 6:23 ` Daniel Campbell
2015-12-14 11:12 ` Patrick Lauer
2015-12-14 17:52 ` Mike Gilbert
2015-12-15 0:31 ` Peter Stuge [this message]
2015-12-21 3:21 ` [gentoo-dev] " Ryan Hill
2015-12-21 18:59 ` Peter Stuge
2015-12-22 0:45 ` Rich Freeman
2015-12-22 9:41 ` Patrick Lauer
2015-12-22 12:08 ` Rich Freeman
2015-12-22 12:53 ` Patrick Lauer
2015-12-22 13:14 ` Rich Freeman
2015-12-22 13:31 ` Patrick Lauer
2015-12-22 14:04 ` Rich Freeman
2015-12-22 18:21 ` Patrick Lauer
2015-12-22 23:55 ` Peter Stuge
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=20151215003159.10996.qmail@stuge.se \
--to=peter@stuge.se \
--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