On Mon, 11 Nov 2013 at 9:32:04 +0300, Yury Tarasievich wrote: > I think we have the gist of the problem right there, in the lines > quoted. I see a plain clash of perspectives there. > > We *might* benefit from the new ideas, generated in the way of > hobbie or otherwise. > We *would* benefit from general production going forward. > > I won't go so far as to declare the "production manager" some sort > of supreme authority. However, it is obvious that not every idea is > bound to make it into the (long-existing) software product, for > which PM is, after all, responsible. > > So I'd say there's an *urgent* need for some kind of contribution > rejection procedure. Something like following: (a) Carlos (or > anybody) with his PM's hat on has the first (immediate) say on what > is *not* going in *right now*. (b) However, there also must be an > (almost immediate) request for comments going into the list, > formal-like. (c) If the request gathers no evidence supporting the > innovation, everything stays as it was. (d) Otherwise, steps are > taken etc. > > I believe this is simple enough and sufficient to block (or > alleviate) the rise of bad feelings.
But this is what happens already, and this thread illustrates that. My first reaction to the theming patch is that we don't need it. The patch is good etc, but the idea behind the patch leads to bloat. My opinion is that not everything that can be done should be done. Bloat starts like this: "wouldn't it be cool if...?" and then you make a small concession because many people appear on the mailing list and say "yes, it is cool, please do it. It doesn't increase the size too much." So in this case, despite the patch being OK I felt the need to stop the idea. Keep the WINGs widgets as simple as possible, no choice of colors whatsoever etc. That is what it has been for the past +15 years already and no one is suddenly going to dislike WM because the widgets cannot be green or red. But given the reaction, I am "forced" to accept the patch. There has even been a suggestion to fork wmaker! And perhaps I'm being too conservative, so it will be OK in the end. But in any case, if the repository was only mine the patch would not go in. So the above situation corresponds to your steps a) - d) above. What I guess it's happening here is that Rodolfo is complaining not because of other people's patches, but because his own patches have a history of a rough ride into the repository. Not everything he codes I like 100% (I have the impression that he was learning how to code along the way last year or so), so sometimes there are clashes and he is fed up. He has a 40-patch series that is not applied yet, and I'm not sure what to do. -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
