From: Paul Sokolovsky <pmiscml@gmail.com>
To: Michael 'Mickey' Lauer <mickey@vanille-media.de>
Cc: openembedded-devel@lists.openembedded.org,
"angstrom-distro-devel@linuxtogo.org"
<angstrom-distro-devel@linuxtogo.org>
Subject: Re: OE & Angstrom reputation (was: [Angstrom-devel] Bugzilla is not USENET)
Date: Sat, 22 Dec 2007 23:24:49 +0200 [thread overview]
Message-ID: <1259186504.20071222232449@gmail.com> (raw)
In-Reply-To: <1773902313.20071222210858@vanille-media.de>
Hello Michael,
Saturday, December 22, 2007, 10:08:58 PM, you wrote:
> Graeme Gregory wrote:
>> Guys the bickering in bugzilla is getting to the point where it
>> is silly.
>> I personally don't feel that this lends a good impression of the OE
>> project and the Angstrom distribution.
>> Also a lot of the actual arguments belong on the mailing list or private
>> emails. People solving bugs don't need to know who annoys who.
>> Can I suggest people start applying the 24hr rule when acting on bugs.
>> For those that don't know. This rule states if something annoys you
>> wait 24hrs before you reply. Its an effective damper for flame wars.
> I couldn't agree more. Thanks for starting this thread, Graeme.
> Just recently the mood surrounding OpenEmbedded and Angstrom has been
> dragged down by lots of small fights and arguments, often put in very
> impolite and arrogant style. People are always leaving projects or starting
> forks -- this is nothing new -- although usually they do this because
> of technical differences, not because they're scared away or
> threatened.
Have to say, I can't agree with this, based on my experience with
open-source. IMHO, most forks are created because of social reasons,
not technical. Of course, that only means that more attention should
be paid to social atmosphere of a project.
> I won't pick any individuals here, but rather want to alert you as a whole.
> This is seriously compromising the reputation of our respective projects.
> A technically superior project can lose big time in a comparison when
> it has a battlesome community. Guys, we're losing opportunities here!
> _Please_ try to act much more diplomatic, in word and deed. If you're angry,
> swallow it down, think a day about it, and formulate a professional
> statement. Don't haste. It's very important.
Well, I really wanted to skip this topic, especially taking into
account that one of the persons involved is particularly sensitive to
this stuff. But I find it amusing that 2 of 2 of our friendly value-added
distro creators participated in the argument in question, even if
other side was me. The meta-topic was release bug management for Angstrom,
and while one of them used to be a bug manager for Angstrom, it took
some time to reach understanding why bugs managed in one way and not
another. I personally regret this, as I really rejoiced our
value-added friends to come back to active OE work right in time for
Angstrom release, as their (both active, experienced developers) help
is very much needed! It's really sad that instead there was another
argument, like few times before, hiccup in bug processing, and
another declaration that someone won't work on Angstrom, like we
already heard, despite most of circumstances were different then.
> Friendly Regards,
> :M:
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-12-22 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071222144058.094eb363@cimmeria>
2007-12-22 20:08 ` OE & Angstrom reputation (was: [Angstrom-devel] Bugzilla is not USENET) Michael 'Mickey' Lauer
2007-12-22 21:24 ` Paul Sokolovsky [this message]
2007-12-24 14:11 ` [Angstrom-devel] OE & Angstrom reputation (was: " Cliff Brake
2007-12-29 23:54 ` Richard Purdie
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=1259186504.20071222232449@gmail.com \
--to=pmiscml@gmail.com \
--cc=angstrom-distro-devel@linuxtogo.org \
--cc=mickey@vanille-media.de \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.