This post is for tasks 4 and 5 for CS-443 for Spring 2025. Since there is no #blogs-and-podcasts channel in the Discord, I am just posting them here.

Task 4

Task 5

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

This post is for tasks 4 and 5 for CS-443 for Spring 2025. Since there is no #blogs-and-podcasts channel in the Discord, I am just posting them here.

Task 4

Task 5

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

This post is for tasks 4 and 5 for CS-443 for Spring 2025. Since there is no #blogs-and-podcasts channel in the Discord, I am just posting them here.

Task 4

Task 5

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

This post is for tasks 4 and 5 for CS-443 for Spring 2025. Since there is no #blogs-and-podcasts channel in the Discord, I am just posting them here.

Task 4

Task 5

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

This post is for tasks 4 and 5 for CS-443 for Spring 2025. Since there is no #blogs-and-podcasts channel in the Discord, I am just posting them here.

Task 4

Task 5

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

This post is for tasks 4 and 5 for CS-443 for Spring 2025. Since there is no #blogs-and-podcasts channel in the Discord, I am just posting them here.

Task 4

Task 5

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

This post is for tasks 4 and 5 for CS-443 for Spring 2025. Since there is no #blogs-and-podcasts channel in the Discord, I am just posting them here.

Task 4

Task 5

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

Before working on anything for LibreFoodPantry, I needed to read up on the project. LibreFoodPantry values FOSSisms: https://opensource.com/education/14/6/16-foss-principles-for-educators. I thought this was an interesting read, especially because I am new to open source culture. It discusses some values and beliefs, one of them being that if something didn’t happen publicly, then it didn’t happen. This would make it easier for people to be able to see what’s being done and join, and documenting things helps keep people up-to-date on such a large project. Some FOSSisms also mention that students’ changes aren’t likely to completely mess up a project because of versioning and branches exist. This is reassuring that something I do for the project, even something small, is still helpful, and changes I make would not be entirely damaging.

I read up on Theas Pantry at https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/documentation/-/blob/main/README.md. An interesting component of information from those files is the User Stories. I wanted to highlight this because it is helpful in helping us understand the flow of how signing in would work for different people, and any restrictions there may be. This gives us a better idea of the coding. For example, we know to code for a blank registration form appearing if the visiting guest’s WSU ID has not been swiped at the pantry before. We would also know to code for the guest’s current information to be displayed if they’ve visited before. On the topic of restrictions, the user story tells us that only one guest is allowed in the pantry at a time, so we know to maybe only code for up to one person to be signed in at a time, and they’d need to sign/check out before another guest could.

From the blog CS@Worcester – CS With Sarah by Sarah T and used with permission of the author. All other rights reserved by the author.

Thea’s Pantry is a GitLab group and a food pantry for our WSU school community. In this Documentation project one of the items that I found useful, interesting, and surprising, is Workflow. The main reason I specify this item is that helps the developers and is the way we will be working on this food pantry.
I choose to write about it because the workflow is one process where we can coordinate and organize well, and also give our contribution toward this project.
In this way, we as students will learn how to work by collaborating, by using the git workflow developed for Thea’s Pantry project.

From the blog CS@worcester – Xhulja's Blogs by xmurati and used with permission of the author. All other rights reserved by the author.

For the cs-448 course we are working on a project which regards to the Worcester states food pantry program called Thea’s Pantry we are working on a project to improve its community. After looking upon the user stories, and I found useful information. This is fascinating on how the documentation gives a breakdown in each category such as the guest visiting inventory, access management, new inventory, etc . Tells how in each bullets on how it is supposed to be configured and implemented throughout the project. helps give an understanding what is needed to be accomplished and/or has been already accomplished.

From the blog cs@worcester – Dahwal Dev by Dahwal Charles and used with permission of the author. All other rights reserved by the author.