> Making 10 changesets of more than 10 features each over a period of at > least 2 weeks without attracting reverts or complaints should be > sufficient I would have thought. That would mean that a newbie who gets > on with it can be 'established' within 2 weeks. I think that was how > long it took me to get rights to upload images to Wikipiedia. Some > vandals will slip through, but that is fine - we can deal with them in > the usual way. We'll have to build a simple, calculateble and provable explanation from that, that every newbee understands. Also we should create a error-text that the tool displays when the conditions are not (yet) matched. This text should not demoralize the avarage user and tell him how long it will take until he can use this tool and why he can't use it yet. Any copywriter out here?
> I think the main message is 'please don't wait for permission to develop > this' and get going! I love you practical energy on this. I agree that a > web-service would be better that a downloadable tool - I would be much > more likely to use a web-service, but any tool is better than no tool. I can allay your doubts: I'm interested in this tool, too. Not so much from the user perspective but more from the programming. I'll start it as soon as I can. It would be very helpful if we got consensus about what it sould do and how it should be used. But pssst: Behind the scenes i just started working on the changeset parser :) > What we need now is for people to just get on with it and make tools and > try them cautiously on small test edits and then try them on bigger > stuff so we are ready for the big nightmare vandalism that could well > occur before anyone attempts it. Before we could start building these tools we should define their use clearly. That makes the development phase a whole lot shorter. Peter _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
