Ihor Radchenko <[email protected]> writes: > Do you have something specific in mind?
Yes, something like an open discussion on FSF/GNU policies and their effect on incentives for Org maintainers and contributors. I'd be surprised if the released policies didn't have any effect on Org contributions. If they do have an effect, it's good to discuss them; if they don't have any effect, maybe it's not necessary. >> 1. Because Org's communication happens on a mailing list, it is still >> between humans. No 100%-IAg-generated issues and PR. Some people may >> be helped by code assistants for patches or for bug tracking, but the >> mailing list is still a place where we can look after each other. > > Which is not a given, actually. Consider the aggressive marketing of "AI > assistants" from google. That includes their JS frontend for writing > emails, as I heard. Yes, there is no absolute and definitive protection, even for mailing list, but contributing to GitHub repos with code generated by Copilot is still relatively easier. > I am very grateful, and keep being surprised that our list is very > civil. Even compared to other Emacs lists. Indeed! > I've put a lot of work into org-contribute file recently, trying to help > contributors send better code, while not putting too many rules in place > that could scare newcomers. And It shows, thanks for that. > I do not want to be the only person left who is contributing to Org :) > So, I have to make sure that others slowly fall into being comfortable > writing more (and more) patches. Later this week I'll announce gnaw.el, a BONE Emacs client that I hope will also make it easier for everyone to confirm bugs, review patches and comment feature requests. Keep up the good work! -- Bastien
