Category Archives: CS-448

Exploring LibreFoodPantry and Thea’s Pantry

 In this post, I want to highlight the Code of Conduct section of the LibreFoodPantry community page. This part of the site outlines a pledge that ensures everyone in the community can participate in a respectful and inclusive environment. What stood out to me is the focus on empathy, kindness, and respect for differing opinions. This is especially important in any community-driven project, as it creates a welcoming atmosphere where individuals feel safe sharing ideas and collaborating. I chose to write about this because it’s easy to overlook how important it is to have an outlined set of guidelines that protect participants. The specific examples of acceptable and unacceptable behavior provided are especially helpful, as they create clarity around what is expected. I thought it seemed very similar to the working agreements we created in our first class, and I understand their importance now.

For Thea’s Pantry, I was really excited to see that they use semantic versioning for their software updates. It was very cool to see a concept we covered in class show up in the real world. I’ve seen semantic versioning used at my job, where we track all of our releases, but that is something I expect from a formal company.. Seeing this system used in a project like Thea’s Pantry really reinforced how valuable these best practices are in professional, open-source development.

It’s a great reminder that the concepts we study in class have tangible applications in real-world projects, and it’s exciting to see them put into action.


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.

Exploring LibreFoodPantry and Thea’s Pantry

 In this post, I want to highlight the Code of Conduct section of the LibreFoodPantry community page. This part of the site outlines a pledge that ensures everyone in the community can participate in a respectful and inclusive environment. What stood out to me is the focus on empathy, kindness, and respect for differing opinions. This is especially important in any community-driven project, as it creates a welcoming atmosphere where individuals feel safe sharing ideas and collaborating. I chose to write about this because it’s easy to overlook how important it is to have an outlined set of guidelines that protect participants. The specific examples of acceptable and unacceptable behavior provided are especially helpful, as they create clarity around what is expected. I thought it seemed very similar to the working agreements we created in our first class, and I understand their importance now.

For Thea’s Pantry, I was really excited to see that they use semantic versioning for their software updates. It was very cool to see a concept we covered in class show up in the real world. I’ve seen semantic versioning used at my job, where we track all of our releases, but that is something I expect from a formal company.. Seeing this system used in a project like Thea’s Pantry really reinforced how valuable these best practices are in professional, open-source development.

It’s a great reminder that the concepts we study in class have tangible applications in real-world projects, and it’s exciting to see them put into action.


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.

Exploring LibreFoodPantry and Thea’s Pantry

 In this post, I want to highlight the Code of Conduct section of the LibreFoodPantry community page. This part of the site outlines a pledge that ensures everyone in the community can participate in a respectful and inclusive environment. What stood out to me is the focus on empathy, kindness, and respect for differing opinions. This is especially important in any community-driven project, as it creates a welcoming atmosphere where individuals feel safe sharing ideas and collaborating. I chose to write about this because it’s easy to overlook how important it is to have an outlined set of guidelines that protect participants. The specific examples of acceptable and unacceptable behavior provided are especially helpful, as they create clarity around what is expected. I thought it seemed very similar to the working agreements we created in our first class, and I understand their importance now.

For Thea’s Pantry, I was really excited to see that they use semantic versioning for their software updates. It was very cool to see a concept we covered in class show up in the real world. I’ve seen semantic versioning used at my job, where we track all of our releases, but that is something I expect from a formal company.. Seeing this system used in a project like Thea’s Pantry really reinforced how valuable these best practices are in professional, open-source development.

It’s a great reminder that the concepts we study in class have tangible applications in real-world projects, and it’s exciting to see them put into action.


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.

Exploring LibreFoodPantry and Thea’s Pantry

 In this post, I want to highlight the Code of Conduct section of the LibreFoodPantry community page. This part of the site outlines a pledge that ensures everyone in the community can participate in a respectful and inclusive environment. What stood out to me is the focus on empathy, kindness, and respect for differing opinions. This is especially important in any community-driven project, as it creates a welcoming atmosphere where individuals feel safe sharing ideas and collaborating. I chose to write about this because it’s easy to overlook how important it is to have an outlined set of guidelines that protect participants. The specific examples of acceptable and unacceptable behavior provided are especially helpful, as they create clarity around what is expected. I thought it seemed very similar to the working agreements we created in our first class, and I understand their importance now.

For Thea’s Pantry, I was really excited to see that they use semantic versioning for their software updates. It was very cool to see a concept we covered in class show up in the real world. I’ve seen semantic versioning used at my job, where we track all of our releases, but that is something I expect from a formal company.. Seeing this system used in a project like Thea’s Pantry really reinforced how valuable these best practices are in professional, open-source development.

