Re: [OSM-dev] Removing functionality and giving just No as answer

On 08/03/17 Tom Hugues wrote: > There is a cargo cult belief that you need to force dirty the tile at > the renderer but that is almost never the case - any changes to nodes > and ways will automatically dirty the relevant tiles. Only changes to > relations are not handled automatically.

Re: [OSM-dev] Removing functionality and giving just No as answer

It's like the close door button in an elevator, you know it usually does not speed things up, but it feels good to press it anyway. Yves Le 8 mars 2017 13:03:32 GMT+01:00, Tom Hughes a écrit : >On 08/03/17 09:35, joost schouppe wrote: > >> While a lot of the comments are a

Re: [OSM-dev] Removing functionality and giving just No as answer

On 08/03/17 09:35, joost schouppe wrote: While a lot of the comments are a bit misguided, I think it is clear that quite a few mappers use this dirty trick to get the render to refresh. As OSM.org is supposed to be a mapper's tool and not a general public website, I think it is quite obvious

Re: [OSM-dev] Removing functionality and giving just No as answer

Just to clarify, Tom, would the example given by mmd ( http://www.sammyshp.de/fsmap/#18/51.01486/13.63683) be something you would deem acceptable in osm.org? BTW, one of the places where people were "canvasing" was here:

Re: [OSM-dev] Removing functionality and giving just No as answer

Am 24.02.2017 um 12:19 schrieb Tom Hughes: > > More specifically there were a number of people asserting that this > feature was somehow to all mappers and I was trying to make the point > that really that wasn't true at all and that the was majority of mappers > would never have any use for it.

Re: [OSM-dev] Removing functionality and giving just No as answer

I'm new to OSM @dev but I see a couple of items that have come up on this thread I wanted to try and note... First, what is actually the request in Issue 1446? Yes, the word-by-word request is to add the entry back to the right-click menu, but it seems a little more than that. Useful (at least to

Re: [OSM-dev] Removing functionality and giving just No as answer

I didn't want to be offencive, sorry if my mail sounds like personall offence, I didn't meant Tom or anybody personally. Most of the open-source projects, as I think, quite authoritarian about commits and pull requests and ruled the way "I'm the boss, fork it if you are desagree" I would be

Re: [OSM-dev] Removing functionality and giving just No as answer

Hi folks, Please consider this a reminder that we should maintain a civil discourse, stay on topic, and not make any personal attacks. The governance of critical pieces of our software ecosystem are important to talk about, but please don't attack or ridicule individuals. Your friendly mailing

Re: [OSM-dev] Removing functionality and giving just No as answer

Ok, lets continue with our current "I'm the boss, that's why" approach. 2017-02-24 13:25 GMT-04:00 Yves : > I have personally three use cases: > a) trigger a faster? rerender in a mapping situation I'm not sure of > myself > b) compare a tile with another > c) get the tile

Re: [OSM-dev] Removing functionality and giving just No as answer

I have personally three use cases: a) trigger a faster? rerender in a mapping situation I'm not sure of myself b) compare a tile with another c) get the tile scheme right zyx or zxy? ___ dev mailing list dev@openstreetmap.org

Re: [OSM-dev] Removing functionality and giving just No as answer

On 24/02/17 17:15, Дмитрий Киселев wrote: The key thing is that you need some mechanism for appointing people to that circle of maintainers who get to vote on which things should be included and which shouldn't. On most projects that is done by promoting from those making useful

Re: [OSM-dev] Removing functionality and giving just No as answer

> > Actually carto has had multiple maintainers for some time. Indeed the > original maintainer, who I assume you are referring to, is not actually > doing very much these days. > While osm.org has only one maintainer we have been getting some more > contributors recently. Andy has been

Re: [OSM-dev] Removing functionality and giving just No as answer

W dniu 24.02.2017 16:59, Darafei "Komяpa" Praliaskouski napisał(a): If you look at it, it's not "community developed this", or "OSMF developed this", or even "a private club developed this" which you paint as a dark scenario. It's being mostly written and deployed by the same person. This is

Re: [OSM-dev] Removing functionality and giving just No as answer

On 24/02/17 16:24, Дмитрий Киселев wrote: > at this moment, we have some widely used resources such as osm.org > and osm carto, started and threated as single persons gh repository. Actually carto has had multiple maintainers for some time. Indeed the original maintainer, who I assume you are

Re: [OSM-dev] Removing functionality and giving just No as answer

My five cents: at this moment, we have some widely used resources such as osm.org and osm carto, started and threated as single persons gh repository. And we (osm community) don't have a way to discuss and evaluate changes in collaborative way. Usually maintainer just decides "Do I love this

Re: [OSM-dev] Removing functionality and giving just No as answer

On 24 February 2017 at 16:14, Tom Hughes wrote: > On 24/02/17 14:43, Blake Girardot HOT/OSM wrote: > >> On Fri, Feb 24, 2017 at 12:33 PM, Dave F >> wrote: >> >> On 24/02/2017 11:19, Tom Hughes wrote: >>> >>> Well it was a little odd that we suddenly

