<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ekta Mishra on Medium]]></title>
        <description><![CDATA[Stories by Ekta Mishra on Medium]]></description>
        <link>https://medium.com/@darecoder?source=rss-88373be9de43------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*fv5t7SrZC0Mjr1jadnUnxw.png</url>
            <title>Stories by Ekta Mishra on Medium</title>
            <link>https://medium.com/@darecoder?source=rss-88373be9de43------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:50:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@darecoder/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Red Hat intern interview experience!!!]]></title>
            <link>https://medium.com/code-for-cause/red-hat-intern-interview-experience-221d511260cf?source=rss-88373be9de43------2</link>
            <guid isPermaLink="false">https://medium.com/p/221d511260cf</guid>
            <category><![CDATA[intern]]></category>
            <category><![CDATA[red-hat-openshift]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Ekta Mishra]]></dc:creator>
            <pubDate>Sat, 09 Jan 2021 15:35:34 GMT</pubDate>
            <atom:updated>2024-06-16T21:56:56.794Z</atom:updated>
            <content:encoded><![CDATA[<p>Did I get selected? Read it till the end to know :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PYQE_QjCP-6y-pGW.jpg" /></figure><p>Hey, so starting with who I am? I’m a final year B.Tech CSE student passing out in 2021 and like most final-year students, I was also looking for some 6-month internship or full-time opportunities. Then, one day I saw a LinkedIn post by Vidhya Raghunath ma’am(Principal TA Red Hat, so now you know whom to contact) regarding Red Hat hiring software engineering interns.</p><p>Then, I also submitted my resume and luckily got the mail for an online coding challenge. You can consider this as the 1st round. In this, there were 2 coding problems and 5 MCQs. One coding question was a pretty easy Adhoc problem and the other was based on Dynamic Programming. If I have to scale them through general Competitive Coding platforms, I would say the questions’ level was Leetcode easy to medium. So, If you practice regularly on Leetcode, you will easily qualify. MCQs were based on Data Structures, time complexity, aptitude &amp; reasoning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9GbWKxQq9Cwy35X2.jpg" /></figure><p>After 3–4 days, I got the result for the previous round, that I’m shortlisted and require to tell the earliest slot possible for the technical interview. I love technical interviews, as it teaches a lot of things, boosts your confidence, you get to interact with some cool engineers and you get a self-analysis of your performance too. In the technical interview, there were 2 interviewers, both were software engineers at Red Hat. Technical interviews are very dynamic in nature as it totally depends on what you had mentioned in your resume, your projects, &amp; interests. So, the interviewer started with the introduction, then moved to what work experience I have in terms of past internship, Open-Source contributions, and tech stack I have worked with. Then he asked some general interview questions based on DBMS, databases like PostgreSQL, MongoDB, etc. He also asked a few things in Operating System. Finally, at the end of the interview, he asked me a question based on Matrices and then asked me to implement(to code on online IDE) Binary Search Tree, few questions on optimization and time complexity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*s0RMyzf8w6qGjkzX" /></figure><p>After that interview, I was very happy with my performance so somewhere I knew that I’ll get the call for the next round and so did it happen. The next round was a very interesting one, you may call it the managerial round as this round was taken by 2 very senior people at Red Hat. Unfortunately only one wasn’t able to take the interview in the 1st managerial round that’s why I had 2 managerial rounds but generally the process includes only one MR. This round is to see if you are a good fit for their company or not, do you understand their work culture or not, and discuss about you. They asked if I’m aware of some products at Red Hat or not. The good thing was I had used and explored some of the Red Hat products in the past so the discussion went very well. In the end, they explained to me that if I get selected on which team I’ll be working on and how it will be for the next 6 months.</p><p>Then, after 1 week I got the results that I’m selected. I was thrilled because in Red Hat you get to work on the latest top-notch technologies and the way Red Hat supports open-source is outstanding so what could have been better than this. I have joined now as an intern in the Developer Engineering team now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kEgObT5dhjJ3mLwQ.jpg" /></figure><p>Feel free to ask anything and if you find this article useful, clap and share :)</p><p><a href="https://twitter.com/darecoder">https://twitter.com/darecoder</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=221d511260cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-for-cause/red-hat-intern-interview-experience-221d511260cf">Red Hat intern interview experience!!!</a> was originally published in <a href="https://medium.com/code-for-cause">Code for Cause</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Outreachy finale: Journey as an intern]]></title>
            <link>https://darecoder.medium.com/outreachy-finale-journey-as-an-intern-1d371fa1e2b4?source=rss-88373be9de43------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d371fa1e2b4</guid>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Ekta Mishra]]></dc:creator>
            <pubDate>Thu, 13 Aug 2020 16:45:02 GMT</pubDate>
            <atom:updated>2020-08-13T18:12:39.953Z</atom:updated>
            <content:encoded><![CDATA[<p>All good things must come to an end, and so is my 3 months roller coaster journey as an Outreachy intern!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/0*xbPZbqBddXtroRRk" /></figure><p>My project for Outreachy internship with OpenRefine was to add support for more Wikidata constraints in OpenRefine. I have already published some blogs about my selection process, OpenRefine, the challenges I faced initially, and how my project tweaked a bit from the original proposal. You can go through those blogs to have a detailed description of every bit of my 3 months journey and much more.</p><p>This blog will be totally about what progress did I made as an Outreachy intern in my technical skills, soft skills, what all did I learned from this, and how it is going to help in my career.</p><p>Initially, when I was selected, I was very good at Java and DSA. But my project wasn’t limited to Java, So obviously I have to learn the other requirements needed for it like TestNG &amp; Mockito testing framework, Native JavaScript, working with Travis CI, and many other things. The interesting fact is when I got selected for the project which was totally based on Wikidata, at that time I didn’t even know much about Wikidata too. But at the end of the day if you’re willing to learn and challenge yourself there’s nothing which can be a roadblock for you.</p><p>I had made the proposal in such a way that the tasks were prioritized in the order easy to complex so that I don’t end up being stuck on a task for a very long time hampering my whole project. I didn’t have the confidence in myself that I would ever be able to complete this project but with the guidance and support provided by my mentor, I moved forward steadily and consistently with great progress.</p><p>With this internship, the major perk that I count is the networking option, you get connected with many families, like the Outreachy team, the organization you got selected in, other co-interns selected along with you as Outreachy intern. Along with this, after the selection, you will get a number of mails, requests, messages over LinkedIn, Twitter, etc about sharing your strategy, experience, queries about the program, requests for help and guidance, and much more. Sometimes, you even get a job offer from the organization you had been an intern for or from some outsider companies seeing your work. So, this was an opportunity I never dreamt of but living these 3 months was no less than a dream.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d371fa1e2b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Modifying Expectations: Progress Report]]></title>
            <link>https://medium.com/code-for-cause/modifying-expectations-progress-report-79ca8f08ede7?source=rss-88373be9de43------2</link>
            <guid isPermaLink="false">https://medium.com/p/79ca8f08ede7</guid>
            <category><![CDATA[internship-experience]]></category>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Ekta Mishra]]></dc:creator>
            <pubDate>Tue, 07 Jul 2020 17:15:18 GMT</pubDate>
            <atom:updated>2020-07-07T17:45:44.130Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Halfway journey as an Outreachy intern for OpenRefine organization</em></strong></p><p>As we all know, before the contribution period we have a list of organizations and projects from which we can easily choose projects and organizations of totally our choice. It’s the most delightful thing about Open-Source programs like Outreachy, GSoC, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YhjdHriIcYYL16sai36L8g.jpeg" /></figure><p>So, when the choice came into my hands, I started making my preferences according to the skills I have already have and those which I was keen to learn. I had a look at nearly every organization, there were about 20–25 organizations so giving a bit of time to read about it, to see what kind of products they make wasn’t really a big task. Exploring organization in my sense doesn’t really means to contribute to it or to set up their products, no not at all. But to just get a gist of what kind of products/ projects they have, so it will not take a lot of your time.</p><p>For instance, you love to learn about networks, and then there is some organization which works for serverless network system, etc. Then, working with that organization will make your journey very delightful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZWLCNUNZLrGCsHZR8IOgyQ.png" /></figure><p>The same is the case when you choose the project on the basis of skills you have or you have an interest in them. I chose the <strong><em>OpenRefine project based on Java — “</em></strong><a href="https://www.outreachy.org/outreachy-may-2020-internship-round/communities/openrefine/#implement-more-constraint-checks-in-openrefines-wi"><strong>Implement more constraint checks in OpenRefine’s Wikidata extension</strong></a><strong>”<em>.</em></strong></p><p>So, the project was to add support for new Wikidata Constraint checks. OpenRefine already has a no. of constraints implemented in it. The project scope also involves improving the existing functionality of the constraints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cmHvTcLKocjhsuey9OG8MQ.png" /></figure><p>I started with the implementation of some simple constraints in 1st phase which was in accordance with my final proposal/timeline I submitted in Outreachy final application. It went smooth I successfully added support for 3 new constraints and along with that improved some basic things in existing constraints. Moving forward with the existing architecture of implementing constraints, I and my mentor found that we need to tweak the existing architecture of Scrutinizer classes and especially the testing of the scrutinizers to improve the readability, understanding, and performance of the constraint checks.</p><p>Then, we decided before implementing or adding support for constraint checks we should improve the current architecture a bit. Earlier the testing classes were depended on MockConstraintFetcher for fetching the required parameters and other data. But in reality, it wasn’t fetching, it provides hardcoded data from that class. Therefore, a better approach was required. We decided to use mocks in the test classes to send the parameters etc for which we preferred Mockito Library.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/347/1*AjG3etoJT0MLVbqvTecphw.jpeg" /></figure><p>I wasn’t familiar with the Mockito testing framework but I studied about it from some tutorial series and took help from my mentor whenever required. After this, we changed the testing architecture to a completely new look which is in my sense more understandable and powerful. Now, we can add as many different test cases in the test files as we want without actually depending on any other file to provide support for it. In reality, this is actually what the unit testing should be where testing of a single unit(i.e. class in Java) shouldn’t depend on the performance of other units.</p><p>Thereafter, we went on to the implementation of the Scrutinizer classes. In those, we are fetching the parameters and checking if the particular property has this constraint applied to it or not. For that also, we shifting the fetching and parsing code for each constraint in the Scrutinizer class itself by adding an inner class in each of them defining the Constraint.</p><p>So, this was how we shifted the goal of our original project to improve the end results of the project. After done with the refactoring of architecture, now we are back on track again. I have started implementing and adding support for the new constraint checks for Wikidata again. But changing the architecture is making the workflow much easier and smoother for me now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*ihyjRrwIdWr1o1KNaxtGNg.png" /></figure><p>Progress so far: <a href="https://github.com/OpenRefine/OpenRefine/pulls/darecoder1999">https://github.com/OpenRefine/OpenRefine/pulls/darecoder1999</a></p><p>Also, I have passes the 1st phase evaluation successfully &amp; got the initial phase payment. Done with the midpoint feedback too, waiting for its results. This was all about an overview of my halfway journey till now as an Outreachy intern. More learning and development is yet to do. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79ca8f08ede7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-for-cause/modifying-expectations-progress-report-79ca8f08ede7">Modifying Expectations: Progress Report</a> was originally published in <a href="https://medium.com/code-for-cause">Code for Cause</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We have to face our ‘Fears’]]></title>
            <link>https://darecoder.medium.com/we-have-to-face-our-fears-246020c33e7a?source=rss-88373be9de43------2</link>
            <guid isPermaLink="false">https://medium.com/p/246020c33e7a</guid>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[fears-and-questions]]></category>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Ekta Mishra]]></dc:creator>
            <pubDate>Thu, 04 Jun 2020 18:55:41 GMT</pubDate>
            <atom:updated>2021-11-04T16:09:52.933Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The choice remains in our hands — to experience adventure or to be limited by the fear of it.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eYAABkCYsGCYfnBt_f5MtA.jpeg" /><figcaption>Quote by Eric Thomas</figcaption></figure><p>OpenSource world has always tried its best to welcome the newcomers and beginners in this beautiful journey. It is built and supported by people that not only run this kind of development world but also always willing to provide a helping hand to everyone. It is more than just a way of software development, its a culture to be followed and promoted.</p><p>But still, even after many efforts of numerous people out there, sometimes it comes out a bit intimidating for newcomers in OpenSource. People get conscious about the fact that their work is open to all, so people might judge their initial contributions, comment on that if it has any silly mistakes, and might think how naive this person is for taking so much time in fixing an issue that is very basic, or maybe having good first issue tag on it. People do overthink these kinds of questions in their mind, it’s human nature.</p><p>Whereas the things turn out totally different in OpenSource, the advantage of openwork is that anyone from the community can review your work that could result in a fast response. Second thing, you will get opinions and suggestions from many people so you will have a better idea of how you can approach an issue, you will easily get help from the community if in case you get stuck anywhere and they won’t judge you for this ever &amp; most importantly those suggestions are also tracked by maintainers and mentors so you will have a very rare chance to get a wrong suggestion from anyone.</p><blockquote><strong>“Ask dumb questions. It’s the smartest thing you can do.”</strong></blockquote><p>The last thing is that it increases your communication with the community. The best way to have better interaction with the community is to talk through your work. The discussion that takes birth in the form of comments &amp; suggestions while reviewing your PR or approaching an issue is the best kind of interaction in OpenSource. Then, through this only, you will get to know how friendly and supportive your co-contributors, maintainers, and mentors are. So, never hesitate or step back to ask questions, to create a pull request, or in helping anyone else. The community is made for this, and the only line which they always cherish is ‘The dumbest question is the one that is never asked’. So, don’t restrict yourselves to speak in a public forum or channel, to showcase your work, to put forward your suggestion on any PR or issue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XYBwEl3BzS6t5f-TUEBDVA.jpeg" /><figcaption>- Alexander Jarvis</figcaption></figure><blockquote><strong>Always welcome others’ opinions &amp; accept your mistakes</strong></blockquote><p>One more thing which I felt at my initial phase of contributions and I know many other people who felt the same is that when you create a pull request regarding any issue, maintainers generally request some changes or modifications to your work, at that time don’t feel like your work is not up to the mark, it has flaws or someone pointed your mistakes or you have done something wrong. The mentors and reviewers don’t want to stoop or humiliate anyone, they just want to improve your work so that it can be merged into the main source code and your name can be listed in the contributors&#39; list. If you feel that they shouldn’t request those changes to improve the code, then what will be the 2nd option left, they’ll just close your pull request without specifying what was wrong in that. And due to this behaviour, no one would ever try again to contribute to OpenSource. But if you will politely accept those changes requested by them and make the desired updates you will get the feeling of making a significant contribution to the Organisation. :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fYr_LETgFNpFADbLmhFAXQ.jpeg" /></figure><blockquote><strong>It’s okay to be stuck.</strong></blockquote><p>My Outreachy internship period started a few weeks ago. In the 1st week, I have to implement some constraint checks for Wikidata imports. Now, clearly the work is based on the constraint, and in the 1st week, I got stuck on a very silly point that how even the constraints are applied on a certain property. I have to go through the documentation and some tutorials to know the working of it. When I started implementing them, sometimes I got stuck in parameters parsing, sometimes in reducing the complexity of the code in terms of efficiency and many more. But I kept on surfing, researching, and exploring the code &amp; documentation. Some things worked, some didn’t. After investing numerous hours implemented a few constraints in the 1st week and created pull requests for it. For some moments, there was a feeling of achievement in myself for accomplishing the weekly tasks.</p><p>Then, after some time, my mentor reviewed my work and requested some changes to it. And you know, the changes he requested sounded very difficult to me because they were out of my thinking scope while implementing them. But the fact that came into my mind at that moment wasn’t the changes he asked to do. It was the fact, that how could he analysed the PR so fast and pointed out those faults, it was unbelievable to me. And it always remains the fact that when we see the contribution of our mentors and other contributors that are working in the organisation for a pretty good time is commendable. They resolve giant issues in a very short period of time, the approach they have for bugs, issues is something that sounds very exceptional to a newcomer.</p><blockquote><strong>“Everyone struggles, don’t ever forget that.” — Anonymous</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gYojMuVVvf0cJ5mWtjec8Q.jpeg" /><figcaption>source: therightmessages.com</figcaption></figure><p>At that time, don’t make yourself feel demotivated due to the fact that how I would be able to work with them, meet their expectations. Rather, you should feel motivated with the fact that they also have had struggles with the code at their initial phase and they also had faced problems at their time and had to invest a numerous hours in understanding the codebase and going around the documentation. We should feel lucky that we have got such mentors that are so qualified enough that they detect are subtle mistakes in a moment of seconds.</p><p>Many a time when I create pull request or change any existing one, the tests fail, sometimes I have no clue how to proceed in implementing a particular class or method, writing tests to test your code is also one of the things I suck too. But the more and more time I’m giving to it, I have started loving to play around it. So, always remember the fact that “Everyone struggles”. Be patient, be consistent, and keep working. Just don’t sit back struggling in a particular problem for days, the mentors are there to guide you, so take their guidance and help to make this journey more beautiful and fruitful.</p><blockquote><strong>Thank You.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=246020c33e7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OpenRefine — The power tool]]></title>
            <link>https://medium.com/code-for-cause/openrefine-the-power-tool-fae34c001d41?source=rss-88373be9de43------2</link>
            <guid isPermaLink="false">https://medium.com/p/fae34c001d41</guid>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[openrefine]]></category>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[java]]></category>
            <dc:creator><![CDATA[Ekta Mishra]]></dc:creator>
            <pubDate>Wed, 27 May 2020 15:15:18 GMT</pubDate>
            <atom:updated>2020-05-29T04:32:23.886Z</atom:updated>
            <content:encoded><![CDATA[<h3>OpenRefine — The power tool</h3><p>OpenRefine, also formerly known as Google Refine, is an Open Source software used to work with messy data and provide many functionalities for data refining, data processing, data manipulation, reconciliation, importing data to wikidata, and other additional support for external web services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*MabQyppm7e3i8Gg4cb4Odw.png" /></figure><p>By using OpenRefine, you can inspect errors in your data, amend your data, and even save its history. What’s more interesting about it, you can reverse your actions to any stage where you want. So, there’s no hassle about either you should apply a certain operation or not. You can always test any kind of operations on it to see how it works on the dataset.</p><p>Many of you have maybe already used OpenRefine for data analysis and linking your data to the web. Still, some of you might not have a detailed view of what actually OpenRefine does. In this Introductory article on OpenRefine, we’ll talk about its applications, working, how to get started with it and contribute to it.</p><p>For using OpenRefine, you can either directly <a href="https://openrefine.org/download.html">download</a> the latest version of it from <a href="https://openrefine.org/">the official website</a> or can build it from <a href="https://github.com/OpenRefine/OpenRefine">the source code</a> available on its Github page.</p><blockquote><strong>Applications:</strong></blockquote><p>OpenRefine provides you an interface through which you can create a project using any CSV, XML, Excel (.xls and .xlsx), JSON, and other Google data documents you can first create your project to perform the operations. You can even create projects by providing valid URLs to download the data. Once you have created the project now using various facet operations you can inspect the nature of the data, you can find out if there are null values, identical values, etc. By using the feature text facet you can even group the data and provide them exactly the same value to all identical cell values, which will make it easier for further processing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E0nHvRuy6BOnXS7_iiLjog.png" /></figure><p>OpenRefine provides another feature to even join the groups of values that are identical without even manually visiting them. You can use the clustering feature to group by the identical values. Performing these kinds of operations provides you the data in a manner where you can have a quick decision about the nature of the data. If done carefully, it also provides good help in reconciling the data. We’ll talk about reconciliation.</p><p>You can even add columns on the basis of existing columns and URLs. You can perform scripting operations with GREL (General Refine Expression Language) on the values of a column to modify it according to your own use-case. GREL provides you something similar to what formulae do to Excel and queries to SQL.</p><p>For instance, you are provided with data of branch post offices having a column of Branch post offices’ name with Pincode and you want to extract names and Pincodes in different columns then, using GREL expressions you can substring the values present in that column and generate two other columns. So, it makes the data more readable. Not only this, but GREL expressions also provide you a lot of power to play with your data.</p><p>Public and open datasets are generally inconsistent and messy. Sometimes, there are unwanted values and columns that you probably don’t want for your use-case. But, public open databases are generally provided in that form so that it can fulfill the needs of a larger audience. Using OpenRefine you can clean your datasets accordingly.</p><p>This was all about the analysis part of the dataset. You can also link your dataset to the web in just a few steps. OpenRefine also facilitates support for a lot of reconciling Webservices. Reconciliation is a process to match the datasets’ values to the data uploaded on to any Open Database such as Wikidata. Reconciliation semi-automates the process of matching data in OpenRefine fields with more authoritative data in external sources. Wikidata (wikidata.org) is a free open database (One of the Wikimedia Foundation’s projects) that anyone can edit if he/she has a wikidata account. So, after you are done with the reconciliation of the data, you have to create a valid wikidata schema to upload your edits to Wikidata.</p><blockquote><strong>Useful links &amp; References:</strong></blockquote><ul><li><a href="https://openrefine.org/">OpenRefine</a></li><li><a href="https://github.com/OpenRefine/OpenRefine/wiki/Screencasts">OpenRefine/OpenRefine</a></li><li><a href="https://www.wikidata.org/wiki/Wikidata:Tools/OpenRefine/Editing">Wikidata:Tools/OpenRefine/Editing</a></li></ul><blockquote>Thank You</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fae34c001d41" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-for-cause/openrefine-the-power-tool-fae34c001d41">OpenRefine — The power tool</a> was originally published in <a href="https://medium.com/code-for-cause">Code for Cause</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I got selected as an Outreachy intern?]]></title>
            <link>https://medium.com/code-for-cause/how-i-got-selected-as-an-outreachy-intern-b0c378a66bed?source=rss-88373be9de43------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0c378a66bed</guid>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Ekta Mishra]]></dc:creator>
            <pubDate>Wed, 06 May 2020 14:23:28 GMT</pubDate>
            <atom:updated>2020-05-07T11:20:09.728Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are one of those people, who don’t have a good idea of what open-source is, what Outreachy program is, and how to get started with open-source software development, then this article is especially for you.</p><blockquote><strong>What is OpenSource?</strong></blockquote><p><strong><em>“The power of Open Source is the power of the people. The people rule.” ~</em></strong>Phillipe Kahn</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*19R5Il0FGNKvPHUuOa7P8Q.png" /></figure><p>Open-source software is a software that provides you the freedom of code sharing, modifying, and redistributing but it may/may not be free of cost. Most of the open-source software is available for free hence commonly termed as FOSS (Free and Open Source Software). It provides power in people’s hands where they can customize their software in accordance with their needs, modify the original software, redistribute it, and whatnot.</p><p>Now, the question is whether you are aware of any opensource software or not? Okay, then answer me, do you use VLC, Mozilla Firefox, Chromium, Linux, Java, Python, WordPress, Notepad++?</p><p>If your answer is ‘yes’, then knowingly or not you are using an OpenSource software and that too for free. Think about this, as if someone asked you that you have to pay for a language like C++, Java, Python for using it, would it have happened that you ever tried to start learning it? If things wouldn’t have been like this, then is there any chance that the growing IT industry we have today, it have been the same? Obviously, no.</p><p>The ideology behind Open source development is to make people more powerful by providing them access to the source code and the freedom to explore it. Opensource is the modern culture for development.</p><p><strong><em>“Open source is a development methodology, free software is a social movement.” </em></strong>~ Richard Stallman</p><p>for more you can read one of my articles: <a href="https://medium.com/@Darecoder/free-as-in-beer-vs-free-as-in-speech-d3d47f87b2e0">Free as in beer Vs Free as in speech</a></p><blockquote><strong>What is Outreachy?</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*w650lSsu6m4SAM-5f_SUCQ.png" /></figure><p>Outreachy is a program that provides internship opportunities twice a year. People can apply from all over the world, work remotely with a highly paid stipend of 5500$ USD for the three-month internship program, and 500$ USD as a travel allowance for attending any tech event, conferences, or summits.</p><p>The motive behind Outreachy internships is to promote diversity in tech, support people from underprivileged groups &amp; underrepresented community in tech. Anyone who faces systemic bias or discrimination in the technology industry of their country is invited to apply. It provides a platform that helps the newcomers to start contributing to free and open-source software.</p><blockquote><strong>Process to apply</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gwNcA279T6GS3OAAET5CIw.png" /></figure><p>Outreachy internships applications are open twice in a year i.e. first in mid-year and second time at the end of the year.</p><p>So, you have the chance to apply twice a year. yaaayyyyy!!!</p><p>Before applying to Outreachy, you should first go through the <a href="https://www.outreachy.org/docs/applicant/#eligibility">eligibility criteria</a> thoroughly.</p><p>For initial applications of mid-year internships, you should start applying in late January and for end of year internships late august. In the initial application, you have to provide your basic information, your time commitment, and 4 <a href="https://www.outreachy.org/docs/applicant/#initial-application">essay questions</a>. Then, after a few weeks of the deadline for the initial application, results are declared for those whose initial applications are accepted.</p><p>From that day, the contribution period starts in which you have to make at least one contribution to the corresponding project you want to apply. And then, finally, draft your final application and get it reviewed by the mentor to make improvements and modifications in it that increases the chances of getting selected.</p><p>I suggest to be an early bird and start exploring the organization and projects before 1–2 months of the initial application start. Most of the time, the organizations are the same but if in some cases, your chosen organization isn’t selected then also the contribution you made will have a significant effect on your final application for other organizations.</p><p>Then, in May and December, the internship period starts for the selected candidates.</p><blockquote><strong>My journey</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/739/1*UzsudBl6aLNRj9WmYBuq8w.jpeg" /></figure><p>It’s not about the journey in the Outreachy selection process, what I really want to share is the path I followed because of my love for open-source software and open-source organizations. Through this article, I want to share what I learned from this journey. Outreachy was not only my wish, somehow it was my need. But I never thought that journey will become this much beautiful.</p><p>My very first interaction with an open-source community was with JBoss Organization. My mentor <a href="https://medium.com/u/de19f5319c0e">Anuj Garg</a>, helped me to connect with the community, explore its projects like KeyCloak, Debezium, Quarkus, WildFly, etc. At first, it all seemed very difficult and tedious to understand or work with. But with time, I became familiar with the projects and started developing interest in them. Later on, I got to know about the program Google Code-In. I applied for the Google Code-In mentor and got selected as a Google Code-In’19 mentor for JBoss Organization.</p><p>Google Code-In is a contest for 13–17 years old pre-university students to help them kickstart their open-source development career. This program was initiated with an idea to make it easy for the children to step into the world of open-source development. The tasks are designed to help the student get comfortable in the environment and develop a number of skills that will help them in later development process. So, the experience of GCI’19 was something that helped me to push myself more into the OpenSource world, I was highly motivated by the enthusiasm shown by the students I mentored.</p><p>Then in January, I applied for Outreachy, filled the initial application, and started exploring the communities selected at that time and the projects released. Unfortunately, till then there were no Java projects released, as I’m more comfortable in Java so, I was looking for that one more eagerly.</p><p>I was also proficient enough in Python so I chose Ceph as my organization and started exploring its project, setup the Ceph cluster storage on AWS which took more than 20 days. Yes, you read it correct, just setting up the project took this much time for me but no worries, finally I achieved it. I started tackling some good first issues but then just a few days before the contribution period starts OpenRefine was added in the list of organizations and it has released the project based on Java. So at that time, no one would have been as happy as I was. Then, I started studying about that project and organization, I was able to set up the project the same day and started looking for its good first issues. After exploring I started working on it and it took about one week to create my first pull request.</p><blockquote><strong>My first pull request</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*2pMs8A6C9AtUPnhIgpv7tA.jpeg" /></figure><p>My first pull request in OpenRefine was a part of freebase cleanup from their project. Freebase is a reconciliation webservice whose services have been closed. Many of you may not believe that my 1st pull request was totally a trivial task, I updated the translation files written for many languages. But the happiness I received after submitting that PR and doing the requested changes asked by the mentors and then finally got it merged was something very exceptional and that feeling is still fresh in myself.</p><blockquote><strong>Interaction with community</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aUktc7KeZFwXWchaoNizgA.jpeg" /></figure><p>The most special fact about any opensource organizations is that they are always willing to help, support, and guide you. In every organization, there is some kind of public channel like slack, gitter channel, or mailing list to discuss any kind of issues, doubts, and general discussion which you should definitely join to have a better interaction with the community.</p><p>I feel blessed for having such supportive and amazing mentors, who entertained even my most basic and obvious doubts. The maintainers and contributors of my organization(i.e. OpenRefine) are too active, they reply on issues, gitter channel as soon as they can. They review the pull requests regularly and help the contributor if they feel he/she is stuck. They always welcome your suggestions on any topic, any feature you want to suggest, etc.</p><p>For being selected in Outreachy, I really want to thank my mentors like Antonin Delpeuch, Owen Stephens, Tom Morris, Thad Guidry, and all other co-contributors for providing guidance and support. Without each one of you, this wouldn’t have been possible.</p><blockquote><strong>Advice for beginners</strong></blockquote><p>Never run for the titles like Outreachy intern or GSoC student. What you should target is the learning part, gain as much knowledge as you can in the process, that is the only asset you will have with yourself always. The stipend will end, the internship period will end but the knowledge you will gain from it, the connections you will build, the family you will make while contributing to that organization is something that you will have forever.</p><p>I’ll end this article by stating a few words that opensource development is all about being consistent. I don’t possess anything special, if I can do this then anyone can do it. It takes time to see a significant move in this field but it never ends to be a waste of time. Even if you didn’t get selected in these kinds of programs then also you will be the part of that community, that organization for always. Your name on the contributor’s list will always shine.</p><p><strong><em>“There are no secrets to success. It is the result of preparation, hard work, and learning from failure.” — </em>Colin Powell</strong></p><blockquote>Reference links:</blockquote><p><a href="https://www.outreachy.org/">https://www.outreachy.org/</a></p><blockquote>Thank you.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0c378a66bed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-for-cause/how-i-got-selected-as-an-outreachy-intern-b0c378a66bed">How I got selected as an Outreachy intern?</a> was originally published in <a href="https://medium.com/code-for-cause">Code for Cause</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Diving into RedHat Ceph Storage]]></title>
            <link>https://darecoder.medium.com/diving-into-redhat-ceph-storage-abf95ef1a540?source=rss-88373be9de43------2</link>
            <guid isPermaLink="false">https://medium.com/p/abf95ef1a540</guid>
            <category><![CDATA[redhat-linux]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[ceph]]></category>
            <category><![CDATA[storage]]></category>
            <category><![CDATA[cloud-storage]]></category>
            <dc:creator><![CDATA[Ekta Mishra]]></dc:creator>
            <pubDate>Sun, 19 Apr 2020 09:27:29 GMT</pubDate>
            <atom:updated>2021-06-17T04:49:04.408Z</atom:updated>
            <content:encoded><![CDATA[<h3>Diving into Red Hat Ceph Storage</h3><p><strong>A platform for petabyte-scale storage.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RlrF7SicHJzu9hnQNohtkA.png" /></figure><p>RedHat Ceph Storage is open-source software, that implements <a href="https://en.wikipedia.org/wiki/Object_storage">object storage</a> on a single distributed <a href="https://en.wikipedia.org/wiki/Computer_cluster">computer cluster</a>, and provides interfaces for object-storage, <a href="https://en.wikipedia.org/wiki/Block_storage">block-</a>storage, and <a href="https://en.wikipedia.org/wiki/Computer_file">file-level</a> storage in a single platform. Ceph provides a software-defined architecture that can be easily integrated into your existing hardware and infrastructure with lower capital costs and more flexibility. It’s a storage architecture that is highly recommended for cloud and virtualization applications like Red Hat Enterprise Linux, OpenStack Platform etc.</p><blockquote><strong>Ceph Storage Cluster</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/1*RDY6zPsqy_-_hBXqZnJF3Q.png" /><figcaption>Architecture of Ceph Storage Cluster</figcaption></figure><p>Ceph is designed in a way that it is having both features for self-healing as well as self-managing the data. Ceph Storage Cluster accommodates a large number of storage nodes that communicate with each other to replicate and redistribute data dynamically. It provides a distributed architecture without a single point of failure. This is because the data in the Ceph Storage Cluster maintains replicas of it.</p><p>For using Ceph Storage services, you need to set up a Ceph Storage Cluster. A Ceph storage cluster consists of two daemons: Ceph Object Storage Daemon that stores the data as object in the storage node and Ceph Monitor that keeps the track of clusters by maintaining a copy of the cluster map. Every Ceph Storage Cluster requires at least one:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*wxc4Vdhq5PtEcsRjg38-OQ.png" /></figure><ul><li><strong>Ceph Monitor : </strong>Monitors maintains the cluster membership and provides the health of the storage nodes. It keeps the track of the cluster but it doesn’t serve the data to the clients. A minimum of 3 monitors is required for the cluster for providing high-availability (to be dependable enough to respond to the client requests). Authenticating clients and daemons is also the job of Ceph monitors.</li><li><strong>Ceph Manager : </strong>It keeps the record of all the runtime scenarios of the cluster. It maintains a check over the system load, utilization of the storage resources, and the Cluster performance metrics. We can check the details provided by the manager from the Dashboard.</li><li><strong>Ceph OSDs : </strong>The OSDs actually provides access to the data. An OSD is installed per disk. It peers with other OSDs for replication and recovery tasks. It works in a peer to peer fashion to fetch the query results without affecting the performance, even if some storage nodes go down. It also provides data to Ceph monitors and Ceph managers by communicating and checking other OSDs.</li><li><strong>Ceph Metadata Server : </strong>It comes into the picture when we talk about the Ceph File System. While using the Ceph file system, when the client requests for some data, the request first goes to the metadata servers where it checks for all POSIX and tells in which directory the data is stored, but the response is still served by the OSDs. So, mainly it maintains the directory hierarchy and stores the metadata about the filesystem.</li></ul><blockquote><strong>CRUSH Algorithm</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/1*wl79urRrLzY_-xmucd6ZzA.png" /></figure><p>Ceph uses the <em>CRUSH</em> algorithm, that decides in which OSD the particular data should be stored. It’s a pseudo-random algorithm, that ensures statistically even distribution of data over the OSDs with the decentralized placement of replicated data. It is because of the <em>CRUSH</em> algorithm which enables the scalability and self-healing/recovering property in Ceph Storage.</p><p><strong>How it works??</strong></p><p>When we have to store some objects, it first hashes the object name and decides in which placement group it should be stored. It also provides a list of devices where the replicas should be stored. It’s not based on the traditional approaches to store data where the directories and devices are already divided based on some pre-calculations made. It provides a stable mapping which means when you do some changes in the data, add or remove some data there’s minimal data migration. The calculation made by CRUSH algorithm is very fast and most of the calculation is done on the client-side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*YlkpiJrwb46lWqXyOuheKg.png" /><figcaption>Data Storage using CRUSH</figcaption></figure><p>Whenever some, storage node gets damaged, the OSDs which works in a peer to peer fashion effectively replicate the data stored in that node and updates the cluster map. Cluster Map comprises of Monitor map, OSD map, PG map, CRUSH map, &amp; MDs map. So, when there’s some change in the OSDs arrangement or after some replication in the data, the cluster map gets updated so that the CRUSH algorithm will provide the updated results next time.</p><blockquote><strong>Contribute to Ceph</strong></blockquote><p>If you liked the philosophy and idea involved in Ceph and want to join or contribute to the community, you can have a look over these links:</p><p><strong>Github page:</strong> <a href="https://github.com/ceph">https://github.com/ceph</a></p><p><a href="https://docs.ceph.com/docs/master/start/get-involved/">Get Involved in the Ceph Community! - Ceph Documentation</a></p><h4><strong>References and other useful links:</strong></h4><p><a href="https://ceph.io/">Homepage - Ceph</a></p><p><a href="https://docs.ceph.com/docs/master/">https://docs.ceph.com/docs/master/</a></p><p><a href="https://www.youtube.com/watch?v=7I9uxoEhUdY">https://www.youtube.com/watch?v=7I9uxoEhUdY</a></p><p><a href="https://www.supportsages.com/ceph-part-3-technical-architecture-and-components/">https://www.supportsages.com/ceph-part-3-technical-architecture-and-components/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abf95ef1a540" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Free as in beer Vs Free as in speech]]></title>
            <link>https://darecoder.medium.com/free-as-in-beer-vs-free-as-in-speech-d3d47f87b2e0?source=rss-88373be9de43------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3d47f87b2e0</guid>
            <category><![CDATA[foss]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[freeware]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Ekta Mishra]]></dc:creator>
            <pubDate>Sat, 27 Jul 2019 05:26:03 GMT</pubDate>
            <atom:updated>2019-07-27T05:26:03.214Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eNQJNnFOwJxl1rv_pGV06Q.jpeg" /></figure><p>This phrase has been famous from all the time when people used to get confused between Gratis and Libre.</p><p>There’s a huge difference between both of them with a minute difference line. This is as ironical as I’ll be explaining about the quote “free as in beer Vs free as in speech”. Being in the field of software development I’ll try to correlate with that.</p><p>Gratis is a freeware which means the software is licensed free of charge for regular use, the developer gets a minimal or no monetary compensation at all. Freeware is one of the earliest and basic forms of software.</p><p>Whereas Libre is open-source or free and open-source software (commonly termed as FOSS). With enhancement and revolution in the software industry, advance license schemes developers got the freedom of code sharing, modifying and redistributing but it may/may not be free of cost.</p><p>So now, it becomes easy to explain free as in beer(Gratis) Vs free as in speech(Libre) after having the understanding of freeware and FOSS.</p><p>Here the word “free” in both of them has the behavior of polymorphism. In freeware, the word “free” means “free of cost” and in FOSS it means “liberty”.</p><p>For suppose you use a freeware(“free as in beer”) means that you can use it for free which sounds nice. But you can’t see it’s implementation, you can’t make its copies, you can’t customize/modify it in accordance with you. But at the same place, if you avail a FOSS( “free as in speech”), that might not be free but it gives you the freedom to get the source code, to modify/customize it as you want and you can even redistribute it.</p><p>One more important thing about FOSS( “free as in speech”) is that you can sell it as “free as in speech” which means it might have some charges but you can’t bind the other person to redistribute it for “free”(free of cost).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*Lla-Q6saN_f72iCHfYWXfA.jpeg" /></figure><p>If someone wants to conclude the above thing, it simply defines as you can enjoy your free beer for which you don’t have to pay but it never means freedom. On the other hand, free speech is the right or freedom that may/may not cost you but it facilitates you to enjoy it all, modify it and redistribute to others the way you prefer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3d47f87b2e0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>