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

Please release the Android app under a free license #1124

Open
pizzamaker opened this Issue Jun 28, 2015 · 68 comments

Comments

Projects
None yet
@pizzamaker

pizzamaker commented Jun 28, 2015

The Windows Phone app is already FLOSS. It would be nice to have Mapillary in F-Droid :)

@de-vries

This comment has been minimized.

Show comment
Hide comment
@de-vries

de-vries Jun 28, 2015

It would be nice to have Mapillary in F-Droid

👍 I vote for this!

de-vries commented Jun 28, 2015

It would be nice to have Mapillary in F-Droid

👍 I vote for this!

@jesolem

This comment has been minimized.

Show comment
Hide comment
@jesolem

jesolem Jun 28, 2015

Contributor

We want this too and will get there.

Contributor

jesolem commented Jun 28, 2015

We want this too and will get there.

@domdomegg

This comment has been minimized.

Show comment
Hide comment
@domdomegg

domdomegg commented Jul 19, 2015

👍

@yogiks

This comment has been minimized.

Show comment
Hide comment
@yogiks

yogiks commented Aug 17, 2015

👍

@shlublu

This comment has been minimized.

Show comment
Hide comment
@shlublu

shlublu commented Aug 17, 2015

👍

@mnalis

This comment has been minimized.

Show comment
Hide comment
@mnalis

mnalis Sep 27, 2015

I agree conpletely, having the app in f-droid is prerequisite for me to start using it!

mnalis commented Sep 27, 2015

I agree conpletely, having the app in f-droid is prerequisite for me to start using it!

@pizzamaker

This comment has been minimized.

Show comment
Hide comment
@pizzamaker

pizzamaker Sep 27, 2015

@jesolem What's the hold-up at this point?

pizzamaker commented Sep 27, 2015

@jesolem What's the hold-up at this point?

@jesolem

This comment has been minimized.

Show comment
Hide comment
@jesolem

jesolem Oct 5, 2015

Contributor

@pizzamaker We're on it, but a LOT on the stack right now. Sorry we can't do this faster. Expect it out very soon, @peterneubauer is working on it.

Contributor

jesolem commented Oct 5, 2015

@pizzamaker We're on it, but a LOT on the stack right now. Sorry we can't do this faster. Expect it out very soon, @peterneubauer is working on it.

@pizzamaker

This comment has been minimized.

Show comment
Hide comment
@pizzamaker

pizzamaker Nov 30, 2015

@peterneubauer Any ETAs? I really want to use this application :)

pizzamaker commented Nov 30, 2015

@peterneubauer Any ETAs? I really want to use this application :)

@kozross

This comment has been minimized.

Show comment
Hide comment
@kozross

kozross Dec 9, 2015

I definitely support the code for this being released under a free software license. Google can't be allowed to rule the world, and this being free software would make a very positive start to ending that dominance.

kozross commented Dec 9, 2015

I definitely support the code for this being released under a free software license. Google can't be allowed to rule the world, and this being free software would make a very positive start to ending that dominance.

@svn-king

This comment has been minimized.

Show comment
Hide comment
@svn-king

svn-king Dec 9, 2015

this is a great idea, it's what's been keeping me from using this app

svn-king commented Dec 9, 2015

this is a great idea, it's what's been keeping me from using this app

@icantsleep

This comment has been minimized.

Show comment
Hide comment
@icantsleep

icantsleep Dec 9, 2015

This would be a very positive step forward. Is there a roadmap for this?

icantsleep commented Dec 9, 2015

This would be a very positive step forward. Is there a roadmap for this?

@rm-rf-github

This comment has been minimized.

Show comment
Hide comment
@rm-rf-github

rm-rf-github Dec 9, 2015

Really hoping this comes through

rm-rf-github commented Dec 9, 2015

Really hoping this comes through

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Jan 5, 2016

I believe this would make a wonderful contribution to free software, and may help a lot of people. Please do free this program, it would really be great to have.

ghost commented Jan 5, 2016

I believe this would make a wonderful contribution to free software, and may help a lot of people. Please do free this program, it would really be great to have.

@sstangl

This comment has been minimized.

Show comment
Hide comment
@sstangl

sstangl Jan 5, 2016

👍 Would love to use on free Cyanogen.

sstangl commented Jan 5, 2016

👍 Would love to use on free Cyanogen.

@PureTryOut

This comment has been minimized.

Show comment
Hide comment
@PureTryOut

PureTryOut Jan 14, 2016

Would love to see this on F-Droid!

PureTryOut commented Jan 14, 2016

Would love to see this on F-Droid!

@blobgo

This comment has been minimized.

Show comment
Hide comment
@blobgo

blobgo Apr 21, 2016

Your service is already about _Open_Data and so as much as possible should also be open source. Especially apps which request location data, camera permissions and internet access at the same time. (I know these permissions are needed, but you could track users in a very good way with them too)

blobgo commented Apr 21, 2016

