Planning Meeting March 23 - Seneca-CDOT/telescope GitHub Wiki

Overview

Seneca's on-campus activities have all been moved online, and we held our first Slack-only meeting today.

Present: humphd, c3ho, A Garcia, Josue, Rafi, Cindy Le, RayGervais, Krystyna, julia-yatsenko, James Inkster

Discussions and Decisions

  1. We want to try and not do everything at scheduled times. Some of us have children or other responsibilities, which make it hard to be present. We'll use Slack, GitHub, and perhaps experiment with some other tools (see below). Everyone is going to need to be more vocal about their needs using this style: if you need help, ask; if you need a review, ping people; if you're lost with code, setup a time to get help online.

  2. One exception we're going to make is for our weekly Triage. We are going to try and do a screencast + voice Zoom session every Wednesday at 11am. The first one will be led by humphd, and he'll send out details on how to join by Tues. We'll use Zoom. People can join via their computer, or by phone, and we'll try doing voice only + a screenshare so people don't have to use video. We'll see how it goes and repeat if it works, or make changes.

  3. A few of us experimented with the VSCode Live Share extension today. It allows anyone to share their VSCode editor with others, and is useful for getting help debugging, or if you need to show people your code or terminal. We can try using it to replace what we used to do in class, when we'd share our code by showing each other our laptops.

  4. We're going to do all of our normal in-class presentations as blog posts. This will mean that everyone needs to step up their game when it comes to how often they post to their blog, and how much content they put there. You need to replace the equivalent of your in-class participation and presentation work with writing in your blog. It should be possible, but people will have to be intentional about writing more and more often.

  5. We're going to have to be sensitive to each other as we merge big changes, especially to the backend. Any PRs that would affect how people run the code locally should be treated specially. We might try having people do a demo of how the change works, how to run things now, and how to alter your setup. This could be done using Zoom or recorded as a video on YouTube, etc. When we review each other's PRs, if you notice a change that will impact other devs on the team, call it out for a demo to be created/given.

  6. We also came up with a plan for releases and our deadlines. It is presented in the table below.

Updated Release Schedule

Release Focus Due Date
0.9 Features April 3
1.0 alpha Finalize 1.0 April 10
1.0 Bug Fixes April 15