Creating a fork of LuaJ #4
Assignees
open-autonomous-connection
Clear assignees
open-autonomous-connection
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: open-autonomous-connection/luaj#4
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Looks like the original LuaJ project is not longer active. As there is some interest in contributing to the project (including myself to some extend), I think the right thing to do is to create a fork of the original project. The license allows us to use the original code and extend/modify it, but in my opinion we should change the name of the project. Of course we should keep the original files copyright notices and clearly state that this is a fork of LuaJ, but I don't think it is a good idea to keep the original name as (as far I understood) this project is not related to the original authors in any way. Also that will allow us to publish new versions to Maven.
It was suggested to use jitpack.io, but in my opinion, while technically it might work, it is not good idea. We should not publish our code pretending to be somebody else - I don't think a message is enough. A new name is much better as it clearly shows the two projects are not the same.
Well, I take my words back. I was able to contact the original authors. As they are still interested in LuaJ and it's not abandoned, I don't think there is a need of a fork - it's better to help the original authors.
That's why I'll close the issue.
Wow. That's great news.
As I was not able to contact the original authors... would you be so kind and ask them if they are interrested in using the luaj Github organization which I have created.
Looking back at it now it was probable a dumb idea to create the Github orga/repo "luaj/luaj", because it sounds kinda official (which it isn't at this point). I would rather hand over the owndership to the original authors and be done with it... ;-)
The first sight I saw this, I also think this is the official project...
But only few stars less than 100
The original repo is still CVS, which SourceForge now only supports in read-only mode.
I have fetched the missing two commits from the original CVS repo and added them.
To make sure that the original commit history was left untouched I had to rebase my own changes onto the original commits, though. This renders all Pull requests to this repo useless, I am afraid. -- they will need to be re-based onto the new HEAD of the master branch...