Justin Buzzard<p>Scrum Process - Designed for planning to ensure the software project stays on course. Monitored through sprints and daily standups with the team and product owner. <a href="https://mastodon.social/tags/scrum" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>scrum</span></a> <a href="https://mastodon.social/tags/sprint" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sprint</span></a> <a href="https://mastodon.social/tags/dailystandup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dailystandup</span></a> <a href="https://mastodon.social/tags/productowner" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>productowner</span></a> <a href="https://mastodon.social/tags/scrummaster" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>scrummaster</span></a></p>
Recent searches
No recent searches
Search options
Only available when logged in.
fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software.
If you wish to join, contact us for an invite.
Administered by:
Server stats:
10Kactive users
fosstodon.org: About · Status · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.3.7
#DailyStandup
0 posts · 0 participants · 0 posts today
Luke T. Shumaker<p>I haven't posted a <a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> since last Wednesday b/c posting is emotional labor and I've been emotionally used-up by shocking revelations in my personal life.</p><p>But! I have been working!</p><p>Been doing:<br />- On Saturday I went to a Colorado Green Builders' Guild event—getting <a href="https://fosstodon.org/tags/FreeSoftware" class="mention hashtag" rel="tag">#<span>FreeSoftware</span></a> onto HVAC equipment! <a href="https://fosstodon.org/tags/OpenHVAC" class="mention hashtag" rel="tag">#<span>OpenHVAC</span></a><br />- Inventing a test-harness for Single Board Computers that I've been fantasizing about for years (thread/)</p><p>Will do:<br />- Tomorrow I'm going to the Northern Colorado Climate Meetup</p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> </p><p>- I think I've completed the terrible preprocessor hack that I'm calling `fuse_optdoc.h`<br />- Working on auditing libfuse's documentation.<br />- Helping <span class="h-card" translate="no"><a href="https://mastodon.social/@amerl" class="u-url mention">@<span>amerl</span></a></span> set up a server</p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> </p><p>Since Friday:<br />- The nspawn FUSE PR got merged! <a href="https://github.com/systemd/systemd/pull/34067" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">github.com/systemd/systemd/pul</span><span class="invisible">l/34067</span></a><br /> <br />Today:<br />- Re-auditing libfuse to make sure that all end-user-facing options are documented. Involves some fancy wrangling of the C preprocessor. The preprocessor hackery felt like a good self-contained puzzle to solve to start the week.</p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> Yesterday:<br />- Got the <a href="https://fosstodon.org/tags/systemd" class="mention hashtag" rel="tag">#<span>systemd</span></a> nspawn FUSE PR to pass CI (…but it's failing again now‽)<br />- Benchmark <a href="https://fosstodon.org/tags/ruby" class="mention hashtag" rel="tag">#<span>ruby</span></a> json patches <a href="https://github.com/flori/json/pull/567#issuecomment-2333350013" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">github.com/flori/json/pull/567</span><span class="invisible">#issuecomment-2333350013</span></a> …"interesting" change in baseline variance since April</p><p>Today:<br />- Respond to feedback on the nspawn PR<br />- Feel spent, figure unstructured work will turn into something productive.… not so far</p><p>Other:<br />- Bugs on <a href="https://www.lukeshu.com/imworkingon/" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://www.</span><span class="">lukeshu.com/imworkingon/</span><span class="invisible"></span></a> 😞</p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> Woops, didn't post Tuesday or yesterday. But it's been productive!</p><p>- <a href="https://fosstodon.org/tags/Parabola" class="mention hashtag" rel="tag">#<span>Parabola</span></a>'s <a href="https://fosstodon.org/tags/Ruby" class="mention hashtag" rel="tag">#<span>Ruby</span></a> is updated!<br />- Submitted a Fix to <a href="https://fosstodon.org/tags/ArchLinux" class="mention hashtag" rel="tag">#<span>ArchLinux</span></a>'s Ruby <a href="https://gitlab.archlinux.org/archlinux/packaging/packages/ruby/-/merge_requests/7" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">gitlab.archlinux.org/archlinux</span><span class="invisible">/packaging/packages/ruby/-/merge_requests/7</span></a><br />- Made a nice README for Parabola's GPL-compatible Ruby releases <a href="https://github.com/parabola-gnulinuxlibre/ruby-json" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">github.com/parabola-gnulinuxli</span><span class="invisible">bre/ruby-json</span></a><br />- Got to "lgtm" on adding FUSE support to <a href="https://fosstodon.org/tags/systemd" class="mention hashtag" rel="tag">#<span>systemd</span></a> nspawn <a href="https://github.com/systemd/systemd/pull/34067" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">github.com/systemd/systemd/pul</span><span class="invisible">l/34067</span></a></p><p>Today:<br />- Getting the nspawn FUSE PR's CI to pass<br />- Updating+benchmarking the GPL-fix to upstream ruby-json.</p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a></p><p>So I'm working on upgrading <a href="https://fosstodon.org/tags/Parabola" class="mention hashtag" rel="tag">#<span>Parabola</span></a>'s <a href="https://fosstodon.org/tags/Ruby" class="mention hashtag" rel="tag">#<span>Ruby</span></a>. But the ARM build takes forever and so my iteration time on solving problems is slow.</p><p>In the course of this I've found some bugs in <a href="https://fosstodon.org/tags/Qemu" class="mention hashtag" rel="tag">#<span>Qemu</span></a> <a href="https://fosstodon.org/@lukeshu/113069912188713315" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">fosstodon.org/@lukeshu/1130699</span><span class="invisible">12188713315</span></a> I'm working around them by disabling affected tests if we're running in a qemu chroot. After I get the bew Ruby out, I'll look into fixing the Qemu bugs... but IDK how I'm going to prioritize that against other existing work.</p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> </p><p>What I did yesterday:<br />- Responded to feedback on the nspawn FUSE PR <a href="https://github.com/systemd/systemd/pull/34067" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">github.com/systemd/systemd/pul</span><span class="invisible">l/34067</span></a><br />- Looked at upgrading <a href="https://fosstodon.org/tags/Parabola" class="mention hashtag" rel="tag">#<span>Parabola</span></a> Ruby 3.0→3.2. Filed <a href="https://gitlab.archlinux.org/archlinux/packaging/packages/ruby/-/merge_requests/6" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">gitlab.archlinux.org/archlinux</span><span class="invisible">/packaging/packages/ruby/-/merge_requests/6</span></a></p><p>What I'm doing today:<br />- Upgrading Parabola's Ruby.<br />- Looking into CI failures on the nspawn FUSE PR.</p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a></p><p>What I did yesterday:<br />- Got a new version of the systemd-nspawn FUSE PR pushed off</p><p>What I'm doing today:<br />- Responding to feedback on said PR.<br />- you decide!</p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a></p><p>What I did yesterday:<br />- I was trying to get a new version of the nspawn-fuse PR ready<br />- but I went down some yaks with the <a href="https://fosstodon.org/tags/systemd" class="mention hashtag" rel="tag">#<span>systemd</span></a> tests, ending up with some hacking on <a href="https://fosstodon.org/tags/mkosi" class="mention hashtag" rel="tag">#<span>mkosi</span></a>.</p><p>What I'm doing today:<br />- A little more work on mkosi. I want better reporting of its capabilities based on what's installed; no more "error, do you have createrepo_c installed?" 20min into a build. I want a real <a href="https://fosstodon.org/tags/Parabola" class="mention hashtag" rel="tag">#<span>Parabola</span></a> story for mkosi.<br />- Anyway, I'm too many yaks deep, I should get back to nspawn-fuse.</p>
Luke T. Shumaker<p>No real <a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> yesterday or today because of dealing with family stuff.</p><p>But I did put up <a href="https://github.com/mailprocessing/mailprocessing/pull/16" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">github.com/mailprocessing/mail</span><span class="invisible">processing/pull/16</span></a> yesterday morning.</p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> </p><p>- On Friday I decided to work on <a href="https://fosstodon.org/tags/Parabola" class="mention hashtag" rel="tag">#<span>Parabola</span></a> stuff to take a break from the doc parser.<br />- But then some hardware came and I worked on reverse-engineering my Sensi Predict to patch their firmware to hopefully keep them out of landfills. <a href="https://fosstodon.org/tags/OpenHVAC" class="mention hashtag" rel="tag">#<span>OpenHVAC</span></a> <br />- But then yak lead to another and now I'm working on supporting FUSE inside of nspawn containers. <a href="https://fosstodon.org/tags/systemd" class="mention hashtag" rel="tag">#<span>systemd</span></a> <a href="https://github.com/systemd/systemd/issues/17607" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">github.com/systemd/systemd/iss</span><span class="invisible">ues/17607</span></a></p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a></p><p>Yesterday:<br />- Made a minor change to the glib doc PR based on feedback; it is now landed <a href="https://fosstodon.org/tags/gtk" class="mention hashtag" rel="tag">#<span>gtk</span></a> <a href="https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4187" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">gitlab.gnome.org/GNOME/glib/-/</span><span class="invisible">merge_requests/4187</span></a><br />- Kept working on getting the gi-docgen parser to pass its tests</p><p>Today:<br />- Still working on the gi-docgen parser. Current status is only 57 failing tests (out of almost 2 million).<br />- There are some emails I should do. We'll see if I actually do.</p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> </p><p>- Inching ever closer to my gi-docgen parser tests passing<br />- I found some mistakes in the glib2 docs' conversion from gtk-doc to gi-docgen, putting together an MR to fix those upstream. <a href="https://fosstodon.org/tags/gtk" class="mention hashtag" rel="tag">#<span>gtk</span></a> (edit: <a href="https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4187" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">gitlab.gnome.org/GNOME/glib/-/</span><span class="invisible">merge_requests/4187</span></a>)</p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> </p><p>So close to being happy with the new gi-docgen parser.</p><p>The 71 failures in pymdext.FuzzFencedCodeXHTML are the core HTML-BlockProcessor and the pymdext FencedCode-BlockProcessor clashing with eachother. I know what's wrong, but am trying to figure out a way to fix it that isn't a PITA.</p><p>The 4300 failures in gidocgen.FuzzHTML are that plus issues with GI-DocGen syntax extensions. It looks like most of them are the test harness not handling [type@name] links correctly.</p><p><a href="https://fosstodon.org/tags/gtk" class="mention hashtag" rel="tag">#<span>gtk</span></a></p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> </p><p>Got back from <a href="https://fosstodon.org/tags/FOSSY" class="mention hashtag" rel="tag">#<span>FOSSY</span></a> last night (instead of mid-day, because ✨airlines✨).</p><p>Gotta email/follow up with several folks who I exchanged business cards with. <a href="https://fosstodon.org/tags/OpenHVAC" class="mention hashtag" rel="tag">#<span>OpenHVAC</span></a>.</p><p>Still working on the new gi-docgen parser. <a href="https://fosstodon.org/tags/gtk" class="mention hashtag" rel="tag">#<span>gtk</span></a></p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> Whoops, no post yesterday</p><p>What I did yesterday:<br />- Fixed more discrepancies between the new doc-parser and existing gi-docgen <a href="https://fosstodon.org/tags/gtk" class="mention hashtag" rel="tag">#<span>gtk</span></a><br />- Reworked the test-util library to be more coherent</p><p>What I'm doing today:<br />- Reworking the tests to use persistent Python processes when testing against gi-docgen (and gtk-doc); this seems to improve the run-time for my expanded >100k entry test corpus from 2h45m to 3m</p><p>What I'm doing tomorrow:<br />- Getting on an airplane and flying to Portland for <a href="https://fosstodon.org/tags/FOSSY" class="mention hashtag" rel="tag">#<span>FOSSY</span></a></p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> </p><p>Today:<br />- Updated some out-of-date <a href="https://fosstodon.org/tags/Parabola" class="mention hashtag" rel="tag">#<span>Parabola</span></a> packages<br />- Picked up the Parabola stickers to give out at <a href="https://fosstodon.org/tags/FOSSY" class="mention hashtag" rel="tag">#<span>FOSSY</span></a>. Very happy with how they turned out.<br />- Still trying to iron out discrepancies in the new gi-docgen-compatible doc-parser. <a href="https://fosstodon.org/tags/gtk" class="mention hashtag" rel="tag">#<span>gtk</span></a></p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> </p><p>I've fixed a number of places where the new doc-parser disagrees with gi-docgen. Hoping to have all of the core markdown disagreements resolved today, and move on to the bits of extension syntax tomorrow. It looks like all of the remaining disagreements in the core markdown might actually be problems in the tests' normalization steps, not actual problems with the parser. <a href="https://fosstodon.org/tags/gtk" class="mention hashtag" rel="tag">#<span>gtk</span></a></p>
Luke T. Shumaker<p><a href="https://fosstodon.org/tags/DailyStandup" class="mention hashtag" rel="tag">#<span>DailyStandup</span></a> </p><p>Yesterday:<br />- Fixed some O(n²) space and time issues in the new doc-parser's inline-parser. <a href="https://fosstodon.org/tags/gtk" class="mention hashtag" rel="tag">#<span>gtk</span></a></p><p>Today:<br />- Discovered this morning that the <a href="https://fosstodon.org/tags/Parabola" class="mention hashtag" rel="tag">#<span>Parabola</span></a> build server's sshd wasn't responding. A system update had bungled our SSO config. Fixed that.<br />- I think I've got the new doc-parser's block parser behavior up to matching Python-Markdown 3.6 (it was matching 3.4.4 before).</p><p>Next up:<br />- Fixing the inline parser. I suspect all of the diffs come down to 1 big bug and 1 small bug.</p>
ExploreLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
LoginDrag & drop to upload