Note:

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

MoodleNet/Beta testing: Difference between revisions

From MoodleDocs
No edit summary
Line 61: Line 61:
''Who is going to be involved in the testing?''
''Who is going to be involved in the testing?''


The plan is to recruit 100 people to test MoodleNet. Although we need learning technologists, system administrators, and other techies to test it eventually, our initial focus should be on early-adopter educators. These will agree our [http://bit.ly/2FvqrM0 Guidelines for Contributors] and agree to give us regular feedback on MoodleNet over a three-week period.
The plan is to recruit 100 people to test MoodleNet. Although we need learning technologists, system administrators, and other techies to test it eventually, our initial focus should be on early-adopter educators. These will agree our [http://bit.ly/2FvqrM0 Guidelines for Contributors] and agree to give us regular feedback on MoodleNet over a three-week period (January 21st - February 11th).  
 
We should aim to have 50 people on the English-speaking HQ MoodleNet instance, and 50 people on the Spanish-speaking instance. On both, we need a mix of:
 
* Moodlers / non-Moodlers
* Experienced / inexperienced teachers
* Genders
* Experience with other social networks and OER repositories
* Educational sectors


=== When? ===  
=== When? ===  

Revision as of 12:46, 4 December 2018

<< Back to MoodleNet index


We'll expand this page as we have more details. Right now, the plan is:

  • January 2019:
    • Open applications to the beta testing programme
    • Create two HQ-run MoodleNet instances (English and Spanish)
    • Invite 100 people to take part in the testing, based on meeting certain criteria (language, location, experience, etc.)
  • February 2019
    • Receive daily/regular feedback from these 100 testers, and improve MoodleNet iteratively
    • Once we're happy with progress, give 10 invites to each test user, increasing the number of people using MoodleNet to 1,000

Why?

Why does MoodleNet exist?

MoodleNet exists to better connect the existing Moodle community, and also to attract new educators. To date, the only Moodle-provided way for educators and other users to share content has been within their Moodle Core installation, backing up and importing activities, or by sharing entire courses. MoodleNet will be upgrade to this, connecting educators via a Moodle-provided open social media platform which focuses on professional development and open content.

What?

What is the value proposition we're testing?

We have done some Value Proposition Design for different groups using MoodleNet and have decided that it will begin life as a place for educators to curate and share collections of resources. Our hypothesis is that the problem of discovery for educators cannot be solved by simply providing a more powerful search engine for the millions of resources already available. This is for at least three reasons:

  • Learning is a social activity - and likewise teaching should be something that is not done entirely on one's own
  • Search engines rely on already knowing what you're looking for - which is not always the case when planning a lesson, scheme of work, or course
  • Individual resources exist in a wider context - including their relation to other resources, the educator's approach to learning, and where the 'classroom' is located

Initially, then, MoodleNet will be a simple web-based application allowing educators to form communities that curate collections of resources. Most of these, we imagine, will be free and openly-licensed, although MoodleNet will be resource-agnostic. Uploading resources directly to MoodleNet is out of scope for the first phase of testing, as we need to decide our approach to file hosting.

How?

How are we going to test MoodleNet?

In early January 2019, we'll put out a call for educators to be involved in MoodleNet testing. We can use something simple such as a Google Form for this, ensuring that there is a privacy notice that they have to agree to on the application.

We're looking for a diverse mix of educators, with our only limiting factor being their ability to speak English and/or Spanish. The kind of information we're looking to capture to make a selection includes:

  • Name
  • Location (country)
  • Languages(s) spoken
  • Current role
  • Subject area(s)
  • Teaching experience (years)
  • Moodle experience (years)
  • Resource-sharing sites currently used
  • Social networks currently used
  • Reason(s) for wanting to be involved in testing

We're interested in every aspect of how they decide to use MoodleNet, including:

  • The communities and collections they decide to create
  • What type of collections they create (subject-based? topic-based? other?)
  • The number and type of communities they decide to join
  • How and when they use tags
  • What kind of comments they add to resources
  • How they respond to a 10-item limit on resource collections

Who?

Who is going to be involved in the testing?

The plan is to recruit 100 people to test MoodleNet. Although we need learning technologists, system administrators, and other techies to test it eventually, our initial focus should be on early-adopter educators. These will agree our Guidelines for Contributors and agree to give us regular feedback on MoodleNet over a three-week period (January 21st - February 11th).

We should aim to have 50 people on the English-speaking HQ MoodleNet instance, and 50 people on the Spanish-speaking instance. On both, we need a mix of:

  • Moodlers / non-Moodlers
  • Experienced / inexperienced teachers
  • Genders
  • Experience with other social networks and OER repositories
  • Educational sectors

When?

When will the testing take place? what comes next?

Where?

Where will users go to test MoodleNet and give their feedback?