Your service is already about _Open_Data and so as much as possible should also be open source. Especially apps which request location data, camera permissions and internet access at the same time. (I know these permissions are needed, but you could track users in a very good way with them too)

@pizzamaker

This comment has been minimized.

Show comment
Hide comment
@pizzamaker

pizzamaker Apr 21, 2016

Also related: #469

pizzamaker commented Apr 21, 2016

Also related: #469

@redsteakraw

This comment has been minimized.

Show comment
Hide comment
@redsteakraw

redsteakraw Jul 3, 2016

FYI I stopped contributing to Mapillary because of the lack of an open source client on F-Droid. I won't contribute until there is one.

redsteakraw commented Jul 3, 2016

FYI I stopped contributing to Mapillary because of the lack of an open source client on F-Droid. I won't contribute until there is one.

@pizzamaker

This comment has been minimized.

Show comment
Hide comment
@pizzamaker

pizzamaker Jul 7, 2016

@redsteakraw Same. And I've been waiting on this one for over a year.

pizzamaker commented Jul 7, 2016

@redsteakraw Same. And I've been waiting on this one for over a year.

@aablaablaa

This comment has been minimized.

Show comment
Hide comment
@aablaablaa

aablaablaa Jul 11, 2016

I want that too! if it would be foss and on F-Droid I would be contributing a lot more! :)

aablaablaa commented Jul 11, 2016

I want that too! if it would be foss and on F-Droid I would be contributing a lot more! :)

@jidanni

This comment has been minimized.

Show comment
Hide comment
@jidanni

jidanni Sep 5, 2017

I'll notify our Taiwan group and see if they are still
enthusiastic about the project.
https://m.facebook.com/groups/1138239502943100

jidanni commented Sep 5, 2017

I'll notify our Taiwan group and see if they are still
enthusiastic about the project.
https://m.facebook.com/groups/1138239502943100

@bmassot

This comment has been minimized.

Show comment
Hide comment
@bmassot

bmassot commented Sep 14, 2017

👍

@hughdavenport

This comment has been minimized.

Show comment
Hide comment
@hughdavenport

hughdavenport Sep 25, 2017

@HolgerJeromin I think it is reasonable that people question Mapillaries motives to be honest. Correct me if I'm wrong, but this issue has been open for multiple years with multiple comments from ex and current users of the application stating displeasure on the timelines given. The responses from the company never quite say that this will ever be open source or not.

When it is pointed out that this ticket is so old and the contributors don't comment, we get a comment such as #1124 (comment) from months ago. Can we have that promised update? Or have those routines put in place to avoid stale issues such as this not doing what those routines should be doing?

Going back further, with a timeline given of late May, in #1124 (comment). It's past that now by several months. Can Mapilliary outline why this target wasn't met, and what they are doing to try and meet it?

Can we simply get a decent timeline on when you will be open sourcing, that you aim very hard to stick with. I think you should agree that this issue has been going on long enough and multiple people have shown displeasure. I'm sure you understand (as your company says it prides itself in being open source), that once you open source, you can get help from developers around the world to fix some of the bugs you have, and help implement new features. I understand that this may place a burden on your developers to triage and clean up any code that is contributed, but in the long run this will help your company build efficient projects easily with a good document on contribution guidelines. If you think this won't be the case, I would be more than pleased to get any links from you of open source projects that are failing due to the fact they are open source. I can certainly find many projects that have thrived, just by searching on github.

If it is simply that you don't want to open source, click the Close button, then the displeased people can leave for good. I personally hope that this isn't the option you choose as this is a great project that should be open to the community. There is already an alternative for viewing Mapillary in a open source app OsmAnd, which I would currently suggest to all the people in this thread that are unhappy with Mapillary's open source stance to start using now.

Cheers,

Hugh

hughdavenport commented Sep 25, 2017

@HolgerJeromin I think it is reasonable that people question Mapillaries motives to be honest. Correct me if I'm wrong, but this issue has been open for multiple years with multiple comments from ex and current users of the application stating displeasure on the timelines given. The responses from the company never quite say that this will ever be open source or not.

When it is pointed out that this ticket is so old and the contributors don't comment, we get a comment such as #1124 (comment) from months ago. Can we have that promised update? Or have those routines put in place to avoid stale issues such as this not doing what those routines should be doing?

Going back further, with a timeline given of late May, in #1124 (comment). It's past that now by several months. Can Mapilliary outline why this target wasn't met, and what they are doing to try and meet it?

Can we simply get a decent timeline on when you will be open sourcing, that you aim very hard to stick with. I think you should agree that this issue has been going on long enough and multiple people have shown displeasure. I'm sure you understand (as your company says it prides itself in being open source), that once you open source, you can get help from developers around the world to fix some of the bugs you have, and help implement new features. I understand that this may place a burden on your developers to triage and clean up any code that is contributed, but in the long run this will help your company build efficient projects easily with a good document on contribution guidelines. If you think this won't be the case, I would be more than pleased to get any links from you of open source projects that are failing due to the fact they are open source. I can certainly find many projects that have thrived, just by searching on github.

