Note: You are currently viewing documentation for Moodle 2.3. Up-to-date documentation for the latest stable version is available here: Derek Chirnside.
News, August 9th. Taking a break from any bigger Moodle issues, like trying to work on basic issues that I've written up here to improve the core moodle, off to do a few weeks of other things.
2.1.1 is out, and I have a playground to see how things are. Not a lot of progress on the useabilility and speed of use/efficiency issues. These I think still make Moodle 2 harder to use in it's present state, now looking to 2.2.
Sad to see Tomaz gone http://tomazlasic.net/, but the classroom benefits. Good to see Moots still happening.
My latest thoughts on Professional Development. "Simple tools, Powerful learning activities" Just Groups, Forums and Files. (Maybe with quizzes). Writing this up at http://wikieducator.org/Moodle_2/Moving_On on Wikieducator. Too many people I have worked with have stalled after just a little Moodle staff development without getting a good grasp of what can actually be done. Too rushed and breathless. Teaching teachers is often like doing heart surgery and still keeping on with the hurley burley of teaching life.
I'm interested in the process of getting small fixes into core Moodle. There seem to be a number of no brainers, and I've often wondered what it needs to get things moving a little. I have also found it hard to follow the tracker. So, this is really list #3, after my list in 2009 and 2010. There is some progress, but it's been 2 steps forward, one step back:
- cohorts (but to make a cohort you need to chose each of the 200 names individually)
- blog comments (But the have removed blogs posts attached to courses)
- themes (but there is no one basic theme with the basic features in it in standard with Moodle now)
- better import and export of activities and resources (at a cost of difficulties in the file management)
- filters (but a lot of hard coding so they are inflexible)
- repositories (sort of)
Some musings. There is a lot of really good things we could do on Moodle. And there are a lot of good plugins. I'm interested in Core Vanilla Moodle. Big organisations can make the changes they want. Small organisations often can survive without them. Slightly bigger: like they don't link to an SMS and have to create 40 courses (No CSV new course upload), they use self enrolment (No e-mail sent to teacher) they can't install plugins (Like the menu to remove the scroll of death) . . .
I worry that the future development of Moodle will head down the lines of Mobile (taking a lot of resources from the basics) or Distros (like ELIS or Totara) or OU-type customisations. MoodleHQ may just not have the time or inclination to get the small helpful fixes into Moodle core.
Footnote: Mobile is interesting: at a Moodle workshop in Singapore in early June I was basically in a room full of folk with iPhone. It was a serious question "Moodle for Mobile" but really only the forums. I've changed my opinion: maybe Moodle for Mobile is needed.
- 1 A PERSONAL WISH LIST
- 2 ADMIN FUNCTIONS
- 3 ACCOUNTS, USERS AND ACCESS MANAGEMENT
- 4 OTHER ITEMS
- 5 MEDIA MANAGEMENT, LINK/UPLOAD SIMPLIFICATIONS
- 6 GROUPS
- 7 BLOGS
- 8 THE MOODLE DEVELOPMENT PROCESS
A PERSONAL WISH LIST
Admin: Cloning items
Coming soon in 2.1, I think.
ACCOUNTS, USERS AND ACCESS MANAGEMENT
A quick update --Derek Chirnside 09:41, 30 September 2012 (WST)
Admin Level: e-mail admin when person self registers account
- E-mail sent to user on manual account creation MDL-19390
- Discussion with code: http://moodle.org/mod/forum/discuss.php?d=85333
- Comment in Forums: http://moodle.org/mod/forum/discuss.php?d=204280
- Authentication: Add option for admin to confirm email based self-registrations: CONTRIB-1444
- NEW PLUGIN: http://moodle.org/mod/forum/discuss.php?d=212648
Manager/Admin: email notifications TO USER when a new manual account created
- Also: MDL-19851 :Messaging: Allow for personalization of message by using ##field## similar to database or [[filtertext]]"
- If you create an account, then you have to send a second message to tell the user of the account information. Tracker: MDL-19390
From the comments in 2009: "There is somewhat of a move away from directly sending emails because of the variety of forms that folks like to receive communications. For example, some users may want to receive an IM or SMS message from Moodle rather than an email. The goal is to use a united messaging system and then let the user control how that message gets sent out"
Teacher: Notification of first time visits/enrolment in a course
- Tracker item: Generate Email Notification to Teachers upon Student Enrollment in a Course MDL-20647
- Tracker item with code: Notify self-enrol by email MDL-20290
Admin: Bulk course create with CSV
Tracker item with code: http://tracker.moodle.org/browse/MDL-13114
Bulk delete, add, indent of items
Tracker item with code: http://tracker.moodle.org/browse/MDL-20213
Teach: E-mail to course members
Override forum setting.
Teach: Provide a quick 1<>1 forum/dialogue in core Moodle
Tracker: Convenience/usability: provide a simple way to provide teachers a 1<>1 conference, journal, conversation, dialogue forum with students. MDL-27223 Similar idea: Autocreate a group for each student in the course and the group name set to the first and last name MDL-21000
MEDIA MANAGEMENT, LINK/UPLOAD SIMPLIFICATIONS
To follow up: CSS to fix size of media: http://moodle.org/mod/forum/discuss.php?d=177107#p777043
Navigation problems with media:
Groups Self enrolment
Rationale: for a student centred/constructivist LMS to have no self signup for groups is a bit of a pity.
SORTED Site wide groups
Now called cohorts
Groups: CSV creation of cohorts
Tracker: Add ability to upload to a cohort via Upload users http://tracker.moodle.org/browse/MDL-26965
SORTED: Blogs: blogs visible at course level only
SORTED: blogs with comments
SORTED Book module in the core
THE MOODLE DEVELOPMENT PROCESS
Just some thoughts, largley unfinished at the moment - "We aim for a transparent and open development process that invites the whole user community to contribute. We welcome PHP programmers of course, but you can also contribute through discussions, testing, feedback and documentation" - from http://moodle.org/development/
- The process: https://docs.moodle.org/dev/Process (This is the latest version, there are others)
- Slightly orphaned talk Page: https://docs.moodle.org/20/en/Development_talk:Process
- Discussion on the process: http://moodle.org/mod/forum/discuss.php?d=174082
The process is still bedding down at the moment, and various developers have their perspectives: the phrases "I hope", "I'd like" and "Maybe" appear regularly in substantive discussions. I'm not convinced that it is working well at the moment. I'm sure it can be improved.
To be continued.