It’s a great reminder that the concepts we study in class have tangible applications in real-world projects, and it’s exciting to see them put into action.


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.

Exploring LibreFoodPantry and Thea’s Pantry

 In this post, I want to highlight the Code of Conduct section of the LibreFoodPantry community page. This part of the site outlines a pledge that ensures everyone in the community can participate in a respectful and inclusive environment. What stood out to me is the focus on empathy, kindness, and respect for differing opinions. This is especially important in any community-driven project, as it creates a welcoming atmosphere where individuals feel safe sharing ideas and collaborating. I chose to write about this because it’s easy to overlook how important it is to have an outlined set of guidelines that protect participants. The specific examples of acceptable and unacceptable behavior provided are especially helpful, as they create clarity around what is expected. I thought it seemed very similar to the working agreements we created in our first class, and I understand their importance now.

For Thea’s Pantry, I was really excited to see that they use semantic versioning for their software updates. It was very cool to see a concept we covered in class show up in the real world. I’ve seen semantic versioning used at my job, where we track all of our releases, but that is something I expect from a formal company.. Seeing this system used in a project like Thea’s Pantry really reinforced how valuable these best practices are in professional, open-source development.

It’s a great reminder that the concepts we study in class have tangible applications in real-world projects, and it’s exciting to see them put into action.


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.

Exploring LibreFoodPantry and Thea’s Pantry

 In this post, I want to highlight the Code of Conduct section of the LibreFoodPantry community page. This part of the site outlines a pledge that ensures everyone in the community can participate in a respectful and inclusive environment. What stood out to me is the focus on empathy, kindness, and respect for differing opinions. This is especially important in any community-driven project, as it creates a welcoming atmosphere where individuals feel safe sharing ideas and collaborating. I chose to write about this because it’s easy to overlook how important it is to have an outlined set of guidelines that protect participants. The specific examples of acceptable and unacceptable behavior provided are especially helpful, as they create clarity around what is expected. I thought it seemed very similar to the working agreements we created in our first class, and I understand their importance now.

For Thea’s Pantry, I was really excited to see that they use semantic versioning for their software updates. It was very cool to see a concept we covered in class show up in the real world. I’ve seen semantic versioning used at my job, where we track all of our releases, but that is something I expect from a formal company.. Seeing this system used in a project like Thea’s Pantry really reinforced how valuable these best practices are in professional, open-source development.

It’s a great reminder that the concepts we study in class have tangible applications in real-world projects, and it’s exciting to see them put into action.


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.

Exploring LibreFoodPantry and Thea’s Pantry

 In this post, I want to highlight the Code of Conduct section of the LibreFoodPantry community page. This part of the site outlines a pledge that ensures everyone in the community can participate in a respectful and inclusive environment. What stood out to me is the focus on empathy, kindness, and respect for differing opinions. This is especially important in any community-driven project, as it creates a welcoming atmosphere where individuals feel safe sharing ideas and collaborating. I chose to write about this because it’s easy to overlook how important it is to have an outlined set of guidelines that protect participants. The specific examples of acceptable and unacceptable behavior provided are especially helpful, as they create clarity around what is expected. I thought it seemed very similar to the working agreements we created in our first class, and I understand their importance now.

For Thea’s Pantry, I was really excited to see that they use semantic versioning for their software updates. It was very cool to see a concept we covered in class show up in the real world. I’ve seen semantic versioning used at my job, where we track all of our releases, but that is something I expect from a formal company.. Seeing this system used in a project like Thea’s Pantry really reinforced how valuable these best practices are in professional, open-source development.

It’s a great reminder that the concepts we study in class have tangible applications in real-world projects, and it’s exciting to see them put into action.


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.

Set-up Task #5

LibreFoodPantry

I found it interesting how thorough the Code of Conduct was. The lists of encouraged and unacceptable behavior as well as the tiered consequences for violating the Code of Conduct made me think that there have been lots of instances of poor behavior in this community in the past. I may be completely wrong about this, but if not, it really makes me think about how or why people would join or be invited to this community dedicated to a good cause only to spread hate and negativity. 

Thea’s Pantry

Despite working with Thea’s Pantry for quite a while now, I have not put much research into it at all. I knew it was a place for students and people to get help with food insecurities but I didn’t really know where it was or how it worked for those people. The User Stories give me a great sense of how the pantry works as a guest and some insight into how staff manage it. I liked the listed step-by-step process for the various interactions that make the pantry what it is. I find that following instructions is much nicer than figuring things out on my own so having these stories of how the pantry is intended to work makes me feel comfortable should I ever be in one of the scenarios.

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