If it is simply that you don't want to open source, click the Close button, then the displeased people can leave for good. I personally hope that this isn't the option you choose as this is a great project that should be open to the community. There is already an alternative for viewing Mapillary in a open source app OsmAnd, which I would currently suggest to all the people in this thread that are unhappy with Mapillary's open source stance to start using now.

Cheers,

Hugh

@katrinhumal

This comment has been minimized.

Show comment
Hide comment
@katrinhumal

katrinhumal Sep 27, 2017

Contributor

@hughdavenport Thanks for your input. We're not closing this issue (or the others) because, as you have pointed out, there are several people who are interested in this topic and want to chime in every once in a while (so they shouldn't need to open a new issue every time). Also, we couldn't even do it on the basis of "if you don't want to open source just close it" since it's not correct.

Open sourcing the Android app (since this discussion shouldn't be expanded to open sourcing all of Mapillary - there are parts that are already open source, as well as parts that likely never will be) has its pros and cons for us, and so far the weights have not been favourable according to our evaluation (which is clearly different from yours). A huge piece of this being, as said before, that we haven't managed to fix the app into a state that we're happy with. And that's also why we don't want to give any more timeframes right now. We are sorry to have promised and not delivered. Can't take that back anymore but that's just how it is.

Contributor

katrinhumal commented Sep 27, 2017

@hughdavenport Thanks for your input. We're not closing this issue (or the others) because, as you have pointed out, there are several people who are interested in this topic and want to chime in every once in a while (so they shouldn't need to open a new issue every time). Also, we couldn't even do it on the basis of "if you don't want to open source just close it" since it's not correct.

Open sourcing the Android app (since this discussion shouldn't be expanded to open sourcing all of Mapillary - there are parts that are already open source, as well as parts that likely never will be) has its pros and cons for us, and so far the weights have not been favourable according to our evaluation (which is clearly different from yours). A huge piece of this being, as said before, that we haven't managed to fix the app into a state that we're happy with. And that's also why we don't want to give any more timeframes right now. We are sorry to have promised and not delivered. Can't take that back anymore but that's just how it is.

@rugk

This comment has been minimized.

Show comment
Hide comment
@rugk

rugk Sep 27, 2017

First great that you still plan to open-source it.

has its pros and cons for us, and so far the weights have not been favourable according to our evaluation

You never mentioned any cons, except of "we need to clean up code", which is not a con, as you can still open-source and clean up the code with the help of the community. Nobody will blame you for that, you will only be blamed if you do not release the source. (I don't know what you fear here…)

we haven't managed to fix the app into a state that we're happy with

Seriously if you as the devs of the app don't like the app I would be very worried about it. If the app is really so terrible as you imply, you would need to have a bad vibe each time you release the app on Google Play or so.
But actually I don't believe your app is so bad. It just needs to compile, to work, etc. That's enough, then you can go ahead and open-source it.

So I do not need any timeframe for releasing the source, but actually the answer to the question: Why not release it right away? Just publish your git repo, create a new git repo or whatever. That's an easy step.

rugk commented Sep 27, 2017

First great that you still plan to open-source it.

has its pros and cons for us, and so far the weights have not been favourable according to our evaluation

You never mentioned any cons, except of "we need to clean up code", which is not a con, as you can still open-source and clean up the code with the help of the community. Nobody will blame you for that, you will only be blamed if you do not release the source. (I don't know what you fear here…)

we haven't managed to fix the app into a state that we're happy with

Seriously if you as the devs of the app don't like the app I would be very worried about it. If the app is really so terrible as you imply, you would need to have a bad vibe each time you release the app on Google Play or so.
But actually I don't believe your app is so bad. It just needs to compile, to work, etc. That's enough, then you can go ahead and open-source it.

So I do not need any timeframe for releasing the source, but actually the answer to the question: Why not release it right away? Just publish your git repo, create a new git repo or whatever. That's an easy step.

@Hapoofesgeli

This comment has been minimized.

Show comment
Hide comment
@Hapoofesgeli

Hapoofesgeli Sep 27, 2017

Mapillary, unlike how it tries to show itself is pretty much a completely closed ecosystem, which makes it even worse than actual closed ecosystems. The fact that they get your data, grant themselves a licence out of it, extract and sell whatever useful comes out of it while locking you away is basically parasitism, especially when they try to show it otherwise. And making the Android app open source won't simply change that fact, even worse, it will make them yet more pretentious. It's sad seeing Mapillary's footprints in many open ecosystems I tend to use, and I really recommend people thinking twice before they contribute to whomever tends to be the next Google.

Hapoofesgeli commented Sep 27, 2017

Mapillary, unlike how it tries to show itself is pretty much a completely closed ecosystem, which makes it even worse than actual closed ecosystems. The fact that they get your data, grant themselves a licence out of it, extract and sell whatever useful comes out of it while locking you away is basically parasitism, especially when they try to show it otherwise. And making the Android app open source won't simply change that fact, even worse, it will make them yet more pretentious. It's sad seeing Mapillary's footprints in many open ecosystems I tend to use, and I really recommend people thinking twice before they contribute to whomever tends to be the next Google.

@hughdavenport

This comment has been minimized.

Show comment
Hide comment
@hughdavenport

hughdavenport Sep 28, 2017

@katrinhumal ok, one question, from the very first comment of this thread

The Windows Phone app is already FLOSS. It would be nice to have Mapillary in F-Droid :)

Has the windows app been changed at all due to the devs thinking anything is wrong with it in the last 2 years?

How different is it from the android app? (I haven't actually got a windows phone so can't see)

What was your thought process years back when you decided to open source the windows one but not the android. It seems a bit backward to me lol :p

Ok, that was a few questions, but all branched off the same thing. I think you could probably agree that they are valid. I still don't see the reason for holding back code just because you don't think it is ready, and as @rugk says, it makes it sound like your app is terrible and that no-one should install it because of that. Is that really the message you want to send people?

@Hapoofesgeli how is replicant going for you ;)? Closed ecosystems are part of the technology world, and infact can help bring technology to the masses, and bring in more contributors to open source systems. Mapillary have done a stunning job IMHO, bringing images from around the world into one app. Some countries wouldn't give a flying **** whether it is open or not, more whether it exists. The fact that you use github makes me think hmm, you know github is closed? Might be running on open source rails, but the code is closed, they have TOS that limit you, but the idea that they brought around is amazing, and has improved the open source world because of it, and now there are several competitors for github that are completely open. Android, open source? at its base yes, in general no, most of the /drivers/, /additional apps/ etc bundled with any standard phone are not open source. cyanogen and forks helped that somewhat by changing the bundled apps, but the drivers are still not. What phone do you use? Are the drivers open source? Same goes for basically any linux laptop, are all your drivers open? Everything is going to have some closed aspect of it, or have performance/compatability issues if completely open until the technology comes up to standard. Sure I'm all for open source, but I think it is wrong to be completely against closed source if you want to contribute in this industry. I think you should think twice before jumping on your internet keyboard and slamming down a perfectly respectable company about their ecosystem and their product just because of your feelings about the world. I don't personally see how that remark would help this issue at all. If you don't think it is good then don't use it, don't try and make others see your bigotted opinion.

hughdavenport commented Sep 28, 2017

@katrinhumal ok, one question, from the very first comment of this thread

The Windows Phone app is already FLOSS. It would be nice to have Mapillary in F-Droid :)

