Update on Open Source Contribution: April 14

Hey there folks!

This week I worked on lots of projects and also continued working on Microsoft calculator. Check out my previous blog post to know more about it.

Project link

Issue link

Pull Request link

While testing we encountered internal server problem with the Azure pipelines. It was fixed by one of the code maintainers when he closed and re-opened the PR. And then, suddenly tests started working. I have never seen this kind of fix ever.

I have already finished my tasks. I am just waiting for them to get it merge with the main codebase.

Firefox Fenix


Firefox Fenix is a new browser for Android

Fenix is a Mozilla project. Soon, the default Mozilla Firefox browser will be archived and Fenix will take over it. I think it’s because fenix had lots of cool features. The main one is that Fenix can save state of your browsing. In programming world it’s like saving the state of collection of numerous tabs.

Its written in Kotlin.

Project link

In this project, I worked on two bugs.

Fenix(Issue-1)

The scroll was working fine in portrait mode but broken in landscape mode. To fix the problem I added Scroll view around Linear layout which simply fixed the problem and scroll was working fine in landscape mode.

Issue link

Pull Request link

Fenix(Issue-1)

Again the problem was related to landscape mode of the app. This time the search input text used to lost whenever user tried to switch his device from portrait mode to landscape mode or vice versa. So, to fix it I found a very common and effective solution to this problem. And, it solved the bug but unfortunately code maintainers didn’t liked my fix.

Issue link

Pull request link

Overall, I really liked working with fenix. I am still looking forward to fix more of its issues.

Mifos mobile


Mifos Mobile Banking App for clients

Its an Android Application built on top of the MifosX Self-Service platform for end-user customers to view/transact on the accounts and loans they hold. Data visible to customers will be a sub-set of what staff can see.

This is a native Android Application written in Java with POJO classes in Kotlin.

Project link

In this project, I worked on two bugs.

Mifos(Issue-1)

It was my first time working on this new project so I tried to chose a easy issue to fix and luckily I found a issue related to UI. All I had to do was to align the text(Account Number) in center.

Before

After

Issue link

Pull request link

Mifos(Issue-2)

Now time was to do something that I have never done before. I found a issues in which they needed a confirmation dialog box whenever a user tries to change the password. So I used material dialog class to do it.

New changes

I always wondered how to implement those fancy dialog boxes and today I actually implemented it myself

Issue link

Pull request link

This week I found developers don’t give much importance to the landscape layout of android apps and due to which number of issues are filed related to the app orientation.

Overall, I feel proud to work on so many projects in just two weeks. Most importantly I got a good opportunity to work on Microsoft and Mozilla project.

I will be still looking out for some other exciting Open Source projects to work on so let me know in comments if you have any recommendations.

Stay Tuned!

Update on Open Source Contribution: April 05

Hey there folks!

Last month I worked on an issue in AntennaPod. Check out my previous blog post to know more about it.

Project Link

Issue link

Pull Request link

Finally, after multiple commits my PR has been merged.

This Month

This week I worked on Microsoft Calculator.

If you are a Windows person you might have came across Microsoft Calculator.

This is how it used to look before
Now it’s the most powerful calculator application

The application is written in C++

The issue that I chose to work on:

Issue link

I found there were several controls (AppBar, OperatorTextBox and OperandTextBox) that were no longer used and were laying in the codebase for no reason. So my task was to remove those controls and its instances from the source code.

I have already submitted my PR, waiting for their review.

Pull request link

Although it was a code cleaning task, I was introduced to an ancient C++ code. I have to say its well written and maintained. Even the setting up the project was a piece of cake.

Overall, It was a great opportunity for me to work on a Microsoft project.

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!

Open Source Contribution Summary: March Edition

Here there folks!

This month I am working on an issue in AntennaPod. Check out my previous blog post to know more about it.

Project Link

About Issue

Issue link

My task was to add empty view to the Episodes, Download, Playback History and Queue history pages. At first, I had some troubles figuring out how fragments work. Later, I found my way out and added the empty views to the required pages. Throughout the process, the code maintainers of the project helped me and gave me amazing tips in android development.

Result

I have already submitted my pull request and currently maintainers are reviewing my code. Hopefully, my code will get merge by next week.

Pull Request link

