<?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: Moodle Roles Explained</title>
	<atom:link href="http://www.clamp-it.org/2010/01/moodle-roles-explained/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.clamp-it.org/2010/01/moodle-roles-explained/</link>
	<description>Building tools and sharing solutions for liberal arts colleges</description>
	<lastBuildDate>Fri, 20 Jan 2012 16:00:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: rcollman</title>
		<link>http://www.clamp-it.org/2010/01/moodle-roles-explained/comment-page-1/#comment-32809</link>
		<dc:creator>rcollman</dc:creator>
		<pubDate>Tue, 20 Sep 2011 20:32:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.clamp-it.org/?p=604#comment-32809</guid>
		<description>It is important to remember that in some upgrade processes, the standard Moodle roles may roll back to the default permission set.  Where the new roles will not be impacted, excpet for new cabilities that have been added, which should assume the Archtype permissions for  the new cabilities.   This is similar to the best practice of not editing a standard theme. The best practice is to make a copy with a new name and tweak that.</description>
		<content:encoded><![CDATA[<p>It is important to remember that in some upgrade processes, the standard Moodle roles may roll back to the default permission set.  Where the new roles will not be impacted, excpet for new cabilities that have been added, which should assume the Archtype permissions for  the new cabilities.   This is similar to the best practice of not editing a standard theme. The best practice is to make a copy with a new name and tweak that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

