From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Notes from the U-Boot BOF Meeting in Geneva 2012/07/12
Date: Mon, 23 Jul 2012 16:37:31 -0700 [thread overview]
Message-ID: <500DE03B.9010406@boundarydevices.com> (raw)
In-Reply-To: <201207240106.19485.marex@denx.de>
On 07/23/2012 04:06 PM, Marek Vasut wrote:
> Dear Eric Nelson,
>
>>> Yea ... I think our community is kinda broken :-(
>>
>> Hey. We heard that...
>>
>> Careful what you say on an open mic!
>
> Oh man ... I guess it sounded bad indeed, I should have though about the wording
> more, sorry.
>
> I mean, we messed up the management (and I wonder who'll start bashing me for
> this one), resulting in the community being misguided sometimes. Making it hard
> to learn how to contribute too (too many rules etc). Custodians being
> overloaded, warding people off because the review takes too long ... stuff like
> that is what I meant.
>
> So we have too much to improve, yet too less time to do that.
>
> Ad community, there's a lot of people obviously, who contribute regularly (of
> course, such as yourself for example). But I wonder if there's enough of us to
> maintain such a big codebase we have. Besides, people care about linux a lot
> more than about uboot, pushing many more of the maintaining tasks on custodians.
> Or maybe it's the structure that doesn't work well enough to handle the flow.
> Honestly, I'm getting lost in it myself.
>
Hi Marek,
I think you misunderstood. I was smiling and laughing when I shot you that note.
All of this discussion about process is welcome and positive, and from where
I stand, things ain't that broken...
U-Boot has a tremendous amount of value to a lot of folks, including those that
don't always chime in or feed back.
Those of you that focus on it every day deserve kudos.
Regards,
Eric
next prev parent reply other threads:[~2012-07-23 23:37 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 21:30 [U-Boot] Notes from the U-Boot BOF Meeting in Geneva 2012/07/12 Detlev Zundel
2012-07-16 23:11 ` Graeme Russ
2012-07-17 10:37 ` Stefan Roese
2012-07-17 12:10 ` Graeme Russ
2012-07-17 12:15 ` Graeme Russ
2012-07-18 7:21 ` Wolfgang Denk
2012-07-18 23:37 ` Graeme Russ
2012-07-21 14:46 ` Marek Vasut
2012-07-23 1:33 ` Graeme Russ
2012-07-23 1:47 ` Marek Vasut
2012-07-23 2:07 ` Graeme Russ
2012-07-23 2:13 ` Marek Vasut
2012-07-23 7:43 ` Andy Pont
2012-07-23 6:27 ` Wolfgang Denk
2012-07-23 6:20 ` Wolfgang Denk
2012-07-23 21:16 ` Tom Rini
2012-07-23 22:15 ` Marek Vasut
[not found] ` <500DD2FA.4060800@boundarydevices.com>
2012-07-23 23:06 ` Marek Vasut
2012-07-23 23:37 ` Eric Nelson [this message]
2012-07-23 6:16 ` Wolfgang Denk
2012-07-25 19:47 ` Tom Rini
2012-07-27 14:17 ` Marek Vasut
2012-07-20 22:51 ` Tom Rini
2012-07-21 1:27 ` Marek Vasut
2012-07-21 4:28 ` Graeme Russ
2012-07-23 16:49 ` Tom Rini
2012-07-23 16:44 ` Tom Rini
2012-07-23 17:17 ` Marek Vasut
2012-07-23 17:28 ` Tom Rini
2012-07-23 18:11 ` Marek Vasut
2012-07-23 19:09 ` Tom Rini
2012-07-23 22:16 ` Marek Vasut
2012-07-18 7:41 ` Wolfgang Denk
2012-07-20 3:57 ` Mike Frysinger
2012-07-21 14:40 ` Marek Vasut
2012-07-23 20:53 ` Tom Rini
2012-07-23 22:14 ` Marek Vasut
2012-07-20 16:36 ` Kim Phillips
2012-07-20 21:09 ` Marek Vasut
2012-07-20 21:34 ` Graeme Russ
2012-07-20 21:40 ` Scott Wood
2012-07-20 22:04 ` Graeme Russ
2012-07-21 14:41 ` Marek Vasut
2013-02-18 6:55 ` Simon Glass
2013-02-18 9:59 ` Wolfgang Denk
2013-02-18 10:40 ` Graeme Russ
2013-02-18 12:39 ` Marek Vasut
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=500DE03B.9010406@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=u-boot@lists.denx.de \
/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