Seif Sekalala

@gcardonag, @RNR1, @freelyPheobe, @tomporvaz (Tom, I hope this is your correct handle)... I just realized something. First of all, to catch you up, Gabe. We had a discussion, re: the...

@tomporvaz, @freelyPheobe, @gcardonag, @dibleauzah, @RNR1: Here's the PR I just created, with a clear explanation of the purposes and evolution of the ticket's tasks. Thanks. PR title and link: Creating...

Hi folks. @tomporvaz, @freelyPheobe, @gcardonag / @RNR1 & @affabillyty: It looks like the last PR (#379) was not approved / completed? Remember @vontell, you helped me fix an issue with...

@affabillyty: I believe the approach that was approved earlier by the group--during the last discussion we had about it--I believe @gcardonag in particular "stamped his approval" on it (that approach),...

Alert: @affabillyty, @gcardonag, @tomporvaz / @freelyPheobe CC: @vontell Here's the sub-directory we created; i.e., "Utilities," at the repo's root--Gabe, Idk if you recall, but you're the one who oh-so-kindly guided...

Awaiting conveners' check and comment/approval for PR: https://github.com/phlask/phlask-map/pull/396 Details of PR: >> 1) I created a couple of the new sub-DIRs to house the tech-stack docs. >> 2) I also...

@RNR1 & @gcardonag Please see PR for my response to Ron.

@tomporvaz & @freelyPheobe / @affabillyty, please note: I just left the comment below on the current relevant PR for this ticket. As soon as it (the PR) is approved, I'll...

Hi, folks. Just a quick update ahead of today's--May 7, 2024--hack-night meetup: I'm still working on this ticket--no "blockers" or problems (/issues) to report. Just a general request to please...

**Brief Update:** I just shared my latest progress via the dev-circle's Slack channel. My request is for anyone with relevant advice to please (kindly) offer it. Most importantly though, I...