Unmaintained

[QuantumEntangledAndy]

thirtythreeforty seems to have left the scene.

Issues are not addressed here and PRs are not merged. See my fork instead

For awhile me and thirtythreeforty worked on this fork together, however this mostly stopped some years ago with me trying to hold the fort by myself for sometime now. Although I have some write access to this repo from the time we worked together I do not have access to write to the main branch without approval from thirtythreeforty.

As a result all active development has moved to my fork. If you have issues please try that fork and open issues there. You will most likely not get a response here.

@thirtythreeforty If you are here and want to keep working on this please let me know, hope you and your family are well. If you are wanting to pass stewardship more formally please also feel free to contact me and we can arrange something.

[rsockanc]

Download links are no longer working.

[QuantumEntangledAndy]

Unmaintained means just that... in any event I opened a PR to address it #377 but I can't merge it myself.

[QuantumEntangledAndy]

You can find some build links at the bottom of this page https://github.com/thirtythreeforty/neolink/actions/runs/8641055411 but they will only work for a month or so before github delete them (you must be logged in to see them, and I do mean the bottom of the page scroll passed all the build messages)

[QuantumEntangledAndy]

Seems I can create releases (but not push to master....) so I put the binaries there https://github.com/thirtythreeforty/neolink/releases/tag/v0.4.0

[thirtythreeforty]

Hey @QuantumEntangledAndy sorry I've been incommunicado. Combination of working on other stuff and not having engineering bandwidth to devote here. I appreciate you carrying the torch.

I'll try to merge active PRs down. We can leave this issue open while we figure out what the right stewardship model looks like - granting more rights or creating a GitHub org or something else. In principle I am happy to work on this but in practice, I haven't been...

[QuantumEntangledAndy]

@thirtythreeforty My fork is quite different after all these years of development, so not sure how to handle this. The code base was rewritten a few times and now uses Tokio under the hood with async streams as well as other new features.

We could merge my code into here but I'd like to avoid the situation where I can't fix and update things because I can't merge

We could change the readme here to point to my fork and keep the development there.

We could make an org and move the code there. But we'd need to move users over to there again

[thirtythreeforty]

At this point, your fork is the maintained one, so it should end up pointing at the tip of your tree. I can't add you as Owner to this repo, and I think that's the only way you can have unfettered access...

So that leaves either changing my readme, or transferring to an org. (GitHub will redirect users from the transferred repo.) I think we can only transfer one of the repos, if that's the route we go. In your opinion would it more valuable to transfer the issues of my or your repo? (Of course you can still reference the other repo by doing things like thirtythreeforty/neolink#370: #370.) If you'd rather have a GitHub org, I can set one up and move the code into it with you as an owner.

If you'd rather just keep the development under your username, I can add a readme message redirecting to your fork. Up to you.

[QuantumEntangledAndy]

Can we update the readme to point to my fork? It would be helpful so as to not have to reply to so many issues here forwarding them to my fork