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.