> Absolutely no concrete assurance (from CF officially) that the LuaJIT project will be developed openly.
The project was never completely developed in the open, with the test suite and the interaction between sponsors and Mike being private.
> On top of all that, the murky posts on the actual list indicate no significant progress has been made on figuring out a new direction for the project, and little to no effort has been made to do more than announce to the community what's (allegedly) going on.
The progress is indeed slow, but it is not surprising given the short delay since the announcement and the complexity of the code.
LuaJIT has currently a bus factor of one. Some people are familiar with some aspects of the code but there are no guaranties that they have the time to take over the project.
From what I gather, ATM, Cloudflare doesn't have employees that could step up and replace Mike, which means it would be foolish of them to burn the bridges with the community.
From what I gather, ATM, Cloudflare doesn't have employees that could step up and replace Mike, which means it would be foolish of them to burn the bridges with the community.
This is true. There is not obvious replacement for Mike at CloudFlare or elsewhere. I've been hoping that discussion on the mailing list would lead to someone emerging or a consensus.
Also, Mike has said he wants the transition to be 'one to two months' and I have not personally been involved with the LuaJIT community so stepping as lightly as possible while trying to do what Mike wanted (which was have CloudFlare take the load off his shoulders and help the transition).
I very much doubt that you and I are going to come to agreement on this. Mike's been involved on the mailing list. Perhaps you should address this directly with him.
Absolutely no concrete assurance (from CF officially) that the LuaJIT project will be developed openly.
