<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for Shaun's Blog</title>
	<atom:link href="http://blogs.gnome.org/shaunm/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/shaunm</link>
	<description>Fourteen hours to save the Earth</description>
	<pubDate>Mon, 06 Oct 2008 23:58:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>Comment on Three Point Zero by Bob</title>
		<link>http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-83</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Sat, 06 Sep 2008 11:27:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-83</guid>
		<description>&#62; We need a strong leader (or a few strong leaders) that can unite the community. In my pow the Gnome community is deeply fragmented

I couldn't agree more. Moreover GNOME seems disconnected from his userbase. Very few feedback.</description>
		<content:encoded><![CDATA[<p>&gt; We need a strong leader (or a few strong leaders) that can unite the community. In my pow the Gnome community is deeply fragmented</p>
<p>I couldn&#8217;t agree more. Moreover GNOME seems disconnected from his userbase. Very few feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Three Point Zero by Bob</title>
		<link>http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-82</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Sat, 06 Sep 2008 11:25:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-82</guid>
		<description>I have nice ideas, I think, for GNOME 3.0. However if you're not a developer, your voice is not really heard. Devs are already very busy for maintaining GNOME 2.xx, will they have the time to think about some farfelous ideas for GNOME 3 ?

I have a lot of complaints too about major GNOME aps : 
Nautilus usability sucks (sorry for dev, but the tab stuff is not what I call a nice innovation), it slows too : showing /usr/bin or a folder with lot of picture is hell slow.

GNOME Office is in a galaxy far far away from KOffice (I know this is not a « official part » of GNOME but it should be), we should really inspire from them.
In regard to the Gimp, Krita is more appealing too.

Evolution, well, Evolution is a bit bloated, Evolution may be a nice apps for power users if you need to connect to Exchange, but for desktop user, I think GNOME should ship a more simple mail client, with separate Calendar/Address Book apps (see Pimlico suite by OH guys). 

Communication/ Collaborative : I wanna be able to send file opened in gedit just using File&#62;Send to... and then it launch my mail client with the attachment. Or use some kind of Telepathy backend for collaborative editing on various apps : some kind of "Contact" menu, that permits to invite someone in your empathy contacts list to work on the current document.

Customization is a problem too. I won't troll like Linus, but hell, why can't I move toolbars, or add/remove buttons ? Let's talk about metacity : no vertical/horizontal window reorganizing ?

GNOME in general lacks of homogeneity, communication between apps, it's more like a collection of soft, rather than a Desktop Environment. Restricting languages used in GNOME Desktop might be a good idea too, for example, we could focus on setting up a C/C++/Vala development environment to appeal new devs, and limit apps' plugins to one scripting language (Python/Ruby/ECMAscript/whatever).

What about setting up a GNOME 3.0 brainstorm where users could send their ideas ?

(ps: yeah I know, lot of critics, but please don't say « Just send your patches », I'm not a dev, and I won't learn how to make good code in one month, and I'm already busy with translations)</description>
		<content:encoded><![CDATA[<p>I have nice ideas, I think, for GNOME 3.0. However if you&#8217;re not a developer, your voice is not really heard. Devs are already very busy for maintaining GNOME 2.xx, will they have the time to think about some farfelous ideas for GNOME 3 ?</p>
<p>I have a lot of complaints too about major GNOME aps :<br />
Nautilus usability sucks (sorry for dev, but the tab stuff is not what I call a nice innovation), it slows too : showing /usr/bin or a folder with lot of picture is hell slow.</p>
<p>GNOME Office is in a galaxy far far away from KOffice (I know this is not a « official part » of GNOME but it should be), we should really inspire from them.<br />
In regard to the Gimp, Krita is more appealing too.</p>
<p>Evolution, well, Evolution is a bit bloated, Evolution may be a nice apps for power users if you need to connect to Exchange, but for desktop user, I think GNOME should ship a more simple mail client, with separate Calendar/Address Book apps (see Pimlico suite by OH guys). </p>
<p>Communication/ Collaborative : I wanna be able to send file opened in gedit just using File&gt;Send to&#8230; and then it launch my mail client with the attachment. Or use some kind of Telepathy backend for collaborative editing on various apps : some kind of &#8220;Contact&#8221; menu, that permits to invite someone in your empathy contacts list to work on the current document.</p>
<p>Customization is a problem too. I won&#8217;t troll like Linus, but hell, why can&#8217;t I move toolbars, or add/remove buttons ? Let&#8217;s talk about metacity : no vertical/horizontal window reorganizing ?</p>
<p>GNOME in general lacks of homogeneity, communication between apps, it&#8217;s more like a collection of soft, rather than a Desktop Environment. Restricting languages used in GNOME Desktop might be a good idea too, for example, we could focus on setting up a C/C++/Vala development environment to appeal new devs, and limit apps&#8217; plugins to one scripting language (Python/Ruby/ECMAscript/whatever).</p>
<p>What about setting up a GNOME 3.0 brainstorm where users could send their ideas ?</p>
<p>(ps: yeah I know, lot of critics, but please don&#8217;t say « Just send your patches », I&#8217;m not a dev, and I won&#8217;t learn how to make good code in one month, and I&#8217;m already busy with translations)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Three Point Zero by Botond Szasz</title>
		<link>http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-81</link>
		<dc:creator>Botond Szasz</dc:creator>
		<pubDate>Fri, 05 Sep 2008 15:59:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-81</guid>
		<description>I agree with Johannes Berg. I think one of the most important things is that we have nice integrated development environment, which is part of Gnome and is just as easy to use like GEdit for example. I start it up create a new project and off I go, I can start writing code. I know that there are a couple very powerful tool for hacking on code, but the thing is that if I download some tar.gz file or I check out an SVN repo for a project I cant just open the project file in a development environment and start looking where can I help or enhance the code or something. The autotools (and possibly other such tools) are not friendly enough. I would like to have a dev tool that is so easy to use that I can learn coding using it. Currently I have to learn first how the different build tools and such work and then learn to how integrate the project into some other editor/ide.
You all lost me half the way. I'm not trying to be a troll, but that's just how things are. I seriously want to be involved in some project or start my own, but the initial barrier is way too high. Something like the MonoDevelop IDE does (having a project file to open and start hacking) is seriously needed for the other languages too. Anjuta is trying to get here with C but it has a long way to go, and its development seems slow.

I would like to have a killer IDE for Vala with integrated Glade, from which I can do anything related to coding without major (possibly any) configuration first.

Having an easily usable dev system would propel Gnome development very much ahead and fast, believe me.

And for this to start rolling a leader is needed.</description>
		<content:encoded><![CDATA[<p>I agree with Johannes Berg. I think one of the most important things is that we have nice integrated development environment, which is part of Gnome and is just as easy to use like GEdit for example. I start it up create a new project and off I go, I can start writing code. I know that there are a couple very powerful tool for hacking on code, but the thing is that if I download some tar.gz file or I check out an SVN repo for a project I cant just open the project file in a development environment and start looking where can I help or enhance the code or something. The autotools (and possibly other such tools) are not friendly enough. I would like to have a dev tool that is so easy to use that I can learn coding using it. Currently I have to learn first how the different build tools and such work and then learn to how integrate the project into some other editor/ide.<br />
You all lost me half the way. I&#8217;m not trying to be a troll, but that&#8217;s just how things are. I seriously want to be involved in some project or start my own, but the initial barrier is way too high. Something like the MonoDevelop IDE does (having a project file to open and start hacking) is seriously needed for the other languages too. Anjuta is trying to get here with C but it has a long way to go, and its development seems slow.</p>
<p>I would like to have a killer IDE for Vala with integrated Glade, from which I can do anything related to coding without major (possibly any) configuration first.</p>
<p>Having an easily usable dev system would propel Gnome development very much ahead and fast, believe me.</p>
<p>And for this to start rolling a leader is needed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Three Point Zero by Mikkel Kamstrup Erlandsen</title>
		<link>http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-80</link>
		<dc:creator>Mikkel Kamstrup Erlandsen</dc:creator>
		<pubDate>Thu, 04 Sep 2008 11:36:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-80</guid>
		<description>“the buck stops here”: - there you said it ;-P

Anyways, Gnome 3.0 is starting to look like a lost battle to me. We need a strong leader (or a few strong leaders) that can unite the community. In my pow the Gnome community is deeply fragmented.

Time is running and the create energies are seeking other outlets.</description>
		<content:encoded><![CDATA[<p>“the buck stops here”: - there you said it ;-P</p>
<p>Anyways, Gnome 3.0 is starting to look like a lost battle to me. We need a strong leader (or a few strong leaders) that can unite the community. In my pow the Gnome community is deeply fragmented.</p>
<p>Time is running and the create energies are seeking other outlets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Three Point Zero by yann</title>
		<link>http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-79</link>
		<dc:creator>yann</dc:creator>
		<pubDate>Thu, 04 Sep 2008 06:47:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-79</guid>
		<description>I would like to submit ideas for a gnome 3.0, but I do not know where to do it.
So I write some ideas here:
- auto-save: the documents should automatically be saved.  (To create a new document, we ask for the document name)
- trace of all actions: all my actions should be traced (talk to XX, delete this file...). A "undo" is proposed for all possible actions. The user is also never scared to do something wrong.
The tracing a all actions could be used to generate macros.
- document sorted by history: when I want to open a document, I have a historical view of all my documents. I can found the presentation I work on 2 days ago for example. The desktop could be this historical view.
- tag documents: I can tag documents to find them quicker the next time.
- no window: all applications are full-screen. One application per virtual desktop. There is always a free virtual desktop (dynamically added).</description>
		<content:encoded><![CDATA[<p>I would like to submit ideas for a gnome 3.0, but I do not know where to do it.<br />
So I write some ideas here:<br />
- auto-save: the documents should automatically be saved.  (To create a new document, we ask for the document name)<br />
- trace of all actions: all my actions should be traced (talk to XX, delete this file&#8230;). A &#8220;undo&#8221; is proposed for all possible actions. The user is also never scared to do something wrong.<br />
The tracing a all actions could be used to generate macros.<br />
- document sorted by history: when I want to open a document, I have a historical view of all my documents. I can found the presentation I work on 2 days ago for example. The desktop could be this historical view.<br />
- tag documents: I can tag documents to find them quicker the next time.<br />
- no window: all applications are full-screen. One application per virtual desktop. There is always a free virtual desktop (dynamically added).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Three Point Zero by iain</title>
		<link>http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-78</link>
		<dc:creator>iain</dc:creator>
		<pubDate>Wed, 03 Sep 2008 18:32:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-78</guid>
		<description>shaunm for president!</description>
		<content:encoded><![CDATA[<p>shaunm for president!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Three Point Zero by shaunm</title>
		<link>http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-77</link>
		<dc:creator>shaunm</dc:creator>
		<pubDate>Wed, 03 Sep 2008 18:15:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-77</guid>
		<description>I'm not sure that's really Stormy's job.  Her job is to handle the business side of things.  It's up to us to handle the technical side.  And yes, I consider release management to be a technical job.  She doesn't dictate the direction of Gnome.  She helps us get Gnome in places where it needs to be.

It should be the release team's job.  That's why we have them.  The problem is that the release team, historically, is a non-decisive body.  Their job has always been to try to capture community consensus.  They're poll counters.  (RT members, please, I'm not trying to be insulting to you personally.  It's just the way we've always run things.)</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure that&#8217;s really Stormy&#8217;s job.  Her job is to handle the business side of things.  It&#8217;s up to us to handle the technical side.  And yes, I consider release management to be a technical job.  She doesn&#8217;t dictate the direction of Gnome.  She helps us get Gnome in places where it needs to be.</p>
<p>It should be the release team&#8217;s job.  That&#8217;s why we have them.  The problem is that the release team, historically, is a non-decisive body.  Their job has always been to try to capture community consensus.  They&#8217;re poll counters.  (RT members, please, I&#8217;m not trying to be insulting to you personally.  It&#8217;s just the way we&#8217;ve always run things.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Three Point Zero by Johannes</title>
		<link>http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-76</link>
		<dc:creator>Johannes</dc:creator>
		<pubDate>Wed, 03 Sep 2008 17:24:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-76</guid>
		<description>I completely agree with you. As I stated before I think we really need to skip on 2.x release before 3.0 to have enough time to get some of the bigger things done. Of course we branch and do things like that but making a 2.x is a huge amount of work for all the core hackers and this won't give them the time to work on the "Next big thing".

Let's start the brainstorming somewhere!</description>
		<content:encoded><![CDATA[<p>I completely agree with you. As I stated before I think we really need to skip on 2.x release before 3.0 to have enough time to get some of the bigger things done. Of course we branch and do things like that but making a 2.x is a huge amount of work for all the core hackers and this won&#8217;t give them the time to work on the &#8220;Next big thing&#8221;.</p>
<p>Let&#8217;s start the brainstorming somewhere!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Three Point Zero by kelemeng</title>
		<link>http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-75</link>
		<dc:creator>kelemeng</dc:creator>
		<pubDate>Wed, 03 Sep 2008 17:16:08 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-75</guid>
		<description>"Somebody has to be willing to say “the buck stops here”."

You misspelled it. Correctly:

"Stormy has to be willing to say “the buck stops here”."

Isn't this why we have her? :)

Hackers tend either to hack away endlessly, "just this one last feature please" or worse, say something like "no, this is a no-go beacuse it's the creation of your employer/the devil/Microsoft". 

Our new boss seems to be not this type at all, is not on the previous list of possible evildoers and has a legitimate power, thus perfect to put an end to such pitiful quarrels and make the necessary decisions, as Johannes said.</description>
		<content:encoded><![CDATA[<p>&#8220;Somebody has to be willing to say “the buck stops here”.&#8221;</p>
<p>You misspelled it. Correctly:</p>
<p>&#8220;Stormy has to be willing to say “the buck stops here”.&#8221;</p>
<p>Isn&#8217;t this why we have her? <img src='http://blogs.gnome.org/shaunm/wp-content/mu-plugins/tango-smilies/tango/face-smile.png' alt=':)' class='wp-smiley' width='16' height='16' /> </p>
<p>Hackers tend either to hack away endlessly, &#8220;just this one last feature please&#8221; or worse, say something like &#8220;no, this is a no-go beacuse it&#8217;s the creation of your employer/the devil/Microsoft&#8221;. </p>
<p>Our new boss seems to be not this type at all, is not on the previous list of possible evildoers and has a legitimate power, thus perfect to put an end to such pitiful quarrels and make the necessary decisions, as Johannes said.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Three Point Zero by Johannes Berg</title>
		<link>http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-74</link>
		<dc:creator>Johannes Berg</dc:creator>
		<pubDate>Wed, 03 Sep 2008 16:12:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/shaunm/2008/09/03/three-point-zero/#comment-74</guid>
		<description>As I'm only loosely following gnome, one big selling point for gnome 3.0 for me personally would be "a better auto" replacement. When I want to start hacking on a project, I don't want to have to fight with the autotools, ideally I'd only have to svn co the right project and then start hacking right away.

Don't get me wrong, autotools might solve the problem, but I'm frequently bitten by them being very hard to use and thus mostly wrong, so often enough I find myself not contributing to a project because the initial barrier is too high.

Yes, of course such a change can be done without a major version change, but it's easier then because it becomes a migration point for projects that want to be part of 3.0.

I agree with you though, gnome needs leadership, decisions like this apparently cannot be made in a huge group.</description>
		<content:encoded><![CDATA[<p>As I&#8217;m only loosely following gnome, one big selling point for gnome 3.0 for me personally would be &#8220;a better auto&#8221; replacement. When I want to start hacking on a project, I don&#8217;t want to have to fight with the autotools, ideally I&#8217;d only have to svn co the right project and then start hacking right away.</p>
<p>Don&#8217;t get me wrong, autotools might solve the problem, but I&#8217;m frequently bitten by them being very hard to use and thus mostly wrong, so often enough I find myself not contributing to a project because the initial barrier is too high.</p>
<p>Yes, of course such a change can be done without a major version change, but it&#8217;s easier then because it becomes a migration point for projects that want to be part of 3.0.</p>
<p>I agree with you though, gnome needs leadership, decisions like this apparently cannot be made in a huge group.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
