[oe] Fwd: [oe-commits] org.oe.dev apm: turn off wifi cards before suspend so they are fully reloaded upon resume. closes 3664.

[Paul Sokolovsky]

Hello Mike,

Thursday, January 17, 2008, 5:09:52 PM, you wrote:

[]

> Actually, this is important to me as well.  I've deliberately distanced
> myself from these discussions on the mailing lists, but I've also withheld a
> number of commits for *EXACTLY* the reasons pointed out by Rolf.

> My last commit was the famous 2.6.23 ixp4xx kernel recipe - I'm quite 
> certain everyone remembers that.  It too turned into what I've been seeing
> lately on this list (and on the angstrom list).  Mickey's comment on this
> thread is the sort of helpful, constructive criticism that will result in
> people becoming better OE developers.  The comments by some others, however,
> are the sort of comments that just result in me maintaining my own personal
> set of changes to OE -- it's just easier on my blood-pressure to deal with
> my own private overlay than to endure the guantlet of hyper-critical, 
> condescending, superiority-laden emails that have characterized some of the
> past responses to my (and other's) commits.

> I doubt that my contributions are of particular interest to the general
> population, but I hardly suspect that I'm alone in this -- which makes it
> rather probable that OE is missing some other, really valuable, 
> contributions from those who have just "walked away" because they fear their
> bitbake recipes do not meet the level of god-like perfection demanded by a
> certain small-but-very-vocal group of developers.

> C'mon folks -- teach me.  Don't beat me.

  IMHO, the problem here is not how to make it more comfortable for
individual developers to contribute to OE - that's big question in
itself, but answers to it are mostly bound to general properties of
OpenSource projects (the bigger they become, the steeper participation
curve, unfortunately ;-( ).

  IMHO, the talk is about how to be on the same direction, and even
steering, where OE goes. There're many meta-level changes are being
done to OE, and it's hard for everyone to be current with all of them.
Yet even more important meta-changes cannot be done literally for
years (packages staging for example), because of lack participation
and inertness of developers.

  With all that in mind, IMHO, it's not too productive to keep silent
instead of participating in communication, and actual meta-work. And
per well-known rules of nature, law of compensation comes into play -
if someone keeps silent, someone has to be more vocal; if someone
thinks and finds that it's easiser to do less that otherwise would
be possible, someone else thinks and finds that more has to be done.



> JMO.  That and 10 USD will get you a cup of coffee.

> Mike (mwester)


-- 
Best regards,
 Paul                            mailto:pmiscml at gmail.com