<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for GlotPress</title>
	<atom:link href="http://blog.glotpress.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.glotpress.org</link>
	<description>Just another WordPress.com weblog</description>
	<lastBuildDate>Tue, 17 Jan 2012 16:58:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Milan I completely agree with this but we&#8217;ll&#8230; by Peter</title>
		<link>http://blog.glotpress.org/2011/10/18/milan-i-completely-agree-with-this-but-well/#comment-1970</link>
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Tue, 17 Jan 2012 16:58:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.glotpress.org/2011/10/18/milan-i-completely-agree-with-this-but-well/#comment-1970</guid>
		<description><![CDATA[Sounds good. Do you with &quot;we do a thorough review and testing&quot; mean the 3 mentioned or will there be a review/testing team, or is it just anybody who can say Yes It Works :)
I do suggest that you and Nikolay setup a roadmap with milestones and assign the tickets accordingly. That way it&#039;s easier to pick up tickets and work on them.

Maybe even set Trac up the way WordPress core is setup.]]></description>
		<content:encoded><![CDATA[<p>Sounds good. Do you with &#8220;we do a thorough review and testing&#8221; mean the 3 mentioned or will there be a review/testing team, or is it just anybody who can say Yes It Works <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
I do suggest that you and Nikolay setup a roadmap with milestones and assign the tickets accordingly. That way it&#8217;s easier to pick up tickets and work on them.</p>
<p>Maybe even set Trac up the way WordPress core is setup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Milan I completely agree with this but we&#8217;ll&#8230; by Zé</title>
		<link>http://blog.glotpress.org/2011/10/18/milan-i-completely-agree-with-this-but-well/#comment-1969</link>
		<dc:creator><![CDATA[Zé]]></dc:creator>
		<pubDate>Tue, 17 Jan 2012 15:21:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.glotpress.org/2011/10/18/milan-i-completely-agree-with-this-but-well/#comment-1969</guid>
		<description><![CDATA[Right now, only Nikolay and myself (and Nacin) can commit, so, the question here is how to work out a way for patches to get in to core? I suggest (subjectively) that we do a thourough review and testing of the more pressing patches and commit those. The quality of code of individual contributors should then, over time, indicate candidates for core-committing privileges. Again, that&#039;s just me, all suggestions are welcome.]]></description>
		<content:encoded><![CDATA[<p>Right now, only Nikolay and myself (and Nacin) can commit, so, the question here is how to work out a way for patches to get in to core? I suggest (subjectively) that we do a thourough review and testing of the more pressing patches and commit those. The quality of code of individual contributors should then, over time, indicate candidates for core-committing privileges. Again, that&#8217;s just me, all suggestions are welcome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Milan I completely agree with this but we&#8217;ll&#8230; by Peter</title>
		<link>http://blog.glotpress.org/2011/10/18/milan-i-completely-agree-with-this-but-well/#comment-1968</link>
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Tue, 17 Jan 2012 15:15:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.glotpress.org/2011/10/18/milan-i-completely-agree-with-this-but-well/#comment-1968</guid>
		<description><![CDATA[As Juan asked, will reviewed patches be merged into the core? The reason for asking is the fact that you yourself have a trac ticket #164,  that is on needs-review for 4 months now.
Is there a development team who approves patches and merges them into the core? I know you can submit to the SVN as can Nikolay of course but who else?]]></description>
		<content:encoded><![CDATA[<p>As Juan asked, will reviewed patches be merged into the core? The reason for asking is the fact that you yourself have a trac ticket #164,  that is on needs-review for 4 months now.<br />
Is there a development team who approves patches and merges them into the core? I know you can submit to the SVN as can Nikolay of course but who else?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Rethinking the GlotPress UI by Carlos E. G. Barbosa</title>
		<link>http://blog.glotpress.org/2011/10/18/rethinking-the-glotpress-ui/#comment-1578</link>
		<dc:creator><![CDATA[Carlos E. G. Barbosa]]></dc:creator>
		<pubDate>Sat, 26 Nov 2011 01:09:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.glotpress.org/?p=89#comment-1578</guid>
		<description><![CDATA[&quot;In my mind GlotPress is exactly that, just an administrative Panel to achieve a goal – collaborative translations of something else.&quot; 
---------------

Hi Hugo,

In my opinion it may be just an administrative panel, if concealed and access-restricted to none else than the registered users. 

But it is not thus.

To achieve its main goal the GlotPress installation must be a &quot;public-facing site&quot; as it is, in fact. How else should the collaborative aspect of the translations be privileged? 

With GlotPress that translation task is no more a blackbox procedure. It is visible and world wide accessible as a site that points to &quot;something else&quot;, isn&#039;t it? The &quot;something else&quot; may give it a reason why, but the translation job has got a face itself. So why be so shy in giving it that nice visual flexibility?]]></description>
		<content:encoded><![CDATA[<p>&#8220;In my mind GlotPress is exactly that, just an administrative Panel to achieve a goal – collaborative translations of something else.&#8221;<br />
&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>Hi Hugo,</p>
<p>In my opinion it may be just an administrative panel, if concealed and access-restricted to none else than the registered users. </p>
<p>But it is not thus.</p>
<p>To achieve its main goal the GlotPress installation must be a &#8220;public-facing site&#8221; as it is, in fact. How else should the collaborative aspect of the translations be privileged? </p>
<p>With GlotPress that translation task is no more a blackbox procedure. It is visible and world wide accessible as a site that points to &#8220;something else&#8221;, isn&#8217;t it? The &#8220;something else&#8221; may give it a reason why, but the translation job has got a face itself. So why be so shy in giving it that nice visual flexibility?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Milan I completely agree with this but we&#8217;ll&#8230; by Juan Ramon</title>
		<link>http://blog.glotpress.org/2011/10/18/milan-i-completely-agree-with-this-but-well/#comment-1550</link>
		<dc:creator><![CDATA[Juan Ramon]]></dc:creator>
		<pubDate>Thu, 24 Nov 2011 14:41:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.glotpress.org/2011/10/18/milan-i-completely-agree-with-this-but-well/#comment-1550</guid>
		<description><![CDATA[I&#039;ve seen that most issues in the &lt;a href=&quot;http://glotpress.trac.wordpress.org/&quot; rel=&quot;nofollow&quot;&gt;trac&lt;/a&gt; are very old. If we review them and upload patches to the trac or we test another patches, it will be merge to the core?]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve seen that most issues in the <a href="http://glotpress.trac.wordpress.org/" rel="nofollow">trac</a> are very old. If we review them and upload patches to the trac or we test another patches, it will be merge to the core?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on When I started GlotPress one of its goals&#8230; by Juan Ramon</title>
		<link>http://blog.glotpress.org/2011/11/14/when-i-started-glotpress-one-of-its-goals/#comment-1548</link>
		<dc:creator><![CDATA[Juan Ramon]]></dc:creator>
		<pubDate>Thu, 24 Nov 2011 14:16:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.glotpress.org/2011/11/14/when-i-started-glotpress-one-of-its-goals/#comment-1548</guid>
		<description><![CDATA[thanks for sharing! Maybe it&#039;s time to dig in the system :)]]></description>
		<content:encoded><![CDATA[<p>thanks for sharing! Maybe it&#8217;s time to dig in the system <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on When I started GlotPress one of its goals&#8230; by Nikolay Bachiyski</title>
		<link>http://blog.glotpress.org/2011/11/14/when-i-started-glotpress-one-of-its-goals/#comment-1332</link>
		<dc:creator><![CDATA[Nikolay Bachiyski]]></dc:creator>
		<pubDate>Tue, 15 Nov 2011 19:00:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.glotpress.org/2011/11/14/when-i-started-glotpress-one-of-its-goals/#comment-1332</guid>
		<description><![CDATA[I would love to finish it, too. And I will.]]></description>
		<content:encoded><![CDATA[<p>I would love to finish it, too. And I will.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on When I started GlotPress one of its goals&#8230; by Stas Sușcov</title>
		<link>http://blog.glotpress.org/2011/11/14/when-i-started-glotpress-one-of-its-goals/#comment-1325</link>
		<dc:creator><![CDATA[Stas Sușcov]]></dc:creator>
		<pubDate>Tue, 15 Nov 2011 17:18:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.glotpress.org/2011/11/14/when-i-started-glotpress-one-of-its-goals/#comment-1325</guid>
		<description><![CDATA[Kudos, for sharing!
I would love to see the testing chapter finished :)]]></description>
		<content:encoded><![CDATA[<p>Kudos, for sharing!<br />
I would love to see the testing chapter finished <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Rethinking the GlotPress UI by Mejorando el aspecto de GlotPress &#124; Tecnologia, Desarrollo Web, Posicionamiento Web SEO</title>
		<link>http://blog.glotpress.org/2011/10/18/rethinking-the-glotpress-ui/#comment-1116</link>
		<dc:creator><![CDATA[Mejorando el aspecto de GlotPress &#124; Tecnologia, Desarrollo Web, Posicionamiento Web SEO]]></dc:creator>
		<pubDate>Mon, 07 Nov 2011 02:07:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.glotpress.org/?p=89#comment-1116</guid>
		<description><![CDATA[[...] Baeta, buen amigo de la comunidad WordPress hispana, se está ocupando de mejorar la interfaz de GlotPress, el software de traducción de código libre utilizado por [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Baeta, buen amigo de la comunidad WordPress hispana, se está ocupando de mejorar la interfaz de GlotPress, el software de traducción de código libre utilizado por [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Rethinking the GlotPress UI by Mejorando el aspecto de GlotPress &#124; Ayuda WordPress</title>
		<link>http://blog.glotpress.org/2011/10/18/rethinking-the-glotpress-ui/#comment-1113</link>
		<dc:creator><![CDATA[Mejorando el aspecto de GlotPress &#124; Ayuda WordPress]]></dc:creator>
		<pubDate>Sun, 06 Nov 2011 23:28:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.glotpress.org/?p=89#comment-1113</guid>
		<description><![CDATA[[...] Baeta, buen amigo de la comunidad WordPress hispana, se está ocupando de mejorar la interfaz de GlotPress, el software de traducción de código libre utilizado por [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Baeta, buen amigo de la comunidad WordPress hispana, se está ocupando de mejorar la interfaz de GlotPress, el software de traducción de código libre utilizado por [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

