-
Notifications
You must be signed in to change notification settings - Fork 2
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
Not Available in AppStore #1
Comments
Hi, Unfortunately I stopped paying the Apple Developer Program some years ago, so indeed this app is now not available on the AppStore. You can still build it yourself though. Kind regards, |
Sidi, I've done some enhancements locally in my own fork of this repo that increase app usability. Also, I'm going to devote some portion of my spare time to this app in the future. As I understood you have no plans to republishing the app to App Store. If it is indeed the case, could I kindly ask you to add the LICENSE file so that anyone is legally allowed to do derivative work? This will allow me to develop my own fork. Including, probably, publishing the app to App Store. Looking forward to hearing from you. Nikolay. |
Hi Nikolay, Of course! It's really exciting to see someone's going to contribute to this (nearly abandoned) project and make it come to life again. Regarding licensing, I think I would go for GPLv2, please let me know if you have other thought on this. Kind regards, |
While I'm ok with GPLV2, I should ask whether GPLV3 works in this case? |
If I understood correctly the difference is minor, so yeah it would also be OK. I'm using GPLv2 mainly because FlightGear and most of the projects related to it are licensed with GPLv2, so I prefer v2 more but can do v3 if you insist. |
Hmm. In this case we may want to go with GPLV2 because V3 is not compatible with V2. |
Hello! I'm new to FlightGear and just came across this application. Sadly, I didn't manage to find it in the AppStore. Is there any chance of you putting it back? Or should I build it myself?
The text was updated successfully, but these errors were encountered: