I also think that a voluntary opt-in review system would work - and only really needs someone to write one, and a JOSM plugin, and a Potlatch 2 patch. It's on my list of things to do, but I doubt I will ever get around to doing it. But that's all that needs happen by someone - do-ocracy etc...
In terms of what's in it for the user - the reviewer sees newbies edits in their area of interest - they can help maintain the area, and the newbie, of course would get valuable feedback. lots of love, chippy. On 26 September 2011 21:26, Gregory <nomoregra...@googlemail.com> wrote: > I add a source tag to a lot of my changesets now. The OSM site these days > makes it very easy to click back and forth between changesets and objects. > > I gave a talk/demo recently on how to edit OSM. I started by introducing > myself and then saying "right, we are now friends. Once you've made an edit, > feel free to contact me in the ways mentioned and I will happily check your > edit/data works and there aren't any obvious mistakes." > I'm aware that really helps people. It's why a lot of people become OSM'ers > after going to a mapping party/event. And I think the teacher inviting > communication with them is the way to do it. At my first mapping party I > only learnt how to survey, but it helped just knowing there were real people > I could contact. > > The other thing is that I watch my area (through the OWL viewer/rss feed) > for edits, especially if they are new users. I try to contact all of them > with a friendly & local message, sometimes offering them advise on what > additional tags they could have used. > > > On 20 September 2011 17:50, John Sturdy <jcg.stu...@gmail.com> wrote: > >> On Tue, Sep 20, 2011 at 3:47 PM, Mike N <nice...@att.net> wrote: >> > >> > Even today, I would find it confusing to edit a group of objects which >> have >> > source tags - it would be more intuitive to put the source in the >> changeset, >> >> That makes sense to me --- surely most changes in a changeset will >> have the same source. Perhaps it could cascade / inherit, so that a >> "source" attached to an individual object will override the "source" >> of the changeset. >> >> __John >> >> _______________________________________________ >> talk mailing list >> talk@openstreetmap.org >> http://lists.openstreetmap.org/listinfo/talk >> > > > > -- > Gregory > o...@livingwithdragons.com > http://www.livingwithdragons.com > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk > >
_______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk