Welcome to The NetBSD Foundation Annual General Meeting 2025! . I will be the voice bot^W^Wmoderator for this year. . In the agenda we will have reports from: - board (billc) - secteam (billc) - releng (martin) - core (riastradh) - finance-exec (riastradh) - membership-exec (martin, christos) - pkgsrc-pmc (wiz) - pkgsrc-security (tm, leot) - gnats (dh) . If there are any last-minute additions please /msg me! . Q&A will be at the end. . When Q&A begins please /msg me "I have question for " or "I have question for " and I will give you voice when it is your turn. . [leot is presenting for me because I'm remote on a potato connection] We will start with board+social presentations, prepared by Cryo! - - submitted by billc for board: - Hello, and welcome to the 23nd Annual General Meeting of The NetBSD Foundation. - First off, I'd like to thank for volunteering to handle moderating and admins for doing the behind the scenes magic to make this event (and all our communication) possible. - 2024 progress (more in releng report): o - NetBSD 10.1 was released December 16, 2024 o - NetBSD 9.4 was released April 20, 2024 o - NetBSD 9.3 was released May 4, 2024 o - NetBSD 10.0 was release March 28,2024 - We are still working towards NetBSD-11 after over a year of development with innovative new features, improvements, and more bug fixes. Your commits are very much appreciated, as is your continued support of the foundation. - Now on to the report from the Board of Directors: - The NetBSD Foundation Board of Directors presents a consolidated list of the relevant and major actions that occurred since last AGM. Quite a few discussions, actions, and follow-ups crossed multiple meetings. Very few meetings resulted in not reaching quorum. Check our weekly meeting minutes in: localsrc/tnf/board/minutes for the latest on our progress. During this period, new director(s) were elected by the members and officers were renewed or installed. We continued with our Bronze level sponsorship support of BSDcan, AsiaBSDcon, and EuroBSDcon to improve our representation at conferences and developer summits. - We participated in the Google Summer of Code for 2024 and attended the Google Summer of Code Mentor Summit in San Jose. We are currently participating in GSoC this year with 3 students! - For 2024: these are the projects that passed o - Test root device and root file system selection o - ALTQ refactoring and NPF integration o - Emulating Missing Linux Syscalls: Tackling The L2N Problem o - Making Network Drivers MPSAFE in NetBSD - For 2025: these projects have been chosen o - Enhancing Support for NAT64 Protocol Translation in NetBSD o - Using bubblewrap to add sandboxing to NetBSD o - Asynchronous I/O Framework - We have provided core with a pre-approved, reasonable budget, to spend as they see most fit (such a projects) without an additional confirmation step from us. - We continued to improve our interaction and relationships with vendors, as well as participating in industry PSIRT/CSIRT with commercial vendors and other open-source projects. - The funded contracts continued for: o - improvements in release engineering - We are 14% through a fundraising campaign. *Please* consider donating, as we are a US IRS 501(c)3 charitable organization. - It has been an honor and pleasure to continue working with abs, dh, leot, khorben, mlelstv, and riastradh to accomplish all that we have in this year. - .eof ['s report, for socialmedia] - - submitted for socialmedia by billc: - A non-scientific representation of Social Media Presence: - X, formerly Twitter: (NetBSD has abandoned) @netbsd still has 9362 down from 10,000 followers @pkgsrc has 654 followers down from 694 NOTE: Due to X/Twitter management, people continue to leave. - - We have an account on the distributed social network ActivityPub ('the fediverse' or better known as Mastodon), where we have a small but dedicated fan base: - @netbsd@mastodon.sdf.org has 2279 followers up from 1800 (very active) - We have no presence on BlueSky (and we should fix that). - Facebook: 2,521 up from 2,400 members (sort of active) - On IRC our numbers are stable. To help improve connectivity options, we have a Matrix bridge to our IRC channel. - irc.libera.chat users: (very very active) #NetBSD: 330 up from 284 #NetBSD-code: 57 up from 53 #pkgsrc: 124 up from 109 - .eof And now... another report from Cryo for secteam! - - submitted by billc for secteam: - This is a brief report for security-team. - Since last AGM, there has been 1 NetBSD Security Advisories: ------------------------------------------------------------ NetBSD-SA2024-002 NetBSD-SA2024-002 OpenSSH CVE-2024-6387 `regreSSHion' - NetBSD-SA2024-001 Inadequate validation of user-supplied hostname in utmp_update(8) - There have been numerous bug fixes applied to the tree, pulled up to the current branch, and in the NetBSD-8, NetBSD-9 and NetBSD-10 releases. - NetBSD continues to be represented in a product security incident response working group with other operating system vendors, as well as a direct contact team with other BSD projects. This framework allows us to better work with vendors requiring an embargoed and/or coordinated release with other operating systems. We can begin working on issues that affect NetBSD much faster, instead of only notified after an embargo is lifted. We are expanding the number of vendors as time goes on, as well as participating in FIRST. - This is teaching us quite a bit of where we needed to improve our process, which is currently on-going. - Submitted respectfully on behalf of the security-officer(s), the security-team, and the sirt team. - .eof Next we have releng presentation. It was prepared by Martin () but unfortunately he could not attend. I will present it. - We are: abs agc bouyer he jdc martin msaitoh phil reed riz sborrill snj Since the last meeting, we have: o - Released NetBSD 10.1 o - Processed hundreds of pullup requests. o - Prepared a new build cluster and made it independent of cvs. Currently we are in the last round of cleanups before branching netbsd-11, a date has not been fixed but it is supposed to happen within the next (very) few weeks. Thanks to big help from admins, maya and especially taylor we have a new build cluster ready to take over the daily builds and it has successfully build most branches from an anonhg clone instead of cvs checkout already. There are very few minor adjustments to do and a few final tests before it goes live. The new build setup will reduce build times significantly (it can build a full HEAD release in less than 4 hours). We are still processing a huge amount of pullups. This is only possible because developers take the time to test their changes on the branch and submit a pullup request. We have been pretty good with this, and pulled up lots of security and usability improvements, as well as bug fixes to the various active branches. This is good for our users, thank you to everyone who cared and made it possible. The biggest current issue is the over-aged netbsd-9 branch. We need to get the NetBSD 11 release out ASAP to be able to move NetBSD 9.x out of support. Please all help with netbsd-11 once it is there to make the release cycle as smooth and short as possible! - Thanks Martin and releng@! Next... it's core@ presentation by Riastradh! (presenting for martin who wasn't able to make it) Core's job is to provide technical leadership for the project, manage funded projects, create roadmaps for the future of the project, and resolve disputes. Since agc retired, we have invited Rin Okuyama to join core after his extensive contributions to all levels of NetBSD, and we're excited to have him working with us. Our group is: Christos Zoulas Chuck Silvers Robert Elz Martin Husemann Matthew Green Taylor R Campbell Rin Okuyama The group can be reached at . One of the tasks of the core team is to oversee, initiate and approve funded projects. We had a few of those in the last year and a few ongoing and planned for the future: - martin and phil working on merging wifi from FreeBSD - releng work (martin) Our funded projects are driven by proposals from developers. We are always open to proposals from developers who would like to work on specific topics that require larger work or have been long neglected and need cleanup. We can make suggestions of areas we would like, but we aren't an employer who can order developers to work on projects -- we can only fund the proposals we get. Another task of the core team is to resolve disputes between developers and provide ruling for contested issues. This year was quiet in this regard. A long standing open technical decision was the move away from CVS to a modern revision control system. After years of discussions and half baked (or missing details) plans, Taylor moved things forward recently and came up with a way to provide both git and hg writable repositories, with a hg repository as the internal backend. He also wrote most of the build cluster adaptation, so it can now use hg clones from anonhg instead of cvs checkouts. There are a few minor open issues and we hope to complete the transition sometime this year. The most painful task for core is to automatically be part of the security team and acting as fallback to make sure that security issues are handled in a timely fashion. Please consider joining our security team to help. Another way you can help the core team is to take over maintenance of some of our big 3rd party software. Currently most of this is done by both christos@ and mrg@, who could use more time for core and other business. If you feel you could help, please contact the current maintainer (see src/doc/3RDPARTY). .eof Thanks Riastradh! Oh, one addendum -- the `[not missing details] plan' mentioned above is here: https://mail-index.NetBSD.org/tech-repository/2025/01/04/msg000805.html Thanks Next in the agenda... finance-exec@ presentation by Riastradh! Finance-exec maintains The NetBSD Foundation's financial records and assets at the board's direction. We balance the books, stand watch over the hoard of treasure in our mountain lair (and the non-cash financial instruments), pay our bills, send thank-you letters to donors so they can get tax deductions (in the US), maintain the list of donors and the amounts donated so far, handle taxes, write financial reports. . We are: - christos (Christos Zoulas) - reed (Jeremy C Reed) - riastradh (Taylor R Campbell) . The NetBSD Foundation's public 2025 financial report is at: https://www.NetBSD.org/foundation/reports/financial/2025.html We produce this from an internal ledger maintained with ledger(1) . . Highlights: - We have net assets of a little over 250k USD. - We received about 51k USD -- hitting our usual donation target. - We spent 66k USD, mainly on: o a new build cluster to replace our >decade-old one o release engineering and wifi update project . Last year we had a project, started as a GSoC project, to reduce the overhead in automatically processing donation acknowledgment letters. It's code-complete, but deployment has stalled and we need more work to finish it and reduce our workload. (If you've donated and haven't heard back yet, sorry -- that's because it takes a lot of clicks to process each donation, so we usually do them in a batch once a month!) . Happy to answer any questions about what finance-exec does, or swap notes on using ledger(1)! Thanks, -Riastradh, on behalf of finance-exec .eof Thanks again Riastradh! Next... we have membership-exec@ presentation prepared by and ! They could not present it so I'm going to present it - The current members of membership-exec are: - Christos Zoulas - Martin Husemann - Lex Wennmacher - Thomas Klausner , and - Ken Hornstein who is on sabbatical. - Membership-exec is responsible for all aspects of "membership", but in practice the main task is to handle membership applications. The number of active developers (as of 2025-05-17) is 145. Note that this number is a bit outdated, as the membership activity validation process required for the board election has not yet happened. - Since the last AGM we gained only 3 new developers, which is (again) way too few. We need to invite more people, please help active users and encourage them to apply. - The difference between developers and active developers is explained in the bylaws - an active developer has actually committed something in the last year, or contributed in an active way, like admins. - We'd like to emphasize that we appreciate all your replies to our membership RFC e-mails, although we do not usually acknowledge them. Please keep on providing feedback to the RFC mails. - Thanks Martin and Christos! Next in the agenda... We have the pkgsrc-pmc presentation prepared by Thomas ()! Unfortunately he could not attend so I will present it - The pkgsrc team kept thousands of packages in pkgsrc up to date and in good working order, and delivered four -- the 83rd through 86th -- stable branches. Great work! The pkgsrc team has welcomed two new developers, lloyd and dkazankov. gdt has stepped down from pkgsrc PMC - thank you very much for your calming and rational input to discussions, and your efforts on improving pkgsrc! dholland has joined us as the new board representative. The current roster is: - agc (emeritus member) - dholland - schmonz - wiz We have implemented a new pkgsrc policy for more stability: basically, for packages with a higher probability of fallout and for bootstrap packages, we ask for bulk builds or review before the commits. See https://NetBSD.org/docs/pkgsrc/policies.html for details. We have also removed support for some operating systems (GNU/kFreeBSD, MirBSD, BSD/OS, and Interix). We had regular pkgsrc branches, the latest ones were done by jperkin and maya - thank you! pkgsrc-releng always welcomes more volunteers. The next big change that is planned is switching the pkgsrc repository to git. One request: please keep pkgsrc/doc/pkg-vulnerabilities up-to-date when committing pkgsrc updates that fix vulnerabilities. Thank you for your help! -- wiz, for pkgsrc-pmc - Thanks Thomas and pkgsrc-pmc! Next in the agenda we have the pkgsrc-security presentation prepared by Thomas () and me - The mission of the pkgsrc Security Team is to ensure that the ever-growing ecosystem of third party software is either safe to use or at least be sure people are aware of the known vulnerabilities. - Our members monitor publicly available vulnerability feeds, mainly CVE. - We aggregate received advisories believed to impact pkgsrc into the pkgsrc vulnerability list. When time allows we try to notify individual package MAINTAINERs and locate, commit patches to fix the vulnerabilities. - Since 2021 our ticket handling crew is currently only 2 people, unfortunately pretty understaffed. We are looking and welcome people volunteering to join us! - Currently handling tickets are: - Leonardo Taccari - Thomas Merkel - The other current members of the team are: - Thomas Klausner - Tobias Nygren - Tim Zingelman - The year in numbers: In 2024, the vulnerability list had 515 lines added to it (202 less than last year) for a total of 40720 known vulnerabilities. In 2024, the ticket queue received 40720 new advisories (10319 more than last year). Of these 40720 new advisories: new: 1587 ( 3.9%) (not able to handle in 2024) stalled: 0 ( 0.0%) resolved: 157 ( 0.4%) (affecting pkgsrc packages) rejected: 38976 (95.7%) (no impact or duplicates) - The current count of vulnerable packages in pkgsrc-current is 649 (58 less than last year), in pkgsrc-stable is 665 (64 less than last year). See the periodic email to packages@NetBSD.org for the list. But we've 3227 vulnerabilities to review! We can always use help locating and committing security patches, in particular for the many of these that are maintained by pkgsrc-users. - We encourage all developers to help us keep the vulnerability list up-to-date. If you become aware of a security issue or perform a security update in pkgsrc please edit the list. You don't need any special privilege for this. You'll find the list in pkgsrc CVS repository: pkgsrc/doc/pkg-vulnerabilities - Please join the pkgsrc Security ticket handling crew, we're pretty understaffed at the moment! Feel free to get in touch with us for additional details or an introduction. - EOF - Next in the agenda... We have gnats presentation by David (dholland)! Here's the bug database report since the last AGM (12 months): GNATS statistics for 2024 (as of May 17 2025) New PRs this year: 1165, of which 783 are still open. Closed PRs this year: 651. Net change: +514. Total PRs touched this year: 1286. Oldest PR touched this year: 1722, which was closed. Oldest open PR: 1677; PR ignored for the longest: 4691. Total number open: 6873 (Recall that this isn't github: in NetBSD "PR" means "problem report", not "pull request".) Unfortunately we are back to a more or less steadily increasing backlog. The total volume this year is up 36% over last year; that in turn was up 50% over the previous year. While more bug traffic isn't entirely a good thing, it's also not really a bad thing: it tracks community engagement. It definitely doesn't mean the codebase is 36% worse than it was last year. This is the weekly plot: * 6900 ****** ********** ************ ****************** ********************** ******** ******************************* ******************************************* ************************************************** ***************************************************** 6360 Note that the variation shown in the graph is only around 9% of the total. If it used zero as the origin the limits of ASCII plots would leave the line entirely flat. Handling the backlog remains difficult. This is mostly a tooling problem; alas, resources and energy to deal with it have been and remain scarce. If anyone was wondering, the oldest open PR (PR 1677) is about a panic in unionfs. This is unfortunately still current. The most untouched PR (PR 4691) is about ECC memory handling on sun3. Anyhow, here are the people who've been fixing the most bugs, as counted by commit messages found in PRs closed during the year. 18 gutteridge@NetBSD.org 26 kre@NetBSD.org 37 christos@NetBSD.org 53 wiz@NetBSD.org 353 riastradh@NetBSD.org This list always has a very long tail, and the difference between being on it and not is only one commit. This year there were 57 people who fixed or helped fix at least one bug report, down a bit from last year. Thanks to one and all. And here are those who've been processing pullups for bugs, according to the same analysis: 1 msaitoh@NetBSD.org (releng) 2 maya@NetBSD.org (releng) 2 riz@NetBSD.org (releng) 3 snj@NetBSD.org (releng) 8 bsiegert@NetBSD.org (releng) 221 martin@NetBSD.org (releng) Note that this reflects pullups specifically linked into gnats, not all releng work. Nonetheless, it remains heavily skewed. Many, many, many thanks, Martin. - Thanks David! We have now the Q&A session. Please /msg me and I will collect the question and then voice you. ok quick question time: what is status of next upddate for drmkms? will we see anything in 11.0? maya and I are slowly working on it, have completed the merge (as in resolving all conflicts) but now it's on to making it build and then on to making it run thanks So it might happen in 11. but no promises second question: WRT pkgsrc, will there be a cvs "bridge" or will we all need to learn the g-word? We may be able to have an ongoing one-way conversion to CVS, which is to say, a hook that just does `cvs commit' -- not built yet, but not hard to build either, just a simple matter of programming. A two-way conversion with CVS, like we have set up between git<->hg, is not feasible. i'd be more concerned with being able to check out a pkgsrc tree using cvs Right, so that's what a one-way conversion can do. (Someone has to do the work, of course -- not technically difficult, but it'll take some testing to make sure it works reliably.) oko thanks. i'm done - silenceme! Thanks PGoyette and Riastradh! what kind of hardware is used for the cluster and where is it hosted ? how big is the cluster? the build cluster crispytoast: Do you have this information handy? I forgot, gotta look it up. It's in New York in a private rack, and I forget whether it's two or four big honkin' machines. Thank you (not sure if christos is still here) Thanks zafer and Riastradh OK, looks like the builder is just one 128-core AMD Epyc system after all, not two or four. (found the receipt somewhere in our treasure horde in the mountain lair over here, had to dig through a pile of hobbit and dwarf bones) not really a question but we should def have a presence on bluesky and the abondened twitter/x account should be reactivated. it still is the largest platform point noted Thanks herdware and Cryo ex-twitter may be `large' in self-reported metrics but we are happy to not participate in the propaganda machine of fascists. Hi, I believe we lost some people due to hg/git discussion (correct me if I am wrong) and some other reasons, typically not voiced so hard to tell. Is there attempts to keep people who want to "resign". Maybe there are chances to invite some back (maybe emotions settled)? Anyone from membership-exec and/or other possible teams that would like to answer vezhlys question? (feel free to /msg me) vezhlys: If you have anyone in particular in mind, we can discuss that offline. It's been a painful subject for a long time and I'm hoping that we can reduce the pain by allowing push and pull by both hg and git. I don't have particular people in mind, but I remember at some point seeing more people retiring, thus it was more a general question. Thanks for all the questions and answers! I think we got some errata to share for the previous presentations For finance-exec I mistakenly linked to a nonexistent `2025' financial report -- oops. The latest financial report is for 2024: https://www.NetBSD.org/foundation/reports/financial/2024.html 2025, of course, has not yet finished! (And we run a Jan 1 to Dec 31 fiscal year, aligned with the calendar year.) Thanks Riastradh! Is there any other last minute questions? OK... if nothing else... Cryo, please go ahead! - - submitted by billc for board: - The NetBSD Foundation thankyous: - Thanks to all the places that host our server machines and thanks to all kind heroes who do hands-on work too on them! - Thanks to all the executive committees who do a lot of work behind the scenes to keep everything running smoothly! - Thanks to everyone who is running our services, participating and helping in mailing lists, chat and other communities and filling PRs! - Finally, thank you, for being part of this process today, fixing bugs, committing new features and making NetBSD and pkgsrc the best operating system and packaging system! - We couldn't do it without you, and please keep up the excellent work! - - Respectfully submitted on behalf of the Board of Directors .eof o/ Thank you all for coming We appreciate you taking time to come to our AGM We look forward to the NetBSD-11 release, and seeing you at the next AGM * Cryo closes the curtains and gets the broom out for the popcorn on the floor... watch out for spilled drinks. EOF Copyright 2025, The NetBSD Foundation, Inc. All Rights Reserved. Objects may appear closer in mirrors.