Week 9/15 + 10/15
I fixed the TV by numbers translator and submitted a PR for it. Following it, I updated the BBC translator for handling old pages. With Zotero 5.0 release, I had to change the document accordingly as the Firefox add-on is no longer supported. I learned what CSS selectors are and will shortly begin to write a translator using them to get clarity on the topic. There are two methods, attr() and text() that have been recently written and will be included into future Zotero versions. So I am trying to figure out where to add them in the docs. Learned about querySelector and querySelectorAll and I am no front-end developer but it seemed such a powerful use of CSS selectors.
The work is fun the new changes in Zotero made me google and learn new stuff. For past two days, I have been going and reading the discussion at https://github.com/zotero/translators/issues/1277 to make sense out of it.I will have to catch up some speed to finish this draft by the end of next week so it can then be reviewed again.
With the mid term approaching, my mentor suggested that the first draft of the doc should be developed such that it can be used to write a translator and then we can note down things that need improvement. I finished the work on coding a translator and the template. This brings section 5 in a concrete shape. I look forward to finish the draft this week.
Other than that I am working on a translator TV by the numbers which needs rewriting.
This weeek I continued my work on the Mediawiki translator and simultaneously documented it. I skimmed through open issues and picked this one https://github.com/zotero/translators/issues/1020 to solve. For the comming week, I look forward to solve some more issues and write a few translators.
For the 6th Week, I finished with the 5th section of the documentation covering the common code blocks in a Zotero translator. I have planned to move the code snippets from this section to the next section which will be covering the working example of mediawiki translator because I will have to explain the code and adding it here will be redundant. I made use of Embedded Metadata.js in the Oxford Reference translator. Waiting for response from the developers.
We had our first meeting on 20th June on #wikimedia-devrel and it was fun to learn from where everyone came from and what they are working on. Most of it was new for me as I didn’t have a chance to take a look on those projects in the past while filing the application. I wish I take some time out and see each one of them since the interns explained their projects very well. So it’ll be easy for me to know what they were talking about 😀 . I also got to know about Wikimania that is taking place in August in Canada. Would have loved to attend it but I will be having my placement session.
Srishti gave me feedback on the work done till now and it is very valuable. I think every fortnight I should (patiently because it takes effort to read something that you wrote again and again) go through the doc and write down the stuff that needs any change.
Welcome back 😀
Our dear chatroom went through some heath issues (technical problems) this week and couldn’t play a part in the communications we made. My mentor suggessted the steps that I could take to bring it back to life. The developers of WMF took a great care of it by making it a “High” priority. A mail this morning greeted me with the good news from my mentor informing me that the chatroom was fit and fine now. Its good to have the non-living member back on the team 😀 😀
Note: Find my work here.
Summers 2017: You must never forget the reasons behind your actions that brought you where you are.
Yes, I agree, 18th May to 1st June, a huge time span. Well, I couldn’t make the last blog post so this will be summing up my work from then till today.
I have decided to write a translator for mediawiki.org and present that as the working example for the documentation. I went through the existing translator Wikipedia.js in order to understand how wiki sites need to be translated and what all data is included in the citation for these articles. Though MediaWiki pages won’t be similarly extracted, it provided a fair idea to me because I was confused about where to begin with translating these huge pages. For translation of search results, I went through Wikisource.js. Things are clearer now. Also, I looked into the user guide of VisualEditor (a quick read, as it is pretty easy to use anyway).The official internship period started on 30th May, 2017. Now I can say, I am an intern at Wikimedia, Woohoo!
For the first week, as planned, I have started working on the two sections of the documentation, brief about Citoid, Zotero and their relationship. I went through all the possible content available on Citoid and wrote a gist about it. Of course with a wiki page dedicated to it, it doesn’t make sense to elaborate it. I came across a research done on Citoid’s support and the TWL/Citoid page. Some issues reported there are resolved, some aren’t. It also made clear how important it is to widen the coverage of Zotero translators.
With at least 7 hours given to the project every day, I am looking forward to creating more translators alongside. I have been a little inactive since the last translator got merged. I have a few sites in line. Let’s see how this week ends.
Deadline: 5th June 2017
Summers 2017: This is what it looks like on heated afternoons.
I am skimming through Paulo Coelho: Confessions of a Pilgrim by Juan Arias and I found this:
We put thirty spokes together and call it a wheel,
But it is on the space where there is nothing that the
usefulness of the wheel depends.
We turn the clay to make a vessel,
But it is on the space where there is nothing that the
usefulness of the vessel depends.
We pierce doors and windows to make a house,
And it is on these spaces where there is nothing that the
usefulness of the house depends.
Therefore just as we take advantage of what is, we should
recognize the usefulness of what is not.
I recently watched a Ted talk https://www.youtube.com/watch?v=w7rewjFNiys&t=853s
Is this an omen?
Pleasure and Happiness
“Pleasure is a ‘good fight’ that is something very different to happiness. I don’t relate happiness to pleasure. The idea I have of happiness is very boring: a Sunday afternoon when nothing happens.The struggle and combat, enthusiasm for fighting a battle for something you believe in, sometimes you win and sometimes you lose, but it doesn’t matter, what counts is the struggle to bring something about. That for me is the pleasure of life. So let us say pleasure is everything you do with enthusiasm in life, which can include suffering and pain, but that doesn’t annul the deep pleasure of knowing you’re struggling for something you love.”
This is my first blog after getting selected as an intern for Wikimedia. Well, this is my first written account of any type after this little achievement. I haven’t yet made a diary entry for it, nor emailed my college mentor thanking him for every possible support. So I think this blog entry might go haywire, but I’ll try my best to keep it formal and on track.
Outreachy, previously called OPW-Outreach Program for Women is a three-month paid internship program for cisgender and transgender women, people of other gender identities that are minorities in open source (including transgender men and genderqueer people). The best part about this program is that it asks you to be 18 years or more of age, nothing else. Just nothing more than that. So you can either come from business or arts, be a single mother or an undergraduate, be in your teens or be a forty plus diva, you are welcomed to apply.
It was my second attempt in Outreachy. I applied in round 13 with Zulip. Though I didn’t make it that time but the experience was very fruitful. It taught me how to study huge projects’ code in a way that you find sections that matter to you in order to solve some specific bug. I learned how to communicate with mentors and peers. Research, try to answer our own questions and if you still feel stuck, ask for help.
I was looking at the participating organization list of round 14 and thought why not Wikimedia? Our college hosted WikiToLearn conference’2017 in January and I think somewhere it played a role why I decided to go through the project list of Wikimedia.
I’ll be documenting the process of creating a Zotero translator. I believe during the documentation, I’ll come across many aspects of Citoid and these translators that I haven’t discovered yet. The existing documentation is pretty old and there are some topics that I want to include in my version.
Work done till 17th May’17
- Joined Zulip server for the participants
- Introduced myself on the mailing list wikitech-l@lists
- Created a Phabricator task for submitting the weekly reports
- Redesigned my blog, which keeps happening
- Updated my Mediawiki user page, this will also happen often in near future
I wanted to set up Citoid because I want to solve issues but it is difficult to find a solution if you don’t know the problem clearly. So I decided to setup Citoid. Documentation is at https://www.mediawiki.org/wiki/Citoid
- In production, node v6 is being used. So install that.
- Follow section 3.1, that is, install from scratch.
- When the server is up, enter the url you want to test.
- To stop the server use ctrl+c and NOT ctrl+z.
- In case you suspend the server with ctrl+z, use
killall -9 node
All for now. Let’s hope I am able to improve some code.