Note:

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

MoodleNet/1.0/Decision Log: Difference between revisions

From MoodleDocs
No edit summary
No edit summary
Line 5: Line 5:
This page serves as a log of decisions made during the development of the MoodleNet project, along with a brief justification.
This page serves as a log of decisions made during the development of the MoodleNet project, along with a brief justification.


* 21 Sep 18 - We've decided that integration with [https://openbadges.org Open Badges] are going to be out of scope for MVP in January. This is because of the extra work we'd need to do to implement them, and also because Moodle Core should have compatibility with v2.0 of the OB spec by then. We're fully intending badges to be a part of MoodleNet post-MVP.
* 20 Sep 18 - We [https://gitlab.com/moodlenet/clients/react/issues/17 reviewed some of the assumptions] we've made during the project so far, and documented some decisions around them
* 20 Sep 18 - We [https://gitlab.com/moodlenet/clients/react/issues/17 reviewed some of the assumptions] we've made during the project so far, and documented some decisions around them
* 17 Sep 18 - We're dropping the idea of providing [https://blog.moodle.net/2018/ux-milestone-2-screencast-2/ 'alt' accounts] as it's a solution looking for a problem, for the time being.  
* 17 Sep 18 - We're dropping the idea of providing [https://blog.moodle.net/2018/ux-milestone-2-screencast-2/ 'alt' accounts] as it's a solution looking for a problem, for the time being.  

Revision as of 08:48, 26 September 2018

<< Back to MoodleNet index


This page serves as a log of decisions made during the development of the MoodleNet project, along with a brief justification.

  • 21 Sep 18 - We've decided that integration with Open Badges are going to be out of scope for MVP in January. This is because of the extra work we'd need to do to implement them, and also because Moodle Core should have compatibility with v2.0 of the OB spec by then. We're fully intending badges to be a part of MoodleNet post-MVP.
  • 20 Sep 18 - We reviewed some of the assumptions we've made during the project so far, and documented some decisions around them
  • 17 Sep 18 - We're dropping the idea of providing 'alt' accounts as it's a solution looking for a problem, for the time being.
  • 22 Aug 18 - While whole collections may be imported from MoodleNet into Moodle, when submitting a resource from Moodle to MoodleNet, we'll do this one at a time.
  • 6 Aug 18 - Elixir will be the main programming language used by MoodleNet's back-end
  • 13th June 18 - Initial integration will be with MoodleCloud, as that makes it easier in terms of versioning and tightly controlling data flows.
  • 6th June 18 - We're going to use GitLab now that Microsoft has acquired GitHub.
  • 23rd Apr 18 - Martin has decided we are going with the name 'MoodleNet'.
  • Feb 18 - the MVP should be focused on resource curation so that we're not just dropping people into a social network that doesn't have a particular purpose
  • 9th Jan 18 - Renaming 'News feed' component of project to 'Activity feed' to more accurately describe what we're developing.
  • 3rd Jan 18 - Social sign-in shouldn't be the only way to log in to Project MoodleNet (rationale)