![\"PythonBrasil](\"https:\/\/rsip22.github.io\/blog\/img\/pybr_logo.png\"){kind=logo}
<\/p>\n<\/p>\n
PythonBrasil<\/a> is the national Python community conference that happens every year, usually in October, in Brazil.<\/p>\n I attended PythonBrasil for the first time in 2016, the year we had started PyLadies Porto Alegre<\/a>. Back then, we were a very small group and I was the only one to go. It was definitely one of the best experiences I ever had, which, of course, set a very high standard for every single tech event I attended afterwards.<\/p>\n Because of the great time I had there, I wanted to bring more and more women from PyLadies Porto Alegre to experience PythonBrasil in the next editions. So, during the PyLadies Porto Alegre 1st birthday party<\/a>, I encouraged the other women to submit activities to try and to go to the conference that would happen in Belo Horizonte.<\/p>\n When attending it for the second time, I didn't go alone. Daniela Petruzalek had her talk accepted. Claudia, also from PyLadies Porto Alegre, was able to go, for the first time, thanks to the support of the PyLadies Brazil crowdfunding campaign. To me, one of the most memorable things about this PythonBrasil was \"The (unofficial) PyLadies House\", where I stayed. It was a huge house that we rented and shared between about 18 people to help with the accomodation costs for all of us. We shared breakfasts and rides and stories. We watched other PyLadies rehearse their talks, made lightning tech talks late at the night and we even had a birthday party!<\/p>\n So, this year? The idea of encouraging PyLadies POA submissions, something that had came up almost spontaneously last year, matured and we have worked to make Pyladies Porto Alegre 2nd Birthday Party<\/a> an all-day event with that purpose. The schedule? Lightning talks about Python projects from its members, talks about experiences as participants and as speakers at Python Brasil and... we also had a help from Vinta Software's Flavio Juvenal, who acted as mentor to the women who were considering to submit an activity to PythonBrasil. He even made a great Github repo<\/a> with a proposal checklist to assist us - and he made himself available for reviewing the proposals we wrote.<\/p>\n The result? We had more than 6 women from PyLadies Porto Alegre with activities accepted to PythonBrasil[14]. Some of them even had more than one activity (tutorial and talk) accepted.<\/p>\n I was among the ones who had been accepted. Ever since attending the conference for the first time, it had been a goal of mine to give a talk at PythonBrasil. But not any talk. I wanted for it to be a technical talk. At last, what I learned during Outreachy and how I had used it for a real task in a job finally gave me the confidance to do so. I felt ready, so I submitted and I was accepted.<\/p>\n I made my way to Natal, the capital of the Rio Grande do Norte (RN) state (in the Northeast of Brazil) two days before the conference was to start, since it was the cheapest ticket I could find. Besides, the PyLadiesBRConf was scheduled to happen on the day before and I was hoping I would be able to attend. PyLadiesBRConf was a full day of talks organized by what one could have called \"the original PyLadies Brazil\", since the Pyladies community in Brazil actually started in Natal and was named so (afterwards we started naming the group with cities' names).<\/p>\n On the next day, PythonBrasil[14] started. It was the biggest PythonBrasil to happen yet, with over 700 atendees (plus staff). Like many PyCons, the conference days are usually split between tutorials, talks and sprints.<\/p>\n The tutorials have free admitance and are open to anyone to attend (no matter if they have bought a ticket to the conference or not). Unfortunatelly, due to the capacity of the rooms where they would be held, there was a limit for 100 registrations for each tutorial. When I went to register for the tutorials of the first day, they were already all booked. Even so, the tutorial I was most interested in, \"Builting REST APIs with Django REST Framework\", had to be cancelled anyway because the presenter missed his flight. :( On this first day, I met with a few PyLadies and people from the Python community who were in Natal, I walked on the beach and I focused on the preparation for my talk.<\/p>\n I must confess that I had registered for the tutorial on Pandas (\"It's not witchcraft, it's Pandas\", by Fernando Masanori) merely because Flavio Juvenal had mentioned Pandas on the feedback for my proposal. I had no idea what that was actually about and why would one even use Pandas. By noon on that second day, though, I was so very glad that I did (and that I got a spot in it!). I learned a bit about Pandas and I also learned about how to use Jupyter Notebooks, something I had never tried before either. I found both Pandas and Jupyter easy and interesting and I look forward to do some projects using them.<\/p>\n Back when we (PyLadies) were discussing submissions to PythonBrasil with Professor Masanori, Data Structures was something that both I and another PyLady (Debora) had mentioned we had been meaning to focus on and study more. So, he came up with the idea for a tutorial about it, called: \"Data Structures are <3\".<\/p>\n On this tutorial, I found it quite interesting learning and playing with recursive functions and with algorithms for searching. I was quite impressed with learning about heapsort (who knew doing such a thing could be so cool?).<\/p>\n Image Licensed CC BY-SA 3.0 Attribution: RolandH<\/a><\/p>\n Everything at PythonBrasil (tutorials, talks and sprint) happened in the same hotel. So, after the tutorials were over, I hung around with some of the people of the community who were staying at the same hostel. The organizing team asked for help in putting together the conference kit (bag, t-shirt, IDs and flyers). We made sort of a production line and cut the time considerably short for the volunteer team.<\/p>\n Afterwards, I was still processing everything that I had learned and I wanted to try the new things, so I went back to the hostel to code some more. I confess that I was so hooked that I stayed up until 2 am to create the code with Pandas that I would incorporate in my talk as a bonus content.<\/p>\n On this day, I had the opportunity to meet and socialize with a lot of people who were coming to Python Brasil for the first time. It was particularly delightful to see a lot of students from a public technical school (Instituto Federal) attending the conference with their teachers. They had been given tickets, which allowed them to attend the (otherwise very expensive) conference and I must say that this is the kind of inclusion that I always want to see in tech events.<\/p>\n From the talks, I want to highlight these moments: I learned about Scrapy (which I have been playing around a bit since then), I watched an awesome talk about using Python with Physics (although I don't have a depth knowledge of Physics, I count as a success that I could follow the talk in it's entirety, so cheers to the presenter, Ana Maria, from PyLadies Teresina) and I must mention that I was quite impressed by Elias Dorneles' talk - about developing software for the command line. Even his \"slides\" were made there - and there was drawings and music too, all made with Python and using the command line!<\/p>\n The second day of talks brought us the much needed talk about AfroPython<\/a>, a initiative that was created to increase representation of black and native brazilian people in our community.<\/p>\n A talk that gathered a lot of attention (and overcrowded the room it was being given at!) was the one about using Python to understand data about suicides to help preventing them. It's a hard subject for many people, but it is one that we definitely need to talk about.<\/p>\n Andreza Rocha's talk \"Dear White People (from HR)\" also touched a lot of people. She drew from her own experiences as a tech recruiter to question about the homogenity that we (still) have in tech. \"Who are the ones who recruit the people?\" she asked. \"For us to be recruited, we (black people) have to be alive.\"<\/p>\n It was on this day that a violation of Python Brasil's Code of Conduct happened. After a PyLady gave her talk, a male participant used the time for questions not to ask a question, but to let's say<\/em>... eulogize the woman who had given the talk... by demeaning all other women who had presented before her and weren't \"technical enough\" or something like that. Oh, how thick we must make our skin for us to be able to come up to a stage knowing we might to be subjected to a moment like that... I am glad the PyLady was experienced and level-headed enough to own the moment and give him the deserving come back. * sigh * (After<\/em> the conference, the organization published a note about the CoC violation.)<\/p>\n Contrary to popular belief, yes, I did watch the last keynote of the day, even though it was Facebook's. And it did surprised me. Rainer Alves spoke about the shifts in corporate culture that happened when they merged infrastructure and development people into a \"Production Engineering\" departament. What I found most relevant, though, was the slide below, about \"Blameless postmortens\". After all, how to actually correct a malpractice or an error other than working collectivelly to figure out the way? \"It's not about what you did, it's about what went wrong.\"<\/p>\n This was the day we took the official photo of Python Brazil:<\/p>\n It was also the day we took a picture with the women who were at the conference:<\/p>\n Sunday arrived and it was time for: 'But can you open it on Excel?' Exporting to TXT, CSV and JSON with Python (\"'Mas d\u00e1 pra abrir no Excel?'' Exportando para TXT, CSV e JSON com Python\")<\/strong>. The focus of my talk was how to export data to those formats using mainly the tools offered by the Python Standard Library. But, as I mentioned before, thanks to what I learned during the PythonBrasil tutorials, I was able to add some extra content and show how the export to CSV could be done with Pandas as well. I was very glad about this, even though I felt like there was so little time to go over all the content I wanted to present (I had time to go through all my slides and for a very brief demonstration, but that was it). I think it went well. I even managed to speak briefly about Free Software (since I don't use Excel, and I made my demonstration with LibreOffice).<\/p>\n When they opened time for questions, I explicitily said \"Questions, not comments, please\" hoping to avoid mansplaing or another incident like the one that had happened the day before. And I know people judged me for that, but... I am also aware they judged me more harshly because I am a woman. After all, in previous editions we have had male keynotes making the very same comment without people being offended by it.<\/p>\n This did not stop people from coming to talk to me afterwards with comments about their experiences anyway - that was definitely better, because I felt like I could talk to them more properly and personally about it, having more time than the 5 minutes alotted to questions and not having to answer under a full audience's scrutiny.<\/p>\n Other than my own talk, I would like to mention some other talks I attended. There was a talk about advanced functional programming (\"Going further than map, filter and reduce\"), which is something that I find interesting to have some idea about it, even though I don't quite fully grasp yet. There was also the PyLadies' talk, where a group representing each region of Brazil with a PyLadies group talked about the work we have been doing. Andressa went on for PyLadies Porto Alegre and talked about all the work we have been doing in particular regarding all the Django Girls workshops<\/a> we have helped at in Rio Grande do Sul since the last PythonBrasil.<\/p>\n Ana Paula made a fun talk about Genetic Algorithm with Python, which uses the language to work with Biology data. Another subject that I am not very familiar with, but that I found quite interesting. And I also saw Camilla Martins live coding to run Python with Node.js on the big stage.<\/p>\n During the lightning talks, something amazing happened: the Instituto Federal students went up on the stage and talked about their experience at PythonBrasil using a regional sung-poetry called Cordel. It was really remarkable.<\/p>\n Also during the lightning talks, we had Thrycia Oliveira, a former participant of Django Girls, calling to attention the fact that we need to have spaces that are inclusive to parents in the community, in particular to moms. She said that PythonBrasil organization tried to arrange so, and she thanked them for that, but it had not been possible. I also remember when she told me about her participation in Python Nordeste (a regional conference that preceeded PythonBrasil) and how she had to alternate with her husband the days she went to, because one of them had to stay at home to watch over their kids (it wasn't really a kids-inclusive event).<\/p>\n This day ended with Betina's keynote \"Does this algorithm have a soul?\", a very relevant question for the state of software development today. Her talk spoke to me and to a lot of people in the audience and I can't picure a more welcoming community to be given to.<\/p>\n Sadly, Python Brazil had to come to an end. Day 6 happened on a Monday, and that meant that the majority of the people, including almost all the Pyladies, had already returned home. :( For personal reasons that I would rather not talk about publicly, I chose not to take part on the coding sprint to help with APyB's site. Instead, because I am looking for work, I used this day mostly for networking and applying to jobs I had heard about during PythonBrasil. I don't have wifi at home and I need to take any opportunity I can get to use the internet to send CVs and taking technical tests, so that is what I did.<\/p>\n And, of course, to finish this post I ought to mention the beach... On my last two days in Natal, I was gifted with the awesomeness that it is the ocean at Ponta Negra during the full moon. There are no words to describe the beauty of it (I am sorry I couldn't take a good picture of it).<\/p>\n I know this post ended up being extensive, but how can one summarize an experience with an event as huge as PythonBrasil? It's hard. I think it's safe to say that to be part of something like that has a lasting impact in my life. All the technical content I have heard about gives me motivation to keep studying and learning new things. All the people I have met, friends old and new, give meaning to the work to make the Python community more open and inclusive.<\/p>\n So, I cannot thank Outreachy<\/a> enough for making my participation in Python Brasil possible!<\/p>\n This whole journey would not be possible without the awesome people below, so I would like to also thank:<\/p>\n This post is long overdue, but I have been so busy lately that I didn't have the time to sit down and write it in the past few weeks. What have I been busy with? Let's start with this event, that happened back in March:<\/p>\n At MiniDebConf Curitiba last year, few women attended. And, as I mentioned on a previous post<\/a>, there was not even a single women speaking at MiniDebConf last year.<\/p>\n I didn't want MiniDebConf Curitiba 2018 to be a repeat of last year. Why? In part, because I have involved in other tech communities and I know<\/em> it doesn't have to be like that (unless, of course, the community insists in being mysoginistic...).<\/p>\n So I came up with the idea of having a meeting for women in Curitiba one month before MiniDebConf. The main goal was to create a good enviroment for women to talk about Debian, whether they had used GNU\/Linux before or not, whether they were programmers or not.<\/p>\n Miriam and Kira, two other women from the state of Parana interested in Debian, came along and helped out with planning. We used a collaborative pad to organize the tasks and activities and to create the text for the folder about Debian we had printed (based on Debian's documentation).<\/p>\n For the final version of the folder, it's important to acknowledge the help Luciana gave us, all the way from Minas Gerais. She collaborated with the translations, reviewed the texts and fixed the layout.<\/p>\n The final odg file, in Portuguese, can be downloaded here: folder_debian_30cm.odg<\/a><\/p>\n Very quickly, because we had so little time (we settled on a date and a place a little over one month before the meeting), I created a web page and put it online the only way I could at that moment, using Github Pages. https:\/\/debianwomenbr.github.io<\/a><\/p>\n We used Mate Hackers' instance of nos.vc<\/a> to register for the meeting, simply because we had to plan accordingly. This was the address for registration:\nhttps:\/\/encontros.matehackers.org\/pt\/projects\/60-encontro-debian-women<\/a><\/p>\n Through the Training Center<\/a>, a Brazilian tech community, we got to Lucio, who works at Pipefy and offered us the space so we could hold the meeting. Thank you, Lucio, Training Center and Pipefy<\/a>!<\/p>\n Because Miriam and I weren't in Curitiba, we had to focus the promotion of this meeting online. Not the ideal when someone wants to be truly inclusive, but we worked with the resources we had. We reached out to TechLadies and invited them - as we did with many other groups.<\/p>\n This was our schedule:<\/p>\n Morning<\/strong><\/p>\n 09:00 - Welcome coffee<\/p>\n 10:00 - What is Free Software? Copyright, licenses, sharing<\/p>\n 10:30 - What is Debian?<\/p>\n 12:00 - Lunch Break<\/p>\n Afternoon<\/strong><\/p>\n 14:30 - Internships with Debian - Outreachy and Google Summer of Code<\/p>\n 15:00 - Install fest \/ helping with users issues<\/p>\n 16:00 - Editing the Debian wiki to register this meeting https:\/\/wiki.debian.org\/DebianWomen\/History<\/a><\/p>\n 17:30 - Wrap up<\/p>\n Take outs from the meeting:<\/p>\n Because we knew more or less how many people would attend, we were able to buy the food accordingly right before the meeting - and ended up spending much less than if we had ordered some kind of catering.<\/p>\n<\/li>\n Sadly, it would be almost as expensive to print a dozen of folders than it would be to print out hundred of them. So we ended up printing 100 folders (which was expensive enough). The good part is that we would end up handing them out during MiniDebConf Curitiba.<\/p>\n<\/li>\n We attempted a live stream of the meeting using Jitsi, but I don't think we were very successful, because we didn't have a microphone for the speakers.<\/p>\n<\/li>\n Most of our public ended up being women who, in fact, already knew and\/or used Debian, but weren't actively involved with the community.<\/p>\n<\/li>\n It was during this meeting that the need for a mailing list in Portuguese for women interested in Debian came up. Because, yes, in a country where English is taught so poorly in the schools, the language can still be a barrier. We also wanted to keep in touch and share information about the Brazilian community and what we are doing. We want next years' DebConf to have a lot of women, specially Brazilian women who are interested and\/or who are users and\/or contribute to Debian. The request for this mailing list would be put through by Helen during MiniDebConf, using the bug report system. If you can, please support us:\nhttps:\/\/bugs.debian.org\/cgi-bin\/bugreport.cgi?bug=895575<\/a><\/p>\n<\/li>\n<\/ul>\n Pictures from the meeting:<\/p>\n Our breakfast table!<\/p>\n Miriam's talk: What is Free Software? Copyright, licenses, sharing<\/p>\n Miriam and Renata's talk: What is Debian?<\/p>\n Renata talking about internships with Debian<\/p>\n Thank you to all the women who participated!<\/strong><\/p>\n And to our lovely staff. Thank you, Lucio, for getting us the space and thank you, Pipefy<\/a>!<\/p>\n This has been partly documented at Debian Wiki (DebianWomen\/History) because the very next day after this meeting, Debian Wiki completely blocked ProtonVPN from even accessing the Wiki. Awesome. If anyone is able to, feel free to copy\/paste any of this text there.<\/p>","pubDate":"Sun, 13 May 2018 17:49:00 -0300","guid":"tag:rsip22.github.io,2018-05-13:\/blog\/debian-women-in-Curitiba.html","category":["blog","personal","debian","debian women"]},{"title":"Pushing a commit to a different repo","link":"https:\/\/rsip22.github.io\/blog\/pushing-a-commit-to-a-different-repo.html","description":" View from the Barra-Galheta beach trail, in Florianopolis, Brazil<\/em><\/p>\n My Outreachy internship with Debian is over. I'm still going to write an article about it, to let everyone know what I worked on towards the ending, but I simply didn't have the time yet to sit down and compile all the information.<\/p>\n As you might or might not have noticed, right after my last Outreachy activity, I sort of took a week off in the beach. \\o\/<\/p>\n Mila, a cute stray dog that accompanied us during a whole trail<\/em><\/p>\n For the past weeks, I've also been involved in the organization of three events (one of them was a Debian Women meeting in Curitiba<\/a> that took place two Saturdays ago and another one is Django Girls Porto Alegre<\/a>, which starts tonight). Because of this last one, I was reviewing their Brazilian Portuguese tutorial<\/a> and adding some small fixes to the language. After all, we are talking to women who read the tutorial during the workshop, so why all the mentions to programmers and hackers and such should mention the male counterpart in Portuguese? Women program, too!<\/p>\n When I was going to commit my fixes, though, I got an error:<\/p>\n Oops?<\/p>\n Yup, as it so happens more often than not, I forgot to fork the repository before starting to change the files! I just did 'git clone' straight to Django Girls' tutorial repository. But, since I had already done all the steps towards the commit, what could I do to avoid losing the changes? Could I just push this commit to another repository of my own and try and open a Pull Request to DjangoGirls\/tutorial?<\/p>\n Of course I had to go and search for that. Isn't that what all programmers do? Go and find someone else who already had the same problem they have to try and find a solution<\/a>?<\/p>\n Quick guide to the solution I've found:<\/p>\n Fork the original repository to my collection of repos (on Github, just clicking 'Fork' will do).<\/p>\n<\/li>\n Get the branch and the id of the commit that had been created. For instance, on this case:<\/p>\n<\/li>\n<\/ul>\n The branch is: master<\/p>\n The id is: 4d314550<\/p>\n Example with my repo:<\/p>\n And this was yet another article for future reference.<\/p>","pubDate":"Fri, 23 Mar 2018 00:49:00 -0300","guid":"tag:rsip22.github.io,2018-03-23:\/blog\/pushing-a-commit-to-a-different-repo.html","category":["blog","personal","git","github","djangogirls"]},{"title":"Women in MiniDebConf Curitiba campaign","link":"https:\/\/rsip22.github.io\/blog\/women-in-minidebconf.html","description":" This is the text of the crowdfunding campaign I am organizing with five other extraordinary women: Alice, Ana Paula, Anna, Luciana and Miriam.<\/p>\n Here is what Anna<\/a> has to say about Debian: \"Debian is one of the strongest GNU\/Linux distributions with the free software philosophy, and that's why it's so impressive. Anyone who comes in contact with Debian necessarily learns more about free software and the FLOSS culture.\"<\/p>\n The Debian project provides travel grants<\/a> for participation in conferences - for people who are considered project members.<\/p>\n And how many of these are women? Very few.<\/p>\n Women interested in attending MiniDebConf Curitiba<\/a> are many, but most of them do not have the means to travel to Curitiba, specially in a big country like Brazil.<\/p>\n It is a fact that women do not have the same opportunities in the IT world as men, but we can change that history. For this, we need your help.<\/p>\n Let's show that, yes, there are many women with potential interested in the world of free technologies and who use Debian. At MiniDebConf, women who could already be contributing to the community will have an opportunity to interact with it, taking part in tutorials, workshops and talks. It is in everyone's best interest that the community get itself ready to include them.<\/p>\n So, our way of helping to increase diversity in MiniDebConf - and perhaps among the people who contribute to Debian as well - is by giving these women the conditions they need to participate in the conference.<\/p>\n The Debian Women community is well developed in other countries, but in Brazil there were still no registered groups.<\/p>\n At last year's MiniDebConf, there was not one single woman speaker<\/a>.<\/p>\n But it does not have to be this way.<\/p>\n To be able to increase diversity and to change the current situation of exclusion that we currently have in the Brazilian community, we must act on many fronts. We are already working to foster the local community and to engage other women in the use and development of Debian.<\/p>\n That is why we want to also bring in women who are already Debian users, so they can share their experiences, so they can act as mentors to the newbies and so we can integrate all of them into the Debian development community.<\/p>\n There have already been successful campaigns in Brazil to include women in conferences and technology communities, both as participants and as speakers: PyLadies in FISL<\/a>, PyLadies in Python Brazil 12<\/a>, PyLadies in Python Brazil 13<\/a> and the Gophercon BR Diversity Scholarship<\/a>.<\/p>\n With your collaboration, this will be another goal achieved - and the Debian and free software communities will become a bit more representative of our own society.<\/p>\n Bitcoin - 15YFYKHr6CfYmBCyf4JM2g8WFkCmNGDGi5<\/p>\n Link to the campaign: https:\/\/www.catarse.me\/mulheres_na_minidebconf<\/a><\/p>","pubDate":"Mon, 05 Mar 2018 12:49:00 -0300","guid":"tag:rsip22.github.io,2018-03-05:\/blog\/women-in-minidebconf.html","category":["blog","personal","debian","debian women","women not in tech"]},{"title":"Woman. Not in tech.","link":"https:\/\/rsip22.github.io\/blog\/woman-not-in-tech.html","description":" Thank you, Livia Gabos<\/a>, for helping me to improve this article by giving me feedback on it.<\/em><\/p>\n Before I became an intern with Outreachy<\/a>, my Twitter bio read: \"Woman. Not in tech.\" Well, if you didn't get the picture, let me explain that meant.<\/p>\n It all began with a simple request I received almost an year ago:<\/p>\n Hey, do you want to join our [company] event and give a talk about being a women in tech?<\/em><\/p>\n<\/blockquote>\n I don't have a job in the tech industry. So, yes, while society does put me in the 'woman' column, I have to admit it's a little hard to give a talk about being 'in tech' when I'm not 'in tech'.<\/p>\n What I can talk about, though, it's about all the women<\/strong> who are not in tech<\/strong>. The many, many friends I have who come to Women in Tech<\/em> events and meetings, who reach out to me by e-mail, Twitter or even in person, who are struggling to get into tech.<\/p>\n I can talk about the only other girl in my class who, besides me, managed to get an internship. And how we both only got the position because we had passed a written exam about informatics, instead of going through usual channels such as referrals, CV analysis or interviews.<\/p>\n I can talk about the women who are seen as lazy<\/em>, or that they just don't get it<\/em> the lessons in tech courses because they don't have the same background and the same amount of time available to study or to do homework at home as their male peers do, since they have to take care of relatives, take care of children, take care of the housework for their family, most of the times while working in one or two jobs just to be able to study.<\/p>\n I can talk about the women and about the mothers who after many years being denied the possibility for a tech career are daring to change paths, but are denied junior positions in favor of younger men who \"can be trained on the job\" and have \"so much more willingness to learn\".<\/p>\n I can talk about the women who are seen as uninterested<\/em> in one or more FLOSS technologies because they don't contribute to said technology, since the men in FLOSS projects have continuously failed in engage and - most importantly - keep them included (but maybe that's just because<\/em> women lack role models).<\/p>\n I can talk about the many women I met not at tech conferences, but at teachers' conferences, that have way more experience with computers and programming than I. Women who after years working on the field have given up IT to become teachers, not because it was their lifelong dream, but because they didn't feel comfortable and well-integrated in a male-dominated full-of-mysoginistic-ideals tech industry. Because it was - and is - almost impossible for them to break the glass ceiling<\/a>.<\/p>\n I can even talk about all the women who are lesbians that a certain community of Women In Tech could not find<\/em> when they wanted someone to write an article about 'being homossexual in tech' to be published right on Brazil's Lesbian Visibility Day<\/strong>, so they had to go and ask a gay man to talk about his own experience. Well, it seems like those women aren't \"in tech\" either.<\/p>\n Tokenization can be especially apparent when the lone person in a minority group is not only asked to speak for the group, but is consistently asked to speak about being a member of that group<\/em>. Geek Feminism - Tokenism<\/a><\/p>\n<\/blockquote>\n The things is, a lot of people don't want to hear any those stories. Companies in particular only want token women<\/em> from outside the company (because, let's face it, most tech companies can't find the talent within) who will come up to the stage and inspire other women saying what a great experience it is to be in tech - and that \"everyone should try it too!\".<\/p>\n I do believe all women should try and get knowledge about tech and that is what I work towards. We shouldn't have to rely only on the men in our life to get things done with our computers or our cell phones or our digital life.<\/p>\n But to tell other women they should get into the tech industry? I guess not.<\/p>\n After all, who am I to tell other women they should come to tech - and to stay in tech - when I know we are bound to face all this?<\/p>\n For Brazilian women not in tech<\/strong>, I'm organizing a crowdfunding campaign to get at least five of them the opportunity to attend MiniDebConf<\/a> in Curitiba, Parana, in April. None of these girls can afford the trip and they don't have a company to sponsor them. If you are willing to help, please get in touch or check this link: Women in MiniDebConf<\/a>.<\/p>\n This is a short story about how chosing to use git branches saved me from some trouble.<\/p>\n Up until certain point, I was just commiting all the code (and notes) I wrote into the master branch, which is the default for Git. No big deal, if I broke something, I could just go back and revert one or more commits and it would be okay.<\/p>\n It got to the point, though, that I would have send the code to people other than the mentors who had been seeing me breaking things: I would have to submit it for other developers to test it. While a broken code was the ideal for my mentors to see and help me in figuring out how to fix it, that wouldn't be useful for people seeing it in production and giving me feedback and suggestions for improvement. I had to send to them a good code that worked, and I had to do that while I worked on the last functionality needed, which is the recurrence rule for events.<\/p>\n After working on the recurrence rule for a few hours I realized that, since it wasn't really functional yet, I couldn't simply commit it on top of the rest of the code that had already been commited\/published. Sure, I could have commented the function and commited the code that way, but it would be just too much trouble to have to comment\/uncomment it every time I would work on that part.<\/p>\n That is how I chose to create a new git branch instead and starting commiting there the changes I had made.<\/p>\n I created a new branch called \"devel\" and asked git to change to it:<\/p>\n Then, I did a \"git status\" to check everything was as expected and the branch had been changed to devel:<\/p>\n Next: staging the files and creating the commit<\/a>:<\/p>\n Because the branch was created on my local machine, if I straight out try to just push the code upstream, it will give an error, because there is no \"devel\" branch on Github yet. So let's give some arguments to the git push command, asking it to set an upstream branch in the origin, which will receive the code:<\/p>\n Simply because, before I sent the code to the moin-devel list, I decided to clean out the repository of the old and repeated code... by deleting those files. I wanted to do that so anyone who came to try it out would be able to spot the macro easily and not to worry whether the other files had to be installed anywhere for the code to work.<\/p>\n Once I had deleted those files using rm -r on the command line and right before I commited, I did a \"git status\" to check if the delete action had been recorded... that was when I noticed that I was still on the devel branch, and not on the master branch, where I wanted this change to take place! My development branch should<\/em> stay the mess it was because it was stuff I used to try out.<\/p>\n I had used \"rm -r\", though, so how did I get those files back to the devel branch? I mean, the easy way, not the downloading-the-repo-again way.<\/p>\n Simple! I would have to discard<\/strong> the changes (deletes) I had made on the devel branch and change to the master branch to do it again:<\/p>\n BE CAREFUL, THIS COMMAND WILL DISCARD ANY CHANGES YOU HAVE MADE WHILE WORKING ON THE CURRENT BRANCH<\/strong><\/p>\n This will throw away the changes. Then, it's possible to move back to the master branch:<\/p>\n And, yup, I'm totally writing this article for future reference to myself.<\/p>\n Hello!<\/p>\n If you follow this blog, you should probably know by now that I have been working with my mentors to contribute to MoinMoin EventCalendar macro, adding the possility to export the events' data to an icalendar file.<\/p>\n The code (which can be found on this Github repository<\/a>) isn't quite ready yet, because I'm still working to convert the recurrence rule to the icalendar format, but other than that, it should be working. Hopefully.<\/p>\n This guide assumes that you have the\nEventCalendar<\/a> macro installed on the wiki and that the macro is called on a determined wikipage.<\/p>\n The icalendar file is now generated as an attachment the moment the macro is loaded. I created an \"ical\" link at the bottom of the calendar. When activated, this link prompts the download of the ical attachment of the page. Being an attachment, there is still the possibility to just view ical the file using the \"attachment\" menu if the user wishes to do so.<\/p>\n There are two ways of importing this calendar on Thunderbird. The first one is to download the file by clicking on the link and then proceeding to import it manually to Thunderbird.<\/p>\n The second option is to \"Create a new calendar \/ On the network\" and to use the URL address from the ical link as the \"location\", as it is shown below:<\/p>\n As usual, it's possible to customize the name for the calendar, the color for the events and such...<\/p>\n I noticed a few Wikis that use the EventCalendar, such as Debian wiki<\/a> itself and the FSFE wiki<\/a>. Python wiki<\/a> also seems to be using MoinMoin and EventCalendar, but it seems that they use a Google service to export the event data do iCal.<\/p>\n If you read this and are willing to try the code in your wiki and give me feedback, I would really appreciate. You can find the ways to contact me in my Debian Wiki profile<\/a>.<\/p>","pubDate":"Wed, 21 Feb 2018 19:49:00 -0300","guid":"tag:rsip22.github.io,2018-02-21:\/blog\/howto-use-the-ical.html","category":["blog","personal","outreachy","development","moinmoin-wiki","icalendar","eventcalendar"]},{"title":"Debugging MoinMoin and using an IDE","link":"https:\/\/rsip22.github.io\/blog\/debugging-moinmoin-and-using-an-IDE.html","description":" When I was creating the cal_action, I didn't quite know how to debug MoinMoin. Could I use pudb with the wiki? I wasn't sure how. To figure out if the code I was writing worked, I ended up consulting the error logs from Apache. It sort of worked, but of course that was very far<\/em> from the ideal. What if I wanted to check something that wasn't an error?<\/p>\n Well, MoinMoin supposedly has a logging module, that lives on I searched some more and found a guide on setting up Winpdb Source Level Debugger<\/a>, but I don't use Windows (really, where is the GNU\/Linux guide to debug?), so that didn't help. 😭<\/p>\n But<\/em>... MoinMoin does offer a guide on setting up a development enviroment with Eclipse<\/a> that I ended up following.<\/p>\n Up until this point, most of the code I created in Python where simple scripts that could be ran and debugged in the terminal. I had used IDLE<\/a> while I was taking the Python para Zumbis<\/a> (Python for Zombies) course, but other than that, I just used a code editor (Sublime, then Vim and, finally, Atom) when programming in Python.<\/p>\n When I was taking a tech vocational course, I used Eclipse, an Integrated development environment, or IDE<\/a> to code in Java, but that was it. After I passed the course and didn't need to code in Java again, I simply let go of the IDE.<\/p>\n![\"picture](\"https:\/\/rsip22.github.io\/blog\/img\/pybr_tag.JPG\")
<\/p>\n![\"picture](\"https:\/\/rsip22.github.io\/blog\/img\/pyladies_br_conf.JPG\")
<\/p>\n![\"picture](\"https:\/\/rsip22.github.io\/blog\/img\/pybr_pybladiesbrconf_pyladies_poa.jpg\")
<\/p>\nThe PythonBrasil[14] conference<\/h2>\n
Day 1 - tutorials<\/h3>\n
Day 2 - tutorials<\/h3>\n
![\"An](\"https:\/\/rsip22.github.io\/blog\/img\/Sorting_heapsort_anim.gif\")
<\/p>\nDay 3 - talks<\/h3>\n
![\"Elias'](\"https:\/\/rsip22.github.io\/blog\/img\/pybr_cli_development.JPG\")
<\/p>\nDay 4 - talks<\/h3>\n
![\"Picture](\"https:\/\/rsip22.github.io\/blog\/img\/pybr_facebook_keynote.JPG\")
<\/p>\n![\"PythonBrasil](\"https:\/\/rsip22.github.io\/blog\/img\/pybr_official_photo.JPG\")
<\/p>\n![\"picture](\"https:\/\/rsip22.github.io\/blog\/img\/pybr_women.JPG\")
<\/p>\nDay 5 - talks<\/h3>\n
![\"picture](\"https:\/\/rsip22.github.io\/blog\/img\/pybr_renata_davila.JPG\")
<\/p>\n![\"PyLadies](\"https:\/\/rsip22.github.io\/blog\/img\/pybr_pyladies_django_girls.JPG\")
<\/p>\n![\"Thrycia](\"https:\/\/rsip22.github.io\/blog\/img\/pybr_thrycia.jpg\")
<\/p>\nDay 6 - sprints<\/h3>\n
Wrapping things up...<\/h2>\n
![\"picture](\"https:\/\/rsip22.github.io\/blog\/img\/pybr_natal.jpg\")
<\/p>\nThank you notes<\/h2>\n
\n
Debian Women meeting in Curitiba (March 10th, 2018)<\/h2>\n
![\"The](\"https:\/\/rsip22.github.io\/blog\/img\/debian_women_05.JPG\")
<\/p>\n![\"A](\"https:\/\/rsip22.github.io\/blog\/img\/folder_Debian_women.JPG\")
<\/p>\n![\"Pipefy](\"https:\/\/rsip22.github.io\/blog\/img\/Pipefy2.png\")
<\/p>\n\n
![\"The](\"https:\/\/rsip22.github.io\/blog\/img\/debian_women_01_breakfast.jpg\")
<\/p>\n![\"Miriam](\"https:\/\/rsip22.github.io\/blog\/img\/debian_women_02_what_is_free_software.JPG\")
<\/p>\n![\"Renata](\"https:\/\/rsip22.github.io\/blog\/img\/debian_women_03_what_is_Debian.JPG\")
<\/p>\n![\"Renata](\"https:\/\/rsip22.github.io\/blog\/img\/debian_women_04_internships_with_Debian.JPG\")
<\/p>\n![\"The](\"https:\/\/rsip22.github.io\/blog\/img\/debian_women_06_Debian_Women_with_staff.JPG\")
<\/p>\n![\"Photo](\"https:\/\/rsip22.github.io\/blog\/img\/trilha_da_galheta_florianopolis.JPG\")
<\/p>\n![\"Renata's](\"https:\/\/rsip22.github.io\/blog\/img\/renata_with_dog.JPG\")
<\/p>\n<\/span>remote<\/span>:<\/span> error<\/span>:<\/span> GH006<\/span>:<\/span> Protected<\/span> branch<\/span> update<\/span> failed<\/span> for<\/span> refs<\/span>\/<\/span>heads<\/span>\/<\/span>master<\/span>.<\/span>\nTo<\/span> https<\/span>:<\/span>\/\/github.com\/DjangoGirls\/tutorial<\/span>\n!<\/span> [<\/span>remote<\/span> rejected<\/span>]<\/span> master<\/span> -><\/span> master<\/span> (<\/span>protected<\/span> branch<\/span> hook<\/span> declined<\/span>)<\/span>\n<\/code><\/pre><\/div>\n\n\n\n
<\/span>[master 4d314550] Small fixes for pt-br version<\/span>\n<\/code><\/pre><\/div>\n\n\n\n
<\/span>git push URL_FOR_THE_NEW_REPO commit_id:branch<\/span>\n<\/code><\/pre><\/div>\n\n\n<\/span>git push https:\/\/github.com\/rsip22\/tutorial 4d314550:master<\/span>\n<\/code><\/pre><\/div>\n\n\n![\"Women](\"https:\/\/rsip22.github.io\/blog\/img\/women_in_minidebconf.png\")
<\/p>\n![\"Women](\"https:\/\/rsip22.github.io\/blog\/img\/who_are_the_women_in_minidebconf.png\")
<\/p>\n\n
![\"A](\"https:\/\/rsip22.github.io\/blog\/img\/debconf_proposal.png\")
\nEven though there are so many Women in Tech communities in Curitiba, as listed above, the all-male 'core team' of the local Debian community itself couldn't find a single woman to work with them for the DebConf proposal. Go figure.<\/em><\/p>\n\n
![\""Don't](\"https:\/\/rsip22.github.io\/blog\/img\/dont_talk_diversity_naomi_ceder.png\")
<\/p>\nAddendum:<\/h4>\n
More on the subject:<\/h4>\n
\n
How did I decide to use a new branch?<\/h3>\n
<\/span>git checkout -b devel<\/span>\n<\/code><\/pre><\/div>\n\n\n<\/span>git status<\/span>\nrenata@debian:~\/foss_events$ git status<\/span>\nOn branch devel<\/span>\n<\/code><\/pre><\/div>\n\n\n<\/span>git add --all .<\/span>\ngit commit -m "COMMENTS FOR THE COMMIT"<\/span>\n<\/code><\/pre><\/div>\n\n\n<\/span>git push --set-upstream origin devel<\/span>\n<\/code><\/pre><\/div>\n\n\nHow did this save me from some trouble?<\/h3>\n
<\/span>git checkout -f<\/span>\n<\/code><\/pre><\/div>\n\n\n<\/span>git checkout master<\/span>\n<\/code><\/pre><\/div>\n\n\nRead more<\/h3>\n
\n
![\"A](\"https:\/\/rsip22.github.io\/blog\/img\/create_ical.png\")
<\/p>\n![\"Wiki](\"https:\/\/rsip22.github.io\/blog\/img\/eventcalendar_with_ical_menu.png\")
<\/p>\n![\"Thunderbird](\"https:\/\/rsip22.github.io\/blog\/img\/events_and_tasks_import.png\")
<\/p>\n![\"Thunderbird](\"https:\/\/rsip22.github.io\/blog\/img\/thunderbird_new_calendar_location.png\")
<\/p>\n![\"Thunderbird](\"https:\/\/rsip22.github.io\/blog\/img\/ical_imported_to_thunderbird.png\")
<\/p>\nDebugging<\/h3>\n
moin-1.V.V\/wiki\/config\/logging\/<\/code>, but I simply couldn't get it to work as I wanted.<\/p>\nUsing an IDE<\/h3>\n
![\"Eclipse](\"https:\/\/rsip22.github.io\/blog\/img\/moin_with_eclipse.png\")
<\/p>\n