I am also looking forward to fix more issues in this project.

Stay Tuned!

Contribution to AntennaPod: March22

A podcast manager for Android

Hey folks,

This week I am working on an issue in AntennaPod. It’s a podcast manager which allows you to subscribe, download top podcasts available in the market.

The project is written in Java and XML.

For the issue, I am adding empty views to various pages. At first I thought the task will be easy but later I found its not that simple. Especially understanding fragments code was a challenge. For almost two days I was lost I had no idea how fragments work. Not only that fragments can be coded in many different ways which makes it more complex to understand as every developer has its own style of writing code. So, I had to do some digging about it.

Issue link

Later I was able to create empty views for some pages. But I wasn’t sure if
my code is according to their project coding standards. So I sent a pull request of my current work for review. Luckily, it passed all the test (hurray!)

Pull request

Then, one of contributor recommended to create only one empty view(xml) instead of recreating empty views for each page. But, he didn’t said anything about my java code (main code) so I believe it’s a good sign.

Now, I am finishing off remaining work and I believe I will submit my final PR to resolve the issue by next week.

Stay Tuned!

Future Open Source Contribution Plan: March Edition

Hey there folks!

This week I will be working on an WordPress android application.

Personally, I have been using wordpress for a quite some time and I love it. It is just so clean and simple to use. Recently, I found that there is an android app for the WordPress which is an Open Source project(repo). These days I have been investing lot of time learning cool things in android development. Soon, I will be uploading my ongoing android projects on Github as Open Source.

For now, I am going to fix some existing bugs or maybe add some cool feature in WordPress app. In process, I will also try to find some undiscovered bugs.

I have already setup my workspace. Throughout the project, I really loved the variable/function naming convention. But, I have to become more familiar with the codebase and get down to work on bugs.

The issues that I am planning to work are as follows:

Issue 1

Issue 2

Issue 3

I will be still looking out for some other exciting Open Source projects to work on so let me know in comments if you have any recommendations.

Stay Tuned!

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!

My Next Steps in Contributing to the Open-Source Society


Photo by Markus Spiske on Unsplash

After successfully getting started with contributing to the Open-Source society. I am planning to work on four new Open-Source projects in the future.

Check out my previous blog post to know more about my first contribution to the Open-Source society.

MICROSOFT – VS CODE

VS Code is a type of tool that combines the simplicity of a code editor with what developers need for their core edit-build-debug cycle. It provides comprehensive editing and debugging support, an extensibility model, and lightweight integration with existing tools.

  VS Code is built using Javascript, Typescript, and CSS on top of Electron framework.

I have been using the VS Code for two years and I love this code editor. I usually develop web apps using the VS Code. Currently, the VS Code has around 4500 issues on GitHub. I want to help the VS Code by fixing some of its issues. Also, I will become more familiar with Javascript and TypeScript.

Website

GitHub

BRAVE – BRAVE BROWSER

Brave is a free and open-source web browser available on Windows, MacOS, Linux, Android, and IOS. Brave is designed with a built-in adblocker to provide an ad-free and seamless browsing experience.

The Brave windows browser is built using JavaScript and Brave android app uses Java.

I have been using Brave for six months but never thought of contributing to it. Now, I am planning to resolve potential issues to both the Brave Windows browser and the Brave Android App. I will be able to improve my front end skills with JavaScript. I will also gain a deeper understanding of different functionalities of the web browser.

Website

Google Play Store

GitHub – Web

GitHub – Android

DUCK DUCK GO – ANDROID

Duck Duck Go is an Internet search engine available on Web, Android, and IOS platforms. The astonishing thing about this search engine is to protect the user’s privacy. It avoids the filter bubble of personalized search results and shows all users the same search results for a given search term.

The Duck Duck Go Android app is built using Kotlin.

It has been a month since I started developing on Android apps using Java but never worked with Kotlin. It will be a great opportunity for me to learn about Kotlin. I am planning to resolve the backend related issues of the project. I will also learn about how a search engine works.

Website

Google Play Store

GitHub

TEAMMATES

TEAMMATES is a free online tool for managing peer evaluations and other feedback paths of your students. It is provided as a cloud-based service for educators/students and is currently used by hundreds of universities across the world.

The Teammates website uses both Java and TypeScript.

