Category Archives: CS@Worcester

Discovering LFP and Thea’s Pantry

The LibreFoodPantry (LFP) website and Thea’s Pantry GitLab Group are full of knowledge about the open-source project itself and related information to support the users and developers. After reading through these resources, I felt I gained a more thorough understanding of the purpose of this software and it’s potential trajectory. Specifically relating to the LFP website – I found the Values section extremely useful, as it provides clear expectations for all community members with links to further understand the Code of Conduct and to learn more about Agile values and FOSSisms. Regarding the information about Thea’s Pantry in GitLab, there are many useful subsections within this group, but I was particularly impressed by the Architecture section as it presents the microservices architecture clearly through diagrams with clear systems, features, and components. An additional useful link relating to Thea’s Pantry GitLab Group is User Stories. After reading through the different situations expressing the intended use of the software, I had a better understanding of the role that this project plays throughout every step of this process on both, the staff side and the guest side. I was surprised reading the User Story titled “A Pantry Administrator Requests a Monthly Report for the Worcester County Food Bank” as I was unaware of the link between the two systems. Overall, these webpages provide a simple and clear interface to learn about the project’s values and community expectations, as well as, technical details.

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

Exploring LibreFoodPantry and Thea’s Food Pantry

After reading about LibreFoodPantry, I found the 16 FOSSisms on the Values page quite useful. A few of them stood out to me, such as “Ask Forgiveness, Not Permission”, which helps encourage students to make changes even if they might be incorrect. These changes, along with their feedback, can provide valuable lessons and experience to the students, and any mistakes can be easily undone. Another FOSS value that stood out was “Begin with the Finishing Touches”, which essentially means that students should start their contributions off with small bug fixes and the like to give them a sense of productive contribution. If they start off too grand, then they might become discouraged and unlikely to be productive. I chose to write about these FOSSisms because they’re helpful and encouraging “rules” for a open-source newcomer to follow, as it can help introduce someone to the space and give them an idea on how to navigate the ethics of open-source.

One thing from Thea’s Pantry I found very useful was the User Stories in the Documentation. These are stories of how the user would interact with the software, which gives a guide to how the software might be designed. I chose to write about this because having step-by-step instructions on how a user or administrator would interact with the software makes it less complicated for developers to understand how the software should work. Figuring out the user interface and design flow first is much easier than trying to code and create the design flow as you go.

From the blog CS@Worcester – Josh's Coding Journey by joshuafife and used with permission of the author. All other rights reserved by the author.

Learning With LibreFoodPantry

LibreFoodPantry provides a very useful and helpful tool for students not only to practice with software development (and understanding Open-Source work), but also to provide a helpful service to local communities. The project provides a food pantry to local communities that use it to teach their students about Free and Open-Source Code. The most useful portion of their site is their values section. This section highlights their values and how they teach their students. They focus on Agile development, Free and Open-Source Code, as well as their Code of Conduct.

I thought this section was most interesting because I found the values enriching to refresh my memory on. I also thought it was very fitting and useful for the site’s mission and methods. It accurately conveyed exactly what they try to do and how they do it in a small section.

Thea’s Pantry is Worcester State’s branch of LibreFoodPantry. I learned with it throughout my time at the University. I found the GuestInfoSystem most interesting, as it was what I worked with in most of my classes, and I got a good grip of it. I found the experiments section interesting, as it showed me what was being worked on and tested currently for the system.

From the blog CS@Worcester – WSU CS Blog: Ben Gelineau by Ben Gelineau and used with permission of the author. All other rights reserved by the author.

Set-up Task #5

One useful aspect I found on the LibreFoodPantry website was on the Organization page, which detailed the layout and relationships between development teams and the Coordinating Committee. The diagram provided information regarding teams receiving guidance from their shop manager, in addition to the committee. Before working on a FOSS project, it’s crucial to know who will handle project direction and issues, as well as how these decisions are handled at the top. Additionally, LFP links to the Agile Development Manifesto, which highlights the twelve Agile Development Principles. Ensuring the every developer that works on the open source project reads the manifesto, will guarantee team collaboration and smooth development progression. Having a Agile as the backbone will also ensure that teams receive a balanced input from both the customer and the shop manager

