-
Notifications
You must be signed in to change notification settings - Fork 30
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
"Source code is not yet up to date"? #153
Comments
(Following) It seems this code is now closed proprietary source, although they still advertise: "free and open platform." |
For the record, the latest libre/open source release is the v2.1.6 |
@Telenav @openstreetcam This is important, the only reason I was using and advertising OpenStreetCam over Mapillary was that the apps and the website where libre. It's weird to require users to use closed tools to work, create and collect libre/open data. |
So we close this issue on closedstreetcam? |
I asked them to clearify the situation via E-Mail and Twitter. |
The Android repo is indeed way behind development, same for openstreetcam.org. Others like upload-scripts and josm-plugin are doing better but still not great. We had to focus lately on some fundamental tech aspects on the platform and maintaining the open source part got deprioritized in the end. In the coming weeks we’ll have code updates on this repo and others, we don’t have any intention of keeping the platform closed. Sorry for not being as active here as we should've. |
Let's keep it open until actual code update. |
Thanks for the update with good news. |
What's the problem to |
https://github.com/openstreetcam/android/issues/153#issuecomment-522945583 --- @Telenav replies that it's still opensource. |
Clean up / small refactoring for external SDK usage, API keys etc. Nothing major but with summer holidays and a small team I can't promise something very very fast. But point well taken. Project's clearly not dead as we update the app on Google Play quite regularly, it's the Github part we have to do a better job at.. |
I don't use Google Play Store. So that means the latest is still 2.4.0, a year old. Did any improvements get made in the last year? |
Going on 2 years since last update, this sounds hollow. Sorry for not being active with my Waylens camera (proprietary) or android app. |
@ec1oud the 2.9.1 .apk is in releases now: https://github.com/openstreetcam/android/releases |
You published the 2.9.1 apk with old source code and nothing is happening in the repo? Why do you care so little about open source, that not even a yearly commit is possible? EDIT: I have to apologize. I didn't find the new 2.9.1 branch. Sorry! |
Check the Thank you for updating the source code! |
Hello, have there been updates? I would really like to have OpenStreetCam on F-Droid (#113). |
@zekooooo 3.0.1 is on play store; only 2.9.1 is on github. It probably won't ever make it to f-droid. |
v3.0.1 source code seems to have been released not in the repo but in the release page as a source code archive. |
No, this is the very old 2.1.6 code (end of 2017). |
Ho damn, you are right :( Yesterday, I just recommended OpenStreetCam at a mapping party just because I though it was libre again T_T |
Version 3.1.6 just released and it's not libre/open source. Latest libre/open source one (2.1.6) has version code 86. So by using Aurora Store or Yalp Store it's possible to get it. (menu => manual download => input the version code) Hopefully version 2.1.6 will still work. |
On http://blog.improveosm.org/en/2019/12/openstreetcam-and-improveosm-are-moving-to-grab/ (Dec 2019 about ImproveOSM and OpenStreetCam):
So Open Source, but with a minor defect: the code is missing. |
Then is not Open Source. The Open Source definition that the software, itself, must be Free Software by design --> https://opensource.org/osd |
You are not the only one... |
Damn I almost felt for the trap. Just discovered "Open"StreetCam, but it's closed source. 😠 Sad world we live in. |
@Extarys, sad yes but the license until 12 Dec 2019 was GNU LESSER GENERAL PUBLIC LICENSE then changed to MIT License. GNU LESSER GENERAL PUBLIC LICENSE, valid until 3.0.0 at least states: So it is not supposed to be closed code at least until 3.0.0. For 3.0.1 and following versions, as it is using a GNU LESSER GENERAL PUBLIC LICENSE for its base, IMHO - but I'm not a jurist - the derivative work like 3.1.6 should comply to the previous statement. |
@Bibi56 What I meant was the current source code in the repo is old (v2.9.1) compared to the current APK. So the latest version is not open source no matter what the license says right now because there is no source. They bought this at the end of last year, so maybe* they'll catch up soon and continue their Open-Source works 🤞 |
@chip-grab do you have an estimate for a release? we are waiting for 3 years... |
Happy to hear this @chip especially in the light of Facebook buying Mapillary.
Sent with [ProtonMail](https://protonmail.com) Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
…On Friday, September 4, 2020 8:05 PM, CHip ***@***.***> wrote:
***@***.***(https://github.com/Extarys), I have an insight on this that ***@***.***(https://github.com/grab) will continue open source work. 😉
Updates to come soon. Stay tunned. 🤞
—
You are receiving this because you were mentioned.
Reply to this email directly, [view it on GitHub](https://github.com/openstreetcam/android/issues/153#issuecomment-687300847), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AIXJIPVWDBYZKV2RSEBOUPLSEET7JANCNFSM4IJDCDSA).
|
@chip-grab has there been any progress on making the app open-source? If I read it correctly, build.gradle still requires proprietary components in |
The source code of the repo and the archive from the releases is still the one of version 2.1.6 (version code 86). So version 4.0 is still not libre/open source |
It is version 4.0, version code 118: |
Bump for progress. |
Bumping again. I'm happy to be of assistance, when I have time and spare executive function (it varies when you have autism). I could help get this release building, too, and try to get in contact with the devs again, but I can't do these things by myself in any reasonable timescale. Shall we start coordinating something? |
Hamish, I've just opened a new issue, asking for the code and source to be uploaded, as this is a requirement of the OS licence, and will enable people to fork, should they want to review or modify the code. |
I received an update, the other day; ver 5.5.1 (150), but I can't see this release on GitHub. Could someone else check, in case I'm being paranoid about open source licenses being contravened. Thanks, Chris |
Hi, this app is not FLOSS anymore sadly. |
Any news on this? This is in contravention of the license, so we should be able to do something about it. |
Hamish, I think you're right, but the only way this will get resolved is by contributors moving to another platform, noting Mapillary is owned by FB/ Meta. I proposed a way to address these concerns, in a different ticket. KV are clearly not interested in a 2-way dialogue with contributers. chris_debian |
Unfortunately you're probably right. Unless the server side code is open, this might be a bit of a lost cause. |
Hmm, the code was LGPL3 until 2019, when 502b900 changed it to MIT license (which is not copyleft, thus cannot guarantee that the code will stay open) ?! Have all people who ever contributed to the code agreed to this license change? If not, this license change is illegal. Call to people: if you ever contributed to code of what is now Kartaview, have not given up / transfered you copyright, and disagree with this license change, please comment here or contact me. |
@mnalis you can see contributors at https://github.com/kartaview/android/graphs/contributors. People that contributed before the license change are @james2432, @vdechenaux and @Xevib. |
@davidak thanks, that indeed lists some of them (and if any of them owns copyright on part of the code and didn't authorize license change I hope they will reply here), however:
|
Why is there no source code published here since December 2017?
The text was updated successfully, but these errors were encountered: