Bastien <[email protected]> writes: > Ihor Radchenko <[email protected]> writes: > >> I am really tempted to ask "do you want to talk about this?" >> Seriously, it is concerning to get less contributions because of LLMs. > > I haven't participated in any Org meetups so far (I only appeared in one > a long time ago), so I'm not really in a position to comment, but making > room for the larger topics of *contribution incentives* would certainly > be useful, especially now that IAg modifies these incentives.
There is always a room for all Org-related topics on the meetups. There is no fixed set of topics there. We just talk about whatever comes up. > I think the topic will come up, either directly or indirectly, during > the Emacs conference - I hope the local discussion on Org can contribute > to the broader discussion among all Emacs developers. Do you have something specific in mind? As you may know, we had a topic on LLM contributions, and it generated very polarized views. In any case, the whole thing is on hold until official GNU assessment on the copyright status of LLM-generated code is released. > When I stepped down, I insisted on three pieces of maintenance advice > (https://bzg.fr/en/notes/org-has-a-new-maintainer/): > > 1. Maintaining Org Mode is about *taking care of users > 2. Be liberal in what you accept and strict in what you give out > 3. It's all about learning! > > It's interesting to see how each one may be affected by IAg: > > 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. I am very grateful, and keep being surprised that our list is very civil. Even compared to other Emacs lists. > 2. The "Postel law" of code and communication has never been more > relevant. This is because the threshold for contributing is perhaps a > little lower, which means that more responsibility falls to current > maintainers — and this is where we all need to be careful. Ideally, > every contributor would follow this Postel law, not just maintainers. 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. > 3. The emphasis on "collective learning" is also relevant: I think every > contributor here is learning, even if some of that learning happens > locally (such as reading documentation or discussing with a code > assistant.) I see current maintainers and contributors spending a lot > of time educating each other, which is really nice. 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. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
