week 8 10 added

_posts/2024-03-17-week08.md

@@ -0,0 +1,8 @@
+---
+layout: post
+title: Week 8 - Finalizing Project and Working As A Team
+---
+
+- After much deliberation and our initial review of scikit-learn, we found that scikit-learn was too daunting and too out of our domain so we switched and decided that we will pick p5.js as our main project to contribute to. We chose p5.js as most of us (except one) are sufficient in javascript and p5.js is mainly a JS project. Right before break we decided to all set up our environments on our laptops (and desktops) and made sure that it can at least run. We ran into a couple of issues on some devices but decided to resolve those after break. We also now set a consistent meeting time of every alternate Tuesday and Friday on top of in class time. I am extremely excited to see what we can do and achieve especially since we actually all like p5.js's mission statement as a team.
+
+- After half a semester of learning the ins-and-outs of open source projects and open source contributing, I am glad that I can finally apply these skills and knowledge into an actual project that I am interested in. For p5.js, they are entering p5.js 2.0 and my team is planning to create proposals (they are accepting idea proposals on their issues) specifically regarding accesibility. We plan to research after spring break and write an entire detail proposal on top of making changes depending on community feedback. Our basic ideas right now from our meeting are features that can help improve physical impairments experiences or something related to their very barebones web editor/ide.

_posts/2024-03-31-week10.md

@@ -0,0 +1,12 @@
+---
+layout: post
+title: Week 10 - We're doing it(?) !!!
+---
+
+- So my group (working on p5.js) had several meetings by now and I am glad to repor that we are making trenmendous progress in multiple aspects of the project we are contributing to. We finally caught everyone up to speed and I figured out a good environment setup for everyone to run, test, and build the code all within the source files without much editing. We started the week off right after break with attempts to fix smaller bugs so that we can better understand the codebase individually. We initally all individually worked on separate bugs creating different branches on one fork and then claiming issues so that we can submit PRs.
+
+- I personally claimed and am done with an issue regarding image loading on attached graphic. This is my very first PR attempt so I am quite excited to get it codereviewed perhaps and seeing if it is a viable solution. This did really help me understand p5's codebase and syntax/style throughout their source code. I think I have a better grasp of what I am able to contribute on a larger scale now. As planned this was the result I wanted. I am currently waiting for the issue to be assigned and then I will link the PR.
+
+- The process of solving this bug was pretty fun once I solved it but it was also quite frustrating trying to understand thousands of lines of code in a project that I never looked at the sourcecode for. Thankfully their doucmentation was very detailed and the person who reported the bug made it easy to reproduce and I was able to figure the issue was regarding a timer that did not exist for the graphic class that existed for their canvas class.
+
+- My groupmates are looking at other issues and they too are now understanding the codebase better. I believe Mathew is working on a feature regarding text input for 3d models and Leo&Robin are looking into a text-alignment issue. Once we all are comfortable we are going back our plan of submitting a project proposal for p5's 2.0 update in the field of accessibility or making a feature that makes p5 more acessible.