As previously mentioned on this blog, I will be working with the LibreFoodPantry project to develop FOSS software for food pantries.

After reading through all the documentation and information available on the website (https://librefoodpantry.org/#/) and taking a look at the redesign of the website (https://librefoodpantry.gitlab.io/website/) for the project, something I found helpful was the linked information regarding FOSSisms (https://opensource.com/education/14/6/16-foss-principles-for-educators). Being new to working in FOSS development, it was beneficial to learn about the various principles associated with FOSS project development.

Specifically, the idea that contributors should “Ask Forgiveness, not Permission” was helpful for me. As someone who can sometimes be a perfectionist, I tend to not want to publish something if I feel it has potential to derail or cause problems with other parts of a project. I will strive to consider this idea as I make contributions.

Sources Referenced:

https://librefoodpantry.org/#/

https://librefoodpantry.gitlab.io/website/

https://opensource.com/education/14/6/16-foss-principles-for-educators

From the blog CS@Worcester – CodeRoad by toomeymatt1515 and used with permission of the author. All other rights reserved by the author.

I just wanted to make this quick post about the Agile values posted in the LibreFoodPantry about section. This sections focuses on defining the principles that will be used when developing this site. I chose this as these values might not be what people traditionally associate with software development. For example,”Individuals and interactions over processes and tools,” show that, despite this being a lot of programming, there is more to keep in mind than just clean and functional code. To be a successful software development team must be able to collaborate with your client to make working changes when necessary to ensure they receive exactly what they want.

On a bit of a side-note, the new design for the LibreFoodPantry looks great! The user interfaces is very clean and I always love the addition of a built in dark mode function.

From the blog CS@Worcester – My Bizarre Coding Adventures by Michael Mendes and used with permission of the author. All other rights reserved by the author.

After reading about the LibreFoodPantry I am thoroughly impressed by the ambitions it has and its aims to provide a much needed to service to food pantries in northeastern America. As a student at WSU, I think the project is not only an intrinsically positive venture but am grateful that it doubles as a practical opportunity to get hands-on programming experience as an undergraduate student.

An ability to participate in a multistate collaborative software project is a substantial driver of my interest but certainly it cannot be discounted that the humanitarian aims are just as enticing. The new site looks hip and modern and I can’t wait to see the entire project come to fruition!

From the blog CS@Worcester – Cameron Boyle's Computer Science Blog by cboylecsblog and used with permission of the author. All other rights reserved by the author.

For the project LibreFoodPantry, although it is pretty new, its main page already includes a lot of useful information about the project as well as related topic such as licensing, code of conduct, and the change log, which I think is really important for users, and developers, establishing professionalism.

From the blog #Khoa'sCSBlog by and used with permission of the author. All other rights reserved by the author.

I enjoyed reading about the FOSSisms because it is all about starting to work on your first open-source piece with others. Since this is my first time working collaboratively to this extent on open-source software I found that it was quite useful to read in order to better adapt to the upcoming challenges. I really enjoyed the particular FOSSism about being productively lost. This means that you will not always know the entire scope of the open-source project you are working on. This means you should take it upon yourself to research deeper Into the project while helping strengthen your skills in the areas you already know well. I wrote about this one because too many times I have been lost in a project and felt hopeless but by taking a deeper dive into each individual component, it allowed for me to grasp the concept.

From the blog CS@Worcester – Journey Through Technology by krothermich and used with permission of the author. All other rights reserved by the author.

Hello All, today I decided to talk about FOSSisms 16 principles of open source software in teaching. On that that found interesting was number seven which was ask for forgiveness not permission. It basically said that should just start working on something and you don’t need to ask first. This is because changes you make have are unlikely to derail a project. This is because of the use of version control which means it is very easy for the community to undo what you did or even fix the mistake you made. I picked this a subject and this particular rule because it very different to how you typically work on group project where you should communicate and talk to other before you do anything

From the blog CS@Worcester – Tim's WebSite by therbsty and used with permission of the author. All other rights reserved by the author.

LibreFoodPantry is the project that my team and I will work on the whole semester for the CS-448 capstone class. This project is an open source base project we can contribute to this project and develop parts init and share it with two other Universities. we going to reflect our work on the WSU food … Continue reading LibreFoodPantry →

From the blog CS@Worcester – Shams's Bits and Bytes by Shams Al Farees and used with permission of the author. All other rights reserved by the author.

For my CS capstone’s setup task 5, I have decided to write about my thoughts on the Principles of the Agile Manifesto linked to in the values section of the about page for LibreFoodPantry. Like the name suggests, the Agile Manifesto keeps you on your toes. Developers must be ready and able to respond to any necessary changes that may arise. The manifesto also requires regular communication. I really like how the principles of the manifesto promote living, evolving projects that adapt to situations as needed. I can see how following these principles will greatly assist in project development and achieving all the project goals. I look forward to adopting these principles and experiencing a project that abides by them.

From the blog CS@Worcester – D’s Comp Sci Blog by dlivengood and used with permission of the author. All other rights reserved by the author.

Looking at the FOSSism link, one FOSSism I related to and liked was FOSSism #2: Be productively lost. Being that the project is open sourced, joining in may be confusing because you may not know what is going on at the time or what the scope is for development. I can relate to this being a CS major. Sometimes learning new things can be quite confusing especially when you start using code that is pre written and has framework available for you to utilize. While that can be convenient it can be bothersome if you don’t yet understand how that code works and perhaps you have different ideas on accomplishing the same thing. This FOSSism is all about embracing that confusion and worry, the open source environment invites new user and it a friendly environment to ask and learn from others.

From the blog cs@worcester – Zac's Blog by zloureiro and used with permission of the author. All other rights reserved by the author.