Re: [OSM-dev] Removing functionality and giving just No as answer

Hi! > OSM Github is not a private club. You should be welcoming other > contributors, not 'closing' on them. > Here lies a heartbreaking thing: openstreetmap-website is actually a single person's project. https://github.com/openstreetmap/openstreetmap-website/graphs/contributors If you look

Re: [OSM-dev] Removing functionality and giving just No as answer

On 24/02/17 14:43, Blake Girardot HOT/OSM wrote: On Fri, Feb 24, 2017 at 12:33 PM, Dave F wrote: On 24/02/2017 11:19, Tom Hughes wrote: Well it was a little odd that we suddenly got several people who are not regular commenters turning up in the space of a few

Re: [OSM-dev] Removing functionality and giving just No as answer

On Fri, Feb 24, 2017 at 12:33 PM, Dave F wrote: > > On 24/02/2017 11:19, Tom Hughes wrote: >> >> >> Well it was a little odd that we suddenly got several people who are not >> regular commenters turning up in the space of a few minute to add "me too" >> style

Re: [OSM-dev] Removing functionality and giving just No as answer

2017-02-24 13:11 GMT+01:00 Michael Zangl < openstreet...@michael.fam-zangl.net>: > This is a not a dev playground, this is a website that > should be used by millions of normal users. It should provide an entry > point for people that want to improve the OSM database. It should not be > a

Re: [OSM-dev] Removing functionality and giving just No as answer

пт, 24 февр. 2017 г. в 14:44, Tom Hughes : > On 24/02/17 11:27, Dave F wrote: > > > On 24/02/2017 10:26, Jóhannes Birgir Jensson wrote: > >> > >> It was closed and rejected in a very abrupt and unconstructive manner. > > > > Yes. This seems to be Tom Hughes's default reaction.

Re: [OSM-dev] Removing functionality and giving just No as answer

Hi, A few words of someone who is just "using" the OSM website: I personally think the current Menu is full enough. We should focus on making that menu better for normal visitors. I could not really think of a use case where a normal user would want to see a specific map tile. In my opinion,

Re: [OSM-dev] Removing functionality and giving just No as answer

On 24/02/17 11:27, Dave F wrote: On 24/02/2017 10:26, Jóhannes Birgir Jensson wrote: It was closed and rejected in a very abrupt and unconstructive manner. Yes. This seems to be Tom Hughes's default reaction. He's certainly trigger happy with the close button. Tickets can always be

Re: [OSM-dev] Removing functionality and giving just No as answer

On 24/02/17 11:33, Dave F wrote: On 24/02/2017 11:19, Tom Hughes wrote: Well it was a little odd that we suddenly got several people who are not regular commenters turning up in the space of a few minute to add "me too" style responses. What's wrong with that? There are numerous discussions

Re: [OSM-dev] Removing functionality and giving just No as answer

On 24/02/17 11:11, Tom Hughes wrote: Rather what happened is that at some point (most likely in the 1.0.0 release about six months ago) leaflet started marking tile images with a CSS attribute that stops the browser offering image options for them in the default context menu. This is the

Re: [OSM-dev] Removing functionality and giving just No as answer

On 24/02/2017 11:19, Tom Hughes wrote: Well it was a little odd that we suddenly got several people who are not regular commenters turning up in the space of a few minute to add "me too" style responses. What's wrong with that? There are numerous discussions in Dev that I have no

Re: [OSM-dev] Removing functionality and giving just No as answer

On 24/02/2017 10:26, Jóhannes Birgir Jensson wrote: It was closed and rejected in a very abrupt and unconstructive manner. Yes. This seems to be Tom Hughes's default reaction. He's certainly trigger happy with the close button. DaveF --- This email has been checked for viruses by Avast

Re: [OSM-dev] Removing functionality and giving just No as answer

On 24/02/17 10:26, Jóhannes Birgir Jensson wrote: As evident in the discussion on issue https://github.com/openstreetmap/openstreetmap-website/issues/1446 there are several people interested in maintaining functionality that existed only a few days ago - being able to view single tiles just as

Re: [OSM-dev] Removing functionality and giving just No as answer

Hi! пт, 24 февр. 2017 г. в 13:30, Jóhannes Birgir Jensson : > As evident in the discussion on issue > https://github.com/openstreetmap/openstreetmap-website/issues/1446 there > are several people interested in maintaining functionality that existed > only a few days ago - being

Re: [OSM-dev] Removing functionality and giving just No as answer

On 24/02/17 10:26, Jóhannes Birgir Jensson wrote: But removing functionality and then denying it to be re-added based on very little but personal objective is unhelpful and detrimental. As far as I know no functionality has been removed, at least not recently. Rather a request to add

Re: [OSM-dev] Removing functionality and giving just No as answer

On Friday 24 February 2017, Jóhannes Birgir Jensson wrote: > As evident in the discussion on issue > https://github.com/openstreetmap/openstreetmap-website/issues/1446 > there are several people interested in maintaining functionality that > existed only a few days ago - being able to view single