This is about how submitting my first pull request to OctoPrint.
Yes, it is a great feeling to able to contribute to an open source project, and I am cherishing these feelings as I write this blog post. I don’t want to be poetic here, but I’m feeling a little accomplished after all my efforts, and struggle I went through to
Continuing from the responses we received from our last work on issue #1149, Kye and I started working on the buttons and went through several iterations to come with the best UI possible without breaking already existing functionality.
Finally, I had the chance to test the software on a 3D printer. Thanks to Ashley for helping us out with the connectivity. I was trying to recreate the issue #1149 as I had written in my last blog post. In short the issue was about adding a layer up and down functionality in the G-Code viewer of OctoPrint. The feature request has two parts: 1) Add buttons for layer up/down 2) Add on-press-key event with the up and down keys. As soon as I commented on the issue ticket, I got some quick responses. One member had already worked on the on-press feature, so I wanted to test it.
Last time I was working on issue #1142 with Kye, and we figured that this issue was resolved in a new plugin, which is in the development branch of OctoPrint, and yet to be released. The issue was marked as a milestone for OctoPrint 1.3 release.
I am switching my project from OpenMRS to OctoPrint.
You might have noticed that I have not blogged in the last few weeks. It is not because I have not been working on OpenMRS. I have been working really hard to get a new module into the OpenMRS standalone but have failed seriously. I’ve not achieved any substantial success that was worth posting.
What makes an effective open source community? _This question might seem a little too broad to be answered in one sentence, as there are so many elements one might think of what makes an effective open source community. In his book “The Art of Community”, Jono Bacon explains that an open source community can be visualized as a social economy, where 1) a sense of belonging keeps people in the open source community, 2) This economy’s currency is not money but social capital, which is measured by strong sense of belonging, 3) participants need to believe in the community, 4) at the heart of the economy is a process that describes how work is done and shared, 5) the process and social capital that generates the belonging needs to be communicated.
It’s time. I have to decide the open source project I would like to contribute to. I have been thinking between OctoPrint and OpenMRS from my last blog post. After, reviewing both the project using the criteria of “newcomer friendliness” from Making Your Open Source Project Newcomer-friendly, I have chosen OpenMRS.
On Wednesday, in my Software Engineering class, I learned that my classmates and I are going to create a contract for assessing our achievements in the course. I, in large, agree with my peers on their thoughts about a contact that will make this a successful course. In this post, I am going to reflect on my thoughts of different elements of the contract we discussed in the class. In the end, I will make some suggestions to what should be included in the contact.
My story with Free and Open Source Software (FOSS) go a long way and this is the story that got me excited to take this course about FOSS Engineering. When I was in Bangladesh I had used FOSS several times like, the OpenPos project (a Point of Sale) to develop custom tailored POS software that helped 2 businesses grow. I have also used OpenCart (an open source CMS) to build my first business BookShopBD.com . I think FOSS can play a big role in terms of improving the economy.