Skip to content

Commit

Permalink
typos fixed
Browse files Browse the repository at this point in the history
  • Loading branch information
kaiserarg committed Apr 1, 2024
1 parent c43c39b commit e168e2b
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 2 deletions.
6 changes: 5 additions & 1 deletion _posts/2024-03-17-week08.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,10 @@ 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 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. Furthermore, it seems that p5.js's contributors are pretty active and code is reviewed decently in time for us to make PRs. The community seems nice too as their mission to make coding accessible and inclusive which is quite a commendable mission.

<!--more-->

- In terms of actual group work, 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.
2 changes: 1 addition & 1 deletion _posts/2024-03-31-week10.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ 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.
- So my group (working on p5.js) had several meetings by now and I am glad to report 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 code reviewed 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. <!--more--> 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.

Expand Down

0 comments on commit e168e2b

Please sign in to comment.