This is a test site. Any changes will be lost!

Roadmap: Difference between revisions

From MoodleDocs
No edit summary
 
(33 intermediate revisions by 5 users not shown)
Line 4: Line 4:
== Version 2.0 ==
== Version 2.0 ==


Expected very early 2009.
Expected mid 2009 <- ''this is obviously wrong! (or, at least, inaccurate) :-P''


===Major features===
===Major features===
* Moodle 2.0 will require PHP 5.2 as a minimum, allowing us to clean up the code in some areas.  For more info see: [http://gophp5.org/ gophp5.org].
* Moodle 2.0 will require PHP 5.2 as a minimum, allowing us to clean up the code in some areas.  For more info see: [http://gophp5.org/ gophp5.org].


* File handling improvements - Moodle.com
====File handling improvements====
** [[Development:File API|File API]] - maintains an internal repository of files and governs access to them
** [[Development:Repository API|Repository API]] - allows users to browse external repositories and select files to bring into Moodle
** [[Development:Portfolio API|Portfolio API]] - allows Moodle content to be captured and pushed out to external repositories.
:: These three are separate but complementary so will be developed together.


* [[Development:Conditional activities|Conditional activities]] - Moodle.com
* [[Development:File API|File API]] - Moodle.com
::Allowing dependencies and forced paths through activities: ie "You can't do this thing until that thing is completed".
::maintains an internal repository of files and governs access to them


* [[Development:Progress tracking|Progress tracking]] - Moodle.com, Catalyst and Google Summer of Code
* [[Development:Repository API|Repository API]] - Moodle.com
::AKA Proper competency tracking, so that individuals can have learning plans listing outcomes/courses which are updated when courses are completed.
:: allows users to browse external repositories and select files to bring into Moodle


* [[Development:HTML editor 2.0|HTML editor 2.0]]
* [[Development:Portfolio API|Portfolio API]] - Moodle.com
::Replaces our ageing HTMLarea with a new one that works on more browsers, enforces XHTML strict and better integrates with the new [[Development:File API|File API]]
:: allows Moodle content to be captured and pushed out to external repositories.


* [[Community hub]] interfaces - Moodle.com and others
:: These three are separate but complementary so will be developed together.
::Makes it easy for users to find and navigate other systems and external Moodle repositories, leveraging the Moodle Network in various ways.


* [[Development:Web_services|Standard Web Services Layer]] - UPC and moodle.com
====Improvements to the organisation of courses====
::Standard set of core API functions made available via SOAP and XML-RPC


* Old DB install/upgrade system removed
* [[Development:Conditional activities|Conditional activities]] - Open University (Sam Marshall)
:: The deprecated system for installing or upgrading database entries used in Moodle < 1.7 will be completely removed, while supporting only the new XML based database scheme introduced in 1.7.  
::Allowing dependencies and forced paths through activities: ie "You can't do this thing until that thing is completed".


* [[Development:dmllib 2.0|dmllib 2.0]]
* [[Development:Progress tracking|Progress tracking]] - REQUIRES FUNDING!
:: MDL-6605 Database access is to be refactored so that: we can use prepared statements everywhere for increased security and some performance, we put datalib functions in a class to allow better unit tests (mock db), and remove the need for slashes in userspace.  This will cause breakage for 3rd party modules (but fixing them won't be too hard).
::AKA Proper competency tracking, so that individuals can have learning plans listing outcomes/courses which are updated when courses are completed.


* [[Development:Pagelib_2.0|Pagelib 2.0]], [[Development:Blocks_2.0|Blocks 2.0]]
* [[Development:Pagelib_2.0|Pagelib 2.0]], [[Development:Blocks_2.0|Blocks 2.0]]   - REQUIRES FUNDING!
:: refactor Blocks and Pages using contexts to allow blocks to go anywhere in Moodle with better control.
:: refactor Blocks and Pages using contexts to allow blocks to go anywhere in Moodle with better control.


* [[Development:Course_completion|Course completion]]   
* [[Development:Course_completion|Course completion]]   
:: interface that allows teachers to specify exactly when a course should be considered finished for each user
:: interface that allows teachers to specify exactly when a course should be considered finished for each user
====Changes to activity modules====
* [[NWiki roadmap|New Wiki]] module (nwiki) - DFWikiteam-UPC
:: To be cleaned up and included as a core module.


* [[Feedback module]] - Andreas Grabs
* [[Feedback module]] - Andreas Grabs
:: Polished and included as a core module.
:: Polished and included as a core module.


* [[NWiki roadmap|New Wiki]] module (nwiki) - DFWikiteam-UPC
* Quiz module and question bank
:: To be cleaned up and included as a core module.
** [[Development:Quiz_report_enhancements|Quiz report enhancements]] - Jamie Pratt, contracted by The Open University
**: Major improvements to the quiz reports, especially regrading and item analysis.
** [[Development:quiz_navigation|Quiz navigation improvements for students]] - Tim Hunt, The Open University
** [[Development:Flagging_questions_during_a_quiz_attempt|Flagging questions during a quiz attempt]] - Tim Hunt, moodle.com.
** [[Development:Quiz_UI_redesign|Quiz editing interface improvements]] - Olli Savolainen, [http://www.coss.fi/web/coss/developers/sum Finnish Summer Code project].
** MDL-8648 Essay questions can now be randomised by random questions. <small>Note that this change is not backwards compatible if you upgrade a Moodle 1.9 site with random questions that pick from categories containing a mixture of essay and non-essay questions. The behaviour of some quizzes will change.</small> - Tim Hunt, moodle.com.
** [[Development:Moodle 2.0 question bank improvements|Question tagging and improved searching in the question bank]] - Tim Hunt, moodle.com.
** [[Development:Administration page for question types|Administration page for question types]] - Tim Hunt, moodle.com.
** [[Question_types#Regular_Expression_Short_Answer|Regular Expression question type]] added to the official Moodle distribution - Joseph Rézeau.
 
====Improvements to other bits of Moodle====


* [[Development:Quiz_report_enhancements|Quiz report enhancements]] - The Open University
* [[Development:HTML editor 2.0|HTML editor 2.0]] - Moodle.com
:: Major improvements to the quiz reports, especially regrading and item analysis.
::Replaces our ageing HTMLarea with a new one that works on more browsers, enforces XHTML strict and better integrates with the new [[Development:File API|File API]]


* Blog 2.0
* [[Student projects/Blog improvements|Blog 2.0]] - Moodle.com
:: Add commenting to blogs (MDL-8776), as well as support for external blogs  
:: Add commenting to blogs (MDL-8776), as well as support for external blogs  


* Messaging 2.0
* [[Development:Messaging_2.0|Messaging 2.0]] - Moodle.com
:: Refactor messaging to use plugins for input and output, controlled by users
:: Refactor messaging to use plugins for input and output, controlled by users


* Secure RSS feeds
* [[Student projects/Secure RSS feeds|Secure RSS feeds]] - Moodle.com
:: Obscure RSS feed URLs using private keys, controlled by users.
:: Obscure RSS feed URLs using private keys, controlled by users.
* [[Development:Backup_2.0|Backup 2.0]] - Moodle.com
:: New backup that actually works on large courses etc and is faster.  Old backup will be retained as a separate directory to import old backups.
* [[Development:IMS_CC|IMS Common Cartridge]] (REQUIRES FUNDING!)
:: IMS CC import and hopefully export.
* Site-wide groups - Moodle.com  (REQUIRES FUNDING!)
:: Site wide groups are a number one request


* More tagging
* More tagging
:: Tagging of courses, activities and other things
:: Tagging of courses, activities and other things


* AJAX for gradebook User Interfaces
* AJAX for gradebook User Interfaces - Moodle.com (REQUIRES FUNDING!)
:: A host of UI improvements to enhance usability and speed
:: A host of UI improvements to enhance usability and speed
* General usability review - Moodle.com
:: We'll be attacking many of the [http://tracker.moodle.org/browse/MDL/component/10309?selected=com.atlassian.jira.plugin.system.project:component-popularissues-panel most popular issues from the Moodle Tracker]
====Administrative improvements====
* [[Community hub]] interfaces - Moodle.com and others
::Makes it easy for users to find and navigate other systems and external Moodle repositories, leveraging the Moodle Network in various ways.
* [[Development:Web_services|Standard Web Services Layer]] - UPC and moodle.com
::Standard set of core API functions made available via SOAP and XML-RPC
* [[Development:Enrolment plugins 2.0|Enrolments improvements]] including groups synchronisation - moodle.com (skodak)
:: Several major improvements related guest access, course enrolments, metacourses and groups synchronisations (aka global groups)
* [[Development:Roles administration improvements for Moodle 2.0|Improvements to the roles administration interfaces]] - Tim Hunt, moodle.com and others.
* [http://tracker.moodle.org/browse/MDL-16348 Admin report plugins can choose where in the admin tree they get added] - Tim Hunt, moodle.com.
====Internal clean-ups====
* [[Development:DB layer 2.0|DB layer 2.0]] - Moodle.com
:: MDL-14679 Database access is to be refactored so that: we can use prepared statements everywhere for increased security and some performance, we put datalib functions in a class to allow better unit tests (mock db), and remove the need for slashes in userspace.  This will cause breakage for 3rd party modules (but [[Development:DB_layer_2.0_migration_docs|fixing them won't be too hard]]).
* Old DB install/upgrade system removed - Moodle.com
:: The deprecated system for installing or upgrading database entries used in Moodle < 1.7 will be completely removed, while supporting only the new XML based database scheme introduced in 1.7.


===Hopefully===
===Hopefully===
* [[Student Information API]]
* [[Student Information API]]
::API for integrating external systems for managing student information
::API for integrating external systems for managing student information
Line 74: Line 120:
::We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.
::We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.
* [[Turnitin Integration]] - Dan Marsden with support from Catalyst NZ
* [[Turnitin Integration]] - Dan Marsden with support from Catalyst NZ
* Improve usability
* Workshop module refactoring and re-inclusion - (REQUIRES FUNDING!)
:: Usability improvements for new and established users through increased field testing, selective feature availability, and research (such as the GSOC project).
* Lesson module refactoring - (REQUIRES FUNDING!)


==See also==
==See also==

Latest revision as of 20:24, 8 April 2011

This roadmap collects the best information about upcoming features in Moodle. It is not 100% certain - features may change according to available funding and developers.


Version 2.0

Expected mid 2009 <- this is obviously wrong! (or, at least, inaccurate) :-P

Major features

  • Moodle 2.0 will require PHP 5.2 as a minimum, allowing us to clean up the code in some areas. For more info see: gophp5.org.

File handling improvements

maintains an internal repository of files and governs access to them
allows users to browse external repositories and select files to bring into Moodle
allows Moodle content to be captured and pushed out to external repositories.
These three are separate but complementary so will be developed together.

Improvements to the organisation of courses

Allowing dependencies and forced paths through activities: ie "You can't do this thing until that thing is completed".
AKA Proper competency tracking, so that individuals can have learning plans listing outcomes/courses which are updated when courses are completed.
refactor Blocks and Pages using contexts to allow blocks to go anywhere in Moodle with better control.
interface that allows teachers to specify exactly when a course should be considered finished for each user

Changes to activity modules

  • New Wiki module (nwiki) - DFWikiteam-UPC
To be cleaned up and included as a core module.
Polished and included as a core module.

Improvements to other bits of Moodle

Replaces our ageing HTMLarea with a new one that works on more browsers, enforces XHTML strict and better integrates with the new File API
Add commenting to blogs (MDL-8776), as well as support for external blogs
Refactor messaging to use plugins for input and output, controlled by users
Obscure RSS feed URLs using private keys, controlled by users.
New backup that actually works on large courses etc and is faster. Old backup will be retained as a separate directory to import old backups.
IMS CC import and hopefully export.
  • Site-wide groups - Moodle.com (REQUIRES FUNDING!)
Site wide groups are a number one request
  • More tagging
Tagging of courses, activities and other things
  • AJAX for gradebook User Interfaces - Moodle.com (REQUIRES FUNDING!)
A host of UI improvements to enhance usability and speed
  • General usability review - Moodle.com
We'll be attacking many of the most popular issues from the Moodle Tracker

Administrative improvements

Makes it easy for users to find and navigate other systems and external Moodle repositories, leveraging the Moodle Network in various ways.
Standard set of core API functions made available via SOAP and XML-RPC
Several major improvements related guest access, course enrolments, metacourses and groups synchronisations (aka global groups)

Internal clean-ups

MDL-14679 Database access is to be refactored so that: we can use prepared statements everywhere for increased security and some performance, we put datalib functions in a class to allow better unit tests (mock db), and remove the need for slashes in userspace. This will cause breakage for 3rd party modules (but fixing them won't be too hard).
  • Old DB install/upgrade system removed - Moodle.com
The deprecated system for installing or upgrading database entries used in Moodle < 1.7 will be completely removed, while supporting only the new XML based database scheme introduced in 1.7.

Hopefully

API for integrating external systems for managing student information
Moodle Voice is a project for embedding VoiceXML support into Moodle Core.
We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.
  • Turnitin Integration - Dan Marsden with support from Catalyst NZ
  • Workshop module refactoring and re-inclusion - (REQUIRES FUNDING!)
  • Lesson module refactoring - (REQUIRES FUNDING!)

See also

Retrieved from "https://docs.moodle.org/test/index.php?title=Roadmap&oldid=49217"
Powered by MediaWiki