On Fri, Dec 20, 2024 at 4:12 PM Maxime Devos via General Guile related discussions <guile-user@gnu.org> wrote:
> >According to the manual Ludovic Courtès and Andy Wingo are the current > maintainers. Although it hasn’t been updated in 5 years. > > https://www.gnu.org/software/guile/manual/html_node/A-Scheme-of-Many-Maintainers.html > > > >But I guess that would be a good place to update if it’s changed. > > I recall hearing that Ludo’ left (or intended to leave?), so I don’t trust > it too much, and both don’t seem active with considering Guile patches. > Also, I’ve seen some other people accepting / merging patches and there > doesn’t appear to be a formal maintainer/committer distinction here, I’d > think there are some others as well. > > I guess I’ll wait for some other replies. > Hi Maxime, I'll let others reply to your specific questions, but can explain a little bit about where I come from. I was once a Guile maintainer. During that time we had a policy of letting people which we considered as having some degree of "good judgement" have write access. It was like that from the start, actually. Guile contributions was in that respect never strictly controlled by the maintainer, even though the maintainer set policy and jumped in to correct things. Guile has in this respect always been kind of "hackable". That said, those with write access had some amount of "self restrain" such that we never committed things that es "controversial" or which we didn't feel helped the project along forward. In the case of the recent for-line-in-file, I might have given you too short notice before committing, but on the other hand I feel it is important that it doesn't become too hard to contribute to Guile. Actually, regarding for-line-in-file: Have you seen the Racket solution? That seems pretty nice. I would really like to have a Python iterator-like stream-based solution. :) Best regards, Mikael
