From: Alyssa Ross <hi@alyssa.is>
To: discuss@spectrum-os.org
Subject: Development streams
Date: Tue, 16 Jan 2024 12:19:04 +0100 [thread overview]
Message-ID: <87y1cpcyqf.fsf@alyssa.is> (raw)
[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]
Hi all,
When we had an informal compartmentalization dinner at NixCon, one thing
that we talked about a lot was how to communicate the ongoing work
happening in Spectrum, make it easier for people to get familiar with
how the project works etc. And the suggestion that really seemed to
vibe with people there was development streams / videos, which have
worked well for projects like Serenity OS and Asahi Linux.
It’s been a while since then, but in the background myself and some
collaborators have been working on setting everything up to be able to
do consistent, high quality Spectrum development streams. I’ve done
three so far this year, and I plan to keep going at that sort of pace.
So far, on stream I’ve been working on implementing support for sharing
files with VMs using the XDG File Chooser Portal.
Streams are broadcast on
https://live.qyliss.net/
And recordings are available at
https://diode.zone/c/spectrum/
Currently, there’s no schedule, as it’s usually hard for me to stick to
that sort of thing, and I want to get into the rythym of just streaming
frequently when I can before I even attempt that. But I’ll try to do
some scheduled streams in future if I can, because I know that would
make it easier for people to join in. For now, you can be notified when
streams start via browser notifications or ActivityPub.
Thanks to everbody who suggested this and helped me get set up for it,
and I hope this and other things I’m doing (like a proper release of the
Cloud Hypervisor patches) make the project seem more alive and vibrant
in 2024. :)
Alyssa
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
reply other threads:[~2024-01-16 11:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1cpcyqf.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=discuss@spectrum-os.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).