Under which license is this project?

[Perflyst]

I don't see any license on this project. The repo you forked does not have one either but you did a lot modifications so I think it is time to add an open source license.

[BaronKiko]

The licence is in the readme, it's not technical or anything but it covers enough and it's inherited from the original project owner so I'm morally obliged to keep it.
I will leave this open as it belongs in its own licence file which can be done easily for next release

[Perflyst]

This is not a clear license. I would ask you to take a look at MIT license.
https://choosealicense.com/licenses/mit/

[BaronKiko]

Sure, will have a look when I'm updating it.

[basxto]

MIT and Apache don’t require to open source derivative work, GPL does.

including a link to this repo. You have to send us a link to the modified version if it is ever public.

That is something you would need to add to all of them. I don’t know how that work, though.

If you want people to send you links, you should should provide an e-mail address or something.
Technically those 22 people, who forked your project on github, needed to send you and parrotgeek1 a link to their fork.

It’s also not allowed to add your app to https://apt.izzysoft.de/fdroid/index/info, since it redistributes binary apps and links to the repos.
Adding the app to f-droid would make it mandatory to change the code, release it, link to your repo and send you a link to it.
If there were a fork of a fork of a fork of a fork in future, a new fork would need to send a link to all 5 of them and also link to all 5 of them.
Forks can’t change the license and the way your license is writte, the code can only be hosted on github, since each fork needs to publish apks via github releases.

Edit: If you change the license, you need the permission of all contributors. That might include Speeddymon in the future.

Edit2: It does not look like f-droid would accept custom licenses. https://f-droid.org/en/docs/Inclusion_How-To/

They will go to your source code repository, and look for copyright notices in license files, including README, to check that the proposed application is released under recognized Free Software license(s).

[BaronKiko]

That requirement is simply there so people don't make an update without letting me know leaving 2 seperate versions in the wild.
I have worked with various licences and so when it comes to it picking one it shouldn't be too hard. The requirement for emails can be dropped without too much concern.
In regards notifying changes I will let all contributors know but one of the issues of such a lax licence is that I can simply change it without breaking the old licence so it's no concern. I will notify them out of courtesy.

Besides, I don't really intend to enforce it unless absolutely required so it's mostly guidelines on being nice with the side effect of making f-droid happy.

[BaronKiko]

This has been resolved on the firetv branch (current dev) and will be moved to main very soon. The project is now using GPL3