Front-end development workshop with Outlandish (19th-21st September 2018)

Whiteboard

This week, the MoodleNet team were in London to work with Outlandish for a workshop on front-end development. Doug Belshaw (MoodleNet Lead) and Mayel de Borniol (Technical Architect) worked with Kayleigh Walsh (project manager), Sam Gluck (developer), and Rob Cornish (designer) on various aspects of how MoodleNet is going to work, look, and feel.

Given that we went into the workshop with a number of assumptions, it was useful to get these out onto the table. Doing so in an open way allowed us to challenge these assumptions in productive ways, leading to some useful decisions.

Everything from the three-day workshop can be found on our GitLab issues board, the highlights of which are perhaps:

We’re planning to continue working with Outlandish around front-end development as we lead up to the beta release, scheduled for January 2019. This will lead to a couple of new front-end development milestones, which we’re currently thrashing out.

Excitingly, next week we’ll be welcoming a new member of our team. More on that soon!

Introducing MoodleNet at ALT-C

Update: watch the recording of the session here!

This week, Doug Belshaw (MoodleNet Lead) is in Manchester, UK for the Association for Learning Technology’s annual conference, ALT-C.

Doug is presenting directly after the keynote in the main auditorium today, giving participants an overview of what MoodleNet is and how they can get involved in shaping it. The slides can be found embedded at the top of this post, or via this link: bit.ly/moodlenet-altc

GitLab issue board

GitLab overview

As mentioned previously, we’ve moved away from Trello cards to keep track of the MoodleNet project. The best link to get an overview of all the issues we’re currently working on at the moment can be found at this link or by clicking on the image above.

We’ve also updated the overview slide deck to v0.7, accessible here.

As ever, you can find everything you need relating to MoodleNet at https://moodle.com/moodlenet

Introducing MoodleNet ‘office hours’

Update: this will now be an hour later at 14:00 UTC.

OPEN

A few months ago, due to advice we received around GDPR legislation in the EU, we postponed future community calls. Now that summer holidays are over in the northern hemisphere, we have some good news!

After further consideration and discussion, we’ve decided to institute ‘office hours’ for the MoodleNet project. These will be times in which the core team (currently Doug Belshaw and Mayel de Borniol) will be available to take your suggestions and answer your questions and concerns.

Our first office hours:

Note that we’re using Zoom to connect, which you’ll need to download and configure beforehand. There’s no set agenda and we won’t be recording the office hours.

If this proves successful, we will run monthly office hours and be more accommodating to various timezones. You are, of course, welcome to interact with this project in a number of other ways, including the discussion forum and our Changemap.

*Alternatively, dial in:
US: +1 669 900 6833 or +1 646 876 9923
Meeting ID: 968 146 5087
International numbers available: https://zoom.us/u/laeOX


Image from pxhere used under a Creative Commons license

Keeping track of and contributing to MoodleNet

MoodleNet architecture of participation v2

Product management is a delicate balancing act between allowing enough ‘wiggle-room’ for innovation while imposing enough discipline to get things done. After all, scope creep applies just as much to the tools we choose to use to complete the project as the output of the project itself.

We’ve been using Trello to keep ourselves organised since the start of the MoodleNet project. While we really like and value that platform, we’ve made the decision to take a different approach for the next stage of the project.

Going forward we’re going to streamline things a little by using the following platforms:

  • Teamwork.com – internal updates, planning, and potentially sensitive information (Moodle HQ members only)
  • Changemap – community-suggested ideas and features
  • Moodle.org – discussions with the Moodle community
  • GitLab – contribute code and find out more about the technical side of MoodleNet

The Trello board we were using remains as an archive of the first five sprints. As ever, the canonical URL for the project (i.e. the one to share) is moodle.com/moodlenet.


Note: we’ve updated the Contributing page on the wiki to reflect these changes.

We’re hiring a Backend Developer for the MoodleNet project!

Now that we’ve made some progress on defining what the first version of MoodleNet will look like and how the ActivityPub-based technical architecture will work (using the Elixir/Erlang stack on the back-end), we have a unique opportunity for a developer to build the federated back-end for MoodleNet.

This is a flexible position and can be based remotely, or out of the new Moodle office in Barcelona. View the job listing for details, and please pass this along to any developer you know who might be interested.

MoodleNet UX Milestone 2: Screencast #4

Over the last few weeks, we’ve been working on UX Milestone 2 with Outlandish. This is the fourth and final screencast from that work, in which we demonstrate how we envisage sending a MoodleNet collection to a Moodle site might work.

You can check out Screencast #1Screencast #2, and Screencast #3 if you missed them.

Remember, this is a prototype with no code behind it. We’re very interested in your opinions, which you can leave in several places:

  1. In the comments section below this post
  2. On the Moodle.org forum
  3. In the comments section of the YouTube video
  4. As a suggestion on our Changemap

MoodleNet UX Milestone 2: Screencast #3

We’ve been working on a series of screencasts as part of our UX Milestone 2 work with Outlandish. You can check out Screencast #1 and Screencast #2 if you missed them.

In this third screencast, we’re demonstrating the user flow for new user sign-up in MoodleNet.

Remember, this is a prototype with no code behind it. We’re very interested in your opinions, which you can leave in several places:

  1. In the comments section below this post
  2. On the Moodle.org forum
  3. In the comments section of the YouTube video
  4. As a suggestion on our Changemap

MoodleNet UX Milestone 2: Screencast #2

Yesterday we posted Screencast #1 from our UX Milestone 2 work with Outlandish. In this second screencast, we’re demonstrating an example of the user flow for adding an ‘Alt account’ in MoodleNet.

Remember, this is a prototype with no code behind it. We’re very interested in your opinions, which you can leave in several places:

  1. In the comments section below this post
  2. On the Moodle.org forum
  3. In the comments section of the YouTube video
  4. As a suggestion on our Changemap

MoodleNet UX Milestone 2: Screencast #1

We’ve been continuing our work with Outlandish on MoodleNet UX. In this first screencast from Milestone 2, we’re demonstrating an example of the user flow for adding a resource in MoodleNet.

Remember, this is a prototype with no code behind it. We’re very interested in your opinions, which you can leave in several places:

  1. In the comments section below this post
  2. On the Moodle.org forum
  3. In the comments section of the YouTube video
  4. As a suggestion on our Changemap