While reading through the LibreFoodPantry main page I found the section on FOSSisms in values quite interesting. As students we don’t know everything, not even close to be honest. Hence why we’re students. The open-source project we’re working not only accept that but encourage it. Part of our job while working on this project is to be “productively lost.” This creates an amazing learning environment for everyone part of the community. Of course, we have our teachers to help guide us but more than that, we have each other too. Because we’re all “lost” together, we can help one another to work through our setbacks and points of friction. This set of values allows for a community of students to grow together and learn to help one another.

While reading through the Thea’s Pantry Gitlab Group I found the workflow section to be useful. As someone who will be working in this GitLab group for the duration of this semester alongside the other four members of my group I think it’s very useful to know what is expected of our workflow. Although it’s a short section focused on the technical aspect of how we will be committing changes and testing our branches before committing them it’s just very useful information to know as well as know where to look and read over again should there be any questions about commits being made. Overall, both of these reads were interesting and useful in their own right.

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

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

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

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

What unexpected thing did I learn about Thea’s Pantry?

That the above-linked wiki services developers, customers, and users all at once instead of there being separate wikis for each customer/user segment.

I was surprised because this observation points to an endemic quality about Thea’s Pantry that I have not witnessed elsewhere: the small scale and scope of the project (and its open-ended FOSS nature) as compared to enterprise solutions means that there are very few levels of separation between the different population segments. I expect to be surprised further as the term progresses, especially since this is my first time working in FOSS/HFOSS.

What unexpected thing did I learn about LibreFoodPantry?

That there was a LibreFoodPantry Discord! Similarly to my hesitation around the lack of dedicated developer and user wikis, it was a bit of a shock to see that LFP had been cultivating an online presence outside of what one would expect from hearing that a project is open source (to be sure, a public GitHub repo or any number of Atlassian product deployments would come to mind). What was even more surprising to me was that developers interested in the project have openly solicitited their services on said Discord and used it to learn more about the project directly, which speaks to a level of engagement and outreach that I have personally never seen before.

That’s all.

Kevin N.

From the blog CS@Worcester – Kevin D. Nguyen by Kevin Nguyen and used with permission of the author. All other rights reserved by the author.

LibreFoodPantry is a open-source software project for local food pantries with Thea’s pantry being one of them located at Worcester State.

Reading the official LibreFoodPantry website we can find some very interesting and informative things. When doing research on the website I was able to figure out how to contribute to the project which I thought was important incase someone was interested in contributing. While that is important I was really impressed by the mission & values, specifically the code of conduct. This code was very well put together and exemplifies what the mission is all about.

Thea’s pantry, as stated, is one of the Pantry locations which uses this software for its system. I was really surprised as to how well documented this was. Looking at each part of the README file, as well as the following documentation directories, you can get a sense of what this software is actually doing & of course how it works. I felt this was an extremely important part to touch on specifically because there are softwares I have seen in the past with terrible documentation that I simply was unable to work on so having it makes it much more enjoyable.

Overall I am excited to be apart of this project and hoping for an amazing development experience.

From the blog CS@Worcester – Petraq Mele blog posts by Petraq Mele and used with permission of the author. All other rights reserved by the author.

Let’s start by diving into what these two Pantries are:

• LibreFoodPantry is a community of people creating free and open-source software for food pantries.

• Thea’s Pantry is one such food pantry, serving the Worcester State University community.

These two entities are currently working in tandem to improve Thea’s Pantry’s operations, to better provide for those in need of food and critical toiletries in the area.

Let’s learn a bit from LibreFoodPantry:

FOSSisms, or Free-and-Open-Source-Software-isms, are a set of concepts that developers can integrate into their general workflows. Two of my favorites are as follows:

• FOSSism #11: It’s not what you know; it’s what you want to learn
• FOSSism #12: Release early, release often

FOSSism 11 embodies the idea that you should not expect to know how to implement everything you want to, yet. It’s almost expected that you will have a ramp-up time to be capable of producing new useful software components, and in the meantime, you need to get in there and mess around to learn that capability.

