Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is the project still being maintained? #443

Open
marek22k opened this issue Nov 30, 2023 · 17 comments
Open

Is the project still being maintained? #443

marek22k opened this issue Nov 30, 2023 · 17 comments
Labels
question Question from the users

Comments

@marek22k
Copy link
Contributor

Hello,

There are some open issues and pull requests. Furthermore, it has been over a year since the last commit. Is the project still being actively maintained?

@FisHlaBsoMAN
Copy link

Screenshot_20231205_032527
Screenshot_20231205_032533
Is the developer still living?

@FisHlaBsoMAN
Copy link

image
This developer is being forcibly kept by Google. Need a fork!

@ROBERT-MCDOWELL
Copy link

I just hope he was not swallowed by the corpofascists!

@FisHlaBsoMAN
Copy link

@gsliepen, if you are still alive, archive the repository or write in readme.txt that you can no longer develop it! If you are captured, blink twice.

@gsliepen
Copy link
Owner

gsliepen commented Dec 5, 2023

Rumors of my demise have been greatly exaggerated. I currently have very little time to work on it. However, nothing prevents people from sending patches, pull requests and/or forking the project. I think that would be more helpful than archiving the repository.

@lancethepants
Copy link

A ton has changed since pre18, including moving to meson. Enough I would think worthy of pre19.

@ROBERT-MCDOWELL
Copy link

@gsliepen glad to seen you again! but what about the pull requests waiting since a year?

@fangfufu
Copy link
Collaborator

fangfufu commented Dec 6, 2023

Perhaps I could start maintaining a staging fork with all the patches that people think that are worth merging? Once I collect enough stuff and done sufficient amount of testing, we could consider merging in the main repository?

I don't have the time or skills to do proper development on this project. I definitely love this project though.

If this is something people think might be worthwhile, do let me know. I don't promise anything.

@ROBERT-MCDOWELL
Copy link

@fangfufu better to wait @gsliepen answer about the waiting PR and the future of how to continue to maintain tinc.

@rzr
Copy link

rzr commented Dec 14, 2023

Or may you consider community cooperative maintenance in @abandonware org ?

https://purl.org/rzr/abandonware

@ROBERT-MCDOWELL
Copy link

@rzr abandonware is a good idea, but maybe the name makes confusion since if the software is alive again so it's not considered as abandoned anymore ;). the biggest issue would be where to host and how. IPFS with IPNS (like archive.org) could be a good alternative in case of the source code is abandoned multiple time and if github disappears too or change their rules. the most complex would be to who admin permissions will be given and how long.

@rzr
Copy link

rzr commented Dec 15, 2023

ok good to know that project is not abandoned anymore (btw there is also @adoptware for maintained @abandonware projects)

regarding preservation purpose may this project answer to the need:

https://www.softwareheritage.org/

it's not decentralized though

@josch700
Copy link

josch700 commented Jan 3, 2024

I really think tinc would have a place in the current state of the industry though.
There is a lot of craze about SD-WAN but all those solutions have one Problem, they have a central controller. tinc is pretty alone in this regard and I think it is much easier to use than plain wireshark. So I would love to somehow reignite the spark in tinc because it has great potential IMHO.
Just a quick disclaimer though, I'm not a dev just a admin who really loves tinc and would like to see it being continued. So I can't help with the coding stuff but I would be glad to help with other aspects.

@splitice
Copy link
Contributor

splitice commented Mar 3, 2024

tinc is still great, just really lacking in time from leadership.

If someone wants to step up I'd be happy to send my PRs in your direction.

@gsliepen
Copy link
Owner

gsliepen commented Mar 3, 2024

I know there are lots of people liking tinc, and indeed it still has unique features that I don't see in other VPN solutions. But development is very slow, and not just because I myself have little time to spend on it; the last year and a half no other developers have spent much time on it either. And while I do get the occasional pull request, it usually it is just to fix an issue, or to add a feature that one particular person wants, there is no one doing general development anymore. In 2022, @hg did a lot of work, and the project needs someone like them to move forward.

I'll keep looking at pull requests, but I do have some standards, and I also am a bit wary about new features that sound great to the person creating them, but might break other people's setups. If anyone feels that this is too restrictive, and wants to have more control over where tinc is heading, then by all means maintain your own fork, and if that goes demonstrably well we can discuss merging that back into the official repository and/or hand over project ownership.

@josch700
Copy link

josch700 commented Mar 3, 2024

I think besides the invite feature and maybe performance improvements (if possible) no new features are really necessary.
Maybe work together with a bigger org that would benefit from something like tinc? Proxmox comes to mind, they are working on SDN features as far as I know

@fangfufu
Copy link
Collaborator

fangfufu commented Mar 4, 2024

no one doing general development anymore

I guess Tinc works well enough so people aren't too worried?

@gsliepen gsliepen added the question Question from the users label Mar 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Question from the users
Projects
None yet
Development

No branches or pull requests

9 participants