Hi Jack, Jack Kamm <jackk...@gmail.com> writes:
>> Would you be okay to add yourself as the ob-python.el maintainer? > > Sure, I've added myself as maintainer to the header of ob-python.el. Thanks! >> I suggest we have a policy that "Org maintainer(s)" have the last >> words on everything in Org's core, but that individual maintainers, >> when known from the header section of an Elisp file, have the very >> "first look" on bug reports and feature suggestions. >> >> WDYT? > > I'm trying to review ob-python related patches and mail as I notice > them, and monitor the list for mails with "python" in the subject, > though some may fall through the cracks occasionally, especially when my > workload is heavy. > > Should I merge in patches to ob-python.el, as I did here? Or should I > simply review them, and let the core maintainers merge them in after > review? Sorry, my policy proposal was incomplete: - A local maintainer is expected to reply to requests and bug reports regarding the local functionalities he oversees. - A local maintainer can commit changes directly to the file(s) he maintains (either submitted changes or his own). - Core maintainers have the final word on any change in any file (so in case of a disagreement with a local maintainer, core maintainers have priority.) In general, I would like to encourage "optimistic merging" from more "local" maintainers. Does that sound right? When in doubt, always discuss changes first. Thanks! -- Bastien