Has the windows app been changed at all due to the devs thinking anything is wrong with it in the last 2 years?

How different is it from the android app? (I haven't actually got a windows phone so can't see)

What was your thought process years back when you decided to open source the windows one but not the android. It seems a bit backward to me lol :p

Ok, that was a few questions, but all branched off the same thing. I think you could probably agree that they are valid. I still don't see the reason for holding back code just because you don't think it is ready, and as @rugk says, it makes it sound like your app is terrible and that no-one should install it because of that. Is that really the message you want to send people?

@Hapoofesgeli how is replicant going for you ;)? Closed ecosystems are part of the technology world, and infact can help bring technology to the masses, and bring in more contributors to open source systems. Mapillary have done a stunning job IMHO, bringing images from around the world into one app. Some countries wouldn't give a flying **** whether it is open or not, more whether it exists. The fact that you use github makes me think hmm, you know github is closed? Might be running on open source rails, but the code is closed, they have TOS that limit you, but the idea that they brought around is amazing, and has improved the open source world because of it, and now there are several competitors for github that are completely open. Android, open source? at its base yes, in general no, most of the /drivers/, /additional apps/ etc bundled with any standard phone are not open source. cyanogen and forks helped that somewhat by changing the bundled apps, but the drivers are still not. What phone do you use? Are the drivers open source? Same goes for basically any linux laptop, are all your drivers open? Everything is going to have some closed aspect of it, or have performance/compatability issues if completely open until the technology comes up to standard. Sure I'm all for open source, but I think it is wrong to be completely against closed source if you want to contribute in this industry. I think you should think twice before jumping on your internet keyboard and slamming down a perfectly respectable company about their ecosystem and their product just because of your feelings about the world. I don't personally see how that remark would help this issue at all. If you don't think it is good then don't use it, don't try and make others see your bigotted opinion.

@Hapoofesgeli

This comment has been minimized.

Show comment
Hide comment
@Hapoofesgeli

Hapoofesgeli Sep 29, 2017

@hughdavenport It's funny how you simply interpret "closed" as if it could only mean "closed source". Github is sure closed source, and I try to avoid it as far as possible when there is not much to gain from it (the fact that I have no working repositories here should simply show that), but, there are many small and big differences between Github and Mapillary, I'll just point one simple one:

Github:

The licenses you grant to us will end when you remove Your Content from our servers

Mapillary:

Contributors grant Mapillary a worldwide, perpetual, and transferable license to use the images and other content

