Thank you for your amazing work, Mike!
Appearance of LuaJIT (especially FFI) was epoch-making for me, it
completely changed my opinion about applicant fields of dynamic languages.
I've been used LuaJIT about 6 years in game industry mainly for building
performant socket server which uses system call directly from LuaJIT VM.
I feel such kind of usage of LuaJIT has high potential, and want to see the
future of it.
I would be happy if I contribute to further improvement of the field of
LuaJIT FFI, through I'm not quite sure that there is something I can do.
2015年7月31日(金) 22:51 Mike Pall <mike-1507@xxxxxxxxxx>:
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.
I would like to see LuaJIT to be well maintained and wisely evolved
into the future. I want to give it in trusted hands. A group of people
with different responsibilities would be best.
For this, the project needs to be set up differently. And, at least in
the beginning, it needs some manpower to organize people, to set up
repos, bug trackers, accounts, etc.
I'm happy to announce that CloudFlare has offered to take over
stewardship for the LuaJIT project. This will certainly aid in making
it a smooth transition.
CloudFlare has a vested interest in the future of LuaJIT: they're one
of the biggest users of LuaJIT and they've sponsored valuable LuaJIT
features in the past. I fully trust CloudFlare to fulfill this
stewardship while preserving the goals and the spirit of LuaJIT.
Please note that stewardship does not mean ownership. The maintainers
and contributors decide. A stewardship is mainly a commitment to help
organize a group of developers. And to solve some issues that may be
difficult for individual contributors.
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!
All of that said: don't worry, LuaJIT is in good shape and it's NOT
going away! It's open source, it has a great community. It just needs
a new management.
Also, I'm still around, I'll answer technical questions, and I'll
promise to take a look at the really tricky bug reports. But I want to
reduce my engagement over time.
I think it should be possible for the transition phase to happen
during the next 1 or 2 months.
That's also the time frame when I'll move LuaJIT 2.1 (as-is) into beta
and cut the 2.1.0 release. Maybe a few things are missing, but 2.1 has
valuable new features and it's stable. There will be a 2.2, 2.3, etc.
for new features.
I'd be really delighted if the discussion here on the mailing list
would focus on the future of LuaJIT. Let's leave the drama and
speculation to the social networks -- they'll have a busy weekend.