The User-Stories documentation page will be crucial to development teams because it will provide a rough sketch for how the food pantry is designed to operate. Having this information readily available to the development team will make decision-making and discussion easier because each team member can ensure that everyone is on the same page in regards to an “end product”. The documentation also provides how the program will operate differently, based on whether or not the student/guest has accessed the food pantry before.

From the blog CS@Worcester – Computer Science Through a Senior by Winston Luu and used with permission of the author. All other rights reserved by the author.

Task 5

I found the website of Libre Food Pantry to be interesting I like the setup of the site and like the aesthetic. It looks very professional and the colors coordinate with the webpage. The section about GitLab stood out to me. It is great to be open to the public where we work on our project. It gives anyone easy access to our work without being able to edit it but look at it and give us feedback. I chose to write about this because sometimes it is hard to find the source of people’s projects but it being easy to see is very useful. In Thea’s food pantry, I found the community section the most important. This should be the first thing that should be clear to anyone working on this project. It tackles a lot of problems that may be up to interpretation but gives clear answers so nobody is confused. For me, the one that stood out the most was the definition of done. To certain people, this may be simple but in reality, it is much more complicated than it is. To be done with code can be a multi-step process. This gives importance to the expectation that everyone must reach when working on this project.

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

WSU Food Pantry Introductions

LibreFoodPantry

One thing I found interesting and surprising from the LibreFoodPantry website was the open source license that the pantry chose for contributors. 

I chose to write about this because last fall we had learned about software licenses, including what they are and examples of different ones, and it’s interesting to actually see what a real open source project chose to distribute under. Just looking at the license can tell how the authors intend for their software to be used and distributed, and because LibreFoodPantry chose the creative commons license, it tells us that they want this software to be open and shared freely, under that condition that the derivative works also follow the same conditions.

Thea’s Food Pantry

Simply by clicking on the link to the Thea’s Pantry gitlab page, I could tell that it was very organized and structured in a way to easily navigate, which is very useful and surprised me in a good way.

Since I am going to be using this gitlab page for the whole semester, I really appreciate that it is organized the way it is. Everything is labeled correctly and under the proper subgroups. Each subgroup also has a brief but detailed description about what is stored in it, making it easier to find the correct file quicker. All of these features make life a lot easier when navigating through this gitlab page. I couldn’t imagine trying to work on the same project with an unorganized mess of a gitlab page. It’s really something that I think gets taken for granted when it’s present but extremely noticeable when it’s lacking.

From the blog CS@Worcester – The Science of Computation by Adam Jacher and used with permission of the author. All other rights reserved by the author.

How LibreFoodPantry and Thea’s Pantry Are Changing the Way to Support the Community

In today’s digital world, even food pantries are using technology to make a bigger impact. Two examples of this innovative approach are LibreFoodPantry and Thea’s Pantry. This is working in unique way to make food distribution more efficient and accessible, but  has its own twist on how to better serve those in need.

One thing that really caught my attention about LibreFoodPantry is how they use free and open-source software to support food pantries. What makes this so interesting is that food pantries typically operate on tight budgets, and paying for expensive software can be a huge strain. By using open-source software, LibreFoodPantry allows pantries to save money and focus more on helping people rather than dealing with costly tech tools. The software is easy to use, which means volunteers can spend more time providing food and less time trying to figure out complicated systems.

What makes this even better is the sense of community that LibreFoodPantry fosters. They encourage food pantries to work together and share ideas, which helps everyone improve. Volunteers and pantry staff can also get involved in shaping the software itself, making sure it fits the real needs of the people using it. This approach helps create a more connected and effective network of food pantries, which ultimately benefits those who rely on them.

On the other hand, Thea’s Pantry takes a slightly different but just as powerful approach. While Thea’s Pantry also provides food, what stood out to me is how they go beyond just feeding people. They offer additional support services like medical and educational resources, helping people address the many challenges they face, not just hunger. This holistic approach makes sure that individuals are supported in multiple areas of their lives, improving their overall well-being.