CS 448-01 Team 3 Sprint 3 Retrospective (5/7)

Following the very close end to our 3rd and last sprint, I feel like we really put in the effort to finish AddInventoryFrontend. As a team, we completed all of the issues that we were assigned as a team and meet up together for many in-person meetings in order to finally finish up some loose-ends.

One of the biggest things that we finished from last sprint was that we were to got AddInventoryFrontend working. Last sprint was very difficult because the code that we were working on was messy and we had to change a few different approaches to the Frontend since our original approach to create a wireframe which would eventually become the UI did not come together. For this sprint, we had updated our code to be able to finally string together the Frontend with the Backend, like changing around our directory, adding in key files to run the Frontend, and then test through trial and error our Frontend. We used our current wireframe in order to build our Frontend to what we ended up with.

For AddInventoryFrontend, I had worked on updating the Documentation of AddInventoryFrontend since I wanted to be able to contribute more in this sprint. When I looked at the documentation in its original state, I was dumbfounded to find that there were almost nothing there to begin with. It must have looked liked a template since it specified that the linter being used was called test.sh instead of lint.sh. Because everyone on my team was doing so much work on the Frontend and its functionality, I wanted to be able to contribute more as a member of the team, so I decided to modify the documentation so that it would reflect the changes that we made as as a team.

Unfortunately, we were unable to completely fix some issue that we had with our Frontend before the end of the sprint. Our Frontend works great and loads properly now that we have fixed it. If we had another sprint left before the end of the semester, we would have worked on optimizing our Frontend so that the button could work so that you can add and remove units of food from the inventory, and also keep track of how much food is in the inventory through a viewable parameter that would check in the database for the inventory amount. With that being said, any issues that we had with AddInventoryFrontend will have to be resolved next year.

As a member of our team, I definitely could work on trying to practicing some code so that I would be able to make changes that they made with the Frontend. The Frontend was not impossible for me to read since I have played around with HTML before, but I was still trying to figure out all the formatting for our Frontend so I took a good look at our code. I could tell that at the very least that we did our best with creating the Frontend with the little time that we had following our previous sprint, but I would like to not forget about the things we did as a team to create our Frontend. I think that I better understand how AddInventoryFrontend works because I did run the environment on my own. For our presentation, I really hope that we can talk more about how we got our Frontend to work rather than just listing out the issues that we did in our sprint.

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

CS 448-01 Team 3: Sprint 2 Retrospective (4/4)

With the second sprint, we had so much trouble with our sprint until near the end of the sprint. To elaborate on what went wrong, I would like to start out with what we were planning from the very start, as this will be very important for what we will be doing for the next sprint.

While our last sprint, we split between meeting remotely and meeting in-person, we finally decided that it would be better for us to meet in-person. We also came up with a wireframe that we decided to use as our template to create our framework for AddInventoryFrontend (https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/documentation/-/blob/main/Developer/Wireframes.md). Since we already had AddInventoryBackend working as intended with the proper testing IDs being used as a way to test our code for the Backend, we only just needed to create AddInventoryFrontend so that we can try to put a frame over all the work that was done with the Backend from last year. At the very least, we knew exactly how we wanted to build our front-end.

On the contrary to how we finally have a plan for our Frontend, I was having lots of trouble with trying to build the Frontend. Since I had lots of trouble with some of the issues that we did, I instead decided to focus on redoing some of the issues we had from last sprint (https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem/addinventoryfrontend/-/issues/36). At the very least, I could at least contribute a little bit to our sprint, knowing the tasks that we were unable to completely finish.

What we as a team learned from sprint 2 was that we learned about using Vue, a Javascript framework that we would use to help build our Frontend. While we were not able to get the entire page running, we added a functionality to be able to add a button to our Frontend, just as we intended when we were following our wireframe example from earlier. Once we had explored our options to how we would build our Frontend, we decided to use a new wireframe that my teammate would create for our team to follow along with.

The things I could do improve on as an individual is that I need to speak out more with my team about the issues that may have, let it be related to work or anything other. I had trouble with this sprint because I was not great with programming with HTML and Javascript, and I felt like that was really hindering my performance as a team member. I did my best with trying to get help with working on the sprint, and when that was not working out well for me, I consulted my search engines instead. As someone who was much better with AddInventoryBackend, working with the Frontend was not my strength as shown in this sprint. I was confused with what wireframe we were using for the sprint until the end of the sprint when we had a semi-functioning Frontend that we were going to tweak in our next sprint. For the next sprint, I am hoping that I can get to do anything that is not too technical like directly running the Frontend, and I hope that then next sprint will be where our team will be able to get a working Frontend by the end of next sprint.

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