Open Source Contribution Summary: Feb Edition

As may have seen my older blog posts in which I posted stuff about my participation in Open Source projects whether it is fixing a small bug, improving UI, fixing typos in a document or implementing a cool feature.

If not, check out my previous posts to get more information about my work on Open Source projects in detail.

Blog post 1

Blog post 2

Blog post 3

Pull Requests

Pull Request 1

Pull Request 2

Pull Request 3

Pull Request 4

Pull Request 5

Github Account

Link to my Github

Lessons learned…

  • Earlier when I was finding a good first issue, my main concern was about fixing an issue, but later I got to know setting up the project on a personal desktop is the real pain. So, always check if the project dependencies are compatible with your machine prior to the installation process.
  • You need to know basic Git commands like push, pull.
  • Find issue easily by filtering search results using label. My favourite label ones are good first issue and bug
  • There so many ways to fix a problem and there might be times when code maintainers don’t like your fix so don’t feel bad instead learn from it.
  • Writing comments above your code is a good practice.
  • Don’t look around too much for a solution, its okay to ask for help from your fellow developers or Open Source community.
  • At the end of the day Stack overflow will be your best friend.
  • Don’t rush, take it easy and enjoy the process.

Some cool things…

  • My GitHub contribution activity table has started looking green now.
  • I was invited to join Code For Boston community on slack and worked with awesome developers.
  • I was added on MojiScript contributors list by the owner.

Reflection

  • I am getting very comfortable with React and Android.
  • I learned to implement APIs in a web application and it will be very helpful in future projects.
  • While finding issues, I discovered several projects that uses machine learning and I am looking forward to work on it.

Overall, it was a great experience!

In upcoming weeks, I will be working and fixing more issue in Open Source projects and definitely will post a blog update about it.

Stay Tuned!

Update on Open Source Contribution: Mar01

Hey there folks!

This week I worked on two projects and learned a bunch of cool stuff.

MojiScript

The first project that I worked on this week is MojiScript.


MojiScript is an Async First, opinionated, and functional language designed to have 100% compatibility with JavaScript engines. This will allow full access to JavaScript modules (NPM) and all tooling already available to JavaScript. This means that MojiScript language features can run in any JavaScript application and vice-versa.

I worked on the issue given below:

The issue I worked on

Setting up the project was easy.

Even the fix was also pretty simple. I just searched for ‘mojiscript/types/is’ text in VS Code search box and found the file (is.mdx) which contain this line of code. And then, I just changed the line from ‘mojiscript/types/is’ to ‘mojiscript/type/is’.

Later, I also change the same code of line in ‘unless.mdx’ and ‘when.mdx’.

My pull request

In the end, I submitted the pull request with my changes and it got merged.

Project Repo Link

Issue Link

Pull Request Link

And then an amazing thing happened

Joelnet (Main code maintainer) added me on MojiScript’s contributor’s list with a link to my personal website.

Readme.md file of MojiScript

Another project that I worked on this week is the Brewery Finder.

Brewery Finder

This is a website built to find any local or nearby brewer. Currently, it only provides breweries information located in the United States.

The website is written in React.

Again, It was a great opportunity for me to work with React.

Also, in one of my school course, I have to work with a project which uses APIs to fetch data. So, my professor recommended me to check some projects on GitHub which utilize APIs to get an idea of implementing APIs in projects. So, Brewery Finder was a good project to work on.

I worked on the issue given below:

The issue I worked on

The fix was not that easy I had to search for hours to find the best solution. Then suddenly JQuery came across my mind and I fixed the issue in minutes.

The owner seems to like my fix.

I submitted the pull request with my changes and it got merged.

Project Repo Link

Issue Link

Pull Request Link

And then suddenly…

The owner reopened the issue and he fixed the issue without Jquery.

Reopened and closed

He fixed it with just one line i.e. given below:

onMouseDown={e => e.preventDefault()}

Ahhh, I didn’t know we can use ‘OnMouseDown’ method. Before fixing it with Jquery I tried the same way but instead, I used the ‘onClick’ method. However, it didn’t work for me.

Well, now I know.

In upcoming weeks, I will be working and fixing more issue in Open Source projects and definitely will post a blog update about it.

Stay Tuned!

Update on Open Source Contribution: Feb22

Hey there folks!

This week I worked on two projects and got an invitation to join an amazing community on Slack.

Community Connect

The first project that I worked on this week is Community Connect.


“Community Connect” is a health resource web application that aims to consolidate information about businesses and organization available in communities that promote healthy lifestyle choices. A health resource is defined as services or materials that improve the quality of life of others, ranging from affordable child care, substance abuse counseling, domestic violence support, and more. 

The website is written in React.

Again, It was a great opportunity for me to work with React.

I worked on the issue given below:

Setting up the project was easy. I just forked, cloned and did ‘yarn install’.

Even the fix was also pretty simple. I just searched for ‘Category’ text in VS Code search box and found the file (CategoryList.js) which contain this form. And then, I just the text from ‘Category’ to ‘Filter by Category’.

My pull request

In the end, I submitted the pull request with my changes and it got merged.

Project Repo Link

Issue Link

Pull Request Link

This is not the END

Since the issue, I fixed was simple. I asked for permission to work on another issue but the issue was already fixed. Later, I got a reply from the code maintainer to join their Slack channel (Code for Boston).

As soon as I joined the Slack channel. I got a text from Galiat (code maintainer) to assist her on contributing.md.

Slack chat
My suggestion regarding contributing.md doc

So I provided her a suggestion to add project setup steps in contributing.md to save some developer’s time.

It’s the first time I got invited by someone to join a developers community to work together. And, I excited and looking forward to fixing more issues on this project with other fellow developers.

Vegeta-Server

Another project that I worked on this week is Vegeta-Server.

A RESTful API server for Vegeta, a load testing tool written in Go.

Vegeta is a versatile HTTP load testing tool built out of a need to drill HTTP services with a constant request rate. The Vegeta library is written in Go, which makes it ideal to implement the server in Go.

I worked on the issue given below:

Setting up the project was easy.

For this issue, I moved some code examples from one MD file to a newly created MD file.

Since I haven’t changed any document in an Open-Source project before, it was a good issue for me to work on.

My pull request

In the end, I submitted the pull request with my changes and it got merged.

Project Repo Link

Issue Link

Pull Request Link

In upcoming weeks, I will be working and fixing more issue in Open Source projects and definitely will post a blog update about it.

Stay Tuned!