2015-03-18 23:56 GMT+00:00 David Bannon <dban...@internode.on.net>: > Kotya, in no way was I criticising the leadership you have shown in this > matter ! > > Its just that I preferred Dan's approach. Key IMHO is - > > * A proposal gets to wiki in much the same manner as now. > > * Once on the wiki, instead of a formal vote period, users (eg) click a > "like" or "dislike" button and aggregate score is shown. For some time > (?). Obviously they can also edit content to say why. > > Now, we don't have that content freeze when voting formally starts. Is > it a problem that I click 'like' and some important change is made to > content later ?
Yes it's a problem, but I hope that's small enough to ignore, because people can delete or switch their votes whenever they like. I guess in the very very first stages, when someone writes something flawed, we might want a "don't vote yet" stage (as we do now) so that a page doesn't accumulate lots of {{no}} of which at least some of them won't bother revisiting their opinion. Dan > David > > On Wed, 2015-03-18 at 23:57 +0100, Kotya Karapetyan wrote: > > >> Ahhm, not sure how it is different, but never mind. I will be happy if >> we all agree on a good solution, and I definitely don't claim the >> authorship of all the good ideas that have popped up here over the >> last couple of days. I just tried to summarize it in something that >> looked to me like a working solution. Dan, thanks for making a good >> illustration :) >> >> Quite a good one really. It meets my >> criteria of giving a new mapper some guidance on what he/she >> should >> use. >> >> >> >> Good to hear :) >> >> Add in taginfo data. >> >> >> Yes: "Opinions "for" and "against" are expressed in the discussions >> and summarized at the top of the page (e.g. "advantages" and >> "disadvantages" of a tag) together with the current usage" >> >> >> And maybe a list of competing approaches so, again, its clear >> to a new >> user what the options are. >> >> >> It clearly belongs a "see also" section IMO. >> >> >> >> >> >> I do think we'd need to have some (usage determined ?) end >> point >> however. Who is going to register their approval of, eg, >> highway= this >> far down the track ? >> >> I think data consumers also need a bit of certainty too. >> >> >> End of what? >> >> Usage, as discussed in another thread, is a vague criterion. Two tags >> may have a full support of the community, one having thousands of uses >> and another (for a rare feature) ten. >> For data consumers---definitely yes, and I suggest it being the moment >> when we remove the "proposal" status, so the page becomes a feature >> page. The moment can be "when the discussion calms down (which can >> even be defined mathematically if needed)". >> >> >> Sorry guys, no more spamming today :) Hopefully we'll converge to >> something good, so these discussions won't be in vain :) >> >> >> Cheers, >> Kotya >> _______________________________________________ >> Tagging mailing list >> Tagging@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/tagging > > > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging