CS 448-02 – Setup Task # 4 Conventional Commits 

I found the conventional commits description under “Thea’s Pantry Workflow” interesting. This is new to me, but I see the importance of being able to control all developers to use the same formula in describing commits. It is also necessary to use the semantic versioning [1] to not only be an asset to developers and managers following other developer’s work in a controlled manner, but allowing the connection of the GitLab commits to be integrated with testing, and deployment in an automated fashion (CI/CD)

[1]  FIX/PATCH  – generally bug fixes

      FEAT/MINOR – a full new feature that does not break the code-base,

      BREAKING CHANGE/MAJOR.

I am also interested in learning Kubernetes, as well as understanding better how continuous integration and deployment will be used in our product.

From the blog cs@worcester – (Twinstar Blogland) by Joe Barry and used with permission of the author. All other rights reserved by the author.

Thea’s Pantry

The section that I choose to focus on is Thea’s Pantry Workflow. The workflow is an important part of this application because the workflow facilitates the flow of information, tasks, and events. A workflow is a blueprint for developers to follow on how to use git. Everyone on the team has access to the information that’s needed to complete the required actions. In Thea’s Pantry, the blueprint is easily readable and understandable on how to use git for this application. Any developer looking at the workflow or any new developers added to the team will be able to follow this process easily. The workflow also lets developers know if any push/commits that failed is explained as to why when using commitlint.

From the blog CS@Worcester – The Dive by gonzalezwsu22 and used with permission of the author. All other rights reserved by the author.

LibreFoodPantry

One thing that I noticed when reading over the LibreFoodPantry code of conduct was how seriously online harassment is taken. I liked how the pantry is a place where people can feel safe to contribute to the project without fear of harassment. The enforcement policy seems extremely fair with many chances for corrective action to be taken.

The pantry enforces their code of conduct across multiple websites and does not tolerate harassment on any platform, including the LibreFoodPantry discord server. I especially like this since there are many organizations who only care about their own platform and do not monitor off-site harassment. This makes LibreFoodPantry a more welcoming environment for all developers and users.

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

LibreFoodPantry

The idea of working with an open source project has always scared me a lot. The way we have been doing projects since freshman year – trusting the professor as our main if not only guide and him being confidential with our bugs, errors and insecurities has been a great comfort and way for me to grow. However, an open source project is completely different and I didn’t know how to get started with it. When reading about the 16 FOSSisms as values of the LibreFoodPantry, I learned so much about the benefits they bring to us as student learners, understood how valuable it is to serve the community with our knowledge and embrace the process of learning instead of being scared of not doing enough or doing things wrong. These values will allow us to do and be our best in this amazing project.

16 maxims from free and open source culture for education | Opensource.com

LibreFoodPantry | LibreFoodPantry

From the blog CS@Worcester – Software Intellect by rkitenge91 and used with permission of the author. All other rights reserved by the author.

Thea’s Pantry

After reading  the items from Thea’s pantry, user stories is the item that I find interesting because it provides me sufficient information that I need to know about the project. The user stories of this project has a total of five stories which are used to describe how the software will interact with the end users through access management, guest visiting, (food) inventory, and the monthly reporting. In other words, the user stories tell me that what inputs should be received and what output should be generated for each interaction between the software and the end users.

On the other hand, I find the user stories useful because it helps me better understand the project’s goals, and also understand the architectural parts more easily. Based on that, I can also figure out what I have to do in my capstone’s project.

From the blog CS@Worcester – T's CSblog by tyahhhh and used with permission of the author. All other rights reserved by the author.

Blog Post 448-01:  Code of Conduct Pledge

I found the pledge for the code of conduct to be really well written. My wife worked for the Office of federal contract compliance program (OFCCP) as a compliance officer to monitor corporate discrimination. Their “affected classes” were limited to a list including the disabled, sexual discrimination (usually with women being paid less than men), Vietnam war veterans, and a few others. It always bothered me that the list of classes never included gender identity, body size, and personal appearance.

The Pledge by LibreFoodPantry fills in many of the gaps with a much fuller definition of areas of discrimination, and then follows with “Our Standards”, which lays out a clear utopian view of how we should behave in teams and is as essential education for students who are about to enter the business world as any of the technical skills we are learning. The stressing of positive communal behavior is probably the most important thing to learn for entry into business world.

From the blog cs@worcester – (Twinstar Blogland) by Joe Barry and used with permission of the author. All other rights reserved by the author.

Familiarizing Myself With Thea’s Pantry

After visiting Theas Pantry’s gitlab, I was about to learn more about what I will be working on this semester and I can say, I am very excited. I will be on the team that will be working with the GuestInfoSystem. In the documentation repository, technology is what drew my attention. In this file, it lists what types of tools and frameworks we will be using for this project. Since I plan on being a full-stack developer, working with these technologies will help me further my knowledge with working with them. Not only that but working on this project will allow me to experience how it will be working with a team on a real project. It’s a preview of what I will be doing when I eventually start working at a company after graduation.

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

LibreFoodPantry

The section that I choose to focus on is the Code of Conduct. While reading through each section from the LibreFoodPantry website, what stook out to me which sometimes is not clear on most apps, is the Guidelines section. The apps policies, if violated one of the community standards, will be temporarily ban the user allowing them to correct their actions. If the user continues to violate the community standards they will then be permanently banned. What I found interesting or rather curious about was whether the app notifies the user of the violation they made? And if so, how many violations are there before permanently banned? I think adding that additional information leaves little wiggle room for the user to claim they were not notified.

From the blog CS@Worcester – The Dive by gonzalezwsu22 and used with permission of the author. All other rights reserved by the author.

Familiarizing Myself With LibreFoodPantry

After visiting the website, LibreFoodPantry.org, I was really impressed by how clean the webpage looked. It really gives a brief idea on what this project is all about. On the main page it shows items such as the mission, values, status, and a few other things about the project. One thing that stood out to me was the User Story Map. I did not expect to see a layout of things that may be incorporated into the project. Seeing this as a student who will be working on this project allows me to better understand what I may be working on. The User Story Map shows features that may be added to the project based on interviews with clients. However, the story map doesn’t guarantee that everything on it will be incorporated, its more to help select what features to have and implement.

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

Thea’s Pantry

I was reading the user stories under the documentation of Thea’s Pantry and had an idea of how everything works. When we take a look at the user stories, we can see how well organized is the system and the step-by-step procedure according to different domains like “Identity and Access Management”, “A Guest Visiting Thea’s Pantry” and many others. Also, I took a look at the Architecture and the UML Design was so impressive. I can see what work has to be done and worked on. I love the way it was divided into different parts, (GuestInfoSystem, IneventorySystem, ReportingSystem, and so on) which makes it easier for developers to understand and have an idea of what to work on.

From the blog CS@Worcester – Gracia's Blog (Computer Science Major) by gkitenge and used with permission of the author. All other rights reserved by the author.