[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 Rolf,

Thursday, January 17, 2008, 4:34:41 PM, you wrote:

> Paul,

> thank you for pointing out the problem and a template solution towards
> the end of your initial rant as well.  In fact I am already working on

  Thanks for acting on that.

> moving the mid-term fix into a separate package to provide an even less
> intrusive mid-term fix ->
> http://oz.leggewie.org/wip/wifi-suspend.patch



> But...

> Paul Sokolovsky schrieb:
>> and of course they need to be supported still, and right now. The question
>> is how that is done - if it comes mixed into one big mess
>                                                        ^^^^
>> I don't appreciate someone moving in the opposite direction just to solve on-spot problem. OE is
>     ^^^^^^^^^^^^^^^^
>> powerful environment allowing to solve make focused, maintainable and
>> reusable changes - even if they're workarounds, and people should
>> learn to use them.

> And I don't appreciate after I have

> * fixed a real usability issue which likely strongly influences the
>   perception of OE-derived distros
> * consulted with a *LOT* of people on IRC and in the bug tracker over
>   several days
> * have put quite some time into finding an acceptable solution for
>   everyone

> that someone comes around who had previously been quiet on this and then
> calls my work a "mess" and generally finds very unappreciative words for
> what I've done and the time I've spent.

  Oh, do we need a bit of affirmative action here again? ;-) Ok, so
"mess" is not your work, it's what core layer of OE runtime is, to the large
extent. Being with OE for quite some time, I know such
problem areas, and try to work towards resolving them. That's hard to
do on one's own, so I humbly expects that other experienced OE
developers to share such approach, instead of trying to apply pain-of-day
patches, just increasing existing mess.

 As for IRC, unfortunately, I don't have much time to be on it
lately, but I try to be on MLs. So, don't get too hot about receiving
*one more* comment if you already received them a lot. OE is big system,
and noone can know and be up to date with all its areas.

> Mickey's comment

> # I agree. The issue to fix is worthwile, but I would prefer seperate
> # packaging as well.

> sounds quite different, don't you agree?

  Nope, I don't ;-). I don't see anything special about communication
which goes your way, no matter who's the other side, sorry ;-).

> FOSS is an incremental process.

> I am willing to get this not only right for me, but to everyone's
> satisfaction.

  Great, so I just provide my comments on the matter. You may wonder
how it gets often that you and I get into communication (though I of
course give comments to other people too). But even that should be
rather clear - because we both care about almost the same area
regarding OE, albeit with different approaches and plans. In this
regard, I appreciate your review, suggestions, and comments!

> But I kindly want to ask you to consider that it is not
> only what you say but also how you say it.

> PS: I don't intend to and hope I did not start another flame war, but
> this is important to me.


  Just in case, there's still personal mail around...


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