Dammit forgot to telly you what (*) was. I assume a gnome-design mailing list would be a source for trolls to show up and make the signal to noise ratio high. I think then that if we make the list open only to GNOME foundation members that might help the signal to noise ratio better.
We want active members of the GNOME community involved in GNOME design not some internet yahoo with an axe to grind. sri On Sun, Apr 22, 2012 at 1:09 PM, Sriram Ramkrishna <s...@ramkrishna.me>wrote: > > > On Sun, Apr 22, 2012 at 9:36 AM, Shaun McCance <sha...@gnome.org> wrote: > >> On Sun, 2012-04-22 at 18:21 +0200, Florian Max wrote: >> >> > Which brings us to the matter of openness: the results of everything >> > the design team does ends up on the GNOME wiki under >> > live.gnome.org/Design. >> >> I think people are more concerned about being able to have input >> on the process, not on seeing the results published on the wiki. >> I'm on #gnome-design all day. I often skim the backlog. I don't >> really see the discussion that leads to the results. Sometimes >> I see mention of meetings. I don't know where those meetings >> happen. >> > > In addition, there is no mailing list either(*). So it's hard to really > gauge what people look at when they go through the design. Having an idea > at least for me is great since I do challenge people who do not like our > designs in the open source community and it's hard for me to counter > arguments like "suspend" vs "shutdown" if I don't have a line of insight on > what goes on there. > > Design team needs to give some of us who are trying to show that the > designs that are coming up are in fact good but sometimes we are not given > the tools for the designs that have already been completed. > > Sometimes I feel that some people have developed a 'bunker' attitude and > are so shell shocked from the waves of negativity that they don't want to > engage. That's fine, but some of us can take a lot more abuse than > others. I'm more than happy to do it. > > In the absence of engagement or even a good experience breeds intolerence > and resentment in a vacuum. I don't feel that way, cuz I'm an old fart and > been in this project like forever. I've probably known some of you since > you had your first taste of beer. > > >> > Of course it would be really fancy if the wiki also contained the >> > reasoning behind decisions, but let's face it - none of us does >> > anything like that (I doubt you are adding comments like "Using a >> > full-blown GObject rather than a boxed type here because ..." or "This >> > variable is a double and not an integer because ..." to your code - I >> > certainly don't. Still, wouldn't that be helpful for newcomers?). >> >> That sounds like exactly the sort of thing I write in my git >> commit messages. I hope you do too. >> >> > Hah, I do that too.. and not because to be helpful to newcomers. When I > write code I end up not looking at it again for 6 months and I need > sometime look at my stream of conciousness again. > > sri > > > >> -- >> Shaun >> >> >> >> _______________________________________________ >> desktop-devel-list mailing list >> desktop-devel-list@gnome.org >> http://mail.gnome.org/mailman/listinfo/desktop-devel-list >> > >
_______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
