At Fri, 10 Oct 2025 01:16:49 +0200, Jörg Sonnenberger <joerg%bec.de@localhost> wrote: Subject: Re: irt: Re: Core statement on version control systems > > As someone who has tried to upstream > hundreds of patches to as many projects, I > want a low effort method. Just because I > send you a fix for a problem, be it > portability or even a bug fix, I don't > want to have any significant attachment to > your project. Having to sign up to a bug > tracker for example is a no-go for that. Indeed! That's why I believe the only viable solution in today's world is to leverage the features of a _public_ _Git_-based hub/forge, or maybe even more than one. Most third parties who might contribute to NetBSD will already have an account on one of those public forges and they will already know how to use Git (and probably like using Git). It must be possible for them to make a public clone on that forge site, push their proposed changes to it, and for there to be some built-in notification method that allows them to write up a request that gets the attention of the NetBSD project, i.e. a developer with a commit bit and the willingness to review those changes and if/when appropriate pull them in. -- Greg A. Woods <gwoods%acm.org@localhost> Kelowna, BC +1 250 762-7675 RoboHack <woods%robohack.ca@localhost> Planix, Inc. <woods%planix.com@localhost> Avoncote Farms <woods%avoncote.ca@localhost>
Attachment:
pgpTahqtaM1dh.pgp
Description: OpenPGP Digital Signature