From: Alyssa Ross <hi@alyssa.is>
To: discuss@spectrum-os.org, devel@spectrum-os.org
Cc: impaqt <impaqt@vendek.net>, Cole Helbling <cole.e.helbling@outlook.com>
Subject: This Week in Spectrum, 2020-W22
Date: Sat, 30 May 2020 19:43:29 +0000 [thread overview]
Message-ID: <87y2p99pjy.fsf@alyssa.is> (raw)
[-- Attachment #1: Type: text/plain, Size: 2420 bytes --]
I began this week feeling very burnt out from some Nix stuff. Later in
the week, I got sick as well (thankfully not with any COVID-19 symptoms)
and ended up spending several days not being able to do much beyond
sleep. So, not a lot from me to report this week I'm afraid. This'll
be a short one.
Documentation
-------------
I documented the memfd server I recently added to crosvm[1]. I sent the
documentation patch to the list, and was very pleased to receive
reviews[2] from impaqt and Cole Helbling. This is really the first time
a patch from me has gone through an actual review cycle with other
people involved, so that's very exciting. Here's to more of that! :)
With that documentation, I was then able to add a memfd server quota to
the Contribution Ideas page[3]. This is an important feature, so if
nobody is interested in working on it I'll do it myself, but it's also a
nice opportunity to do a pretty self-contained bit of work on crosvm, so
I'm going to leave it up for a bit in case somebody else wants to try
it.
[1]: https://spectrum-os.org/doc/developer-manual.html#_the_memfd_server
[2]: https://spectrum-os.org/lists/archives/spectrum-devel/C312TALEYVQS.RICE3VLEBSMM@jupiter/T/#m2ff54b74c87ccb89f47cb5737a75b3212714b5e7
[3]: https://spectrum-os.org/todo.html
Infrastructure
--------------
Increased the maximum message size on devel@ to 80K from 40K, because a
patch I sent was too big and got held for moderation.
Nixpkgs
-------
The expected Chromium OS update was released this week (instead of last
as I'd expected). crosvm now wants the minijail source code, which
isn't hosted on chromium.googlesource.com. This required making the
update script a bit smarter. I posted the patch series improving the
update script and then updating chromiumOSPackages to the list[1]. More
details there.
Another shout out to Cole for having a go at doing this update, even if
he didn't get all the way because he needed the cores on his computer
for other things. Thanks Cole!
[1]: https://spectrum-os.org/lists/archives/spectrum-devel/20200530190028.6388-1-hi@alyssa.is/T/#t
I'm mostly feeling better now (although still getting tired very
easily), so hopefully things will go faster again next week. Too early
to be certain, though. I'm happy to have at least got the
chromiumOSPackages update out the way, and delighted to have received
the reviews on the documentation patch.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
reply other threads:[~2020-05-30 19:43 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=87y2p99pjy.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=cole.e.helbling@outlook.com \
--cc=devel@spectrum-os.org \
--cc=discuss@spectrum-os.org \
--cc=impaqt@vendek.net \
/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).