The 'polite' thing to do is to use a different name and clearly credit on your documentation; stating that it's based on Lua but not 'official' Lua. AFAIK, the licence doesn't legally require even that; but it's what you're expected to do.
Remo.D mentioned the Idle case; personally, i don't like the attitude of "this fixes the problems with Lua" that i kinda read on Idle's webpage and his messages to the Lua list; but it's widely recognized that he's doing the right thing: a different name and openly showing credits.
If you want to be really popular in the Lua community; you could try to release your code not as a fork of Lua; but as a set of patches to the core. It's more work, I'm sure; but it has a much higher chance of being used by more people; and maybe (big maybe) some ideas could eventually be integrated in the core.
发布评论
评论（2）
我的第一个建议是向 Lua 人员发送一封电子邮件。我99.9%确信你不会有任何问题。
现在我想起来了，另一个人创建了一种名为“Idle”的语言，如果我没记错的话，它很大程度上基于 Lua。
只要你正确地表现出应有的功劳并公平地表现出与 Lua 的差异，我相信你会没事的。
My first suggestion would be to send an email to the Lua folks. I'm 99,9% sure you won't have any problem.
Now that I think about it, another guy create a language called "Idle" which, if I remember well, is heavily based on Lua.
As long as you properly show the due credits and fairly represent the differences with Lua, I'm sure you'll be fine.
“礼貌”的做法是使用不同的名称并在您的文件中明确注明；声明它基于 Lua，但不是“官方”Lua。 AFAIK，该许可证在法律上甚至没有要求；但这是你应该做的。
Remo.D 提到了 Idle 情况；就我个人而言，我不喜欢我在 Idle 的网页上看到的“这解决了 Lua 的问题”以及他给 Lua 列表的消息的态度；但人们普遍认为他做的是正确的事：使用不同的名字并公开展示制作人员名单。
如果你想在Lua社区真正受欢迎；你可以尝试发布你的代码而不是作为 Lua 的分支；而是作为一组核心补丁。我确信这需要更多的工作；但它被更多人使用的机会要高得多；也许（也许很大）一些想法最终可以集成到核心中。
The 'polite' thing to do is to use a different name and clearly credit on your documentation; stating that it's based on Lua but not 'official' Lua. AFAIK, the licence doesn't legally require even that; but it's what you're expected to do.
Remo.D mentioned the Idle case; personally, i don't like the attitude of "this fixes the problems with Lua" that i kinda read on Idle's webpage and his messages to the Lua list; but it's widely recognized that he's doing the right thing: a different name and openly showing credits.
If you want to be really popular in the Lua community; you could try to release your code not as a fork of Lua; but as a set of patches to the core. It's more work, I'm sure; but it has a much higher chance of being used by more people; and maybe (big maybe) some ideas could eventually be integrated in the core.