Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Developer meeting January 2014: Difference between revisions

From MoodleDocs
mNo edit summary
(Saving meeting notes)
Line 16: Line 16:
|}
|}


In this meeting we will focus on Moodle development happening outside Moodle HQ.  
In this meeting we focused on Moodle development happening outside Moodle HQ.  


The meeting will be streamed live on YouTube with chat through the regular Dev chat room and comments on Twitter.
The meeting was streamed live on YouTube with chat through the regular Dev chat room and comments on Twitter.


== Agenda ==
== Agenda ==
* Quiz editing changes (Tim Hunt, Colin Chamber, Mahmoud Kassaei, OU)
=== Possible future changes to Conditional Activities (Sam Marshall, OU) ===
* Possible future changes to Conditional Activities (Sam Marshall, OU)
* More flexible, plug-able conditions
* Moodle 2.7 progress
* Better access through groupings
** Prototypes site (Martin Dougiamas)
* Better interface, lean and mean
** Clean as default theme (Jérôme Mouneyrac)
* No docs yet, spec and issues coming
*** Should we move most themes to Plugins Directory?
 
*** Bootstrap 3?
=== Quiz editing changes (Tim Hunt, Colin Chamber, Mahmoud Kassaei, OU) ===
** Editor replacement (Damyon Wiese)
* [https://tracker.moodle.org/browse/MDL-40987 Issue], [https://moodle.org/mod/forum/discuss.php?d=231180 Discussion]
** Old Assignment removal (Damyon Wiese)
* Dependency between questions as a user works through a quiz
** Outcomes (Andrew Davis)
* Improving the interface to make it simpler, similar to course page editing, which people are familiar with.
** New logging (Rajesh Taneja)
* Possibly a new "combinable" question type that allows something similar to cloze, but with a simpler interface.
* Moodle Mobile update (Juan Leyva)
* Possibly other OU question types coming to core. It would be good if the community could provide feedback on what's in the Plugins Directory currently.
* Integration update  (Dan Poltawski)
 
** Pre-checking of issues by CiBot
=== Moodle 2.7 progress ===
** Testing requirements
=== Prototypes site (Martin Dougiamas) ===
** Behat improvements
* [http://prototypes.moodle.net prototypes.moodle.net]
** Misc
* A site for early development to gather feedback
* Long term support (Martin Dougiamas)
* Projects currently there include navigation, editor replacement, forum changes, outcomes...
* A better video conferencing solution for Gen Dev meetings? (Michael de Raadt)
 
=== Clean as default theme (Jérôme Mouneyrac) ===
* [https://docs.google.com/presentation/d/1eea9oQj1bihpWpsYJGstX_CASLBFF7N51M6DLquixK0/edit?pli=1#slide=id.g2a33bfb2a_097 Notes]
* Resolve open bugs
* Default theme on new install
* Increase configurability, requires ability to compile LESS on-the-fly.
* New navigation is being considered
* Adding an element library
* Allow people to add bootswatches
* It intended that we will move most themes to Plugins Directory (not Standard, Clean or base themes)
* Bootstrap 3 has been considered and won't be adopted yet
 
=== Editor replacement (Damyon Wiese) ===
* [https://docs.moodle.org/dev/Editor_2.7 Docs]
* TinyMCE3 is out of support
* Editor is critical part of Moodle and has huge impact on user experience
* Editor search narrowed down to TinyMCE4, CKEditor and Atto.
* Prototypes were put up and feedback requested.
* Tending towards Atto, with a CKEditor in the Plugins Directory for those who want it.
 
=== Old Assignment removal (Damyon Wiese) ===
* [https://tracker.moodle.org/browse/MDL-33952 Issue]
* The old assignment has been removed and on upgrade instances of the old assignment will be converted to the new.
* If you are using an old assignment type that is not represented in the new assignment you will have to install the old assignment module from the Plugins Directory
 
=== Outcomes (Andrew Davis) ===
* [https://tracker.moodle.org/browse/MDL-40230] Issue, [https://docs.moodle.org/dev/Outcomes_Specification Docs]
* A lot of work done on Outcomes before 2.6 that didn't make it into the release.
* We're reviewing Totara and Elis to see what features are needed overall.
 
=== New logging (Rajesh Taneja) ===
* New events system is in place
* Old logging calls are being converted to events
* More information captured than previous logging
* Performance is an issue, with more events being captured
** Initiatives to optimise DB queries with a single batch insert at the end of a page load.
* Ability to create new observers to reduce the reliance on the log table for real-time analytics
* Logging system is more plugable.
** Potential to push logs to external database
 
=== Moodle Mobile update (Juan Leyva) ===
* New version of app coming soon
* Potential to use the app from the desktop
 
=== Integration update  (Dan Poltawski) ===
* Pre-checking of issues by CiBot (Continuous integration bot) automated checks on changes before they are submitted to integration (waiting for integration, peer review or with label "cime") ([https://tracker.moodle.org/browse/MDLSITE-2662 Issue])
* Testing requirements
** PHPUnit or Behat tests required for changes
* Behat improvements
** Working on Linux and Windows. Firefox is the preferred browser. Chrome is being improved. IE is somewhat working and Safari... ([https://docs.moodle.org/dev/Acceptance_testing/Browsers Docs])
** You can get automatic screenshots when a test fails ($CFG->behat_screenshots_path: [http://git.moodle.org/gw?p=moodle.git;a=blob;f=config-dist.php#l659 link])
** Parallel Behat testing ([https://tracker.moodle.org/browse/MDL-39752 issue])
* Misc
** Specific rules for [https://docs.moodle.org/dev/Integration_Review#Backporting backporting]
** Please be aware of the [https://docs.moodle.org/dev/Integration_Review#Schedule weekly integration schedule]
 
=== Long term support (Martin Dougiamas) ===
* 2.7 is going to be a long-term release that will be supported for longer (3 years instead of 18months)
* Backports will be required to backport bug-fixes to the LTS release
 
=== A better video conferencing solution for Gen Dev meetings? (Michael de Raadt) ===
* F.lux was suggested
* GoToMeeting (no free)


Questions
Questions

Revision as of 06:51, 22 January 2014

Developer meetings > January 2014 meeting notes

Time 13:00 UTC on Tuesday, 21 January 2014
Meeting room Moodle HQ YouTube channel (changed since last meeting)
Chat Regular Dev chat
Twitter #moodledev

In this meeting we focused on Moodle development happening outside Moodle HQ.

The meeting was streamed live on YouTube with chat through the regular Dev chat room and comments on Twitter.

Agenda

Possible future changes to Conditional Activities (Sam Marshall, OU)

  • More flexible, plug-able conditions
  • Better access through groupings
  • Better interface, lean and mean
  • No docs yet, spec and issues coming

Quiz editing changes (Tim Hunt, Colin Chamber, Mahmoud Kassaei, OU)

  • Issue, Discussion
  • Dependency between questions as a user works through a quiz
  • Improving the interface to make it simpler, similar to course page editing, which people are familiar with.
  • Possibly a new "combinable" question type that allows something similar to cloze, but with a simpler interface.
  • Possibly other OU question types coming to core. It would be good if the community could provide feedback on what's in the Plugins Directory currently.

Moodle 2.7 progress

Prototypes site (Martin Dougiamas)

  • prototypes.moodle.net
  • A site for early development to gather feedback
  • Projects currently there include navigation, editor replacement, forum changes, outcomes...

Clean as default theme (Jérôme Mouneyrac)

  • Notes
  • Resolve open bugs
  • Default theme on new install
  • Increase configurability, requires ability to compile LESS on-the-fly.
  • New navigation is being considered
  • Adding an element library
  • Allow people to add bootswatches
  • It intended that we will move most themes to Plugins Directory (not Standard, Clean or base themes)
  • Bootstrap 3 has been considered and won't be adopted yet

Editor replacement (Damyon Wiese)

  • Docs
  • TinyMCE3 is out of support
  • Editor is critical part of Moodle and has huge impact on user experience
  • Editor search narrowed down to TinyMCE4, CKEditor and Atto.
  • Prototypes were put up and feedback requested.
  • Tending towards Atto, with a CKEditor in the Plugins Directory for those who want it.

Old Assignment removal (Damyon Wiese)

  • Issue
  • The old assignment has been removed and on upgrade instances of the old assignment will be converted to the new.
  • If you are using an old assignment type that is not represented in the new assignment you will have to install the old assignment module from the Plugins Directory

Outcomes (Andrew Davis)

  • [1] Issue, Docs
  • A lot of work done on Outcomes before 2.6 that didn't make it into the release.
  • We're reviewing Totara and Elis to see what features are needed overall.

New logging (Rajesh Taneja)

  • New events system is in place
  • Old logging calls are being converted to events
  • More information captured than previous logging
  • Performance is an issue, with more events being captured
    • Initiatives to optimise DB queries with a single batch insert at the end of a page load.
  • Ability to create new observers to reduce the reliance on the log table for real-time analytics
  • Logging system is more plugable.
    • Potential to push logs to external database

Moodle Mobile update (Juan Leyva)

  • New version of app coming soon
  • Potential to use the app from the desktop

Integration update (Dan Poltawski)

  • Pre-checking of issues by CiBot (Continuous integration bot) automated checks on changes before they are submitted to integration (waiting for integration, peer review or with label "cime") (Issue)
  • Testing requirements
    • PHPUnit or Behat tests required for changes
  • Behat improvements
    • Working on Linux and Windows. Firefox is the preferred browser. Chrome is being improved. IE is somewhat working and Safari... (Docs)
    • You can get automatic screenshots when a test fails ($CFG->behat_screenshots_path: link)
    • Parallel Behat testing (issue)
  • Misc

Long term support (Martin Dougiamas)

  • 2.7 is going to be a long-term release that will be supported for longer (3 years instead of 18months)
  • Backports will be required to backport bug-fixes to the LTS release

A better video conferencing solution for Gen Dev meetings? (Michael de Raadt)

  • F.lux was suggested
  • GoToMeeting (no free)

Questions

  • What are the plans in 2.7 for Gradebook improvements?
  • Will the base theme no longer receive updates or be actively worked on?
  • Anymore changes to the event system? We want to start planning/scoping out analytics/alerts using the new event system in 2.6, but don't want to progress if more changes are expected.
  • Global Search ?
  • Any plans to actually treat the code freeze deadline as a code freeze for 2.7?

If you have something you'd like to add to the agenda, please edit this page or contact Michael d.

Retrieved from "https://docs.moodle.org/dev/index.php?title=Developer_meeting_January_2014&oldid=43602"
Powered by MediaWiki