Re: LuaJIT project governance

  • From: Stefano <>
  • To: luajit@xxxxxxxxxxxxx
  • Date: Tue, 18 Aug 2015 20:11:33 +0200

On 18 Aug 2015 18:34, "Aleksey Demakov" <ademakov@xxxxxxxxx> wrote:

On Tue, Aug 18, 2015 at 1:58 PM, John Graham-Cumming
<dmarc-noreply@xxxxxxxxxxxxx> wrote:
Compilers take a lot of competence and dedication. It is a highly
specialised field. It takes a certain level of prowess in computer
science in order to read recent research papers. At the same time
ability to apply theoretical knowledge practically, writing highly
efficient code, deal with very complex and obscure bugs. And know
the source base from bottom up. And it's a full time involvement.

It is not going to work with occasional contributors making random
enhancements here and there.

Also having a community voting for one feature or another is not
going to work.

As in by now forgotten ESR's terms, bazaar is not going to work
with a compiler. Any compiler inherently is a cathedral. And the
worst kind of it. It requires very sound architecture, very strict
adherence to chosen design principles. Every change must be
thought out very thoroughly and its impact on the whole systems
and its individual parts must be measured and well understood.

All in all, to keep the project alive, it will be required to find a
replacement for Mike. Perhaps it might be two persons not one.
But these two persons will need to govern the project, contribute
most of the code, accept or reject patches, decide where to move
on. They will need to *own* the source base.

I don't believe a distributed self-governing team is going to work
for such kind of a project.


At the risk of sounding pessimistic I agree with this view.
While small tasks can be taken care of by the "comunity", big features at
the core of LuaJIT like a new GC can be realistically tackled only by
experts in the field who can afford to spend considerable time on the


Other related posts: