On Tue, 2025-09-23 at 11:44 +0000, Terry Cocksworth wrote: > I appreciate the lightheartedness but surely something this important > could not rest on the shoulders of one sole project member and their > agreeing to extended travel in order to unclog some server? Is there > no one else - project member or server host staff - who can perform > this task? This comes off as trifle. It's positively absurd. But I > am asking in all seriousness with no intent to come off as a critic. > > After reading the other thread I now realize the project is coming up > on a bloody full year of inaction and Arm64 debacle. What prevents the > "management" from stepping in and sorting this out? Can anyone help? > Do you need more economic donations to allocate a replacement set of > Arm64 servers? Another year of extra time? The donation goals suggest > that there's at least plenty of funds to pay for flights.
My observation, perhaps incorrect, of the OpenBSD project over the last twenty years or so is that by and large there is no "management" in the sense that you mean--i.e., someone saying "you work on this, and you work on that." Work gets done because people work on the things they are interested in or feel is important. As a general observation, asking open-ended questions in a tone implying that somebody else owes you the work *you* want done is unlikely to bear fruit. Off the top of my head, you have several options: 1. Be content with the original packages (i.e., don't worry about following -stable) 2. As Crystal said in another reply, follow -stable and build the packages yourself 3. Run -current instead 4. Convince Stuart (or somebody) to do whatever is needful to get that server back running/useful 5. Some combination of 2 and 4: stand up your own build server and make those packages available online, potentially coordinating with Stuart (or whoever) 6. Run something besides OpenBSD for your arm64 workloads
