Re: [ANN] Looking for new LuaJIT maintainers

  • From: Stefano <>
  • To: luajit@xxxxxxxxxxxxx
  • Date: Sat, 1 Aug 2015 17:24:55 +0100

On 31 July 2015 at 14:49, Mike Pall <mike-1507@xxxxxxxxxx> wrote:

It has been almost 10 years since the first public release of LuaJIT.
It's time for me to move on.

I'm looking for new maintainers to take over the LuaJIT project.


If you would like to help shape the future of LuaJIT as part of a team
of maintainers, please apply here on the mailing list. Thank you!

Hi Mike,

I am sorry to hear that, but hopefully this is for the best!
I was actually going to write you to enquire about the future
directions of LuaJIT, I guess your post renders that unnecessary :)

Having discovered LuaJIT just by accident some 5 years ago, it has
been a pleasure working with it and seeing it grow.

I myself have a vested interest in the future of LuaJIT as I invested
considerable time on a number of projects including:
- a LuaJIT multi-os, multi-arch portable distribution and its package
manager (new release scheduled in 2 weeks)
- a number of binding libraries and a general purpose scientific
computing framework for LuaJIT
- a work in progress paper (to be published in a scientific journal)
on black box frequentist and Bayesian inference based on LuaJIT

I do not feel qualified to work or comment on the LuaJIT code
implementation right now.
However I am more than willing to contribute and give a helping hand
if a relevant role can be found, so please count me in as well.
After all you mention that a group of people with different
responsibilities would be best.

I do not know to what extent it is relevant, but I am working on
automating (via my server instance) the building and distribution of
LuaJIT binaries to avoid falling behind the latest developments.
The same holds for the tracked Lua/LuaJIT modules.
I also had a number of thoughts on how a LuaJIT-centred ecosystem
could be organised.

More broadly discussing about the future of LuaJIT, it is unclear to
me how much human capital is available right now on the development
side. By that I am thinking of people able to code non-trivial
features like the major ones mentioned on the 3.0 / 2.1 roadmaps and
the WiKi open sponsorship webpage (hyperblock scheduling, new gc,
intrinsics and vectorised operations, ...).

Thus, if you can find the time, I most definitely second the
suggestion to add code documentation and explanations of key design
decisions. Maybe a guide similar in spirit to your previous "Lua -
Recommended reading order" [1] could help as well.
This should lower the barrier of entry to new and existing developers
willing to contribute.

One final note, I understand that your 'moving on' includes sponsored
work, is that correct?

Again, thank you very much for all the great work that you have
committed to LuaJIT, it has been really appreciated.
All the bests with your future plans!



Other related posts: