===Profile Information
Name: Maudite (Candela)
IRC nickname on Freenode: maudite
Web Profile: github.com/mauditecandela and maudite.cc (in progress)
Resume (optional)
Location (country or state): Berlin
Typical working hours (include your timezone): 9:00 - 18:00 (UTC+2)
===Synopsis
Programs & Events Dashboard (code) is a Ruby on Rails app with a React.js frontend. Its main purpose is to help organize and track group editing projects on Wikipedia and other wikis. It was initially designed to support the Wikipedia Education Program on English Wikipedia, in which university students write Wikipedia articles in the classes, but is gradually being extended to support other use cases such as edit-a-thons, and to work better for other languages and projects.
After reading the Dashboard Report feedback, I did some analysis on the main problems of the current version of it and we could divide in three main topics: 1) Improve organizers work 2) Better on boarding of editors and 3) Lack of integration of other software (databases difficult to maintain).
As the main goal of the Art+Feminism program is to increase the visibility of women and art on wikipedia, and the organization is already migrated to the dashboard as users, I have decided to concentrate in the first two topics.
First I would like to get in touch with the Art+Feminism organizers in order to get their feedback on my specific ideas and understand better the problems that they might have. The main topics I would like to discuss are:
- Visibility of events: How to improve the sorting of them, and how to keep clean the list of them (enable users to delete duplicated events or change the titles of them, add specific campaigns by default…)
- Facilitate the on boarding of editors e.g. by creating short urls
- UX related to dates: time zones, start/end dates not working as expected…
- Improve editors onboarding: clarify or make easier the two steps process (oAuth)
- Disable the enroll link for specific times in order to avoid misunderstandings
After discussing these ideas, I would like to do some investigation of the technical difficulty of each of them and write the different tasks/stories on Phabricator/Github. I will also discuss them with my mentors for a proper estimation and prioritization. After this work I would like to work on the first solutions in two rounds, in order to get some feedback from the A+F organizers in the middle of the project. After the final proposal, I would like to write technical documentation.
This way, the Programs and Events Dashboard will not only be improved by specific features but also some user research and stories definition that, in case that some work is left, could also be worked by other contributors. This will improve the documentation of the project.
====Possible Mentor(s):
Ragesoss and Capt_swing
====Have you contacted your mentors already?
Yes.
===Deliverables
====Timeline:
5.12 - 15.12: Contact and feedback from Art+Feminism Organizers. Technical investigation for the different features: Login auth, start/end date, event sorting, user rights, campaign and templates management, shortlink creation, enroll link capabilities.
18.12 - 22.12 Feedback with mentors. Prioritization, list of tasks, estimations. Definition of specific outcome.
27.12 - 12.01 - Code and testing.
15.01 - 19.01 - Fix of bugs and testing.
22.01 - 26.01 - Feedback round with Art+Feminism. User testing. Possible improvements.
29.01 - 16.02 - Code period after feedback.
19.02 - 23.02 - Second round of feedback.
26.02 - 05.03 - Documentation* and publishing. Communication of the improvements.
*I consider documentation a daily work, so I plan to do it at the same time I am coding. Anyway, I would like to allocate some time just in case the documentation needs some readjustments.
===Participation
- I have already forked the repo and have worked on my branch, but will also create new branches for the different stories. I will use clear messages on the commits and specify in each Pull Request what is going to be merged.
- The code will be periodically pushed and published then.
- I will be reachable on Slack and IRC on my working ours (09:00-18:00 UTM+2).
- I will be reachable via email for any kind of emergency or problem.
- I will document the whole process and the code being written.
===About Me
====Education:
I completed two MA in 2009 and 2011:
MA in Audiovisual Communication (Universidad Complutense of Madrid, 2009). Major: Cinema
MA in Cultural Management (Universidad Carlos III of Madrid, 2011). Major: Cultural Management
Since 2011 I also studied the first year of Bachelor of Computer Sciences (UNED) and Bachelor of Informational Sciences (Universidad Carlos III of Madrid). I dropped out of them because of the need of finding a full time employment.
After 5 years working in the tech industry as Technical SEO and Product Manager, I finally took the decision of pursuing my dream and become a developer. Since May of this year I am a self taught developer. I have completed different courses (e.g. Complete Javascript Course by Udemy) and attend to study/user groups in Madrid (RubyMonstas, Rails Girls…).
====How did you hear about this program?
Through a friend! She is a developer too that was part of the Rails Summer of Code of 2016 and said that Outreachy could be a great initiative to improve my skills and work in great projects.
====Will you have any other time commitments, such as school work, another job, planned vacation, etc, during the duration of the program?
I have not another commitments. I would like to spend time with my family from 24th of December till the 1st of January but I am flexible.
====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)?
There’s no Summer of Code right now. I will possibly apply for the next one in March.
====What does making this project happen mean to you?
I strongly believe in Creative Commons and Free Culture, so working for Wikimedia is a dream. I believe that Open Source is a great tool to enable the access to software to everybody, so working in both principles is a great motivation to me. Furthermore, I have been committed to different feminist activists groups in the past 10 years and I think that Art+Feminism Program is a wonderful initiative to improve the visibility of feminism in art. I really think that having references and role models is fundamental for empowerment, so giving more visibility to women in wikipedia will inspire a lot of women and girls in the world.
From a technological perspective, I have been learning Rails and Javascript in the past five months, so I believe that working on this project will help me improving my knowledge on them and also get to learn React.
===Past Experience
In 2011, I was part of the team of LABoral Centro de Arte. My role was technical assistant of the production center and there I got in contact with a lot of open source projects (not only software, also hardware), specially related to art. I would mention two specific projects which I enjoyed a lot: I helped organizing Summerlab of 2011 (http://www.laboralcentrodearte.org/en/education/summerlab-2011) and supported TVLab (http://tvlab.laboralcentrodearte.org/) with their educational programs. This is where my interested by Open Source started.
In 2015 I was one of the main collaborators and contributors of http://www.fabcollective.org/, an online platform for personal and small-scale digital fabrication which aims to connect people, projects and needs, based on the principles of collaborative creation and commons. The biggest two learnings from that experience were building an automatic watering system with Arduino and building the website (Drupal).
I also was Product Manager at DaWanda for the past 2 years Product Manager which gave me a great knowledge about prioritization, workflows design and user research. I think the main lesson I learnt in those 2 years was that is very important to listen to the user (quantitatively and qualitatively) in order to build great technology.
Currently I am part of Rubymonstas, a study group based in Berlin who is working on improving diversitytickets.org, an open source tool that aims to help the access to tech to women and other underrepresented groups in the IT field.
I have also contributed to some open source projects for this round of the Outreachy Program (Discourse and Wikimedia). In my free time I also helped some local artists to create their own websites by setting up their Wordpress Website and helping them on how to design it and maintain it. (www.elenacuadrado.com, www.leyrearin.com, e.g. )
The small contributions for the Art+Feminism program I already did are:
- https://github.com/WikiEducationFoundation/WikiEduDashboard/pull/1413 which was a fix for this issue: https://github.com/WikiEducationFoundation/WikiEduDashboard/issues/1407 Working on this contribution was wonderful as I got introduced to the base code, helped fix a bug, but also refactored part of the javascript of the project. Ragesoss was a great mentor and also explained to me how to run and write tests for the software I implemented.
- https://github.com/WikiEducationFoundation/WikiEduDashboard/pull/1424 which was a fix for this issue: https://github.com/WikiEducationFoundation/WikiEduDashboard/issues/1407. Here I got to use my recent learnings on Rails to improve the base code of Wikimedia.
- https://github.com/WikiEducationFoundation/WikiEduDashboard/pull/1446 [Open] which is a fix for the the task https://github.com/WikiEducationFoundation/WikiEduDashboard/issues/1295
- I am currently having a look to: https://github.com/WikiEducationFoundation/WikiEduDashboard/issues/1005 as the statistics is one of the main issues at the A+F Program Feedback
===Any Other Info
I would like to create a blog about the whole project and process and my learnings with outreachy: blog.maudite.cc