<?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/"
		>
<channel>
	<title>Comments on: Changes in Elgg&#8217;s support</title>
	<atom:link href="http://openedweb.com/blog/2009/01/07/changes-in-elggs-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://openedweb.com/blog/2009/01/07/changes-in-elggs-support/</link>
	<description>Education and Technology</description>
	<lastBuildDate>Sun, 22 Jan 2012 03:29:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tradenet</title>
		<link>http://openedweb.com/blog/2009/01/07/changes-in-elggs-support/comment-page-1/#comment-3044</link>
		<dc:creator>Tradenet</dc:creator>
		<pubDate>Sat, 10 Jan 2009 15:08:07 +0000</pubDate>
		<guid isPermaLink="false">http://openedweb.com/blog/?p=978#comment-3044</guid>
		<description>Frankly, I really like the Drupal model as an example of this. It seems to be working.</description>
		<content:encoded><![CDATA[<p>Frankly, I really like the Drupal model as an example of this. It seems to be working.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://openedweb.com/blog/2009/01/07/changes-in-elggs-support/comment-page-1/#comment-3022</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 08 Jan 2009 23:46:23 +0000</pubDate>
		<guid isPermaLink="false">http://openedweb.com/blog/?p=978#comment-3022</guid>
		<description>My experience has been that wikis have a way of working with some tending. People who make contributions watch their pages because they want to protect their contribution against vandalism. They also want to know what others might contribute on a topic that is important to them.

Both FB or WP require registration to make edits. The main pages are often locked. I have seen similar implementations elsewhere.</description>
		<content:encoded><![CDATA[<p>My experience has been that wikis have a way of working with some tending. People who make contributions watch their pages because they want to protect their contribution against vandalism. They also want to know what others might contribute on a topic that is important to them.</p>
<p>Both FB or WP require registration to make edits. The main pages are often locked. I have seen similar implementations elsewhere.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://openedweb.com/blog/2009/01/07/changes-in-elggs-support/comment-page-1/#comment-3018</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 08 Jan 2009 21:11:40 +0000</pubDate>
		<guid isPermaLink="false">http://openedweb.com/blog/?p=978#comment-3018</guid>
		<description>Matt--

You do parse well! You have replied with some of what I included in a draft, but edited or softened! Two points in particular: Elgg would be best served by the core devs relinquishing some control of some aspects of this project. Secondly, Curverider&#039;s priorities and those of the the community are not identical. It would be best to harness this.

As one who has written a few simple plugins, I agree with your final point. In the spirit of open source, I&#039;d rather the community feel ownership of the plugin.</description>
		<content:encoded><![CDATA[<p>Matt&#8211;</p>
<p>You do parse well! You have replied with some of what I included in a draft, but edited or softened! Two points in particular: Elgg would be best served by the core devs relinquishing some control of some aspects of this project. Secondly, Curverider&#8217;s priorities and those of the the community are not identical. It would be best to harness this.</p>
<p>As one who has written a few simple plugins, I agree with your final point. In the spirit of open source, I&#8217;d rather the community feel ownership of the plugin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tradenet</title>
		<link>http://openedweb.com/blog/2009/01/07/changes-in-elggs-support/comment-page-1/#comment-3017</link>
		<dc:creator>Tradenet</dc:creator>
		<pubDate>Thu, 08 Jan 2009 18:11:06 +0000</pubDate>
		<guid isPermaLink="false">http://openedweb.com/blog/?p=978#comment-3017</guid>
		<description>I agree that whole plugin repository is a mess. You got a bunch of new and outdated stuff in there. It really needs some organization. This is where you are going to get most of the &quot;complaints&quot; from.</description>
		<content:encoded><![CDATA[<p>I agree that whole plugin repository is a mess. You got a bunch of new and outdated stuff in there. It really needs some organization. This is where you are going to get most of the &#8220;complaints&#8221; from.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cash</title>
		<link>http://openedweb.com/blog/2009/01/07/changes-in-elggs-support/comment-page-1/#comment-3015</link>
		<dc:creator>Cash</dc:creator>
		<pubDate>Thu, 08 Jan 2009 14:42:51 +0000</pubDate>
		<guid isPermaLink="false">http://openedweb.com/blog/?p=978#comment-3015</guid>
		<description>When a newer version of a plugin is uploaded, the older one remains available but doesn&#039;t show up on the list of plugins. There is a link to previous versions on the newest upload.</description>
		<content:encoded><![CDATA[<p>When a newer version of a plugin is uploaded, the older one remains available but doesn&#8217;t show up on the list of plugins. There is a link to previous versions on the newest upload.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Leifer</title>
		<link>http://openedweb.com/blog/2009/01/07/changes-in-elggs-support/comment-page-1/#comment-3011</link>
		<dc:creator>Matt Leifer</dc:creator>
		<pubDate>Thu, 08 Jan 2009 13:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://openedweb.com/blog/?p=978#comment-3011</guid>
		<description>This is great news.  The changes all seem positive and I&#039;m particularly happy to hear about version control on plugins, even if it is very basic.

However, I agree with the criticism about the Elgg developers not relinquishing enough control.  The documentation would probably vastly improve if anyone, or at least registered users, could make edits.  Maybe the developers are worried about having to constantly monitor the wiki for accuracy, but most wikis are self policing, i.e. people who care about the individual pages check them regularly.  It&#039;s possible that the Elgg community is not large enough yet for this to work properly, but I think it&#039;s worth the experiment.

On the same theme, I think the pace of development would be greatly increased if there were a better mechanism to submit patches to the core, rather than having the Curverider folks take sole responsibility for them.  People will work on the bugs and features that they care about and the communities priorities might not completely match Curverider&#039;s priorities.  Not having this defeats much of the purpose of Open Source.  Similar functionality is needed for plugins.  I may not care to revisit a plugin that I wrote if it works on my site, but I certainly want others to be able to improve it without having to fork the code.</description>
		<content:encoded><![CDATA[<p>This is great news.  The changes all seem positive and I&#8217;m particularly happy to hear about version control on plugins, even if it is very basic.</p>
<p>However, I agree with the criticism about the Elgg developers not relinquishing enough control.  The documentation would probably vastly improve if anyone, or at least registered users, could make edits.  Maybe the developers are worried about having to constantly monitor the wiki for accuracy, but most wikis are self policing, i.e. people who care about the individual pages check them regularly.  It&#8217;s possible that the Elgg community is not large enough yet for this to work properly, but I think it&#8217;s worth the experiment.</p>
<p>On the same theme, I think the pace of development would be greatly increased if there were a better mechanism to submit patches to the core, rather than having the Curverider folks take sole responsibility for them.  People will work on the bugs and features that they care about and the communities priorities might not completely match Curverider&#8217;s priorities.  Not having this defeats much of the purpose of Open Source.  Similar functionality is needed for plugins.  I may not care to revisit a plugin that I wrote if it works on my site, but I certainly want others to be able to improve it without having to fork the code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Edminster</title>
		<link>http://openedweb.com/blog/2009/01/07/changes-in-elggs-support/comment-page-1/#comment-3006</link>
		<dc:creator>Matt Edminster</dc:creator>
		<pubDate>Thu, 08 Jan 2009 05:35:56 +0000</pubDate>
		<guid isPermaLink="false">http://openedweb.com/blog/?p=978#comment-3006</guid>
		<description>Steve, I agree that Elgg could benefit from the additions of qualified and constructive contributors. But things could also get sloppy and sour if the wrong people started making additions and/or edits. How have WP and FB embraced the good and avoided the bad?</description>
		<content:encoded><![CDATA[<p>Steve, I agree that Elgg could benefit from the additions of qualified and constructive contributors. But things could also get sloppy and sour if the wrong people started making additions and/or edits. How have WP and FB embraced the good and avoided the bad?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil</title>
		<link>http://openedweb.com/blog/2009/01/07/changes-in-elggs-support/comment-page-1/#comment-3004</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Wed, 07 Jan 2009 22:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://openedweb.com/blog/?p=978#comment-3004</guid>
		<description>I think it looks good and the changes are positive.
But it&#039;s too early to say whether it will need much tweeking.
I&#039;m delighted though that things are moving forward in a good way providing more scope for interaction.
I hope that plugin development gathers pace again now.

I&#039;m still wondering why some plugins that were available in the google group weren&#039;t left there or released at the .org site.
It does seem that dave &amp; co are very reluctant to give up any stewardship to others and I find it hard to imagine how, as the project gathers followers again, the new structure will cope. Where will all the trivial enquiries go. Inmy head I see a big road sign with arrows on it showing very clear directions for people with specific areas to move to.
Are the new areas to which people will be inclined to go responsive enough. Because you know what it&#039;s like, people will want a response.
I hope plugin developers don&#039;t get too much flack because they&#039;ll then discourage feedback.
Perhaps I&#039;m overthinking it here, I&#039;m happy to sit and see how it goes anyway.

Phil</description>
		<content:encoded><![CDATA[<p>I think it looks good and the changes are positive.<br />
But it&#8217;s too early to say whether it will need much tweeking.<br />
I&#8217;m delighted though that things are moving forward in a good way providing more scope for interaction.<br />
I hope that plugin development gathers pace again now.</p>
<p>I&#8217;m still wondering why some plugins that were available in the google group weren&#8217;t left there or released at the .org site.<br />
It does seem that dave &amp; co are very reluctant to give up any stewardship to others and I find it hard to imagine how, as the project gathers followers again, the new structure will cope. Where will all the trivial enquiries go. Inmy head I see a big road sign with arrows on it showing very clear directions for people with specific areas to move to.<br />
Are the new areas to which people will be inclined to go responsive enough. Because you know what it&#8217;s like, people will want a response.<br />
I hope plugin developers don&#8217;t get too much flack because they&#8217;ll then discourage feedback.<br />
Perhaps I&#8217;m overthinking it here, I&#8217;m happy to sit and see how it goes anyway.</p>
<p>Phil</p>
]]></content:encoded>
	</item>
</channel>
</rss>

