Hackfest UK 2014: Difference between revisions
From MoodleDocs
No edit summary |
(Adding other topics) |
||
| Line 36: | Line 36: | ||
* Git | * Git | ||
==Specifications== | == Specifications == | ||
Specifications from subsequent work will be linked from here | Specifications from subsequent work will be linked from here | ||
| Line 58: | Line 58: | ||
* [[Add-ons trust model]] | * [[Add-ons trust model]] | ||
* [https://docs.google.com/document/d/15hme5Ky_YVQzks78HjDt8-kmZ3sT71WI4a_AK2LkSc8/edit Drag and Drop activities notes] | * [https://docs.google.com/document/d/15hme5Ky_YVQzks78HjDt8-kmZ3sT71WI4a_AK2LkSc8/edit Drag and Drop activities notes] | ||
== Other suggested topics == | |||
These are topics that were suggested, but were not chosen for sessions (unconference style), but may be worth future consideration. | |||
* MUC best practice discussion | |||
* Converter for Word docs to pages (possibly with drag-and-drop) | |||
* Student > Group > Course > Qualification > Body hierarchy | |||
* Internal verification and validation | |||
* Course reset for blocks and local plugins | |||
* RTL CSS as a separate file | |||
* Global change data recorded on database tables | |||
* In course search | |||
* Resource tagging / Index | |||
* Sharepoint integration repository | |||
* Scheduled fileless backups | |||
* How the OU does "View as student" | |||
* Better way to hide activities, but have them available | |||
* All communication via messaging sends multi-part emails | |||
* "Safe" group membership upload/import | |||
* Facebook style "Like" button or + and - buttons for ratings | |||
* Blind marking issues for administrative users | |||
Revision as of 04:46, 2 May 2014
Developer meetings > UK Hackfest April 2014
| When | Thursday 17 April, 2014 |
| Where | Moodlemoot Edinburgh, UK |
| Hashtag | #mootuk14 |
What happened?
A Hackfest brings together Moodle developers to brainstorm future Moodle developments.
This hackfest had a group of around 40 developers. We met in Edinburgh on 17th April 2014 to discuss a range of topics (decided by the participants in unconference fashion), wth an aim to distilling knowledge into some blueprints for specifications of future Moodle features.
Group notes
Tools
- Php Xref
- Xdebug + IDE
- XHprof
- codechecker
- PHPUnit
- MDK
- Moosh
- Grunt
- Git
Specifications
Specifications from subsequent work will be linked from here
Session 1
Session 2
- Lesson refactoring notes
- A few more thoughts --Michael Hughes (talk) 17:38, 22 April 2014 (WST)
- Email Logging Functionality and Reporting notes
- Bootstrap3 notes
Session 3
Other suggested topics
These are topics that were suggested, but were not chosen for sessions (unconference style), but may be worth future consideration.
- MUC best practice discussion
- Converter for Word docs to pages (possibly with drag-and-drop)
- Student > Group > Course > Qualification > Body hierarchy
- Internal verification and validation
- Course reset for blocks and local plugins
- RTL CSS as a separate file
- Global change data recorded on database tables
- In course search
- Resource tagging / Index
- Sharepoint integration repository
- Scheduled fileless backups
- How the OU does "View as student"
- Better way to hide activities, but have them available
- All communication via messaging sends multi-part emails
- "Safe" group membership upload/import
- Facebook style "Like" button or + and - buttons for ratings
- Blind marking issues for administrative users