So yeah before you start attacking me for no reason and trying to teach me what is open source and what is not, you might want to notice some more stuff. Like the fact that Openstreetcam existed from 5 years before Mapiilary. Note that this is not to discuss why it failed and which is better etc, just to show you that unlike what you said, many open alternatives exist before the closed ones appear.

"I think it is wrong to be completely against closed source"
Although I am against it at any case, that has little to to with what I said, again you have failed to see the difference between data and source code.

And as your favourite Github allows me, I'm allowed to say whatever I like, till I can't. So how about you bring your complaints to it, rather than personally attacking me to defend something that barely has a value to you. And as "someone is wrong on the internet" discussions don't reach anywhere there is no point in continuing this any further, so good luck.

Hapoofesgeli commented Sep 29, 2017

@hughdavenport It's funny how you simply interpret "closed" as if it could only mean "closed source". Github is sure closed source, and I try to avoid it as far as possible when there is not much to gain from it (the fact that I have no working repositories here should simply show that), but, there are many small and big differences between Github and Mapillary, I'll just point one simple one:

Github:

The licenses you grant to us will end when you remove Your Content from our servers

Mapillary:

Contributors grant Mapillary a worldwide, perpetual, and transferable license to use the images and other content

So yeah before you start attacking me for no reason and trying to teach me what is open source and what is not, you might want to notice some more stuff. Like the fact that Openstreetcam existed from 5 years before Mapiilary. Note that this is not to discuss why it failed and which is better etc, just to show you that unlike what you said, many open alternatives exist before the closed ones appear.

"I think it is wrong to be completely against closed source"
Although I am against it at any case, that has little to to with what I said, again you have failed to see the difference between data and source code.

And as your favourite Github allows me, I'm allowed to say whatever I like, till I can't. So how about you bring your complaints to it, rather than personally attacking me to defend something that barely has a value to you. And as "someone is wrong on the internet" discussions don't reach anywhere there is no point in continuing this any further, so good luck.

@hughdavenport

This comment has been minimized.

Show comment
Hide comment
@hughdavenport

hughdavenport Sep 29, 2017

... You simply have had no conversations in this ticket apart from to attack mapillary, not sure how that is helpful for you or anyone actually involved. I understand that there is a closed data issue, but as there isn't really a viable alternative that isn't then I don't personally see an issue with it, and any step towards being more open helps alternatives come. Your comments simply don't help that cause.

github was merely just one example, you can bring up many examples of popular open source projects with closed data, but lets not go there.

I also understand that openstreetcam existed (was openstreetview back then), but also understand that it actually gained a lot more traction after mapillary launched, hard to know reasons why though, but may be due to people wanting more open source/data/whatever. I think we should also note that google street view was around from even before then.

As for "someone is wrong on the internet", not sure what your original comment was, but it sure seemed like you were pointing out that mapillary, and everyone on this ticket were wrong, which I found quite attacking personally as I believe that I'm working towards a better system which is more open. Might not be 100%, or even 1% open in terms of data, but I think it is still a worthy project to follow and didn't appreciate you jumping in after not having participated ever before and saying that I'm wrong to think that. I'm sorry I might have offended you in my response, understand that I didn't mean to come across as attacking but I typed that in the heat of the moment after reading your comments.

hughdavenport commented Sep 29, 2017

... You simply have had no conversations in this ticket apart from to attack mapillary, not sure how that is helpful for you or anyone actually involved. I understand that there is a closed data issue, but as there isn't really a viable alternative that isn't then I don't personally see an issue with it, and any step towards being more open helps alternatives come. Your comments simply don't help that cause.

github was merely just one example, you can bring up many examples of popular open source projects with closed data, but lets not go there.

I also understand that openstreetcam existed (was openstreetview back then), but also understand that it actually gained a lot more traction after mapillary launched, hard to know reasons why though, but may be due to people wanting more open source/data/whatever. I think we should also note that google street view was around from even before then.

As for "someone is wrong on the internet", not sure what your original comment was, but it sure seemed like you were pointing out that mapillary, and everyone on this ticket were wrong, which I found quite attacking personally as I believe that I'm working towards a better system which is more open. Might not be 100%, or even 1% open in terms of data, but I think it is still a worthy project to follow and didn't appreciate you jumping in after not having participated ever before and saying that I'm wrong to think that. I'm sorry I might have offended you in my response, understand that I didn't mean to come across as attacking but I typed that in the heat of the moment after reading your comments.

@Alessandro-Barbieri

This comment has been minimized.

Show comment
Hide comment
@Alessandro-Barbieri

Alessandro-Barbieri Sep 30, 2017

Mapillary and openstreetcam have different goals

Alessandro-Barbieri commented Sep 30, 2017

Mapillary and openstreetcam have different goals

@rugk

This comment has been minimized.

Show comment
Hide comment
@rugk

rugk Sep 30, 2017

