Thanks for your answers. Ihor Radchenko <yanta...@gmail.com> writes:
>> In general, Org contributors with push access can fix bugs directly, >> without announcing this on the mailing list. But *all other changes* >> should be submitted and discussed on this mailing list. > > Sure. It is always nice to have historical records on why certain > decisions have been made. It is not just to be able to keep track of discussions that led to decisions: it is also to be able to be as *inclusive* as possible. Of course, time and skills (and other psychological traits) are the main parameters deciding whether someone can participate to these discussions: but the more they take place on the mailing list, the more inclusive they are IMHO. (I know this opinion is debatable: most <30yo (<35yo) hackers out there will say that relying on a mailing list for such discussions wards them off, insisting we should go on GitHub... but *anyone* can send an email to a list, while only registered GitHub users can open an issue. We certainly don't want to encourage anyone to register on GitHub.) -- Bastien
