Introduction to LibreFoodPantry and Thea’s Pantry

 

Reading over the website, I found out that LibreFoodPantry requires that all code contributions be licensed under the GNU General Public License version 3 (GPL-3.0) and that all content be licensed under the Creative Commons Attribution-ShareAlike 4.0 International License (CC-BY-SA-4.0). Also, it was with a very strict code of conduct that warns for bans as this project is for a community effort to make free and open source software to help society.  I chose to write about this because it shows how seriously LibreFoodPantry takes responsibility, fairness, and collaboration in an open-source community. These strict licensing ensures that the software and content remain free and accessible to everyone, while the strong code of conduct protects contributors and keeps the project focused on its social mission.

For thea’s pantery I found out IdCardScanner.md which was the most interesting part for me when looking at how the system work. Allowing IDs to be entered either manually or through a swipe reader makes the system more accessible and efficient, especially during busy pantry hours while in real life, i have not used much technology related to swiping because today’s technology just asks for card numbers and cvv instead of swiping as technology advances. Therefore, I think is a great opportunity to know how this architecture works in real life 

Comments

Post a Comment

Popular posts from this blog

Waterfall 2.0

  When looking around the internet, I found that there was waterfall 2.0 version of the waterfall software development methodology that we learned at start of class. After I saw the article, I found out that even the most established practices can transform to meet the demands of new era. Therefore, I chose this article as it provides basic summarization of waterfall 2.0 and the difference between traditional waterfall model. As we talked about why waterfall method was being replaced by agile and scrum, I thought there will be some people who will try to improve and use the old working method so using this article showed me how waterfall transformed to adopt need of current workflow. Therefore, I decided to look into it as a background for finding out about the improved version as it revives the dying method into a new form.              This article uses baking as an example to illustrate the principles of waterfall 2...
Read more

Is Agile going to fail?

  This article by Jeff Gothelf asks the question “Is Agile finally over?” after 20+ years of implementation to tech field. He argues that even though Agile’s widespread adaptation hasn’t got the result that Agile was intended for. Many companies claimed to be “Agile” as they copy each other, but the implementation of it was shallow or almost non-existent to make changes according to it. Therefore, he says that agile does not seems working as companies try to make employee follow set of rules instead of working in following the basic principles of Agile. He concluded that organizations need to focus on true organizational agility rather than rigid framework adoption. This article caught my attention while searching through the internet as it criticizes Agile’s current status in the business world as ideal of agile does not really fit in reality in organization experience. The vague promises and core ideas are often overlooked to the ‘wants’ of either customer or the organization...
Read more

Clean code and reality.

  The article examines the question, “is clean code by Robert Martin still matters?” From author’s 16-year coding experience, he writes about reality in writing clean code and its criticism. He acknowledges that t in the end meeting the deadline with functional and bug free code is more important then elegant code following the principle of clean code. However, he argues in the end as a developer, trying to integrate small aspects of clean code into your code base is going to make your skill improve as an engineer in the long run even if many people will not care about it. I selected this article as it addresses some uncertainty that I had with clean code. All the code I have written feels like I got pressure to deliver functional code as quickly as possible and now I’m supposed to write elegant, maintainable code so I wanted to see the real live example from experience if clean code was that necessary. The author’s real-world experience and practical approach toward the subjec...
Read more