FOSSism 12 builds perfectly off of the previous point. There is fear for many, that they must wait until their project or component is perfect before releasing any version of it whatsoever. This is one of the most important habits to break as soon as possible, we should seek out every source possible for improving our work, including others.

And a touch from Thea’s Pantry:

Thea’s Pantry has a very useful set of documentation, including docs describing the tech stack and the architecture of the service. I found looking at the integration and deployment diagrams to be exceptional for helping me get a grasp on what Thea’s Pantry actually is under the hood.

Here’s hoping for a successful semester of messing up lots, and creating awesome software the whole while!

From the blog CS@Worcester – KeepOnComputing by CoffeeLegend and used with permission of the author. All other rights reserved by the author.

Let’s get right into it and start with LibreFoodPantry which is a free and open source software that helps local food pantries distribute food and serve their clients and guests. Reading more about them on their website I learnt a lot. They showed a really strong coordinated and structured team, so being able to work and contribute into a real life project that’s goal and mission is to help a community feels amazing. I had seen how we have used their software to help us with our school’s pantry and after talking to organizers of the Pantry itself on Thursday it felt really special. Now I have a more complete sense of what is happening as I know how they want the system to do and also learning about the backend of it since last semester. 

Next, is our very dear Thea’s Pantry, which provides not only food but other essentials to students, staff and faculty. I think this is a really nice addition to our campus as it offers a lot of help to people who are in need of essential stuff and makes the campus more welcoming as everyone is ready and more than happy to help each other in times of need. One thing that I did find surprising when we visited the pantry is the only thing that they are tracking for what students are taking is basically the weight and there are some limitations on how much stuff you can take per week on selective products. At first I thought students had to declare everything that they got but I guess they only focus on how much inventory there is left. 

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

Familiarizing LibreFoodPantry & Thea’s Pantry

After reviewing the LibreFoodPantry website and exploring Thea’s Pantry GitLab repositories, I gained a much clearer understanding of both the mission behind the project and the technical structure supporting it. This experience helped connect the purpose of the organization with the real-world software practices used to support it.

One aspect of LibreFoodPantry that stood out to me was its mission and values. The project is mainly focused on using free and open-source software not only to support food pantries, but also to educate students through hands-on development. I chose to focus on this because it highlights a balance that isn’t common in many academic projects, serving the community while still prioritizing student learning. Seeing values like collaboration, transparency, and long-term sustainability reflected in the project made it feel meaningful beyond just coursework.

From Thea’s Pantry, the most interesting component for me was the architecture documentation. Reading through it helped understand how the system is broken into multiple subsystems, each with a clear responsibility. I chose to write about this because it showed how large applications are intentionally designed to remain maintainable and scalable. Instead of building one massive system, the project separates concerns in a way that supports teamwork and long-term development, which aligns closely with real industry practices.

Overall, this assignment helped me see how everything we’ve learned so far comes together in a real, impactful project. I’m excited to continue developing both my technical and collaboration skills throughout this Capstone experience!!

From the blog CS@Worcester – function & form by Nathan Bui and used with permission of the author. All other rights reserved by the author.

I was also impressed by how detailed the GitLab files were. Looking through the files helped me start to piece together concepts and skills I have been learning in my CS-343 (Software Construction, Design, and Architecture) course. These files provided great imagery for what working on this project in my capstone course will actually look like. Specifically, looking at the UserStories, Architecture, and Workflow files made everything feel much more tangible.

In the Architecture file, it was also interesting to see diagrams we studied in CS-343 applied to a much larger and functioning system like Thea’s Pantry. This was the first time I had looked at a WorkFlows document; however, seeing the architectural patterns transition from practice exercises to a live system is, for lack of better words, so cool! I am looking forward to seeing how our contributions will help improve this resource and better serve the community!

From the blog CS@Worcester – Vision Create Innovate by Elizabeth Baker and used with permission of the author. All other rights reserved by the author.