#108 EDU Hub
Opened 8 years ago by decause. Modified 6 years ago

As part of the University Involvement Initiative, the development of an "EDU Hub" was identified as a major goal and task (https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative). This hub would include elements such as:

  • Hyperkitty mailing List widget (EDU list)
  • Campus Ambassador information and Activity
  • Fedocal Widget for onboarding calendar
  • Information about Specific remixes/spins that would be useful to students
  • other EDU related content and communities Fedora is involved with (POSSE, GSoC, Outreachy, etc...)

Assigning to chhavi for initial user research to help us start specing this out. chhavi is going to start by interviewing folks involved in EDU initiatives in India.

Awesome @chhavi! To help point you in the right direction, there's probably some people you could try reaching out to in the Fedora community working on EDU outreach in India. Here's some of their contact info:

  • Sumantro Mukherjee
    • FAS username: sumantrom
    • IRC handle: sumantro
    • Email: sumukher [at] redhat [dot] com
  • Kanika Murarka
    • FAS username: a2batic
    • IRC handle: a2batic
    • Email: murarkakanika [at] gmail [dot] com
  • Vipul Siddharth
    • FAS username: siddharthvipul1
    • IRC handle: siddharthvipul1
    • Email: siddharthvipul1 [dot] gmail [dot] com

I know all three of these people are doing some awesome work with Fedora events at universities across India. Hope this helps!

Competitive Analysis

I started out with reaching out first to the contacts Justin shared. I prepared a rough draft of a questionnaire but since I did not have much clarity on how most of the student outreach programs work, I decided to conduct a competitive analysis to get a general overview of such programs and figure out what works and what does not for others.

Mo and I decided upon five outreach programs to compare (Mozilla, HackerEarth, Wikipedia, Microsoft and Drupal). The main criterion for the study were
• on-boarding for new ambassadors and contributors
• content and guidelines available for conducting events
• past experiences/reports of the attendees and organisers
• methods for universities to reach out to us/ contacts of mentors and active contributors
• presentation of information about the program
• layout of the portal

The detailed sheet of the study and a brief summary is attached with this ticket. Some constant components of the portals were
• All of them have mostly a cover banner/grid of pictures of their community, which helped connect better to the viewer than having no/illustrated pictures.

• Linked names of mentors, ambassadors, etc 

• Action buttons to “get involved”, “start contributing”, etc
• Links to join the mailing list, view the calendar
• About page has stats about the community in numbers and a few milestones, goals
-A sorted user journey, usually starting with the “start contributing” link
-Resources for ambassadors and for learning

The green colored comments in the sheet highlights the factors that works for such programs while red are which do not work.


CompetitiveAnalysisSummary.pdf
Competitive_Analysis_-_Fedora_EDU_initative.xlsx
CompetitiveAnalysisSummary.pdf

Competitive Analysis

I started out with reaching out first to the contacts Justin shared. I prepared a rough draft of a questionnaire but since I did not have much clarity on how most of the student outreach programs work, I decided to conduct a competitive analysis to get a general overview of such programs and figure out what works and what does not for others.

Mo and I decided upon five outreach programs to compare (Mozilla, HackerEarth, Wikipedia, Microsoft and Drupal). The main criterion for the study were
• on-boarding for new ambassadors and contributors
• content and guidelines available for conducting events
• past experiences/reports of the attendees and organisers
• methods for universities to reach out to us/ contacts of mentors and active contributors
• presentation of information about the program
• layout of the portal

The detailed sheet of the study and a brief summary is attached with this ticket. Some constant components of the portals were
• All of them have mostly a cover banner/grid of pictures of their community, which helped connect better to the viewer than having no/illustrated pictures.

• Linked names of mentors, ambassadors, etc 

• Action buttons to “get involved”, “start contributing”, etc
• Links to join the mailing list, view the calendar
• About page has stats about the community in numbers and a few milestones, goals
-A sorted user journey, usually starting with the “start contributing” link
-Resources for ambassadors and for learning

The green colored comments in the sheet highlights the factors that works for such programs while red are which do not work.


CompetitiveAnalysisSummary.pdf
Competitive_Analysis_-_Fedora_EDU_initative.xlsx
CompetitiveAnalysisSummary.pdf

Questionnaire for the User Interviews

All the questions were aimed to probe the ambassador about the following
• What are their goals/vision as a campus ambassador? How are they working towards it and what are the problems that they encounter while at it?
• What opportunities does the ambassador see for Fedora usage at the universities they're familiar with.
• Strengths, Weaknesses, Opportunities and Threats to the current FSA program

The full questionnaire is attached with this ticket. It was divided into sections
• background of the ambassador
• event organisation : venue, setup, etc
• preparations/problems/positive points before/during an event
• follow up/on boarding of potential contributors
EDUInitiativeAmbassadorsQuestionnaire.pdf

Questionnaire for the User Interviews

All the questions were aimed to probe the ambassador about the following
• What are their goals/vision as a campus ambassador? How are they working towards it and what are the problems that they encounter while at it?
• What opportunities does the ambassador see for Fedora usage at the universities they're familiar with.
• Strengths, Weaknesses, Opportunities and Threats to the current FSA program

The full questionnaire is attached with this ticket. It was divided into sections
• background of the ambassador
• event organisation : venue, setup, etc
• preparations/problems/positive points before/during an event
• follow up/on boarding of potential contributors
EDUInitiativeAmbassadorsQuestionnaire.pdf

User Interviews of Indian Ambassadors/Contributors

I conducted two interviews with active contributors. In a broad picture of Fedora in India, both the interviews pointed towards the 
-informal approach we are using in India for contacting universities and gathering audience for it (through word of mouth, social media, mutual friends, etc)
• the follow up is dependent on the mentors and the time they are able to invest in the contributors
• less knowledge about Fedora (FOSS in general), and various ways people can contribute to it.
• no standardized content guidelines or details about previously held events except fedora blogs
• difficulty in finding active ambassadors/contributors/mentors in your region.

The complete transcripts of the interviews and major pain points in attached with this ticket. The sheet is also tagged with major topics and "how might we" questions that we will ask ourselves while coming up with wireframes.

UserInterview1.pdf

User Interviews of Indian Ambassadors/Contributors

I conducted two interviews with active contributors. In a broad picture of Fedora in India, both the interviews pointed towards the 
-informal approach we are using in India for contacting universities and gathering audience for it (through word of mouth, social media, mutual friends, etc)
• the follow up is dependent on the mentors and the time they are able to invest in the contributors
• less knowledge about Fedora (FOSS in general), and various ways people can contribute to it.
• no standardized content guidelines or details about previously held events except fedora blogs
• difficulty in finding active ambassadors/contributors/mentors in your region.

The complete transcripts of the interviews and major pain points in attached with this ticket. The sheet is also tagged with major topics and "how might we" questions that we will ask ourselves while coming up with wireframes.

UserInterview1.pdf

Login to comment on this ticket.

Metadata