Eh, really which? See also the issue in OpenStretCam where I asked about differences/collaboration and after a long discussion i think we know there were not much differences, from a license perspective e.g.

rugk commented Sep 30, 2017

Eh, really which? See also the issue in OpenStretCam where I asked about differences/collaboration and after a long discussion i think we know there were not much differences, from a license perspective e.g.

@Alessandro-Barbieri

This comment has been minimized.

Show comment
Hide comment
@Alessandro-Barbieri

Alessandro-Barbieri Sep 30, 2017

@rugk openstreetcam goal is to collect photos for improving openstreetmap

Alessandro-Barbieri commented Sep 30, 2017

@rugk openstreetcam goal is to collect photos for improving openstreetmap

@rugk

This comment has been minimized.

Show comment
Hide comment
@rugk

rugk Sep 30, 2017

Mapillary's goal is also to collect photos, e.g. for improving OpenStreetMap.

rugk commented Sep 30, 2017

Mapillary's goal is also to collect photos, e.g. for improving OpenStreetMap.

@HolgerJeromin

This comment has been minimized.

Show comment
Hide comment
@HolgerJeromin

HolgerJeromin Oct 1, 2017

Windows phone app was not build by mapillary staff but one single private dev. Thats why it has a different licence.

HolgerJeromin commented Oct 1, 2017

Windows phone app was not build by mapillary staff but one single private dev. Thats why it has a different licence.

@jaakkoh

This comment has been minimized.

Show comment
Hide comment
@jaakkoh

jaakkoh Oct 2, 2017

@rugk , Regarding differences between Mapillary and OpenStreetCam it's noteworthy to remember that OpenStreetCam is a project fully financed and run by Telenav, Inc., a publicly traded company (NASDAQ:TNAV) with its core business in wireless location-based services including satellite navigation, local search, automotive navigation solutions, mobile advertising, enterprise mobility and workflow automation (per Wikipedia).

With the above it is not a surprise that OpenStreetCam has been developed rather purely to capture roads. By opening the app it is (or at least was a year ago) clear from the very beginning.

I'm not saying this is a bad thing by itself. But I think it's worth keeping in mind that the owner of the project guides the development of the project heavily (as a common note) and I find this to be the case with OpenStreetCam too. I'd also note that while OpenStreetCam is positioned as and technically released to be open source (I don't know if totally fully -- are there e.g. full dumps of the imagery available?) it's just one aspect in the big picture.

jaakkoh commented Oct 2, 2017

@rugk , Regarding differences between Mapillary and OpenStreetCam it's noteworthy to remember that OpenStreetCam is a project fully financed and run by Telenav, Inc., a publicly traded company (NASDAQ:TNAV) with its core business in wireless location-based services including satellite navigation, local search, automotive navigation solutions, mobile advertising, enterprise mobility and workflow automation (per Wikipedia).

With the above it is not a surprise that OpenStreetCam has been developed rather purely to capture roads. By opening the app it is (or at least was a year ago) clear from the very beginning.

I'm not saying this is a bad thing by itself. But I think it's worth keeping in mind that the owner of the project guides the development of the project heavily (as a common note) and I find this to be the case with OpenStreetCam too. I'd also note that while OpenStreetCam is positioned as and technically released to be open source (I don't know if totally fully -- are there e.g. full dumps of the imagery available?) it's just one aspect in the big picture.

@rugk

This comment has been minimized.

Show comment
Hide comment
@rugk

rugk Oct 2, 2017

