move curriculum content to github

[mikelmaron]

Lot of content in the moodle. Let's think about how to structure this in GitHub, where it's easier to revise and reuse

[russdeffner]

I think this is related to #77?

[mikelmaron]

Not entirely. #77 is about setting up GitHub tickets to track actions needs on the curriculum. This ticket is about finding a flexible home for the content.

Does moodle have an export function?

[russdeffner]

I am not entirely sure off-the-top of my head, but it's got a whole bunch of stuff I don't know about. I think before we 'export' or try to make an editable source, it's needs a 'once-over'. In general, maybe it's best to try and research some 'best practices' for moodle up-keep (and translation, etc. - which I do know there is a built-in function, just haven't got there yet).

[dalekunce]

+1 for @mikelmaron suggestion. To give it the once over lets port everything here. It will make collaborating a lot easier with PRs and such.

[russdeffner]

Ok, I'm making some minor corrections today; will hold off on anything 'major'.

[smit1678]

@russdeffner @mikelmaron @dalekunce Is there interest to pick up this conversation again? Was this discussed in the Training or Activation working groups when this was brought up originally?

[smit1678]

It looks like it was picked up in #89

[russdeffner]

Yes, we can probably close this one. Porting content to gitbooks is on hold at the moment, but I have been doing some direct updating of courses as necessary to keep everything complete-able. Came up in last Training WG and will probably continue there until AWG is restarted.

[smit1678]

Ok thanks @russdeffner, was there a specific reason for putting this on hold or just the time and ability to do it?

I'll throw some notes up for the next Training WG meeting. I'd like to talk through some other documentation needs that fit under both the Tech and Training WG and so it'd be good to discuss and coordinate.

[mikelmaron]

@smit1678 I think it would be great to have consistent framework and style guidance across all HOT documentation projects. Moving to GitBooks for several pieces, like the activation curriculum, could be a solid move.

[russdeffner]

This is a duplicate of #89

[smit1678]

From Tech WG on March 20, we talked about how this needs to be revisited, partly because of need to help unify content and partly because of need to look at our hosting of tools. Overall we're in agreement that content would benefit from moving to Github and Gitbooks (some is already in LearnOSM). But still need to resolve the process side of Courses.

Considerations:

• Managing the onboarding process. Managing users who have reviewed the content and express interest in getting involved during an Activation, getting endorsements, and finding mentors.
• OpenBadges was raised as an important connection with Moodle
• Having a good entry point to the content and process

Other questions I have to help us hone in on solutions:

• Do quizzes put a barrier to going through the process? Can this be done with a good 1:1 onboarding process for individuals interested?
• Do people use OpenBadges a lot and is it critical to the process?

Next steps here are to outline some ideas to be discussed at next AWG.

[russdeffner]

Here is the link to the Gitbooks site we started copying content to: https://www.gitbook.com/book/bgirardot/hotosm-activation-curriculum/details (originally posted by Mikel in #89

[russdeffner]

This has been done, https://github.com/russdeffner/ActivationCurriculum & https://russdeffner.gitbook.io/curriculumworkspace/ - next, need to clone it to the HOT github. Anything I need to know before requesting that?

[russdeffner]

This is complete.