Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Ushahidi : Working openly and encouraging contribution from international development workers, activists and volunteers #32
Project Leads: @Erioldoesdesign
Welcome to OL6, Cohort A! This issue will be used to track your project and progress during the program. Please use this checklist over the next few weeks as you start Open Leadership Training
Before Week 1 (Sept 11): Your first mentorship call
Before Week 2 (Sept 18): First Cohort Call (Open by Design)
Before Week 3 (Sept 25): Mentorship call
Before Week 4 (Oct 3): Cohort Call (Build for Understanding)
Before Week 5 (Oct 10): Mentorship Meeting
Before Week 6 (Oct 17 ): Cohort Call (Participation & Inclusion, Feedback Workshop)
Before the call
Assignments (all optional)
Before Week 7 (Oct 24): Mentorship Meeting
Before Week 8 (Oct 31): Cohort Call (Build for Participation & Inclusion)
Before Week 9 (Nov 7 ): Mentorship Meeting
Before Week 10 (Nov 14 ): Cohort Call (Empower for Participation & Inclusion)
Before Week 11 (Nov 21): Mentorship Meeting
Before Week 12 (Nov 28): Cohort Call (Build for Understanding - Demo prep)
Before Week 13 (Dec 5): Mentorship Meeting
This is your final scheduled call with your mentor! Be prepared to celebrate all you've accomplished and debrief your time together. We'll also be sending out a final anonymous survey for any additional feedback.
Before Week 14 (Dec 28): Cohort Call (Final Demos - Celebration!)
On the demo call, each project will have a chance to share:
This issue is here to help you keep track of work during the first month of the program. Please refer to the OL6 Syllabus for more detailed weekly notes and assignments past week 4.
Vision or Mission Statement - Final
I’m working with Community development workers, international development workers, activists and volunteers to first, understand what the barriers* to contribution are and test/build a method/framework so that Community development workers, international development workers, activists and volunteers can be an integral part of the contribution process and can see clearly how their experiences and input affects the tools that will help them with their causes.
*Perceived barriers to contribution:
4 key areas: Time pressure, relevance to work, ease of adoption/contribution, Tech is scary
Vision statement feedback:
Perhaps state explicitly what they are contributing to and to what end?
You got all what you need in your vision...I think it just need some small text correction :)
Hi @Erioldoesdesign. I’m very interested in following this issue, as both a non-techie myself and as a project leader who would like to encourage / enable more non-techie contributors.
FWIW in my experience with our project at Hack for L.A., the main obstacles I perceive are:
I'm still new to GitHub, so I wonder if you or others reading have experience using it as a version control system for non-code assets.
Goal 1 - Engage with at least one group that has used Ushahidi platform before.
Goal 2 - Via survey information collection, discussion, interviews or other research methods; discover/validate the barriers to contributing to OSS tech/code projects are.
Goal 3 - Design a potential way for the int dev, activists and volunteers to contribute based off the information gathered in goals 1 & 2
Goal 5 - Gain at least 5 contributions from my target groups or beyond.
Findings from Hacktoberfest:
Findings from Mozfest session:
Findings from Google code-in:
Findings from meeting with Bristol Women's voice (BWV):
The issues picked for BWV are:
Obfuscation (formerly "Anonymization") v2 #3181
Notes: The admins find it useful to know precise location of a report/response in order to lobby local authorities/government for better provisions (more street lighting, remove bushes etc.) in high volume response/post areas or extreme instances. Allows them to take direct action.
Semi-Anonymous Posting #1571
Notes: BWV currently ask demographic questions as part of their survey set up but indicate it would be useful to be able to collect this in a protected way. BWV never want a responder to become a 'user' e.g. sign up for an account on the deployment as the nature of the responses/posts are typically one off or even if there was multiple responses/posts by one person then they do not need to be connected yet.
Anonymization of Reporters Mobile #2685
Notes: Hesitation to automatically record responder mobile location. Responder may not be in the place that it happened and may be reporting it later at home or days/weeks after the incident. Responders should also be notified that their GPS could be used before it is used.
Allow changing map icons #1436
Notes: BWV say this could be useful for outside campaign uses but it's not essential. More useful would be colour coding (which exists but they struggled to discover)
Custom Icons #1941
Notes: See above re. changing icons.
BWV then talked about some innovations that would be useful without issues to prompt including:
Platform = An instance of the Ushahidi data collection product is referred to as 'platform' or 'a deployment'
Report/Response/Post = A single instance of a person completing a response to a survey on a particular deployment.
Responder = A person responding to one of Bristol Women's Voice surveys on the Ushahidi platform about street harassment
Admin/s = The person/s that own the platform deployment of Bristol Women's Voice street harassment
Who are my users? - Write Personas to validate
Persona 1 - (Individuals in) Charities/NGOs/Non-profit orgs - Fans & Skeptics - Need Most.
Persona 2 - Individual international development workers/consultants. Fans - Need.
Persona 3 - Volunteers & Activists - Fans & Skeptics - Need most.
Techy personas (support the effort)
Persona 4 - News, media and Journalists - Skeptics.
Persona 5 - Technical people working in Charities/NGOs/Non-profit orgs - Fans - Need most.
Persona 6 - Technical people not yet volunteering - Need.
Persona 7 - For profit businesses - Fans.
Visualise your support network