MoodleNet/Contributing: Difference between revisions

Revision as of 13:57, 6 June 2018

Contributing to the MoodleNet project

MoodleNet is a new open social media platform for educators, focussed on professional development and open content. In May 2018 we created a prototype overview as the result of a design sprint, which gives a flavour of where we're headed.

To get there, we need people like you to contribute to this project to make it the best it can be. Got an idea? Share it! Have a question? Ask it!

There are a number of ways you can contribute to this project:

Discussion forum - ask questions, make suggestions, and connect with other members of the MoodleNet community
Community calls - participate in these monthly calls
Trello board - comment on work in progress

Note: you don't have to have any particular pedagogical or technical expertise to make suggestions or get involved. All that's needed is enthusiasm!

MoodleNet Lead: Doug Belshaw MoodleNet Technical Architect: Mayel de Borniol

We're working as openly and transparently as possible with this project. As a member of the MoodleNet community, almost everything you come across should link to something else that you have access to. If you don't, it's by exception. In other words, it's commercially-sensitive, or includes personal details that we want to protect.

If you happen to be attending a MoodleMoot, there's a good chance that there will be someone talking about MoodleNet. Check out programmes to see if there's a dedicated session!

Finally, we're planning to issue a series of badges to contributors to the MoodleNet project. Watch this space!

@@ Line 10: / Line 10: @@
 To get there, we need people like ''you'' to contribute to this project to make it the best it can be. Got an idea? Share it! Have a question? Ask it!
+-----
 There are a number of ways you can contribute to this project:
@@ Line 21: / Line 23: @@
 -----
-To add (from [http://dougbelshaw.com/blog/2017/03/09/build-architecture-participation this post]):
+MoodleNet Lead: '''Doug Belshaw'''
+MoodleNet Technical Architect: '''Mayel de Borniol'''
+We're working as openly and transparently as possible with this project. As a member of the MoodleNet community, almost everything you come across should link to something else that you have access to. If you don't, it's by exception. In other words, it's commercially-sensitive, or includes personal details that we want to protect.
-# A clear mission – why does this project exist? what is it setting out to achieve?
+If you happen to be attending a [https://moodlemoot.org/ MoodleMoot], there's a good chance that there will be someone talking about MoodleNet. Check out programmes to see if there's a dedicated session!
-# An invitation to participate – do you have an unambiguous call to action?
-# Easy onboarding – are there small, simple tasks/activities that new volunteers can begin with?
-# A modular approach – do volunteers have to commit to helping with everything, or is there a way which they can use their knowledge, skills, and interests to contribute to part of the project?
-# Strong leadership – do the people in control of the project embody the mission? do they have the respect of volunteers? have they got the capacity to make the project a success?
-# Ways of working openly and transparently – does the project have secret areas, or is everything out in the open? (this post may be useful)
-# Backchannels and watercoolers – are there ‘social’ spaces for members of the project to interact over and above those focused on project aims?
-# Celebration of milestones – does the project recognise the efforts and input of volunteers?
-In addition, consider (from Greg McVerry's comments):
+------
-* Recruitment Events. Organizations need to actively plan and seek out contributors. Just labeling something “first bug” is not the way to engage the new people.
+Finally, we're planning to issue a series of [https://openbadges.org badges] to contributors to the MoodleNet project. Watch this space!
-* Leadership and Learning Opportunities: Think about the value add for a contributor. What are you offering to them beyond mission alignment?
-* Digestible Workflow: Beyond simply working in the open is your timetable, roadmap, and how you work easily digestible?
-* Transition Planning: Do you have a “handhsake”plan for contributors when either a staff member who guided them leaves or a project is sunsetted?

Documentation

MoodleNet/Contributing: Difference between revisions

Revision as of 13:57, 6 June 2018

Contributing to the MoodleNet project