Martin Dougiamas

Hi all,

I'm really happy to announce that the new Moodle Plugins database is now live!  (at last)

It doesn't have much data in it yet, so it's not quite ready to replace the old Modules and Plugins database.

We would now like you (Moodle developers!) to start adding your own plugins to the new database.  You'll need to register a new entry for the plugin itself, and then create a "version" within that plugin every time you make a release.  At first you'll have to wait for everything to be approved before it goes live, but trusted developers will get more privs later.

Once we have a critical mass of data we'll start directing everyone there to the new one and will gently retire the old one (but keep it visible for reference purposes, since I suspect a lot of old stuff in there will never (and should never) be migrated to the new one).

Eventually the new database will also be the source of data for a new "Check for updates" feature within Moodle, that's why we are being very strict about the naming and formatting in this one.

It will also be the location for official reviews of plugins for security, accessibility etc

Thanks to Sam, Marina, Anthony, Michael and everyone else who has helped getting the database where it is so far.  We'll keep continuing to tweak and improve it while it gathers data and feedback.

Cheers,
Martin

You'll have to ask the Sloodle team: http://slurl.com/secondlife/sloodle/129/129/24

Best of luck!

I've made an issue for you here, Tim     MDL-28308

Please add comments and votes there.

You need to take these case-by-case I think.

Please remember that the main docs are now focussed on being user docs, about the Moodle software itself.

1) Performance is version-specific.  They will vary more and more.  It makes sense to have versioned pages.  And yes there will be common stuff ... people need to start being aware of which version they are editing and remember to update the latest as well (if they aren't already doing so).

2) These sort of pages (installation/upgrades) are extremely version-specific, and also good candidates to add specific links to other versions of the page to help people get to the right place.

3) Code of conduct, and anything else like that which is not part of the user documentation for Moodle itself should go to other places.  Policy stuff can move straight on moodle.org as a normal uneditable web page.  The list of user groups could go into a Moodle wiki on moodle.org, or a database.  Anything development-related must move to the development wiki (that includes versions, release notes and roadmaps etc).

+100 on WebDAV. Tim has described it well.

The main thing allowing write access would be Private Files, that's easy to manage as it's all one user and you have full privs.

Secondly would be "folder" and "file" resources, and possibly legacy course file areas.

More could be added later.