I found something interesting on the LibreFoodPantry website was the Code of Conduct. It was nice to see examples given of positive behavior, negative/unacceptable behavior, and the enforcement responsibilities, along with the scope and the enforcement of the Code of Conduct. It shows that there is enforcement in place to keep people of negative intentions out of the project. It is also nice to see Enforcement Guidelines in place to help correct any negative behavior, so that everyone gets the same things enforced, so there is no pick and choose. It shows that the community behind the LibreFoodPantry is good, in my opinion.

From the blog CS@Worcester – Erockwood Blog by erockwood and used with permission of the author. All other rights reserved by the author.

Getting Familiar with LibreFoodPantry

After reading the different items listed in LibreFoodPantry’s main page, the most surprising and important things to me were some of the information presented in the FOSSisms article. The FOSSisms article is about sixteen basic principles that should be held by students involved in open source projects. Many of these FOSSisms, including but not limited to numbers 5, 7, 8, and 11, stuck out to me as being peculiar but important for me as not only as a future software developer, but as a student working on an open source project. 

I especially found the “FOSSism #8: Branches are free” FOSSism novel, because my conception of branching was a lot more strict instead of experimental. It has given me a bit of a different outlook for development and experimentation.

Links:

https://opensource.com/education/14/6/16-foss-principles-for-educators

From the blog CS@Worcester – Chris's CS Blog by Chris and used with permission of the author. All other rights reserved by the author.

One line that I found interesting was “Being respectful of differing opinions, viewpoints, and experiences” under the Code of Conduct. I agree with this statement, and what I find interesting about this line is the fact that when we write something on the internet, sometimes what we write might be misconstrued or misinterpreted by others. I think this is partly because it is difficult to detect the tone something is written on the internet. So, we may end up offending someone even if we do not mean to. One such example is sarcasm. Sarcasm is hard to detect online so even if we did not mean to be disrespectful, it may come off that way. So, I think it’s something people should keep in mind when posting something on GitLab or Discord. I chose this topic because I like satire and dark humor, so I use sarcasm a lot online.

https://librefoodpantry.org/docs/code-of-conduct

From the blog CS@Worcester – Just a Guy Passing By by Eric Nguyen and used with permission of the author. All other rights reserved by the author.

Christian Shadis

I will be spending my final semester at Worcester State University contributing to the LibreFoodPantry Humanitarian Free and Open-Source Software (HFOSS)¹ project. In reviewing the mission statement, values, and other biographical sections of their website, I was directed to a list of Heidi Ellis’ sixteen ‘FOSSisms’², advice primarily for developers new to open-source projects. There was a recurrent theme among some FOSSisms – a developer should contribute as much as they can, regardless of the size of the fix they provide, or how perfect the code is. Version control allows for easily fixing mistakes, and creating new branches allows for editing code without affecting the main branch. I have been a perfectionist throughout my college career, so I found that perspective both surprising and helpful. I plan to apply these (and the rest of the) FOSSisms in these coming months.

¹https://librefoodpantry.org/
²https://opensource.com/education/14/6/16-foss-principles-for-educators

From the blog CS@Worcester – Christian Shadis' Blog by ctshadis and used with permission of the author. All other rights reserved by the author.

One thing I found useful was reading the FOSSisms that came from the Values on the LibreFoodPantry website. FOSSism are pieces of wisdom for individuals who are about to work in an open source community. I will focus on the second FOSSism that stood out to me. This FOSSism instructed individuals to “Be productively lost”. This resonated with me because I feel like my technical skills still have a ways to go. It helped ease some of my anxiety around this topic because a period of feeling disoriented is described as being “perfectly natural”. Furthermore, I was advised to use this moment productively to learn more about the open source project/community I am about to be a part of. This was only one of the first FOSSisms that caught my eye but I would like to include the link here because there are many more I could write about.

FOSSisms Link: https://opensource.com/education/14/6/16-foss-principles-for-educators

From the blog Sensinci's Blog by Sensinci's Blog and used with permission of the author. All other rights reserved by the author.

After reading through the LibreFoodPantry website, I was really impressed by the code of conduct. I think it’s well written and very considerate of all parties involved. I liked how the pledge was explicit on what’s expected from members of the community. The standards were clearly stated, and the enforcement guidelines carefully explained. I also appreciated the fact that there are warnings and temporary bans for different offenses. I think it is very thoughtful to give members another chance to be better before taking any final decision.

I chose to write about it because I believe that making sure that all members of the community feel safe, respected and appreciated helps the company move forward. There is no way to produce an excellent job if the brains behind the work are somehow being marginalized or oppressed.

From the blog CS@Worcester – Delice's blog by Delice Ndaie and used with permission of the author. All other rights reserved by the author.

In the next few months, I’m going to be doing my capstone course for my computer science degree. It’s going to (possibly) involve working on the LibreFoodPantry project, so I decided to look over the website.

The first thing that stood out to me was the Coordinating Committee. Previously I had been picturing this project as essentially just something a handful of people were working on on the side. In reality it has slightly more people directing it than I imagined and also a much more rigorous organization and schedule than I had assumed.

More specifically, I thought that there being three versions of the software meant that there were three people managing a shop of developers, as the page says, but there’s actually six.

From the blog CS@Worcester – Tom's Blog by Thomas Clifford and used with permission of the author. All other rights reserved by the author.

In the Values section of the LibreFoodPantry documentation, there’s a section linked to 16 “FOSSisms” that I found particularly interesting. They are essentially maxims for students that are working on open source projects, like LibreFoodPantry. They explain how students should become involved in a project’s community, how they should contribute and start contributing, and in the end how they should leave documentation that is good enough for others to be able to carry the torch once the semester is over.

This section particularly spoke to me because I have never worked on an open-source project, and it is a little daunting to start on, so knowing that the values of the project are geared towards people in my position makes it all a little less scary. It shows that it is an organization geared towards learning and reassures me that it is alright to make mistakes here.

From the blog CS@Worcester – Kurt Maiser's Coding Blog by kmaiser and used with permission of the author. All other rights reserved by the author.

As some may know or not know, Libre Food Pantry is the work of several colleges around New England with the goal of creating software for food pantries everywhere to use in order to manage operations. Their mission is simple, create free software to be used at any and all food pantries in order to better serve their guests.

However, the most interesting part of this collaboration is that this is instructor led, and student built. Students have worked to create prototype software ranging from database solutions at Worcester State, to mobile app based solutions at Nassau Community College. These institutions assist and add to this software along with other contributors with the goal of helping those in need while furthering their own education.

Those who are interested as I am should take to their website to learn more about their story and how far they have come.

https://librefoodpantry.org/

From the blog CS@Worcester – George Chyoghly CS-343 by gchyoghly and used with permission of the author. All other rights reserved by the author.

The mission of the Libre Food Pantry is to offer free and open-source software to manage the logistics of operating a food pantry. The project is developed using agile values and adhered to FOSSisms which are a collection of quotes that relate to open-source software development. The code of conduct of the Libre Food Pantry is to not tolerate discrimination of any form and to operate with a strict equity policy. Those who contribute must follow the GPLv3 and attributions must follow the CC-BY-SA 4.0 where each sign-off follow the Developer Certificate of Origin 1.1 schema. The Libre Food Pantry acknowledgments detail the sponsors, software, clients, people, and institutions that make the project possible. A major sponsor is AWS which provides free hosting for the project. I chose to write about these details to familiarize myself with the details of the development process of this project.

From the blog CS@Worcester – Jared's Development Blog by Jared Moore and used with permission of the author. All other rights reserved by the author.