Linked by Thom Holwerda on Mon 14th Mar 2011 18:59 UTC
Talk, Rumors, X Versus Y And over the weekend, the saga regarding Canonical, GNOME, and KDE has continued. Lots of comments all over the web, some heated, some well-argued, some wholly indifferent. Most interestingly, Jeff Waugh and Dave Neary have elaborated on GNOME's position after the initial blog posts by Shuttleworth and Seigo, providing a more coherent look at GNOME's side of the story.
Thread beginning with comment 466066
To read all comments associated with this story, please click here.
in one comment
by robmv on Mon 14th Mar 2011 19:26 UTC
robmv
Member since:
2006-08-12

this comment on Aaron blog, extracted by Dave Neary tells a lot:

CSD is really not a good example of how stuff development between Canonical and GNOME should work. I’m the person at Canonical who started CSD, but never finished it.

It started as just an experimental hack, and somehow got picked up as a “Canonical project”. Once that happened my immediate manager told me to stop committing code to GNOME git and do any further work on it privately in bzr.

For me this made developing it further much more difficult, because it was an extremely large and intrusive change into GTK+ source code and my manager didn’t want upstream developers to help me with at least peer code review.

Reply Score: 5

RE: in one comment
by acobar on Mon 14th Mar 2011 19:41 in reply to "in one comment"
acobar Member since:
2005-11-15

It still do not fix the problems. Fact is, gnome people did know that an effort was in course to provide a common notification area.

Now, instead of reload the process and work to provide even a temporary solution for this mess, some guys are just hunting witches.

Reply Parent Score: 4

RE[2]: in one comment
by robmv on Mon 14th Mar 2011 19:52 in reply to "RE: in one comment"
robmv Member since:
2006-08-12

yes witch hunt is bad but what could GNOME developers do if the effort in course was done privately?, become Canonical employees to have access to those discussions?, or wait until the code dump is thrown in their faces, accept it!!!. If GNOME developers decided to implement something resembling what Canonical was doing in closed doors, I do not blame them

Edited 2011-03-14 19:58 UTC

Reply Parent Score: 5

RE: in one comment
by Richard Dale on Mon 14th Mar 2011 20:34 in reply to "in one comment"
Richard Dale Member since:
2005-07-22

this comment on Aaron blog, extracted by Dave Neary tells a lot:

"CSD is really not a good example of how stuff development between Canonical and GNOME should work. I’m the person at Canonical who started CSD, but never finished it.

It started as just an experimental hack, and somehow got picked up as a “Canonical project”. Once that happened my immediate manager told me to stop committing code to GNOME git and do any further work on it privately in bzr.

For me this made developing it further much more difficult, because it was an extremely large and intrusive change into GTK+ source code and my manager didn’t want upstream developers to help me with at least peer code review.
"

It doesn't tell us a lot because CSD or 'Client Side Decorations' are not anything to do with app indicators. It was just an experiment, and as far as I can see a long way from ever being included in either Gnome or KDE. Whether such an experiment is commited to the Gnome repo or Canonical one doesn't actually matter much in practice.

Reply Parent Score: 5

RE[2]: in one comment
by robmv on Tue 15th Mar 2011 16:01 in reply to "RE: in one comment"
robmv Member since:
2006-08-12

It talks about one example of how Canonical does not prefer to develop with the community, they forced the developer in this case to work privately

Reply Parent Score: 1