Annual General Meeting 2026

Today, the NetBSD Foundation had an open annual general meeting in a public IRC channel. It began with presentations, and was followed by a Q&A session where we took questions from the public. Here's the full log.

14:06:44  * Cryo turns the lights down
14:08:01 @leot Hello everyone!
14:08:01 @Cryo I'll start off by thanking you for coming.
14:08:13 @Cryo and handing it to leot!
14:08:24 @leot Thanks Cryo and thanks for coming!
14:08:29 @leot .
14:08:31 @leot Welcome to The NetBSD Foundation Annual General Meeting 2026!
14:08:36 @leot .
14:08:42 @leot In the agenda we will have reports from:
14:08:45 @leot .
14:08:52 @leot - board (<billc>)
14:08:52 @leot - core (<kre>)
14:08:53 @leot - admins (<spz>)
14:08:53 @leot - finance-exec (<riastradh>)
14:09:03 @leot - membership-exec (<martin>)
14:09:03 @leot - releng (<martin>)
14:09:04 @leot - security-team (<martin>)
14:09:12 @leot - pkgsrc-pmc (<wiz>)
14:09:12 @leot - pkgsrc-security (<tm>)
14:09:14 @leot .
14:09:24 @leot If there are any last-minute additions please /msg me!
14:09:26 @leot .
14:09:32 @leot The Q&A session will be at the end of all the presentations.
14:09:36 @leot .
14:09:44 @leot When Q&A begins please /msg me with "I have question for <team>" or
14:09:44 @leot "I have question for <nick>" and I will give you voice when it is
14:09:44 @leot your turn.
14:09:56 @leot .
14:10:49 @leot Next presentation is prepared by <billc> and board@ for board!
14:12:00 @leot I will present on <billc> behalf
14:12:09 @leot .
14:12:16 @leot Welcome to the 24th Annual General Meeting of The NetBSD Foundation.
14:12:19 @leot .
14:12:25 @leot 2025 progress:
14:12:25 @leot - Recent stable releases include NetBSD 10.1 (Dec 2024), 9.4, and 9.3
14:12:29 @leot - Development is currently focused on the imminent transition to NetBSD-11 [RC4]
14:12:35 @leot .
14:12:43 @leot We are preparing for:
14:12:43 @leot - BSDcan in Ottawa, Canada
14:12:43 @leot - The ISF Common Good Cyber Fund (CGCG) application window, which runs
14:12:43 @leot   from June 23 to August 4, 2026.
14:12:59 @leot .
14:13:08 @leot We recognize that different avenues may well be available to us regarding grants
14:13:08 @leot and funding, and we are looking for volunteers to help us investigate, apply,
14:13:08 @leot and deliver for the programs available. This includes, but is not limited to,
14:13:09 @leot potential opportunities from the Internet Society, the Linux Foundation through
14:13:09 @leot Alpha-Omega, Germany's Sovereign Tech Agency and Prototype Fund, or grants from
14:13:09 @leot the European Union through NLnet.
14:13:32 @leot .
14:13:41 @leot The NetBSD Foundation Board of Directors presents a consolidated list
14:13:42 @leot of the relevant and major actions that occurred since last AGM.
14:13:54 @leot Quite a few discussions, actions, and follow-ups crossed multiple meetings.
14:13:55 @leot Very few meetings resulted in not reaching quorum.
14:14:09 @leot During this period, new director(s) were elected by the members and
14:14:09 @leot officers were renewed or installed.
14:14:20 @leot We continued with our Bronze level sponsorship support of BSDcan,
14:14:20 @leot AsiaBSDcon, and EuroBSDcon to improve our representation at conferences
14:14:20 @leot and developer summits.
14:14:31 @leot .
14:14:41 @leot We participated in the Google Summer of Code for 2025 and we attended
14:14:41 @leot the Google Summer of Code Mentor Summit in Munich, Germany.
14:14:41 @leot We are currently participating in GSoC this year with 5 students!
14:14:51 @leot .
14:14:58 @leot For 2025, these are the projects that passed:
14:14:58 @leot - Asynchronous I/O Framework
14:14:58 @leot - Using bubblewrap to add sandboxing to NetBSD
14:15:02 @leot - Enhancing Support for NAT64 Protocol Translation in NetBSD
14:15:11 @leot .
14:15:18 @leot For 2026, these projects have been chosen:
14:15:24 @leot - Improving and Stabilizing the racoon2 IKE Daemon in NetBSD
14:15:25 @leot - Port the Enlightenment desktop environment to NetBSD
14:15:25 @leot - improving RAIDframe
14:15:36 @leot - Testing Compat Linux: Syscall testing
14:15:38 @leot - Convert a Wi-Fi driver to the new Wi-Fi stack
14:15:39 @leot .
14:15:54 @leot We continued to improve our interaction and relationships with
14:15:54 @leot vendors, as well as participating in industry PSIRT/CSIRT
14:15:55 @leot with commercial vendors and other open-source projects.
14:16:04 @leot .
14:16:18 @leot We successfully completed the large-scale migration of our repository
14:16:18 @leot infrastructure from CVS to a Git/Mercurial ecosystem, including the
14:16:33 @leot launch of live hgweb and gitweb test environments.
14:16:39 @leot .
14:16:56 @leot We also advanced our security and compliance posture by initiating CNA (CVE Numbering
14:17:01 @leot Authority) onboarding with MITRE and ensure readiness for the EU Cyber
14:17:02 @leot Resilience Act (CRA).
14:17:13 @leot .
14:17:20 @leot We also implemented "Anti-Slop" protocols to protect codebase integrity
14:17:20 @leot against code not written by humans.
14:17:25 @leot .
14:17:32 @leot The funded contracts continued for:
14:17:33 @leot - improvements in release engineering
14:17:49 @leot .
14:17:54 @leot We are 12% through a fundraising campaign. *Please* consider
14:17:59 @leot donating, as we are a US IRS 501(c)3 charitable organization.
14:18:15 @leot .
14:18:27 -- Mode #netbsd-agm [+v krelz] by leot
14:18:31 @leot EOF
14:19:09 @leot Next in the agenda we have... core@ presentation by <kre>! krelz, please go ahead!
14:19:36 +krelz Hi everyone, before I begin, any other core members who want to add something
14:20:02 +krelz to what I am about to present, msg leot and I'm sure you can be snuck in when I
14:20:12 +krelz am done, which won't take long...
14:20:14 +krelz .
14:20:25 +krelz Report from core for 2026 NetBSD AGM
14:20:33 +krelz .
14:20:37 +krelz core is tasked with technical management of the NetBSD project.
14:20:41 +krelz .
14:20:45 +krelz The current members of core are:
14:20:50 +krelz .
14:20:55 +krelz         Christos Zoulas         christos@
14:20:55 +krelz         Chuck Silvers           chs@
14:20:55 +krelz         Robert Elz              kre@
14:20:55 +krelz         Martin Husemann         martin@
14:20:55 +krelz         Matthew Green           mrg@
14:20:56 +krelz         Taylor R Campbell       riastradh@
14:20:56 +krelz         Rin Okuyama             rin@
14:20:58 +krelz .
14:21:04 +krelz Actual technical management is difficult in a volunteer project,
14:21:05 +krelz as developers work on whatever interests them.   One aspect
14:21:05 +krelz which is sometimes important is in setting disputes between
14:21:05 +krelz developers.   Fortunately there was only one such dispute in
14:21:05 +krelz the past year, which was easily amicably settled.
14:21:06 +krelz .
14:21:12 +krelz Core doesn't hold regular formal meetings, issues are discussed
14:21:12 +krelz when they arise, otherwise we're mostly fairly dormant.
14:21:13 +krelz .
14:21:19 +krelz core, as a group, can be reached at core@netbsd.org
14:21:20 +krelz .
14:21:40 +krelz That's it for me, for this year's core report, I will be here for questions later
14:21:43 +krelz .
14:21:57 @leot Thank you kre!
14:22:04 -- Mode #netbsd-agm [+v spz] by leot
14:22:16 @spz good localtime() all
14:22:16 @spz ,
14:22:16 @spz admins is the following people:
14:22:17 @spz christos, dogcow, kim, mspo, phil, riastradh, riz, seb, soda, spz, tls
14:22:17 @spz ,
14:22:30 @leot Next in the agenda... we have the admins@ presentation from spz! Please go ahead!
14:22:42 @spz Statistics:
14:22:42 @spz - admins runs the following TNF systems:
14:22:42 @spz @ TastyLime
14:22:43 @spz + 8 hardware systems, 6 'regular' Xen guests and 3 repotest Xen guests
14:22:43 @spz = 1 earmv7hf, the rest amd64
14:22:43 @spz - public services, the repo(s), sundry
14:22:55 @spz @ AOA
14:22:55 @spz + 6 hardware systems
14:22:55 @spz = all amd64
14:22:55 @spz - the NetBSD build farm
14:23:03 @spz @ Washington University
14:23:03 @spz + 7 hardware systems
14:23:03 @spz = 2 aarch64 and the rest amd64
14:23:04 @spz - two pkg builders, the repo conversion and a CI system, sundry
14:23:14 @spz @ Regensburg
14:23:14 @spz + 2 hardware systems, one of them with 2 Xen guests
14:23:14 @spz = all amd64 (+ a sparc64 serving consoles)
14:23:14 @spz - the offsite backup, archive, wip.pkgsrc.org and a CI system
14:23:25 @spz ,
14:23:25 @spz - CDN services donated by Fastly
14:23:25 @spz - Housing donated by TastyLime, Two Sigma, WWU, and spz
14:23:26 @spz ,
14:23:27 -- Mode #netbsd-agm [-v krelz] by leot
14:23:37 @spz NetBSD versions in use:
14:23:37 @spz 6   10.0_STABLE (1 earmv7hf, 1 aarch, 4 amd64)
14:23:37 @spz 6   10.1 (5 amd64)
14:23:37 @spz 13  10.1_STABLE (13 amd64)
14:23:37 @spz 1   11.0_RC3 (amd64)
14:23:38 @spz 2   11.0_RC4 (aarch64, amd64)
14:23:38 @spz ,
14:23:47 @spz Changes:
14:23:47 @spz Riastradh spent even more time on the mail system so we can still send
14:23:47 @spz mail to Google mail accounts.
14:23:48 @spz Also Riastradh has been developping the future reposerver setup.
14:23:48 @spz ,
14:24:01 @spz Notable issues:
14:24:01 @spz - spam suppression by technical means, which makes life hard(er) for
14:24:02 @spz   legitimate mailing lists and hasn't stopped spammers (or phishing) yet.
14:24:20 @spz - LLM scraping. Anti-social "all your resources are belong to us",
14:24:20 @spz   total disregard for robots.txt, and backed by lots of money
14:24:21 @spz   so they can buy all the shady "residential proxies" they want,
14:24:21 @spz   so IP blacklists aren't feasible. Their capacity to scrape
14:24:22 @spz   vastly outnumbers our capacity to serve, they are very aggressive,
14:24:22 @spz   so the chance of a human getting to use the wip.pkgsrc.org website
14:24:23 @spz   is slim. And to add insult to injury they could just download the repo
14:24:23 @spz   instead of diffing every possible version of every file against every
14:24:24 @spz   other version via the web interface:
14:24:24 @spz   the point is they don't want to use resources carefully, because that
14:24:24 @spz   would require thought and LLMs are all about not expending that.
14:24:25 @spz   (if you detect some foaming at the mouth here: yes. aarrrggghhh!)
14:24:28 @spz ,
14:24:59 @spz   We are very sorry but we'll have to add countermeasures like for
14:24:59 @spz   archive.NetBSD.org, if possibly not the same, or shut the
14:25:00 @spz   web interface down like we did with the cvsweb access to wikisrc.
14:25:03 @spz ,
14:25:11 @spz   The other NetBSD web sites survive thanks to having a limited
14:25:11 @spz   number of links (the scrapers only visit each one twice a day),
14:25:12 @spz   and CDN caching.
14:25:29 @spz - hardware aging at TastyLime, both the TNF servers and the network
14:25:29 @spz   equipment. The latter is being dealt with, there will be a downtime
14:25:30 @spz   for sometime soon. The former suffers from requiring half a week time
14:25:30 @spz   on-site and roughly two weeks from off-site to get anything working
14:25:31 @spz   properly again, and the activation energy required to do that is a lot.
14:25:59 @spz - the perennially full /pub/pkgsrc/packages on ftp.NetBSD.org.
14:26:00 @spz   we have a plan, it "just" needs implementing.
14:26:04 @spz ,
14:26:15 @spz We often get asked:
14:26:16 @spz - why don't you use a Cloud provider or rent servers instead:
14:26:24 @spz         + did that with the offsite backup server, the provider ceased
14:26:24 @spz         operations and just shut everything off: our data? sucks to be us.
14:26:25 @spz         If we own the server it might get switched off, but we could get
14:26:25 @spz         it (and thus our data) back
14:26:41 @spz         + but you could have backups: having 50TB in total backed up and
14:26:41 @spz         not paying an arm and a leg for retrieval and making certain the
14:26:42 @spz         backup provider isn't going funny is either expensive or difficult
14:26:55 @spz         + in the long run renting servers is not cheaper if they actually
14:26:56 @spz         are busy all the time
14:27:04 @spz         + we should always consider if this (whatever this) is a good use
14:27:04 @spz         of TNF funds.
14:27:15 @spz - we could sponsor you a server
14:27:15 @spz         Thanks, kind of you to offer. However:
14:27:26 @spz         If it's just one server we couldn't do OS updates. Having IPMI
14:27:27 @spz         on the open Internet for console access is not a good security
14:27:27 @spz         stance. Thus we are at a server and a console server, and having
14:27:28 @spz         a console server and several servers just scales better.
14:27:41 @spz         Plus we'd like to have at least one member of admins in viable
14:27:41 @spz         site visit distance and an expectation of duration: site moves
14:27:42 @spz         aren't much less work than hardware renewals.
14:27:52 @spz ,
14:27:52 @spz Thanks to riz, tls and phil for their resources, time
14:27:52 @spz and blood sacrifices, too. :}
14:27:53 @spz ,
14:27:58 @spz Back to moderator.
14:28:24 @leot Thank you very much spz!
14:28:41 @leot Next in the agenda we have... Riastradh with the finance-exec@ presentation!
14:28:47 -- Mode #netbsd-agm [+v Riastradh] by leot
14:28:52 @Riastradh Hi, folks!
14:28:57 @Riastradh Finance-exec hoards the cash, keeps the books, sends
14:28:58 @Riastradh thank-you notes to donors, and pays out contracts and
14:28:58 @Riastradh reimbursements.
14:28:58 @Riastradh .
14:29:07 -- Mode #netbsd-agm [-v spz] by leot
14:29:18 @Riastradh We are:
14:29:19 @Riastradh - christos (Christos Zoulas)
14:29:19 @Riastradh - reed (Jeremy C Reed)
14:29:19 @Riastradh - riastradh (Taylor R Campbell)
14:29:19 @Riastradh .
14:29:31 @Riastradh The NetBSD Foundation's public 2025 financial report is at:
14:29:31 @Riastradh https://www.NetBSD.org/foundation/reports/financial/2025.html
14:29:31 @Riastradh We produce this from an internal ledger maintained with
14:29:31 @Riastradh ledger(1) <https://www.ledger-cli.org/>.
14:29:31 @Riastradh .
14:29:52 @Riastradh Highlights:
14:29:52 @Riastradh - We have net assets of a little over 400k USD as of today
14:29:52 @Riastradh   (we received a large donation in 2026).
14:29:52 @Riastradh - In 2025, we received about 80k USD -- far surpassing our
14:29:52 @Riastradh   usual donation target of 50k USD!
14:29:54 @Riastradh - We spent 21k USD, mainly on:
14:29:57 @Riastradh   o supporting conferences and sending developers to them
14:29:59 @Riastradh   o release engineering
14:30:02 @Riastradh .
14:30:20 @Riastradh That was a lot more income and a lot less expenses than we
14:30:20 @Riastradh usually have.  But forecasting:
14:30:20 @Riastradh - We expect to purchase some more hardware replacements this
14:30:20 @Riastradh   year, and components like RAM have gotten much more
14:30:20 @Riastradh   expensive recently.
14:30:23 @Riastradh - We have more funds for funded projects now, and while core
14:30:25 @Riastradh   or pkgsrc-pmc directs the funds, they're really driven by
14:30:28 @Riastradh   the developer proposals that are available -- so if you
14:30:30 @Riastradh   want to work on a funded project, send a proposal!
14:30:33 @Riastradh .
14:30:46 @Riastradh Happy to answer any questions about what finance-exec does,
14:30:46 @Riastradh or swap notes on using ledger(1)!
14:30:46 @Riastradh Thanks,
14:30:46 @Riastradh -Riastradh, on behalf of finance-exec
14:31:27 @leot Thanks a lot Riastradh!
14:31:43 @leot Next presentation is from <martin> with the membership-exec@ presentation!
14:31:50 -- Mode #netbsd-agm [+v __martin] by leot
14:31:53 +__martin thanks
14:31:57 +__martin The current members of membership-exec are:
14:31:57 +__martin - Christos Zoulas <christos>
14:31:57 +__martin - Martin Husemann <martin>
14:31:57 +__martin - Lex Wennmacher <wennmach>
14:31:57 +__martin - Thomas Klausner <wiz>, and
14:31:58 +__martin - Ken Hornstein <kenh> who is on sabbatical.
14:32:01 +__martin  -
14:32:05 +__martin Membership-exec is responsible for all aspects of
14:32:05 +__martin "membership", but in practice the main task is to handle
14:32:05 +__martin membership applications. The number of active developers
14:32:05 +__martin (as of 2026-06-06) is 138. Note that this number is a
14:32:05 +__martin bit outdated, as the membership activity validation process
14:32:06 +__martin required for the board election has not yet happened.
14:32:16 +__martin  -
14:32:20 +__martin Since the last AGM on 2025-05-17 we gained only 5 new
14:32:21 +__martin developers, which is (again) way too few. We need to invite
14:32:21 +__martin more people, please help active users and encourage them to
14:32:21 +__martin apply.
14:32:33 +__martin  -
14:32:36 +__martin The difference between developers and active developers
14:32:36 +__martin is explained in the bylaws - an active developer has
14:32:36 +__martin actually committed something in the last year, or contributed
14:32:36 +__martin in an active way, like admins.
14:32:44 +__martin  -
14:32:48 +__martin We'd like to emphasize that we appreciate all your replies
14:32:48 +__martin to our membership RFC e-mails, although we do not usually
14:32:48 +__martin acknowledge them. Please keep on providing feedback to
14:32:48 +__martin the RFC mails.
14:33:07 +__martin thanks, back to moderator
14:33:15 @leot Thank you Martin!
14:33:33 @leot Next presentation... always from Martin but this time with the releng@ hat! :) Please go ahead __martin!
14:33:43 +__martin hi again
14:33:47 +__martin We are:
14:33:47 +__martin abs agc bouyer he jdc martin msaitoh phil reed riz
14:33:47 +__martin sborrill snj
14:33:52 +__martin    -
14:33:55 +__martin Since the last meeting, we have:
14:33:55 +__martin  o Branched netbsd-11.
14:33:55 +__martin  o Not released any formal release (only four release
14:33:55 +__martin    candidates for 11.0).
14:33:55 +__martin  o Processed hundreds of pullup requests.
14:33:56 +__martin  o Streamlined the process of cutting a release.
14:34:01 +__martin    -
14:34:05 +__martin Currently we are about to release the fifth (and
14:34:05 +__martin this time definitvely last) release candidate for 11.0.
14:34:05 +__martin 11.0 has had bad luck with security updates of 3rd party
14:34:05 +__martin components last minute and slow progress on making
14:34:05 +__martin these components updatable on relelase branches
14:34:06 +__martin (like libssh moving to /usr/lib/private/).
14:34:12 +__martin    -
14:34:16 +__martin We have only two issues open for 11.0:
14:34:16 +__martin  (1) the missing unbound import (catch-up to current)
14:34:16 +__martin  (2) a new expat release that has not made it into
14:34:16 +__martin      -current, but fixes a few security issues
14:34:20 +__martin    -
14:34:22 +__martin Volunteers are welcome to help with both - please
14:34:23 +__martin contact me directly if you have some time to help.
14:34:31 +__martin    -
14:34:34 +__martin I hope to cut RC5 later this weekend or early next week,
14:34:34 +__martin and then the final release maybe 10 days later. If one
14:34:34 +__martin of the above items does not make it in, so be it.
14:34:39 +__martin    -
14:34:43 +__martin We have streamlined the process of actually cutting a
14:34:43 +__martin release (or release candidate) and admins made it possible
14:34:43 +__martin to completely stay out of this process now. Only one releng
14:34:43 +__martin member and one security-office member are needed now.
14:34:50 +__martin    -
14:34:54 +__martin A release still takes realistically slightly less than 24h
14:34:54 +__martin wall clock time, the biggest time consumers are all fully
14:34:54 +__martin automated: 4h build time, 6h network transfer to ftp, 1h
14:34:54 +__martin generating hashes. Plus various minor manual things like
14:34:54 +__martin editing the web page and posting the release annoucement.
14:35:06 +__martin    -
14:35:09 +__martin We are still processing a huge amount of pullups.
14:35:09 +__martin This is only possible because developers take the time
14:35:09 +__martin to test their changes on the branch and submit a
14:35:09 +__martin pullup request. We have been pretty good with this,
14:35:09 +__martin and pulled up lots of security and usability
14:35:10 +__martin improvements, as well as bug fixes to the various
14:35:10 +__martin active branches. This is good for our users, thank you
14:35:11 +__martin to everyone who cared and made it possible.
14:35:19 +__martin    -
14:35:24 +__martin The following paragraph is (unfortunately) a verbatim
14:35:24 +__martin copy from last year - and still valid.
14:35:27 +__martin    -
14:35:30 +__martin The biggest current issue is the over-aged netbsd-9 branch.
14:35:30 +__martin We need to get the NetBSD 11 release out ASAP to be
14:35:30 +__martin able to move NetBSD 9.x out of support.
14:35:35 +__martin    -
14:35:40 +__martin After the 11.0 release (and probably the repository switch)
14:35:40 +__martin I plan to start a discussion about rules and processes,
14:35:40 +__martin trying to make the time from branching to first release way
14:35:40 +__martin smaller. A slow release cycle is not that bad overall (IMO)
14:35:40 +__martin but a year long delay between branching and first release
14:35:41 +__martin is clearly wrong.
14:35:45 +__martin    -
14:35:48 +__martin That is all from release engineering for this year, we are
14:35:49 +__martin hoping to have a list of several formal releases in next
14:35:49 +__martin years report and also be close to the final release of
14:35:49 +__martin 12.0.
14:36:31 @leot Thank you Martin!
14:36:50 @leot Next in the agenda we have... Again Martin, but with the security-team@ hat! Feel free to go ahead __martin!
14:36:56 +__martin This is a brief report for security-team.
14:36:57 +__martin  -
14:36:57 +__martin We are: agc billc cherry christos chs cyber hgutch joerg js
14:36:57 +__martin kre martin maya mrg riastradh rin shm spz
14:37:02 +__martin  -
14:37:05 +__martin Since last AGM we have not published any security
14:37:05 +__martin advisories. We have fixed (and pulled up) one issue that
14:37:05 +__martin has an SA pending, but it has not been finalized.
14:37:08 +__martin  -
14:37:13 +__martin There have been numerous bug fixes applied to the tree, and
14:37:14 +__martin pulled up to NetBSD-9, NetBSD-10 and NetBSD-11 release
14:37:14 +__martin branches. We also have updated lots of 3rd party components
14:37:14 +__martin in the tree when they had new releases fixing security
14:37:14 +__martin issues. Right now only the expat library needs an update in
14:37:14 +__martin -current.
14:37:21 +__martin  -
14:37:24 +__martin Most security work goes on "behind the scenes" and we
14:37:24 +__martin usually concur with request of reporters for a specific
14:37:24 +__martin publication date.
14:37:34 +__martin  -
14:37:37 +__martin Where needed we also involve NetBSD developers outside the
14:37:37 +__martin team when special expertise is needed. While we try to
14:37:37 +__martin assess all reported issues timely, we sometimes struggle
14:37:37 +__martin with doing so. Currently we have (if I did not miscount)
14:37:37 +__martin two open reports that need to be addressed.
14:37:43 +__martin  -
14:37:49 +__martin To improve our own process, becoming more reliable and more
14:37:50 +__martin transparent we are currently applying to become a CNA (CVE
14:37:50 +__martin number authority). This will allow us to assign and publish
14:37:50 +__martin our own CVE records. The process forces us to have public
14:37:50 +__martin statements of response times and processes for issues
14:37:50 +__martin reported to us. We might need to introduce a ticket system
14:37:50 +__martin to help with doing timely responses.
14:38:01 +__martin  -
14:38:05 +__martin NetBSD continues to be represented in a product security
14:38:05 +__martin incident response working group with other operating system
14:38:05 +__martin vendors, as well as a direct contact team with other BSD
14:38:05 +__martin projects. This framework allows us to work better with
14:38:05 +__martin vendors requiring an embargoed and/or coordinated release
14:38:06 +__martin with other operating systems. We can begin working on
14:38:06 +__martin issues that affect NetBSD much faster, instead of only
14:38:07 +__martin being notified after an embargo is lifted. We are expanding
14:38:07 +__martin the number of vendors as time goes on, as well as
14:38:08 +__martin participating in FIRST.
14:38:13 +__martin  -
14:38:16 +__martin This is teaching us quite a bit of where we need to
14:38:17 +__martin improve our process, which is currently on-going.
14:38:22 +__martin  -
14:38:24 +__martin Thanks to everyone helping with security issues!
14:38:43 -- Mode #netbsd-agm [-v __martin] by leot
14:38:59 @leot Thank you very much Martin!
14:39:19 @leot Next in the agenda we have... pkgsrc-pmc presentation, written by <wiz>!
14:39:35 @leot Unfortunately <wiz> could not attend the AGM so I will present it
14:39:46 -- Guest52 is now known as VE3QBZ
14:39:50 @leot The pkgsrc team kept thousands of packages in pkgsrc up to date and in
14:39:50 @leot good working order, and delivered four -- the 87th through 90th --
14:39:51 @leot stable branches. Great work, and thank you to bsiegert@ and maya@ for
14:39:51 @leot handling the branches!
14:40:02 @leot .
14:40:08 @leot The pkgsrc team has welcomed one new developer, kikadf, who takes good
14:40:09 @leot care of chromium and wayland.
14:40:15 @leot .
14:40:24 @leot The current roster is:
14:40:24 @leot - agc (emeritus member)
14:40:24 @leot - dholland (board representative)
14:40:24 @leot - schmonz
14:40:24 @leot - wiz
14:40:32 @leot .
14:40:37 @leot Thank you for working on pkgsrc!!
14:40:37 @leot -- wiz, for pkgsrc-pmc
14:40:54 @leot Thanks!
14:41:54 @leot Next in the agenda... we have pkgsrc-security@ presentation, prepared by <tm>!
14:42:18 @leot He's only online via a mobile, so I will present it!
14:42:29 @leot The mission of the pkgsrc Security Team is to ensure that the ever-growing
14:42:29 @leot ecosystem of third party software is either safe to use or at least be sure
14:42:29 @leot people are aware of the known vulnerabilities.
14:42:29 @leot         -
14:42:43 @leot Our members monitor publicly available vulnerability feeds, mainly CVE.
14:42:43 @leot         -
14:42:50 @leot We aggregate received advisories believed to impact pkgsrc into the pkgsrc
14:42:51 @leot vulnerability list. When time allows we try to notify individual package
14:42:51 @leot MAINTAINERs and locate, commit patches to fix the vulnerabilities.
14:42:51 @leot         -
14:43:13 @leot Since 2021 our ticket handling crew is currently only 2 people, unfortunately
14:43:13 @leot pretty understaffed. We are looking and welcome people volunteering to join
14:43:13 @leot us!
14:43:13 @leot         -
14:43:26 @leot Currently handling tickets are:
14:43:26 @leot  - Leonardo Taccari <leot>
14:43:26 @leot  - Thomas Merkel <tm>
14:43:26 @leot         -
14:43:38 @leot The other current members of the team are:
14:43:38 @leot  - Thomas Klausner <wiz>
14:43:38 @leot  - Tobias Nygren <tnn>
14:43:38 @leot  - Tim Zingelman <tez>
14:43:38 @leot         -
14:43:47 @leot The year in numbers:
14:43:56 @leot In 2024, the vulnerability list had 9482 lines added to it (8967 more than last
14:43:56 @leot year) for a total of 30231 known vulnerabilities.
14:44:06 @leot In 2025, the ticket queue received 50050 new advisories (9330 more than last
14:44:06 @leot year). Of these 50050 new advisories:
14:44:16 @leot  new:        302 ( 0.6%) (not able to handle in 2025)
14:44:16 @leot  stalled:      0 ( 0.0%)
14:44:16 @leot  resolved:  1697 ( 3.4%) (affecting pkgsrc packages)
14:44:16 @leot  rejected: 48051 (96.0%) (no impact or duplicates)
14:44:16 @leot         -
14:44:30 @leot Zafer Aydogan <zafer> also joined pkgsrc-security rotation list for several
14:44:30 @leot months in 2025 and helped us. Thanks Zafer!
14:44:30 @leot         -
14:44:47 @leot The current count of vulnerable packages in pkgsrc-current is 787 (138 more
14:44:48 @leot than last year), in pkgsrc-stable is 809 (144 more than last year).
14:44:48 @leot See the periodic email to packages@NetBSD.org for the list.
14:44:57 @leot But we've 3548 vulnerabilities to review!
14:45:04 @leot We can always use help locating and committing security patches, in particular
14:45:04 @leot for the many of these that are maintained by pkgsrc-users.
14:45:05 @leot         -
14:45:30 @leot We encourage all developers to help us keep the vulnerability list up-to-date.
14:45:30 @leot If you become aware of a security issue or perform a security update in pkgsrc
14:45:31 @leot please edit the list. You don't need any special privilege for this.
14:45:31 @leot You'll find the list in pkgsrc CVS repository:
14:45:31 @leot  pkgsrc/doc/pkg-vulnerabilities
14:45:31 @leot         -
14:45:48 @leot Please join the pkgsrc Security ticket handling crew, we're pretty understaffed
14:45:48 @leot at the moment! Feel free to get in touch with us for additional details or an
14:45:49 @leot introduction.
14:45:49 @leot         -
14:45:57 @leot EOF
14:46:08 @leot Thank you very much <tm>!
14:46:37 @leot We have another presentation that was not in the agenda!
14:48:09 @leot There is a gnats@ presentation by <dholland>!
14:48:16 -- Mode #netbsd-agm [+v nbdholland] by leot
14:48:26 @leot Feel free to go ahead David!
14:48:38 +nbdholland (This got held up by a schmozzle yesterday. Thanks to riastradh@ for running my dodgy scripts for me.)
14:48:40 +nbdholland  
14:48:42 +nbdholland Here's the bug database report since the last AGM (12 months):
14:48:43 +nbdholland  
14:48:50 +nbdholland GNATS statistics for 2025 (as of June  6 2026)
14:48:51 +nbdholland  
14:48:58 +nbdholland New PRs this year: 880, of which 578 are still open.
14:48:58 +nbdholland Closed PRs this year: 445. Net change: +435. 
14:48:58 +nbdholland Total PRs touched this year: 946.
14:48:58 +nbdholland Oldest PR touched this year: 5514.
14:48:58 +nbdholland Oldest open PR: 1677; PR ignored for the longest: 4691.
14:49:01 +nbdholland  
14:49:06 +nbdholland Total number open: 7313
14:49:07 +nbdholland  
14:49:13 +nbdholland (Recall that this isn't github: in NetBSD "PR" means "problem report",
14:49:13 +nbdholland not "pull request".)
14:49:14 +nbdholland  
14:49:27 +nbdholland This is the weekly plot:
14:49:27 +nbdholland  
14:49:27 +nbdholland                                                        * 6900
14:49:27 +nbdholland                                                   ******
14:49:27 +nbdholland                                               **********
14:49:27 +nbdholland                                             ************
14:49:27 +nbdholland                                       ******************
14:49:28 +nbdholland                                   **********************
14:49:28 +nbdholland                 ******** *******************************
14:49:29 +nbdholland              *******************************************
14:49:29 +nbdholland       **************************************************
14:49:30 +nbdholland    ***************************************************** 6360
14:49:30 +nbdholland  
14:49:31 +nbdholland If anyone was wondering, the oldest open PR (PR 1677) is about a
14:49:31 +nbdholland panic in unionfs. This is unfortunately still current. The most
14:49:32 +nbdholland untouched PR (PR 4691) is about ECC memory handling on sun3.
14:49:32 +nbdholland  
14:49:47 +nbdholland Unfortunately, we seem to have reverted to our old pattern of an ever-increasing backlog.
14:49:49 +nbdholland  
14:49:57 +nbdholland Anyhow, here are the people who've been fixing the most bugs, as
14:49:57 +nbdholland counted by commit messages found in PRs closed during the year.
14:49:57 +nbdholland  
14:49:57 +nbdholland   10  skrll@netbsd.org
14:49:57 +nbdholland   14  martin@netbsd.org
14:49:58 +nbdholland   15  bsiegert@netbsd.org
14:49:58 +nbdholland   18  gutteridge@netbsd.org
14:49:59 +nbdholland   23  jkoshy@netbsd.org
14:49:59 +nbdholland   27  kre@netbsd.org
14:50:00 +nbdholland   29  dmcmahill@netbsd.org
14:50:00 +nbdholland   50  nia@netbsd.org
14:50:01 +nbdholland   53  wiz@netbsd.org
14:50:01 +nbdholland  105  riastradh@netbsd.org
14:50:02 +nbdholland  
14:50:09 +nbdholland This list always has a very long tail, and the difference between
14:50:09 +nbdholland being on it and not is only one commit. This year there were 55 people
14:50:09 +nbdholland who fixed or helped fix at least one bug report, down a bit from last
14:50:09 +nbdholland year. Thanks to one and all.
14:50:13 +nbdholland  
14:50:27 +nbdholland And here are those who've been processing pullups for bugs, according
14:50:27 +nbdholland to the same analysis:
14:50:27 +nbdholland  
14:50:27 +nbdholland    1  snj@netbsd.org (releng)
14:50:27 +nbdholland    2  bsiegert@netbsd.org (releng)
14:50:28 +nbdholland    2  jdc@netbsd.org (releng)
14:50:28 +nbdholland    4  bouyer@netbsd.org (releng)
14:50:29 +nbdholland   16  maya@netbsd.org (releng)
14:50:29 +nbdholland  127  martin@netbsd.org (releng)
14:50:30 +nbdholland  
14:50:35 +nbdholland Note that this reflects pullups specifically linked into gnats, not
14:50:35 +nbdholland all releng work. Nonetheless, it remains heavily skewed. Many, many,
14:50:36 +nbdholland many thanks, Martin.
14:50:37 +nbdholland  
14:50:39 +nbdholland <eot>
14:50:59 @leot Thank you very much nbdholland!
14:51:13 -- Mode #netbsd-agm [-v nbdholland] by leot
14:51:27 @leot Now we can start the Q&A session.
14:51:45 @leot I have at least 2 questions already in the queue
14:52:15 @leot If you have more questions, feel free to /msg me with possible <team> / <nick> that may answer the question and I will voice you when it's your turn
14:52:43 -- Mode #netbsd-agm [+v racoon] by leot
14:52:54 @leot racoon has some questions for admins@! racoon, feel free to go ahead!
14:53:00 +racoon hello netbsd, hello admins
14:53:08 @leot (admins@ feel free to /msg me if you can answer their questions!)
14:53:50 +racoon my first question is whether it's possible to whitelist netbsd ftp(1) so that it doesn't need to pass a challenge to download files from archive.netbsd.org. my own experience of AI scrapers would say that's an unusual user agent to scrape, but i don't know how heinous they are. i'd like to do e.g. automated fetches of old distfiles
14:54:04 +racoon *unusual user agent to fake
14:54:37 @Riastradh racoon: the captcha in there is a temporary workaround, we might deploy anubis or something in the near future
14:54:52 @spz if ftp has a recognisable user agent that might actually a great idea
14:54:59 +racoon my second question is whether it's possible that more hardware might be moved to e.g. germany, japan in the future, so that we're less centralized in the US
14:55:24 @Riastradh racoon: Some of the hardware is in Germany already!
14:56:21 @spz it's easier for TNF to buy stuff in the US, typically cheaper too. We'll have to think about it.
14:56:25 @Riastradh (we are already running anubis on https://hgweb.test.netbsd.org and https://gitweb.test.netbsd.org/, just haven't deployed it or anything comparable on other services yet)
14:56:51 +racoon thank you
14:57:01 @Riastradh racoon: We would need a rack to do it, with enough machines to make it worthwhile to maintain there.  If you have a rack to offer, we could arrange that!
14:58:26 @leot Thanks racoon, spz and Riastradh!
14:58:49 -- Mode #netbsd-agm [-v racoon] by leot
14:59:10 -- Mode #netbsd-agm [+v cagney_] by leot
14:59:38 @leot We have a question from cagney_, probably for admins@ / gnats@!
14:59:45 @leot cagney_, feel free to go ahead with your question(s)!
14:59:55 +cagney_ leot, tks, yes; and hello all
15:00:01 -- Mode #netbsd-agm [+v nbdholland] by leot
15:00:45 +cagney_ I'm just wondering if, once NetBSD makes it off CVS, if the next big plan is the bug database? Any plans for that?
15:00:51 @Riastradh heh
15:01:07 @Riastradh We have had so many grandiose plans for bug database migration I lost count!
15:01:22 @spz yes, but it's got goats feet and then some
15:01:33 @spz since we do not want to lose old info
15:01:46 +nbdholland This has a long and unfortunate history
15:01:56 @Riastradh So, yes, it would be nice to migrate off gnats but we don't have a plan.
15:01:56 @spz otherwise: gnats should die. die die die die already. :-P
15:02:02 +nbdholland and what spz said.
15:02:09 @Riastradh But maybe we can start planning after we're done with CVS.
15:02:42 +nbdholland We've already done a lot of planning. The problem has always been getting any real work done on it
15:02:57 @Riastradh (Actually we won't quite be _done_ with CVS because there'll still be a read-only CVS front end!)
15:03:41 +cagney_ My only experience is that while it matters to preserve old bugs, it matters less to migrate them to a new system.
15:03:51 +cagney_ anyway, looking forward to move ment
15:04:40 @leot Thanks cagney_, spz, Riastradh and nbdholland!
15:04:51 -- Mode #netbsd-agm [-v cagney_] by leot
15:05:07 @leot We have another question, from ktnb... probably for security-team@ / core@ I think!
15:05:14 -- Mode #netbsd-agm [+v ktnb] by leot
15:05:19 +ktnb Hello!
15:05:31 +ktnb it seems like there are endless numbers of bugs and security bugs being around daily nowadays. I'm not sure if these bugs are found mostly by AI or not but is there any consideration on how or if we should do audits to find holes in NetBSD? in other words, how do we plan to 'keep up with the times' in this security bug world?
15:05:41 -- Mode #netbsd-agm [+v __martin] by leot
15:06:06 @leot If anyone would like to answer and has not been voiced, feel free to /msg me!
15:06:42 +__martin I'll try to answer that
15:06:58 +__martin we currently receive real bug reports at still moderate rates
15:07:03 -- Mode #netbsd-agm [+v krelz] by leot
15:07:29 +__martin we see a few "spamish" things that first ask for bug bounty programs and then never come back with real issues
15:07:30 -- Mode #netbsd-agm [+v nbdholland] by leot
15:07:49 +__martin so right now I'd say it is still handable w/o additional measures
15:08:22 +nbdholland In the long run we would also like to use formal verification tools to get ahead of the game
15:08:25 +krelz I didn't mention it in the core report, as I'm not a finance person and didn't
15:08:45 +krelz want to commit TNF to spend money, but core can receive proposals for projects
15:09:04 +krelz which can be funded if they seem worthwhile (at moderate rates)
15:09:22 +krelz If there are any proposals for how we could do active audits of the code,
15:09:39 +krelz rather than just waiting for someone else to find bugs and tell us about them,
15:09:57 +krelz that seems like something which might be worthy of some expenditure
15:10:01 +krelz .
15:10:29 +ktnb That was kind of my concern: are we not getting a lot of bugs because of lack of usage or are we just _that_ good
15:11:03 +krelz It is probably some of both of those, much of our codebase is old, and fairly
15:11:33 +krelz satble, there aren't a lot of bugs (even less security issues) to find probably,
15:11:52 @Riastradh Perhaps but we shouldn't get cocky...
15:11:54 +krelz and most of what does exist, is relatively harmless (unlikely, and not catastrophic)
15:12:23 +krelz But also, our user base isn't all that huge, compared to other systems, so
15:12:39 +krelz stray bugs can take longer to be encontered.
15:13:00 +krelz But that's also (in some respects) a good thing, as finding bugs in NetBSD
15:13:20 +krelz isn't so profitable for hackers, that they are less likely to bother
15:13:21 +krelz .
15:13:43 -- Mode #netbsd-agm [+v khorben] by leot
15:14:13 +khorben I'd like to add and emphasize on a few things: in NetBSD we rely on third-party components
15:14:36 +khorben some of these components have a security impact and subject to scrutiny (and CVEs)
15:15:02 +khorben so regardless of our relevance, we are targets too and should fund efforts ourselves
15:15:20 +khorben as mentioned earlier in board's summary, we are looking for volunteers to help us do that
15:15:47 +khorben thanks!
15:15:49 +khorben .
15:16:02 +krelz Agreed.   Send proposals to core@
15:16:29 +ktnb Thank folks!
15:16:47 @leot Thanks ktnb, __martin, nbdholland, krelz, Riastradh and khorben!
15:16:54 -- Mode #netbsd-agm [-v ktnb] by leot
15:16:56 -- Mode #netbsd-agm [-v __martin] by leot
15:17:00 -- Mode #netbsd-agm [-v nbdholland] by leot
15:17:03 -- Mode #netbsd-agm [-v krelz] by leot
15:17:06 -- Mode #netbsd-agm [-v khorben] by leot
15:17:09 -- Mode #netbsd-agm [-v Riastradh] by leot
15:17:42 @leot We have another question! From Ltning... probably for some pkgsrc folks! (maybe I can answer it, but if you can answer it, feel free to request voice via /msg me)
15:17:48 -- Mode #netbsd-agm [+v Ltning] by leot
15:18:16 +Ltning Hey all, I am a first-ish time pkgsrc patch submitted, specifically 60114
15:18:39 +Ltning It's a simple patch, of which I'd like to contribute more from time to time, but it seems "stuck"
15:19:09 -- Mode #netbsd-agm [+v racoon] by leot
15:19:15 +Ltning I guess my questions are 1) What can I do differently to get it unstuck, and 2) is there documentation on not just how to submit patches but how to "chase" them?
15:19:50 +racoon Ltning: since mail is a non-live medium, and irc is, my main suggestion would be to poke us on irc
15:19:58 +Ltning (I realise the pkgsrc team, like all others, are understaffed and overworked, so this is not meant to be criticism :)
15:20:15 +racoon it's also always helpful to say which platforms you've tested on
15:20:24 +racoon just because it shows confidence in the patch
15:20:53 @Riastradh Ltning: One thing that would be helpful is to make sure the `make test' target works, in addition to saying what platforms you've tested it on.
15:21:16 +Ltning Yeah - I have tried a couple times, but I guess not insistently enough. So perhaps the documentation could mention how-to-poke and also these things.
15:21:49 -- Mode #netbsd-agm [+v nbdholland] by leot
15:22:08 +nbdholland Another thing is, as per the discussion above, we all dislike gnats, and one of the reasons is that it's very difficult to find things in it
15:22:15 +Ltning Roger that - thanks. Will follow up with that.
15:22:34 -- Mode #netbsd-agm [+v krelz] by leot
15:22:36 +nbdholland So if you file a patch in a gnats PR, and it doesn't get attention quickly, chances are you need to poke someone about it
15:22:50 +krelz Also remember that everything in netbsd (incl pokgsrc)
15:23:05 +krelz is done by voolunteers - the best way to get someone to look
15:23:05 @Riastradh .oO(pokage source)
15:23:27 +krelz at a patch, is to find a developer with similar interests
15:23:31 +krelz (sorry for typos...)
15:23:47 +krelz and convince them to take a look - any developer will do,
15:24:07 +Ltning Yea. I guess the last comment from me then is - this is useful information, and I wish I didn't have to waste your time in this "call" to get it. 
15:24:12 +krelz the "pkgsrc team" (I believe) are generally more interested in
15:24:23 +Ltning Don't forget the impostor syndrome - I may be brave enough to poke randomly on IRC, but not everyone will be ..
15:24:30 +krelz the workings of pkgsrc itself, rather than individual packages
15:24:52 +krelz Finally, for an upgrade, which your PR is, it really helps to include
15:25:08 +krelz info on what has changed, why someone would want the upgrade
15:25:09 +krelz .
15:26:35 @leot Thanks Ltning, racoon, nbdholland Riastradh and krelz!
15:26:52 @leot We have another question, probably for finance-exec@
15:26:58 -- Mode #netbsd-agm [-v Ltning] by leot
15:26:59 +nbdholland Stuff like this about prodding people about patches being forgotten does appear on the lists at times
15:27:11 +nbdholland and it's ok to ask procedural questions there
15:27:16 -- Mode #netbsd-agm [+v Uilebheist] by leot
15:27:26 +Uilebheist Hi all, Hi NetBSD
15:27:29 +Uilebheist You mentioned that you are a US IRS 501(c)3 charitable organization - which is great for US people wanting to make a donation, but do you have or plan anything for people elsewhere?
15:28:06 @Riastradh We have discussed forming a potential nonprofit organization in Europe.
15:28:32 -- Mode #netbsd-agm [+v khorben] by leot
15:28:40 @Riastradh The main question is: How much administrative overhead does this bring on us (recall we're pretty much all volunteers, plus some part-time contracts with TNF)?
15:28:51 @Riastradh And, is that administrative burden worth the additional fundraising it would bring in?
15:29:06 @spz specifically, there are EU-wide nonprofits, but that's a lot of red tape
15:29:07 +khorben I can add to that, we have tried to revive an existing NetBSD structure in Germany to help with this
15:29:26 +khorben unfortunately it hasn't brought fruition as of now
15:29:47 @Riastradh And the administrative burden is likely to be more than just the sum of the administrative burden of two organizations separately, because they would have to be notionally independent, and we would have to have to come up with a reasonable governance structure for managing the assets.
15:29:56 +khorben and indeed there are already broader OSS structures in Europe and elsewhere
15:30:33 +khorben (and what Riastradh says)
15:31:41 +Uilebheist Thank you.  I guess for now we might just make a slighly smaller donation and not get tax back!
15:32:00 @Riastradh For example, you may be familiar with the FSF (Free Software Foundation) and FSFE (Free Software Foundation Europe) -- although they are mostly aligned in goals, they are independent organizations with independent governance structure, and sometimes disagree.
15:32:21 +Uilebheist Ah yes, noticed these.
15:33:31 @leot Thanks Uilebheist, spz, Riastradh, nbdholland and khorben!
15:33:44 -- Mode #netbsd-agm [-v Uilebheist] by leot
15:33:58 @leot I think the questions queue via my /query is currently empty!
15:34:01 @leot Any other questions?
15:34:26 @leot (And/or if I've missed any questions, please /msg them again!)
15:35:11 @Cryo Alright, thanks everyone for coming.
15:35:14 @leot Cryo: wait!
15:35:18 @leot We have another question! :)
15:35:32 -- Mode #netbsd-agm [+v wiedi] by leot
15:35:37 +wiedi Hi, is there a status update on the repo migration? (Thanks to everyone working on it!)
15:36:17 @Riastradh We have infrastructure in place, just requiring tying up some loose ends for deployment, and we need to prepare a clean final conversion.
15:36:59 +krelz Also, there is the test infrastructure, that not enough developers have been using
15:37:36 @Riastradh The infrastructure has taken a while because we're doing it a little differently from before, so we can reproducibly generate fresh images to test and deploy, rather than manually tinkering with a long-term server installation, and it took some engineering to get the software in shape for that.
15:38:05 +wiedi Thank you, looking forward to using it :)
15:38:29 +wiedi does the test infra also have a pkgsrc repo? I forgot... will have a look
15:38:44 @Riastradh yes, it does
15:38:52 +wiedi amazing, thanks for your work and answers :)
15:38:56 @leot Thanks wiedi, Riastradh and krelz!
15:39:05 -- Mode #netbsd-agm [-v wiedi] by leot
15:39:10 @leot Any other questions? :)
15:39:11 @Riastradh There are currently two test deployments, not all aligned on repository data (will change that soon), which you can test as a developer and anonymously.
15:39:45 @Riastradh Developer access is at hg.test.n.o or git.test.n.o over ssh, and anonymous access is at anonhg.test.n.o or anongit.test.n.o (or https://hgweb.test.netbsd.org/ or https://gitweb.test.netbsd.org).
15:40:41 +krelz Please, developers, use that, so you canb be familiar with
15:40:54 @Riastradh and there's a test repsitory called testsrc which is small to mess around with
15:40:56 +krelz how things will work.  Less issues after the real change happens.
15:41:07 @Riastradh Notes on usage: https://www.netbsd.org/developers/mercurial/ https://www.netbsd.org/developers/git/
15:41:11 +krelz Nothing can be :bad: in the tests, you can play safely
15:41:43 @Cryo Alright, again, thanks for coming. We are excited about the roadmap ahead and look forward to achieving these milestones together. Thank you for your time and your dedication to NetBSD.
15:42:03 @Cryo See you next year!
15:42:07 @leot Thank you!
15:42:08 @Riastradh There's also still read-only CVS access via anoncvs.test.n.o (testsrc only for now, will be everything once deployed) for access on small machines where git and hg have trouble running.
15:42:24 +khorben thanks @all!
15:42:53  * Cryo turns up the lights