2.7 - 83 issues closed
Tags: opensource
Published: 2022-02-20 01:16:12

## 2.7 Update stream
Starting with the juiciest, the stream on what we've done for this release.

{% twitch https://www.twitch.tv/videos/1303803789 %}

I later attempted to take on [the issue](https://github.com/Seneca-CDOT/telescope/issues/2877) live, but I did forget I didn't get any instruction on the matter, but I was supposed to get it before I really can contribute :D I will have to schedule a meeting asking for help on this later. So, I guess not conquering it today!

At least you can watch me try to take on something I clearly can't, lol. I was even maybe getting somewhere...? Not sure if I was. But it felt that way. Sometimes.

## Slack bot beginnings
As I have started on [this issue](https://github.com/Seneca-CDOT/telescope/issues/1366), I have played around making a slack bot. There seems to be a lot of issues on just making the thing work, their auth tokens and permissions are very diverse, I definitely got lost in those. 

I have also tried to do this in Go, because I always would try to do something in Go given the opportinity, but the [Go Slack API](https://github.com/slack-go/slack) was using the outdated auth system, there was simply no documentation to follow at all. I see this in my second attempt at using Go, having no tools to use, or no instruction to follow. Oh well, maybe the next project...


## Finalizing Projects
Projects now all follow the same description structure and may not be all filled in, but are consistent with their data. I have not had a chance to fix my mistakes with the templates yet, but it is a technical small housekeeping part, I will get to it eventually, I will not close the [main issue](https://github.com/Seneca-CDOT/telescope/issues/2655) until I do.


## Learning about Supabase
We have had a meeting this week about Supabase and I had a chance to ask many questions I needed to complete documentation and to understand what it is myself. I go over it on my stream in more detail, but I have also started a [scrap page](https://github.com/Seneca-CDOT/telescope/wiki/Supabase-documentation
) for the documentation file on the wiki. 

### Using wiki to make docs
By the way, this is the first time we use Wiki to start docs. Here's why. Docs, especially in the beginning need a lot of editing, which is also collaborative work. If we were to use the regular system, we'd have to get many PRs approved for stupidest of changes and would have to wait for reviews every time. It just seems more handy to start in Wiki, and hopefully that doesn't make people forget it exists easier. 

## How does Auth work?
In the meeting we have also been explained some intricacies on authentication for Telescope, and apparently it's not straight forward. It's actually very complicated and has to be explained every time. Well, it doesn't have to be. Since I have started to make a [doc](https://github.com/Seneca-CDOT/telescope/wiki/How-Auth-works
) on it, so that we don't need to repeat the same informaiton like a legend. Hopefully, again, people work on this and we have something to refer to.

## Labels for PR reviews
Another small change some might notice is a new label group for PRs:
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/4zqn92zuoqozpf0sq97k.png)
There was an issue at some point having many PRs stacked up, and some of which containing minimal changes, but having to be treated the same way as the more complex PRs. I feel like having a difficulty would encourage reviewers to even try to take it on themselves. I'm not sure if this will get used, it is an experimental feature. There might be a need for the PR template to mention `to ensure a faster review and approval, please add a difficulty label to your PR`. And describing how to really judge a difficulty of a PR. I judge it by 2 factors: novelty and amount. 

Novelty would play a big role if it is about working with a completely new technology, and it would require for the reviewer to also learn that technology to be able to review. And, well, amount. Just files changes (unlesss those are generated).


## Tough week
I have planned to complete more things than I have in the end this week. The doom that I expected to arrive on schedule has been delayed, but certainly happened this week. Instead of being it a background surrounding the ~4 weeks, it instead was a wave that hit me for a couple of days. Oh well, I am happy I was able to do the stream at last. And write this post, even if late.