Re: [Talk-ca] Telenav mapping turn restrictions

[m]

Yes, if you ask me, changeset comments are (and will stay) the #1 place to 
discuss mapping issues. If a mapper continues to do questionable edits, the 
public channels like this mailing list are a good place to go to. 

To look at recent changeset comments, I use Pascal Neis’s tool. If you haven’t 
seen that yet you should definitely check it out: 
http://resultmaps.neis-one.org/osm-discussions?c=Canada#5/48.805/-99.802 
 

So like I said in my other response just now, GitHub issues are secondary to 
that, more like a convenient way for us to track and for  mappers to see what 
projects we are proposing and working on, and if you happen to have a Github 
account you can also comment. 

Sorry that was not more clear from the outset.

Martijn

> On Apr 26, 2017, at 10:22 AM, Stewart C. Russell  wrote:
> 
> On 2017-04-25 11:55 PM, m...@rtijn.org wrote:
>> 
>> Let me suggest this: I will take the concerns raised here to our team
>> and get back to the list before the end of the week with proposed next
>> steps to fix where possible. We will use Github tickets to track
>> this.
> 
> As a process suggestion, may I recommend some integration with OSM
> changeset discussion? We ran into an issue last year when Mapbox was
> also adding turn restrictions. There was some friction between local
> mappers and Mapbox staff, as mappers asked questions in changeset
> discussion and didn't see the tickets on Github, while Mapbox staff
> didn't respond to the changeset discussion and assumed the Github
> tickets were authoritative.
> 
> I know that Github issues are the industry standard, and the OSM
> comment/discussion mechanisms may seem a little quaint, but we risk
> talking past one another if we splinter the discussion.
> 
> cheers,
> Stewart
> 
> 
> ___
> Talk-ca mailing list
> Talk-ca@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca

___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca

Re: [Talk-ca] Telenav mapping turn restrictions

[m]

Yes, I agree with you, and we will keep discussing through the ‘real’ OSM 
channels. I don’t expect people to sign up for Github. I see it more as a 
public way for us to track our mapping projects, so that everyone can see 
what’s going on and respond there if they choose to. I definitely don’t see it 
as the only / exclusive way to discuss.

Martijn

> On Apr 26, 2017, at 10:49 AM, Michael Reichert  wrote:
> 
> Hi Martijn,
> 
> Am 26.04.2017 um 18:22 schrieb Stewart C. Russell:
>> I know that Github issues are the industry standard, and the OSM
>> comment/discussion mechanisms may seem a little quaint, but we risk
>> talking past one another if we splinter the discussion.
> 
> Just my 2 cent as a non-Canadian. I think you, Martijn, cannot expect an
> average mapper to sign up for Github (a platform which belongs neither
> to the OSMF nor to any local chapter) just to be able to complain about
> someone else edits. There is already a plenty of platforms which can be
> used to discuss things in the OSM universe, changeset discussion and
> this mailing list are two of them.
> 
> Best regards
> 
> Michael
> 
> -- 
> Per E-Mail kommuniziere ich bevorzugt GPG-verschlüsselt. (Mailinglisten
> ausgenommen)
> I prefer GPG encryption of emails. (does not apply on mailing lists)
> 
> ___
> Talk-ca mailing list
> Talk-ca@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca


___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca

Re: [Talk-ca] Telenav mapping turn restrictions

[James]

For once, I agree with Nakaner.

On Wed, Apr 26, 2017 at 12:49 PM, Michael Reichert  wrote:

> Hi Martijn,
>
> Am 26.04.2017 um 18:22 schrieb Stewart C. Russell:
> > I know that Github issues are the industry standard, and the OSM
> > comment/discussion mechanisms may seem a little quaint, but we risk
> > talking past one another if we splinter the discussion.
>
> Just my 2 cent as a non-Canadian. I think you, Martijn, cannot expect an
> average mapper to sign up for Github (a platform which belongs neither
> to the OSMF nor to any local chapter) just to be able to complain about
> someone else edits. There is already a plenty of platforms which can be
> used to discuss things in the OSM universe, changeset discussion and
> this mailing list are two of them.
>
> Best regards
>
> Michael
>
> --
> Per E-Mail kommuniziere ich bevorzugt GPG-verschlüsselt. (Mailinglisten
> ausgenommen)
> I prefer GPG encryption of emails. (does not apply on mailing lists)
>
>
> ___
> Talk-ca mailing list
> Talk-ca@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca
>
>


-- 
外に遊びに行こう！
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca

Re: [Talk-ca] Telenav mapping turn restrictions

[Michael Reichert]

Hi Martijn,

Am 26.04.2017 um 18:22 schrieb Stewart C. Russell:
> I know that Github issues are the industry standard, and the OSM
> comment/discussion mechanisms may seem a little quaint, but we risk
> talking past one another if we splinter the discussion.

Just my 2 cent as a non-Canadian. I think you, Martijn, cannot expect an
average mapper to sign up for Github (a platform which belongs neither
to the OSMF nor to any local chapter) just to be able to complain about
someone else edits. There is already a plenty of platforms which can be
used to discuss things in the OSM universe, changeset discussion and
this mailing list are two of them.

Best regards

Michael

-- 
Per E-Mail kommuniziere ich bevorzugt GPG-verschlüsselt. (Mailinglisten
ausgenommen)
I prefer GPG encryption of emails. (does not apply on mailing lists)



signature.asc
Description: OpenPGP digital signature
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca

Re: [Talk-ca] Telenav mapping turn restrictions

[Stewart C. Russell]

On 2017-04-25 11:55 PM, m...@rtijn.org wrote:
> 
> Let me suggest this: I will take the concerns raised here to our team
> and get back to the list before the end of the week with proposed next
> steps to fix where possible. We will use Github tickets to track
> this.

As a process suggestion, may I recommend some integration with OSM
changeset discussion? We ran into an issue last year when Mapbox was
also adding turn restrictions. There was some friction between local
mappers and Mapbox staff, as mappers asked questions in changeset
discussion and didn't see the tickets on Github, while Mapbox staff
didn't respond to the changeset discussion and assumed the Github
tickets were authoritative.

I know that Github issues are the industry standard, and the OSM
comment/discussion mechanisms may seem a little quaint, but we risk
talking past one another if we splinter the discussion.

cheers,
 Stewart


___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca