Week 13 HFOSS & Open Source Business Models

HFOSS Continued

In Monday’s lecture, we continued our discussion on Humanitarian Free Open Source Software (HFOSS) and I had the opportunity to learn about a lot of cool humanitarian and social good projects. I was very interested in Alex, a tool that catches insensitive, inconsiderate phrasing in markdown or plain text and was did a project evaluation of it with other classmates who were also interested in Alex. I copied and pasted the evaluation template into the online demo and this was what I got:

Alex

Although not sure why “simply” may be insensitive, I was able to see how Alex can be a useful tool in writing. It seemed that the project was pretty active back in 2018, but not very active anymore. I also found that many closed issues have the label “hacktoberfest”, which is the event mentioned by Vicky Steeves earlier in the semester. These issues all look quite newbie-friendly and can be resolved in a relatively short time. Looking forward to this year’s Hacktoberfest!

Alex_issues

I also liked Tidepool, a platform that aims to make diabetes data more accessible, actionable, and meaningful for both patients and clinicians. People with diabetes or those who are caring for someone with diabetes can use the platform to manage their diabetes data, while doctors and healthcare providers can use the data to help their patients. I understand that for chronic diseases data can be essential, and I’m interested in contributing to Tidepool or similar projects for other chronic conditions.

Open Source Business Models

In Wednesday’s lecture we had a discussion on the business models of free and open source software. Joanna started with the question: what is the first company that successfully made money around open source software? If asked to name a company that makes money with open source, my answer would be Red Hat, but I didn’t realize that it is also the first company that had the success. For some reason Red Hat sounds like a relatively new company to me, which is not true as it was founded in 1993 (probably because I did not pay much attention to it prior to taking this class).

Of all the business models, donations is the one I’m most familiar with as Wikipedia asks for my donation every year. I’ve done some research on whether Wikipedia really needs my money to keep the site online, the conclusion was no but since Wikipedia has been a very useful tool I still decided to donate. Donations is also quite common business model for many open source projects I’ve seen. The payment methods can often be found in the readme file sitting in the repository or the website of the project.

I found the open core model kinda confusing. In my opinion, if only the core of the project is open source and the remaining parts are proprietary, then I won’t consider the project as truly open source. I do understand why some projects would choose this model — after all, being able to maintain the service is important. I personally prefer the dual licensing / selling exceptions model to open core, for the reason that contributors can have more freedom.

I also learned that Sakai, the learning management system NYU Classes is built with, is open source. It was surprising to me as I thought it would be proprietary. With some further googling, I found that many other popular learning management systems such as Moodle and Canvas are also open source. It is really cool that schools can build their own systems with these open source softwares.

Lemmy

For the past week I’ve been reading the Rust documentation and the source code of Lemmy trying to figure out how should I contribute to the code. But in this week’s lecture Joanna mentioned that in the past some students made the mistake of trying to understand the whole code base (which is not very possible). So I decided to start writing some actual code instead of staring at someone else’s code aimlessly all day long. I thought it wouldn’t be too hard to get the issue I’ve been looking at resolved; turned out I was naive. Unfortunately I ran into a huge blocker at step 1: set up the docker development environment. I kept running into the following error:

docker

I spent like a whole day trying to fix this (by googling) but so far none of the solutions I found online worked. I’ve been stuck in the infinite loop of : 1. copy & paste the error message and google; 2. try the solution found; 3. try to build again and wait forever; 4. build fails at the exact same place, which has been really frustrating for me. I’m planning to open an issue soon and hope someone in the community can offer some much needed help.

P.S. what I found when trying to find a solution which made my day:

rust

diesel

Written before or on April 26, 2020