When I explored the page for Libre food pantry I found the coordinating committee page to be very interesting. I chose this as the most interesting because it shows the different universities and shop managers that are working on this project. I found that there are people from Nassau Community College, Western New England University, Drexel University, alongside Worcester State who are working on Libre food pantry. I did not know it was such a collaborative effort between so many universities.

While reviewing the Gitlab for Thea’s pantry, I found that going through the workflow and architecture documentation was especially helpful. In the summer, when I was working on linters for Libre Food Pantry and Theas Pantry, I got to get a look at some of the systems for Thea’s pantry but I did not thoroughly understand what each system uses. The part of the architecture documentation that explains the features and their components thoroughly laid out how the systems work together. I found the integration and deployment diagrams to be helpful in providing a visual aspect of how the systems work together. The workflow documentation was helpful because it served as a reminder of the workflow that I used during the summer. The bullet point about using a “breaking change” footer or a “!” after the type if the work introduces a breaking API change is helpful because I’ve never worked on a breaking change.

From the blog CS@Worcester – Live Laugh Code by Shamarah Ramirez and used with permission of the author. All other rights reserved by the author.

In my exploration of LibreFoodPantry’s main page and Thea’s Pantry, I found myself captivated by the community’s commitment to fostering a positive environment, as reflected in their Code of Conduct.

LibreFoodPantry’s Code of Conduct: A Commitment to Inclusivity

One aspect that particularly caught my attention was LibreFoodPantry’s inclusive pledge. This commitment ensures that participation in the community remains a harassment-free experience for everyone, irrespective of diverse characteristics. The explicit mention of age, body size, disability, ethnicity, gender identity, and more reinforces the community’s dedication to creating a welcoming space for all. Choosing to delve into this aspect was essential as it resonated with my belief in the significance of inclusivity in collaborative environments.

Thea’s Pantry GitLab Group: Enforcing Standards

Diving into Thea’s Pantry GitLab group, I focused on the enforcement responsibilities outlined in their Code of Conduct. Community leaders play a crucial role in clarifying and enforcing acceptable behavior, ensuring a positive and respectful space. The detailed enforcement guidelines, ranging from correction to permanent bans, showcase a structured approach to maintain community standards. Highlighting this aspect in my blog emphasizes the importance of clear guidelines and consequences in creating a conducive collaborative environment.

In conclusion, LibreFoodPantry and Thea’s Pantry’s Codes of Conduct provide a framework for inclusive and respectful collaboration. The commitment to inclusivity in LibreFoodPantry’s pledge and the structured enforcement approach in Thea’s Pantry underscore the essence of fostering positive community dynamics. These aspects not only shape the communities themselves but also serve as an inspiration for others in the open-source landscape. Through these Codes of Conduct, both projects are actively contributing to a culture of diversity, respect, and collaboration in the realm of software development.

From the blog CS@Worcester – Hieu Tran Blog by Trung Hiếu and used with permission of the author. All other rights reserved by the author.

Thea’s Pantry helps provide food and other essentials to students, staff, and faculty in need. The pantry was established to help students who experience food insecurity, to allow them to focus on their studies and complete their education. In regards to researching more on Thea’s Pantry, it’s surprising how many different systems, components, and features are involved with the systems architecture. There are a few different systems including GuestInfoSystem, InventorySystem, ReportingSystem, IAMSystem, and EventSystem, that each have their own separate components and features that each complete their own specific tasks. I selected this for the reasoning that many individuals believe that these type of systems can be constructed and running easily and quickly. In actuality when creating these complicated systems involves lots of trial and error, testing, and lots of work to ensure every system and component is running efficiently, correctly, and used as intended.

LibreFoodPantry is a project that is being constructed primarily by instructors and their students. What is interesting about this is that not only Worcester State students are participating in this project. Students from Nassau Community College, Western New England University, and Worcester State University are all participating in this project. Anyone can work and contribute to this project, adding new features or improvements or addressing known issues within the system. A singular individual may not know how to address every problem or issue. Therefore having the capability to interact with other people working on the project and having others review work can be extremely beneficial and help anyone learn more than what they previously knew.

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

Exploring LibreFoodPantry and Thea’s Pantry

LibreFoodPantry is a community building free and open source software for food pantries. Thea’s Pantry is the food pantry provding food and other essentials to the Worcester State community,

LibreFoodPantry

