General discussion

Keeping track of and contributing to MoodleNet

 
Picture of Doug Belshaw ๐Ÿ‡ช๐Ÿ‡บโ˜ ๏ธโœŠ
Keeping track of and contributing to MoodleNet
 

Architecture of participation v2

As the MoodleNet project develops, it's important to ensure we're using the best tools for job. This post explains that we're moving on from using Trello in favour of other platforms.

>>>ย Click here for the postย <<<ย ย 

We're particularly interested in your feedback on Changemap. What do you think of the tool? It's currently in beta and the developer is asking for feedback. Please do respond in the comments section of the post or here on the forum.

Picture of Matteo Scaramuccia
Re: Keeping track of and contributing to MoodleNet
 

Hi Doug,
I'm still lurking here and this might be a silly question blush, so I apologize in advance: I've just realized that code will be contributed via GitLab and not via GitHub (GH): does it relate to M$ having "almost" acquired GH or to the lack of some features in GH?

TIA,
Matteo

Picture of Doug Belshaw ๐Ÿ‡ช๐Ÿ‡บโ˜ ๏ธโœŠ
Re: Keeping track of and contributing to MoodleNet
 

Good question, Matteo!

I think there were many people in open source development who were uneasy about GitHub hosting much of the world's open source code, without it being open source itself. Microsoft's acquisition brought that into sharp focus.

Moodle HQ in fact uses already uses GitLab for development and mirrors this to GitHub for code contribution. MoodleNet will be working a little more publicly, hence our GitLab being available via the gitlab.com site.

In terms of functionality and features, GitLab has a really nice way of dealing with issues across multiple projects (repositories). We're aware, though, that not everyone feels comfortable in that sort of environment, hence Changemap smileย 

Picture of Matteo Scaramuccia
Re: Keeping track of and contributing to MoodleNet
 

TNX Doug for your reply Yes.

Matteo