===Profile Information
**Name:** Anna e só
**IRC nickname on Freenode:** contraexemplo
**Mastodon profile:** [[ https://cybre.space/@Anna | @Anna]]
**Github profile:** [[https://github.com/contraexemplo | contraexemplo]]
**E-mail:** contraexemplos@gmail.com
**Location (country or state):** Brazil
**Typical working hours (include your timezone):**
* **Morning**: From 08:00 to 12:00.
* **Afternoon**: From 14:00 to 18:00.
Brazil has a daylight saving time from October 15, 2017 to February 17, 2018, so during that period of time my timezone will be UTC -2h. After February 17, 2018 it will be back to normal (UTC -3h).
===Synopsis
Although documentantion is one of the most important parts of any project, many will say it is also one of the most neglected. This is the case with localization of Wikimedia documentation, as can be seen in [[https://www.mediawiki.org/wiki/Documentation | this page about it]].
Aside from English (since it is the source language), documentation is only 100% translated to two different languages: French and Polish. It is also 86% translated to Spanish and 71% translated to Italian, Lithuanian and Chinese. Other languages have less than 55% of work done.
It is fundamental to make all documentation extensively accessible. Although English is somewhat an universal language for software, having all documentation only available in a few languages or only English is not compatible with one of Wikimedia values, [[https://wikimediafoundation.org/wiki/Values | "We welcome and cherish our differences"]] and with its mission, [[https://wikimediafoundation.org/wiki/Open_access_policy | "to disseminate open knowledge effectively and globally"]]. Providing accessibility to people in as many countries as possible can provide easier ways to present technical information to contributors while making them more qualified to make use of the software.
**Possible mentor(s):** @Johan and @Trizek-WMF.
**Have you contacted your mentors already?** Yes.
===Timeline
<table>
<tr>
<th>Period</th>
<th>Task</th>
</tr>
<tr>
<td>December 5–12</td>
<td>**Community bonding period**. Getting to know more about current tools, what has been done before, what is realistically possible to do considering limitations.</td>
</tr>
<tr>
<td>December 13–20</td>
<td>Discussion. Consulting notes done before. Reach out communities and other collaborative parties to ask them about difficulties and suggestions. Identifying problems, ranking and labeling them as "root" or "symptomatic".</td>
</tr>
<tr>
<td>December 21–January 02</td>
<td>Strategy building. Write down possible solutions, ranking them accordingly to possible effectiveness, labeling them as "long-term" or "immediate". Provide detailed description about how to apply those strategies.</td>
</tr>
<tr>
<td>January 03–February 03</td>
<td>Initial outreach. Applying strategies described on previous task.</td>
</tr>
<tr>
<td>February 04–08</td>
<td>**Initial outreach evaluation**</td>
</tr>
<tr>
<td>February 08–09</td>
<td>Initial outreach discussion. What did work? What did not?</td>
</tr>
<tr>
<td>February 10–March 05</td>
<td>Continious outreach while also analysing results. Final evaluation.</td>
</tr>
</table>
===Participation
* I will make weekly reports about my findings which will be sent to my mentors when required, compiled as the timeline progresses and fully available at the end of the internship at any place of choice.
* I will be available at IRC in my working hours to collaborate with my mentors.
* I will use Phabricator for managing subtasks and asking for help and suggestions.
* I will be at reach through e-mail when needed.
===About Me
Currently a mechanical engineering undergraduate. Passionate about technology, open-access and the free software movement. As a visually impaired person, one of my greatest motivations to pursue those things is to provide universal accessibility since I know how difficult it is to live in a inaccessible world.
===How did you hear about this program?
I am always looking for new ways to engage with FOSS and general technology communities, so I was searching for any event that would take place at my city. This year, Goiânia hosted a meeting called [[ http://encontro2017.mulheresnatecnologia.org/ | 5º Encontro Nacional de Mulheres na Tecnologia ]]. I read their schedule and saw a talk about internship opportunities that mentioned Outreachy. I couldn't go, but this brand new information stuck with me. So I eagerly waited since May to apply.
===Will you have any other time commitments, such as school work, another job, planned vacation, etc, during the duration of the program?
* As stated on my application on Outreachy's site, even though I am currently a undergrad my university break is between December and March. I have only one exam after the internship starts, **but my professor is willing to antecipate it** so it does not disturb my schedule.
* My possible mentors mentioned they will take some time at the end of the year for the holidays so I'd like to do it as well between December 24th and January 1st.
===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)?
No. Even though I know how to code, I identify more with Outreachy's core values and goals.
===What does making this project happen mean to you?
I fell in love with this project. Not only I want to gain experience so I can build a career but also because I admire Wikimedia's work and I share the same core-values. **I've always pursued a way to make a difference in the world and I believe this is one of the most effective ways this could happen: providing open-knowledge side by side with amazing collaborators.**
Outreachy's existence per si pushed me to get even more involved with FOSS communities. I was once afraid of contributing but finding projects filled with passion made me passionate as well, so I stopped worrying and started working. I see this internship as a way of thanking the people who makes initiatives like these possible with my hard work and as a form to demonstrate that people like me — a disabled woman — can find their place in the technology field. **I want to be the model I wanted to have when growing up.**
===Past Experience
I am a long time FOSS user but only began contributing to open-source projects in the last few months. This change was motivated by quitting Twitter and signing up to Mastodon, a free open-source microblogging plataform for everyone. As I became more and more comfortable since the community is very welcoming, I felt a need of thanking those developers for building this amazing software in a time I didn't feel optimist about social media and the state of internet. I noticed how similar European Portuguese and Brazilian Portuguese translations were and I decided to localize Mastodon fully to my language:
* [[https://github.com/tootsuite/mastodon/pull/4700 | Pull request #4700]]
* [[https://github.com/tootsuite/mastodon/pull/4882 | Pull request #4882]]
* [[https://github.com/tootsuite/mastodon/pull/4953 | Pull request #4953]]
This also motivated me to translate its landing page, https://joinmastodon.org:
* [[https://github.com/tootsuite/joinmastodon/pull/48 | Pull request #48]]
which was acknowledged [[https://mastodon.social/@Gargron/20055661 | by Mastodon's main developer, Eugen Rochko]].
Those were the first times I've ever used GitHub and git and it helped me establish a workflow. Not only I've dealt directly with translation documentation but I've also led some tests thanks to it. Those tests involved installing and running a local instance, loading the right files, making some debugging and gathering information from those who used it. Once it was approved by me and my testers, I submitted a pull request that was later merged to the source code. To sum up, this is what I learned:
* to organize my workflow;
* to use git and GitHub;
* to read and follow properly the official documentation;
* to run a virtual machine with Ubuntu Server 16.04;
* to install, run and maintain a Mastodon instance;
* to manipulate YAML, erb and JSON files;
* to do l10n work;
* to run tests and gather information from testers.
I also helped to localize two of my favorite apps for Android:
* [[https://crowdin.com/project/twidere/pt-BR/activity | Twidere]]
* [[https://github.com/stom79/mastalab_localization/pull/3 | Mastalab]]
And made some minor contributions to other things I use:
* [[https://github.com/ytaudiobot/ytaudiobot-l10n/pull/151 | ytaudiobot, a Telegram bot]]
* [[https://github.com/tgwizard/sls/pull/400 | Simple Last.fm Scrobbler]]
As for other experiences, I was enrolled in a course about software engineering for avionics for nearly two years (from 2015 to 2016). Not only I learned a lot about complex systems and documentation surronding them but I also improved my communications and leadership skills as it was required to make projects as a team. I would say that was the first time I got interested in localization since in my free time I voluntarily (and unofficially) translated part of documentation used in one project so my team mates could understand it better.
===Contributions
* T158564: Translate a couple of help pages
* https://www.mediawiki.org/wiki/Special:Contributions/Contraexemplo
* Translation of the last Tech News released to date:
* https://meta.wikimedia.org/wiki/Special:Contributions/Contraexemplo
==Other info
I will be writing about my experience with Outreachy and Wikimedia at anna.flourishing.stream!