When familiarizing with LibreFoodPanty, I found the Coordinating Committee page to be be the most interesting. This is because it shows the different universities that are working together to create software for food pantries. Those working with LibreFoodPantry are Nassau Community College, Western New England University, and Worcester State University. These three universities working together strengthens the Mission statement of LibreFoodPantry by being three smaller communities coming together to make one larger community who believes software can be used to help society.

Thea’s Pantry

While exploring the Thea’s Pantry Gitlab group, the architecture of the entire system is what I found to be most interesting. Thea’s Pantry uses a microservices architecture which involves breaking down the system into smaller subsystems. In the context of Thea’s Pantry, there are 5 total systems being used where two of them are from a third-party. Each subsystem is composed of features which uses components.

I found the architecture to be most interesting because we will be working on different parts of the system; therefore, understanding how the system is composed and how it functions would be helpful.

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

For my capstone class, I needed to familiarize myself with these before working on the project.

With regard to the LibreFoodPantry docs, I think the organization structure is fairly interesting. It’s a great idea to give students a direct opportunity to engage in FOSS development in the real world and actually take part in something. It’s good for experience regardless of where students decide to go with their education. Not to mention that this is an actual piece of software being used across multiple campuses for a good cause.

We’ve spent a fair amount of time with an older version of Thea’s Pantry for one of my previous courses, but I didn’t get to really look at the actual up to date repository. It’s interesting to see all of the individual systems that combine into a full Microservice structure. With regard to the documentation, I found it fairly admirable to have a piece on inclusivity in the Computer Science space. It really is important to allow people who are interested in the space to feel welcome instead of outcasted and feeling like they don’t belong, whether by intention or not. As the documentation says, these perspectives are definitely an important addition so that software can be even better, I recall statistics that show a more diverse team tends to make a higher quality product.

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

I find the Code of Conduct outlined by LibreFoodPantry particularly interesting. It establishes a commitment to maintaining a harassment-free and inclusive community for all members, emphasizing values such as empathy, kindness, and respect. The use of specific examples of acceptable and unacceptable behavior, along with a clear enforcement process, contributes to making a positive environment within the community. I chose to write about this because it reflects the project’s dedication to developing open-source software and to create a supportive and diverse community. The emphasis on social good and the proactive approach to ensuring a welcoming atmosphere align with the broader mission of using technology for society better.

Regarding Thea’s Pantry, the user stories caught my attention. Specifically, the process of handling guest visits, including the registration of new visitors and the streamlined checkout system, stood out. The attention to detail in managing inventory, tracking guest visits, and handling new donations showcases a well-designed system to efficiently serve the community. I chose to write about this aspect because it highlights the practical application of the software in a real-world context, demonstrating how technology can enhance the operations of a food pantry and contribute to a more organized and effective service for both staff and visitors.

From the blog CS@Worcester – Site Title by rkaranja1002 and used with permission of the author. All other rights reserved by the author.

I’m starting my (hopefully) last semester in Worcester State’s Computer Science program, and the focus of our capstone course will be contributing to the microservices supporting Thea’s Pantry at Worcester State University. Thea’s Pantry is using a guest frontend, reporting and inventory system built by the LibreFoodPantry humanitarian free open-source software community. LibreFoodPantry is managed by a coordinating committee and a board of trustees, and has adopted a Code of Conduct modeled after the Contributor Covenant. I hadn’t heard of the Contributor Covenant before reviewing the website for Thea’s Pantry. The Contributor Covenant provides a general set of community guidelines that foster a respectful and welcoming space for collaborative open-source software development. I have previously learned that a policy of enthusiastic inclusivity and openness is essential to an open-source project’s success, but I hadn’t realized that such a policy would consequently necessitate the creation of a robust code of conduct for the project’s contributors.

In the Software Design & Architecture course I took last semester, I learned about semantic versioning in software and how it’s used to keep track of a software’s present state even after many alterations to the source code. In order for Gitlab to correctly increment a commit’s semantic versioning number, contributors to Thea’s Pantry are expected to attach commit messages to their work that adhere to the Conventional Commits standard. The Conventional Commits standard requires developers to include a type of change such as “fix” or “feat” at the beginning of their commit message. “Fix” commits signal a patch, and will increment the rightmost semantic versioning number, while “Feat” commits signal a feature update that would be reflected by an increase in a middle semantic versioning number. If a breaking change will be introduced, that would be notated by either a “BREAKING CHANGE:” footer, or a “!” appended to the commit type.

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