What I really love about Thea’s Pantry is how they look at the bigger picture. They understand that food insecurity is often linked to other problems like health issues or lack of access to education. By providing more than just food, they help people get back on their feet in a more comprehensive way.

Both LibreFoodPantry and Thea’s Pantry are doing incredible work, each in their own way. LibreFoodPantry uses technology to make food distribution easier and more efficient, while Thea’s Pantry offers a well-rounded approach that supports people in more areas of their lives. Together, they’re showing us new, more effective ways to help those in need.

From the blog Discoveries in CS world by mgl1990 and used with permission of the author. All other rights reserved by the author.

Week 0 – Set Up Task 5

Been a hot second since I wrote here, but nonetheless, I’m happy to be back. This week I’ll be taking a look at the project I will be working on all this semester for CS-448, LibreFoodPantry and Thea’s Pantry.

Professor Wurst wanted us to take a look at each project, and find things we found interesting about each. Starting with LibreFoodPantry, I actually chose their Mission statement, because it gave me a lot more insight into this project then I initially had. I had assumed it was specifically a project Worcester State was doing for Thea’s Pantry, but no. It’s actually a project that spans across multiple college campuses, which I found to be very interesting. I am curious to see if this year we will be working with any other colleges also working for LibreFoodPantry.

As for Thea’s Pantry, I chose the Technology tab, because I was curious as to the technology we were using. In specific, I was surprised to find we were working with GitLab again this semester. I have known for awhile now that the industry standard for repositories in GitHub, so I’m interested to learn and know exactly why we are using GitLab over it. I also am happy to see we will be utilizing Docker and MongoDB from previous courses with Professor Wurst.

Overall, looking into these documentation, I am excited to be working on these projects for my Capstone. Here’s to another semester at Worcester State with Professor Wurst!

From the blog CS@Worcester – You're Telling Me A Shrimp Wrote This Code?! by tempurashrimple and used with permission of the author. All other rights reserved by the author.

Exploring LibreFoodPantry and Thea’s Pantry

The LibreFoodPantry’s Mission page stood out to me for its dual focus on developing free, open-source software (FOSS) for food pantries and educating students on using tech to address social inequalities like food insecurity. By using coding as a tool for social good, the project transforms classroom learning into real-world impact for example, building inventory systems to help pantries distribute resources more efficiently. I chose this because, as I prepare to contribute until graduation, I want to see how my technical efforts can address community needs. LibreFoodPantry’s mission aligns with my goal to work on projects that prioritize purpose over profit, and it’s motivating to know my contributions at Worcester State could directly support local food pantries.

In Thea’s Pantry’s GitLab repository, I explored the Inclusive Language documentation and was surprised by its integration of the Alex linter—a tool that flags exclusionary terms in documentation, such as gendered language or ableist phrases like “crazy.” This was my first encounter with such a tool. I chose this because it reflects the project’s commitment to inclusivity at every level, ensuring contributors feel welcome. As a student entering the tech field in the future, this practice resonates deeply; it’s a reminder that ethical design isn’t just about functionality but also about creating spaces where diverse voices can thrive.

From the blog CS@Worcester – CodedBear by donna abayon and used with permission of the author. All other rights reserved by the author.

LibreFoodPantry and Thea’s Pantry

For my Software Development Capstone, I will be working on the LibreFoodPantry, a Free Open Source Software project, and more specifically, the Worcester State University food pantry, Thea’s Pantry.

After reading through the LibreFoodPantry website I found it interesting how it mixes Free Open Source Software (FOSS) with a humanitarian project, as I think those two go well together naturally, both being non-profit and for a noble cause. But another part of the LibreFoodPantry program that it also works closely with college students in the computer science field. This is another way that the entire structure of the LibreFoodPantry helps, because it allows student to learn from real software that is used in the real world and gets them involved with humanitarian causes within their major.

Going further into the specific system I will be working on, I read about Thea’s Pantry. What I found to be the most interesting thing is how the whole project is organized. With a lot of different people working on the same software and making different changes and using it for different purposes, there can be a lot of things that then don’t work with each other or become incompatible or cause communication issues. The entire project is organized in a way to allow many different iterations to exist without coming into conflict and being adaptable.

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