Name: Abel Lifaefi Mbula
IRC nick: bam (on Freenode)
Location (country or state): DRC
Typical working hours: 9am - 1pm and 6 - 10pm - UTC + 2
In various Wikipedia outreach campaigns and events (editathons), participants often want to collaborate on improving articles that share a common theme or perhaps exhibit a common problem, such as being too short or lacking sufficient citations.
Events' organizers manually develop their on-wiki based worklist which:
- can be challenging to manage for new users, or
- require using tools not designed for tracking completion
The project idea aims at:
Developing a new tool to facilitate collaboration on worklists of articles that could be used for campaigns. This tool will be able to:
- Define new worklists of articles (examples: “Articles with no references”, “Articles about Colombia”, …)
- Worklists can be imported from PetScan queries (http://petscan.wmflabs.org/)
- Share worklists with other users using a link
- Manually list the articles inside a worklist, claim or assign one to work on and mark it completed when done
- View which articles are claimed by which other users and whether they're being worked on or already done, in real time
Junias Mbele, 27 years old, software dev and free culture enthusiast
Junias is a free/open source software dev. He is pationnate about free culture community. On his spare time he usually organize Wikipedia editing events with colleges and students. He manually prepares his worklist or rarelly uses PetScan tool. He is not unfortunately satisfied totally when it comes to track users contributions or manage worklists. Because things are done manually, there's very often editing conflit because 2 or more users work on the same article at the same time.
To track users contributions he creates a hashtag and uses hashtags tool. Unfortunately most of the time users forget to use hashtag; so some articles are not tracked at all.
Merveille Kalenga, 20 years old, student in medicine
Merveille is studing medicine. She uses Wikipedia as a go-to source for resolving arguments with friends and even with professors as, e.g. the history of medecine. She sometimes finds lack of info on Wikipedia or reliable citation; so she participates in Wikipedia editing events to help improve the encyclopedia. One thing she hates in these events is that there's still editing conflict between other users and her.
Before April 23:
- To familiarize myself to toolforge, the hosting service for my tool
- Study MediaWiki API
- To search and read all necessary documentations
April 23 - May 14 (Before the official coding time):
- To get ready with specs (functional and tech)
- I will remain in constant touch with mentors and some events' organizers so that I can deeply understand their real need in order to build a tool that meet their expectation
- To design the database architecture and refine specs
July 25 – July 31:
- For Documentation
A buffer of two weeks has been kept for any unpredictable delay.
- Creating Tasks in Phabricator.
- Getting Tools Lab access.
- Creation of the UI templates.
- Design the FLASK app frontend components.
- Design the FLASK app backend components.
- Providing OAuth authentication with Wikipedia.
Describe how you plan to communicate progress and ask for help, where you plan to publish your source code, etc
Tell us about a few:
- Your education (completed or in progress)
- How did you hear about this program?
- Will you have any other time commitments, such as school work, another job, planned vacation, etc, during the duration of the program?
- We advise all candidates eligible for Google Summer of Code and Outreachy to apply for both programs. Are you planning to apply to both programs and, if so, with what organization(s)?
- What does making this project happen mean to you?
Describe any relevant projects that you've worked on previously and what knowledge you gained from working on them. Describe any open source projects you have contributed to as a user and contributor (include links). If you have already written a feature or bugfix for a Wikimedia technology such as MediaWiki, link to it here; we will give strong preference to candidates who have done so
Any Other Info
Add any other relevant information such as UI mockups, references to related projects, a link to your proof of concept code, etc