I am really good at Java programming and want to contribute my skills and time to resolve issues on the project. Moreover, I will be able to develop my programming skills with TypeScript. I will be able to further develop my knowledge/understanding of the Java production-ready applications.

Website

Github

Let me know if you want to recommend any Open-Source projects related to JavaScript, Android and Machine Learning.

My First Open Source Contribution Experience


Photo by Finn Hackshaw on Unsplash

This week I got an opportunity to work on Filer web filesystem project. Check out this link to know more about the project.

Throughout the whole time, I got hands-on experience on both Github and Git.

At first, I was confused between Git and Github.

Later, I found out…

Git is Version Control System.

GitHub is a web-based service for version control using Git.

In easy words…

Git helps us to keep track of our files and any changes made to those files on our local machine.

Github is a website that contains source code in different repositories managed through Git.

You can install Git through this link. Also, you need a GitHub account in order to make a contribution to any Open Source Project on GitHub.

How can I contribute to Open Source Society?

Well, there are so many ways……

Now, I am going to show you how I contributed to the Filer project on the GitHub

1) Firstly, I navigated to the Filer project on the GitHub.

2) Then, I forked the project by clicking on the button as shown in the image below

By forking, GitHub created a repository under my GitHub account.

3) After forking, I cloned the filer project on my local machine.

To clone the project click on the green button “Clone or download” and copy the link. You can either use a “Clone with SSH” or “Clone with HTTPS”.

Tip - Use "clone with ssh" to save your time in the future. With  ssh, you don't have to input your GitHub credentials and other details later when creating a pull request. But beforehand, you need to set-up an ssh key. Refer to this link to set up an ssh key. 

4) I opened my code editor (Visual Studio Code) and created a repository on my local machine by using git clone command shown below

git clone git@github.com:jatinkumarg/filer.git

5) After the cloning, I used “npm test” to make sure everything installed properly.

6) Now, it was time to either find a good bug or issue a bug.

You can find lots of bugs under the “Issues” tab.

I decided to file an issue.

So, I browsed around the code for some time and then I found files in which some of the variables use “var” as a data type which quite outdated. According to ES6 declaration style, “let” and “const” should be used to declare any variable in JS. Refer to this link to know more about ES6 declaration style.

7) Since it was my first time reporting a bug on GitHub so I just chose one file i.e. fs.readdir.spec.js filing for the issue.


Link of my issue page.

Soon I was assigned to fix the issue.

Now, It was time to code

8) I opened the earlier cloned project on Visual Studio Code and opened the fs.readdir.spec and changed the “var” declared variables with either “const” and “let” as shown below

9) After the required changes, I again executed “npm test” to check the code.

10) I used “git add” to stage the changes

git add fs.readdir.spec.js

Then,

git commit -m "Fixed #667: Replaced var with either const or let and added strict mode in fs.readdir.spec.js"

And later,

git push origin issue 667

It generated a link through which I was able to create a pull request for the filer project.

Link of my pull request.

Almost done,

After pull request, GitHub generated a CodeCov Report using Travis CI.

Luckily, I passed all the checks with 86.71% coverage.

You can review my changes through the “Files changes” tab. (link)

Red lines represent lines before changes and green lines represent after changes.

In the end, I reviewed other developer’s pull request.

Review 1

Review 2

Review 3

Conclusion

While reviewing (Review 1) pull request I found one of the contributors recommended to use ‘use strict’ at the top of the file. Then I found ‘use strict’ prevent certain actions from being taken and catches any thrown exceptions. (link) So, I added the ‘use strict’ at the top of the “fs.readdir.spec.js”. And, recommended other developers to add ‘use strict’ at the top of their file(Review 3).

Also through (Review 2), I found ‘const’ is more preferred over ‘let’ when variables aren’t changing their values. So, I changed variables declared with ‘let’ to use ‘const’ in “fs.readdir.spec.js”.

There were a few times when I was lost during the process of creating a pull request on GitHub but anyhow I figured it out through quick Google searches.

Tip - Listen to music while doing reasearch on Google (Really helps!)

In the future, I will ask my fellow developers for assistance to save some time.

Overall, I really enjoyed the whole process and I am looking forward to contributing more to the Open Source Society in the future.