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

"Source code is not yet up to date"? #153

Open
vpzomtrrfrt opened this issue Aug 3, 2019 · 45 comments
Open

"Source code is not yet up to date"? #153

vpzomtrrfrt opened this issue Aug 3, 2019 · 45 comments

Comments

@vpzomtrrfrt
Copy link

Why is there no source code published here since December 2017?

@githubber42
Copy link

(Following) It seems this code is now closed proprietary source, although they still advertise: "free and open platform."

@tuxayo
Copy link

tuxayo commented Aug 19, 2019

For the record, the latest libre/open source release is the v2.1.6
https://github.com/openstreetcam/android/tree/2.1.6

@tuxayo
Copy link

tuxayo commented Aug 19, 2019

@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.

@PanderMusubi
Copy link

So we close this issue on closedstreetcam?

@davidak
Copy link

davidak commented Aug 19, 2019

I asked them to clearify the situation via E-Mail and Twitter.

@alexandrui-telenav
Copy link
Contributor

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.

@alexandrui-telenav
Copy link
Contributor

alexandrui-telenav commented Aug 20, 2019

So we close this issue on closedstreetcam?

Let's keep it open until actual code update.

@PanderMusubi
Copy link

Thanks for the update with good news.

@davidak
Copy link

davidak commented Aug 20, 2019

maintaining the open source part got deprioritized in the end.

What's the problem to git push at the end of the workday? Then we see at least that the project is not dead.

@532910
Copy link

532910 commented Aug 20, 2019

https://github.com/openstreetcam/android/issues/153#issuecomment-522945583 --- @Telenav replies that it's still opensource.

@alexandrui-telenav
Copy link
Contributor

maintaining the open source part got deprioritized in the end.

What's the problem to git push at the end of the workday? Then we see at least that the project is not dead.

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..

@ec1oud
Copy link

ec1oud commented Aug 31, 2019

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?

@githubber42
Copy link

Sorry for not being as active here as we should've.

Going on 2 years since last update, this sounds hollow. Sorry for not being active with my Waylens camera (proprietary) or android app.

@mds08011
Copy link

mds08011 commented Oct 2, 2019

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?

@ec1oud the 2.9.1 .apk is in releases now: https://github.com/openstreetcam/android/releases

@camelCaseNick
Copy link

camelCaseNick commented Nov 15, 2019

maintaining the open source part got deprioritized in the end.

What's the problem to git push at the end of the workday? Then we see at least that the project is not dead.

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..

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!

@siliconninja
Copy link

siliconninja commented Nov 21, 2019

Check the release_2.9.1_github branch. I see some updated source code there, the new branch just wasn't announced in this issue. It's not in the default master branch.

Thank you for updating the source code!

@zekooooo
Copy link

zekooooo commented Jan 6, 2020

Hello, have there been updates? I would really like to have OpenStreetCam on F-Droid (#113).

@githubber42
Copy link

@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.

@tuxayo
Copy link

tuxayo commented Feb 20, 2020

v3.0.1 source code seems to have been released not in the repo but in the release page as a source code archive.

@Zahnstocher
Copy link

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).
It is not even the latest available 2.9.1 code:
https://github.com/openstreetcam/android/tree/release_2.9.1_github

@tuxayo
Copy link

tuxayo commented Feb 25, 2020

build.grade => appVersionName : "2.1.6",

Ho damn, you are right :(

Yesterday, I just recommended OpenStreetCam at a mapping party just because I though it was libre again T_T

@tuxayo
Copy link

tuxayo commented Jun 11, 2020

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.

@Bibi56
Copy link

Bibi56 commented Jun 19, 2020

On http://blog.improveosm.org/en/2019/12/openstreetcam-and-improveosm-are-moving-to-grab/ (Dec 2019 about ImproveOSM and OpenStreetCam):

Open Source: Good news, the code license is changing from LGPL to the more permissive MIT license. The imagery license will remain the same, CC BY-SA version 4.

So Open Source, but with a minor defect: the code is missing.

@EchedelleLR
Copy link

Then is not Open Source. The Open Source definition that the software, itself, must be Free Software by design --> https://opensource.org/osd

@EchedelleLR
Copy link

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.

You are not the only one...

@Extarys
Copy link

Extarys commented Sep 3, 2020

Damn I almost felt for the trap. Just discovered "Open"StreetCam, but it's closed source. 😠

Sad world we live in.

@Bibi56
Copy link

Bibi56 commented Sep 3, 2020

@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:
The "Minimal Corresponding Source" for a Combined Work means the
Corresponding Source for the Combined Work, excluding any source code
for portions of the Combined Work that, considered in isolation, are
based on the Application, and not on the Linked Version.

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.
So at least we are missing the 3.0.0 source code here.

@Extarys
Copy link

Extarys commented Sep 4, 2020

@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.
Also, I discovered this yesterday so I didn't have time to investigate the "new" company behind this and make my mind about their reputation and if they should be trusted.

They bought this at the end of last year, so maybe* they'll catch up soon and continue their Open-Source works 🤞

@chip-grab
Copy link
Contributor

@Extarys, I have an insight on this that @grab will continue open source work. 😉
Updates to come soon. Stay tunned. 🤞

@davidak
Copy link

davidak commented Sep 4, 2020

@chip-grab do you have an estimate for a release? we are waiting for 3 years...

@zekooooo
Copy link

zekooooo commented Sep 6, 2020 via email

@mnalis
Copy link

mnalis commented Jan 19, 2021

@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 4.0 (quick glance)?

@tuxayo
Copy link

tuxayo commented Feb 17, 2021

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

@Zahnstocher
Copy link

Zahnstocher commented Feb 17, 2021

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:
https://github.com/kartaview/android/blob/master/build.gradle#L134
It was released on 2 Dec 2020:
ae5b56b
I tried to build it a few days later, but I failed.
Some things in the code are not defined and it heavily depends on third party libs, some are closed source, some are not available in the repositories and I had to find them myself.
Then I found out, that I need API key for Mapbox, so I registered there.
For Google (analytics or something like that), I created a dummy API key file.
Then I found out, that I need Skobbler API keys, which I don't have. Why is Skobbler dependency still there, I thought it was replaced by the new Mapbox dependency...
After several hours I gave up, it was just a waste of time. 😢
I think this open source project is completely broken.
I wonder if the developer who committed this code ever tried to build it. 😕

@hamishmb
Copy link

hamishmb commented Jul 4, 2022

Bump for progress.

@hamishmb
Copy link

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?

@chrisdebian
Copy link

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.

@chrisdebian
Copy link

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
chris_debian

@EchedelleLR
Copy link

Hi, this app is not FLOSS anymore sadly.

@hamishmb
Copy link

hamishmb commented Apr 3, 2023

Any news on this? This is in contravention of the license, so we should be able to do something about it.

@chrisdebian
Copy link

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

@hamishmb
Copy link

hamishmb commented Apr 4, 2023

Unfortunately you're probably right. Unless the server side code is open, this might be a bit of a lost cause.

@mnalis
Copy link

mnalis commented Aug 21, 2023

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.

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.

@davidak
Copy link

davidak commented Aug 23, 2023

@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.

@mnalis
Copy link

mnalis commented Aug 24, 2023

@mnalis you can see contributors at https://github.com/kartaview/android/graphs/contributors.

@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:

  • there are even more contributors produced by git log --before '2019-12-12' | grep '^Author:' | sort -u
  • I'm not sure if git commit list all contributors (depending on contribution, i.e. if someone sent patch by e-mail etc.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests