Thanks for the dialogue on this...I was a bit thrown off by the issue of school's claiming ownership over a teacher's lesson plan and created educational materials and realize it's really a legal issue. I joined the cc-education list and submitted my concerns there as well...is that the legal list you speak of or is there another way to get 'lawyerly love'.
Back to the cchost issues...I'll look into adding a patch by comparing with what is in the Moodle code. Both of the features i discussed are an integral part of moodle and offer on/off features...so I don't think this should be too difficult to implement I just need to isolate the code and make some minor adjustments.
When submitting a patch what is proper procedure for doing so?
My instinct is to make minor code adjustments to existing files which reference any complete features as separate files...
Anyway once I isolate the moodle code I may pick your brain on where/how you think the best way to implement would be.
On 4/26/06, Jon Phillips <email@example.com> wrote:
On Wed, 2006-04-26 at 11:06 -0700, Victor Stone wrote:
> On 4/26/06, Zero Mass <
> > Is it possible to restrict registered users to a specific email domain?
> > (like .edu?)
> not without adding code. There is an event that's fired on every form
> submit/verification and you could catch that and validate the email
> field of the profile form.
Maybe this is some code that you would like to contribute to the
> > Or possible to restrict downloads to only registered users? (forcing a
> > registry before browsing, moodle does this)
> That won't happen because it would be counter to the Creative Commons
> philosophy behind providing ccHost in the first place.
Actually, I think there are several places where this could be a useful
feature, like for working in groups, or having some private content.
Maybe you could provide a patch to support this type of situation you
propose. I don't want to detract from your ideas, but want to support
you if you really want to implement this.
> > These issues are coming up with school systems in regards to who can access
> > the site...
> > (students being able to download homework with answer keys, etc)
> again, CC hosting is about sharing, not restricting.
Yet again, I would say that if you want to submit a patch to support
this, I think this is great. I really think the best way to deal with
this is to add proper users and groups to ccHost. Please see my other
email...the best way to see this type of custom feature is to submit a
software patch. Think about how you can expand ccHost and make whatever
you submit optionally turned on/off.
> > Another semi-related issue is that some school districts I have emailed are
> > actually claiming to hold an All Rights Reserved copyright over the
> > educational materials that their teachers create, prohibiting them from
> > sharing on a site.
> Then it's quite possible that a Creative Commons hosting tool may not
> be appropriate in those cases.
IMO I think that cchost would be a great tool for your needs. I just
think there are some custom tweaks that you need, and the easiest way is
to submit some patches to the codebase which can be optionally enabled,
and are not hardcoded, which would help you and other projects in a
I really think the best approach to developing this ccHost solution is
to implement proper user and group permissions that could be used to
govern different types of content.
While I work for CC and support many of the ideals, it is really up to
this community to decide the direction of this community-based project
through participation and code contribution.