search

robinpaulson / SimpleRT

Simple Reverse Tethering utility for Android
GNU General Public License v3.0
906 stars 101 forks source link

Future of this project : forks #58

Open tuxayo opened 3 years ago

tuxayo commented 3 years ago

Hi, this is to document forks that have or might have additional commits.

https://github.com/iteratec/SimpleRT https://github.com/vejed/SimpleRT https://github.com/eugene-sevostianov-sc/SimpleRT https://github.com/xobyx/SimpleRT https://github.com/vejed/SimpleRT

robinpaulson commented 3 years ago

After a bit of research, it appears this fork has had the most effort put into it: https://github.com/CandySunPlus/SimpleRT I have contacted the developer, if he responds we will get it into the F-Droid repos and continue development on it.

softwarecreations commented 3 years ago

https://techgaun.github.io/active-forks/index.html#https://github.com/vvviperrr/SimpleRT

vvviperrr commented 3 years ago

@robinpaulson hi. if u have any interest of maintaining this project - feel free to contact me (mail or telegram, nickname the same). i can transit ownership of this repo to u.

robinpaulson commented 3 years ago

Hi, I can't find your telegram username; I'm very new to tg. No matter, we can talk here. Yes, I am interested in taking over the repo, to continue the development. How would that go, are there any conditions you have? Of course, I would keep it as free software, GPL3. No ads, no other nasties incompatible morally or legally with free software.

robinpaulson commented 3 years ago

Thanks guys, these are interesting forks. Are there any particular commits you would like adding to this repo?

softwarecreations commented 3 years ago

I haven't looked through the forks yet. Features are nice, as long as it doesn't break the core functionality of actually providing internet access. RT never worked for me at all, I tried on a few devices. The project was just a wee bit broken and I think the F-Droid version was always outdated or whatever.

I'm sure if it can work, and is user-friendly, it'll gain users. You could even setup a patreon at some point. The first step is to get a functional version on f-droid ASAP then contact hackernews or whatever to get people using it. Then bells and whistles :) UX is important. It can't be some broken looking app that doesn't explain anything etc that assumes the user is an expert on everything and also expert at finding hidden buttons etc. It doesn't need to be pretty. Just simple enough that your mom can use it.

robinpaulson commented 3 years ago

Thanks, these are all good points. I'm not too concerned about extra features either, this is a classic UNIX cli tool, with one simple thing to do. Anything else is feature-creep.

That's interesting it didn't work for you, do you know why? Are there any particular issues on here which cover the brokenness?

softwarecreations commented 3 years ago

Thanks @robinpaulson it's been years since I tried it so if it seems to be working for you, best is to get it on F-Droid and we can all test it out etc. I'll be happy to give feedback :) Keen to see this get a lot of users with some articles on Hackernews and some Android blogs etc.

softwarecreations commented 3 years ago

Also, once we get to that point, we can also contact the maintainers of all the forks, which should inspire them to contribute to the project that's on F-Droid. Will be great!

robinpaulson commented 3 years ago

Yes to collecting ideas from other forks, I agree.

robinpaulson commented 2 years ago

@softwarecreations The new version, 1.1.1 landed in the f-droid tubes a couple of days ago. I'd be interested to know what you think.

CandySunPlus commented 2 years ago

After a bit of research, it appears this fork has had the most effort put into it: https://github.com/CandySunPlus/SimpleRT I have contacted the developer, if he responds we will get it into the F-Droid repos and continue development on it.

what can I do for you？

robinpaulson commented 2 years ago

@CandySunPlus Hi, my initial contact was mostly speculative. Thinking on, it feels potentially redundant (although this may not be a bad thing) to continue two slightly different versions of the code. What do you think, how might we progress? We could merge the two, taking the best bits of both, then continue working on a single code base? Or continue as-is, or something else?