(I don't know if totally fully -- are there e.g. full dumps of the imagery available?)

Not even the app is fully open-source. So as you can see it has the same (or similar) problem as Mapillary here. It is also still not included in F-Droid:

openstreetcam/android#8

They use proprietary components…

rugk commented Oct 2, 2017

(I don't know if totally fully -- are there e.g. full dumps of the imagery available?)

Not even the app is fully open-source. So as you can see it has the same (or similar) problem as Mapillary here. It is also still not included in F-Droid:

openstreetcam/android#8

They use proprietary components…

@jaakkoh

This comment has been minimized.

Show comment
Hide comment
@jaakkoh

jaakkoh Oct 2, 2017

@rugk Hmm. I didn't know that and am slightly surprised. Then again, maybe not really.

jaakkoh commented Oct 2, 2017

@rugk Hmm. I didn't know that and am slightly surprised. Then again, maybe not really.

@ltog

This comment has been minimized.

Show comment
Hide comment
@ltog

ltog Jan 14, 2018

New year, new hope...

How is the FLOSS client coming?

ltog commented Jan 14, 2018

New year, new hope...

How is the FLOSS client coming?

@peterneubauer

This comment has been minimized.

Show comment
Hide comment
@peterneubauer

peterneubauer Jan 14, 2018

peterneubauer commented Jan 14, 2018

@rugk

This comment has been minimized.

Show comment
Hide comment
@rugk

rugk Jan 14, 2018

Sure, just don't let free software "dominate your roadmap". Who needs that anyway…

Also just to be sure: we do not (only) want a floss SDK. Open source the whole app, so we can have it on F-Droid (as for the android app), etc.

rugk commented Jan 14, 2018

Sure, just don't let free software "dominate your roadmap". Who needs that anyway…

Also just to be sure: we do not (only) want a floss SDK. Open source the whole app, so we can have it on F-Droid (as for the android app), etc.

@elgaard

This comment has been minimized.

Show comment
Hide comment
@elgaard

elgaard Mar 21, 2018

OpenStreetCam is not on F-droid. But it should be possible to fork it and make a free version.
With OpenStreetCam you can capture images (you have to disable MP4) without logging in. The images can then be accessed from a computer and uploaded to Mapillary. I made a small POC script to set the
GPS EXIF from OpenStreetCam before uploading to Mapillary. https://github.com/elgaard/OpenStreetmapTools/blob/master/setPosFromTrack.py

This way I can capture images and upload them to both OpenStreetCam and Mapillary.
Of course, it would be better to be able to do this from the android app.
It would be great to change the OpenStreetCam app to capture images, and then prompting to upload them to OpenStreetCam, Mapillary, user-defined accounts (webdav, ssh etc.)

elgaard commented Mar 21, 2018

OpenStreetCam is not on F-droid. But it should be possible to fork it and make a free version.
With OpenStreetCam you can capture images (you have to disable MP4) without logging in. The images can then be accessed from a computer and uploaded to Mapillary. I made a small POC script to set the
GPS EXIF from OpenStreetCam before uploading to Mapillary. https://github.com/elgaard/OpenStreetmapTools/blob/master/setPosFromTrack.py

This way I can capture images and upload them to both OpenStreetCam and Mapillary.
Of course, it would be better to be able to do this from the android app.
It would be great to change the OpenStreetCam app to capture images, and then prompting to upload them to OpenStreetCam, Mapillary, user-defined accounts (webdav, ssh etc.)

@alexgleason

This comment has been minimized.

Show comment
Hide comment
@alexgleason

alexgleason Apr 20, 2018

Interesting. I found Mapillary because OsmAnd~ recommends it through their app. Was surprised it's proprietary. Just wanted to echo the sentiment of others; I'd love to contribute, but I won't until the Android app is free.

It seems clear the authors are well intentioned. Still, I do not understand why improving the codebase should precede an Open Source release. I would appreciate if someone would be willing to elaborate on that.

Is it because of fear? Pride? Maybe the app contains bugs that others will see and exploit. Or maybe it could hamper your reputation because the code isn't good enough? Or maybe it will disappoint people. These feelings are common when taking a mature proprietary project and throwing its code into the wild. But I don't think breaking out the SDK will actually reduce these fears. It seems like a rationalization for avoiding this perceived risk.

Honestly, what is really the worst thing that could happen? Imagine a real play-by-play and ask yourself if it's realistic. If it's not, try again. Once you find some realistic bad outcomes, ask yourself if it's really that bad. Usually it's like a pinprick, a slight momentary pain, but with long-term benefits.

If I were you, I would really just go for it. It seems scary, but probably, everything will be just fine. There's a mantra in software development, "Fuck It, Ship It" that I really like. Like an artist who never sees their painting as truly "finished," you won't either, so you might as well push it out now, bearing the risk, before it's too late.

alexgleason commented Apr 20, 2018

Interesting. I found Mapillary because OsmAnd~ recommends it through their app. Was surprised it's proprietary. Just wanted to echo the sentiment of others; I'd love to contribute, but I won't until the Android app is free.

It seems clear the authors are well intentioned. Still, I do not understand why improving the codebase should precede an Open Source release. I would appreciate if someone would be willing to elaborate on that.

Is it because of fear? Pride? Maybe the app contains bugs that others will see and exploit. Or maybe it could hamper your reputation because the code isn't good enough? Or maybe it will disappoint people. These feelings are common when taking a mature proprietary project and throwing its code into the wild. But I don't think breaking out the SDK will actually reduce these fears. It seems like a rationalization for avoiding this perceived risk.

Honestly, what is really the worst thing that could happen? Imagine a real play-by-play and ask yourself if it's realistic. If it's not, try again. Once you find some realistic bad outcomes, ask yourself if it's really that bad. Usually it's like a pinprick, a slight momentary pain, but with long-term benefits.

If I were you, I would really just go for it. It seems scary, but probably, everything will be just fine. There's a mantra in software development, "Fuck It, Ship It" that I really like. Like an artist who never sees their painting as truly "finished," you won't either, so you might as well push it out now, bearing the risk, before it's too late.

@utack

This comment has been minimized.

Show comment
Hide comment
@utack

utack Apr 25, 2018

I went ahead and created you your own personal newsletter
Feels fair to remind you about this, since you remind me every week about what I contributed!
newsletter

utack commented Apr 25, 2018

I went ahead and created you your own personal newsletter
Feels fair to remind you about this, since you remind me every week about what I contributed!
newsletter

@HolgerJeromin

This comment has been minimized.

Show comment
Hide comment
@HolgerJeromin

HolgerJeromin May 4, 2018

Just a comment from a person who works on a closed source software for living.

Releasing the code without allowing/supporting PRs from others is useless.
And managing and coordinating work from others also needs much work.
The author of streetcomplete for example investes a big amount of time reviewing and optimizing 3rd party code instead of coding.
Typescript as a second example has many pr open without reactions of the maintainers.

features can be out of scope for mapillary but they have to deal with the "noise".

So releasing the code is no "others will improve the app for free without costs" solution.

HolgerJeromin commented May 4, 2018

Just a comment from a person who works on a closed source software for living.

Releasing the code without allowing/supporting PRs from others is useless.
And managing and coordinating work from others also needs much work.
The author of streetcomplete for example investes a big amount of time reviewing and optimizing 3rd party code instead of coding.
Typescript as a second example has many pr open without reactions of the maintainers.

features can be out of scope for mapillary but they have to deal with the "noise".

So releasing the code is no "others will improve the app for free without costs" solution.

@rugk

This comment has been minimized.

Show comment
Hide comment
@rugk

rugk May 4, 2018

  1. The already have much of the noise, because of thius issue tracker here. Most of the noise is froim issues anyway, not from PRs.
  2. They can release the code without accepting PRs. Not nice, but totally possible – and certainly better than not releasing it at all.

rugk commented May 4, 2018

  1. The already have much of the noise, because of thius issue tracker here. Most of the noise is froim issues anyway, not from PRs.
  2. They can release the code without accepting PRs. Not nice, but totally possible – and certainly better than not releasing it at all.
@mnalis

This comment has been minimized.

Show comment
Hide comment
@mnalis

mnalis May 7, 2018

@HolgerJeromin I strongly disagree that releasing the code without supporting PRs is useless. Among other things, it allows for for forks which require no time at all from Mapillary (if they don't want it). Also, it allows for code inclusion in other products (for example, OsmAnd support is one I want for example - there is no way I'll use closed source app to contribute, and taking pictures and uploading manually is way too much volunteer work)

If you ask yourself "why would they want others to release their code and not take any code from community back", then remember that Mapillary does not make a living by selling this software, but by getting volunteer produced data - and anything that gives them more exposure and more volunteers is very good thing for them. The software they code is actually just necessary evil they must spend developer hours on in order to get more quality data.

Also, PR from others could be accepted with almost no work at all into separate "community" branch. Which not only makes "open source loving" people happy and contributing, but also gives additional benefit as Mapillary itself can cherry pick stuff they want. While importing to "official" branch will of course take some work, it is waaaay less work for Mapillary then coding/fixing those issues themselves. And of course, they can decide not to import (some or all) PRs to official branch if they so choose, it is also fine.

mnalis commented May 7, 2018

@HolgerJeromin I strongly disagree that releasing the code without supporting PRs is useless. Among other things, it allows for for forks which require no time at all from Mapillary (if they don't want it). Also, it allows for code inclusion in other products (for example, OsmAnd support is one I want for example - there is no way I'll use closed source app to contribute, and taking pictures and uploading manually is way too much volunteer work)

If you ask yourself "why would they want others to release their code and not take any code from community back", then remember that Mapillary does not make a living by selling this software, but by getting volunteer produced data - and anything that gives them more exposure and more volunteers is very good thing for them. The software they code is actually just necessary evil they must spend developer hours on in order to get more quality data.

Also, PR from others could be accepted with almost no work at all into separate "community" branch. Which not only makes "open source loving" people happy and contributing, but also gives additional benefit as Mapillary itself can cherry pick stuff they want. While importing to "official" branch will of course take some work, it is waaaay less work for Mapillary then coding/fixing those issues themselves. And of course, they can decide not to import (some or all) PRs to official branch if they so choose, it is also fine.

@alex9099

This comment has been minimized.

Show comment
Hide comment
@alex9099

alex9099 May 26, 2018

It would be pretty nice to have the app open source, i only use F-Droid and compile apps from source, rarelly i touch play store

Currently i use OpenStreetCam because it is open source, i would consider to contribute to both, but closed source is a no go for me

alex9099 commented May 26, 2018

It would be pretty nice to have the app open source, i only use F-Droid and compile apps from source, rarelly i touch play store

Currently i use OpenStreetCam because it is open source, i would consider to contribute to both, but closed source is a no go for me

@ovivoda

This comment has been minimized.

Show comment
Hide comment
@ovivoda

ovivoda Jul 9, 2018

mapillary_issues is no longer an active repository.

Let’s continue discussing features in our forum! We will import this issue as topic to the Mapillary Forum in the coming weeks. We’ll notify here once it’s been done. See you there!

ovivoda commented Jul 9, 2018

mapillary_issues is no longer an active repository.

Let’s continue discussing features in our forum! We will import this issue as topic to the Mapillary Forum in the coming weeks. We’ll notify here once it’s been done. See you there!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment