Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow user to request feedback when saving #4133

Closed
bhousel opened this issue Jul 9, 2017 · 10 comments
Closed

Allow user to request feedback when saving #4133

bhousel opened this issue Jul 9, 2017 · 10 comments

Comments

@bhousel
Copy link
Member

@bhousel bhousel commented Jul 9, 2017

This comes up for discussion sometimes in other channels but we don't have an issue to track it here.

The idea would be to have a checkbox labelled something like "I'd like somebody to review these edits". Then iD would add a special changeset tag (e.g. review_requested=yes?) and it would get special treatment by review systems like OSMCha.

similar: #3968

@willemarcel
Copy link
Contributor

@willemarcel willemarcel commented Aug 8, 2017

@bhousel It's a good idea! Some time ago someone suggested to add a hash tag like #pleasereview to the changeset comment, so we could track it on osmcha. Let me know if I can help on this!

I think we could add the information both in the changeset tag and in the comment. The tag makes it easier to be identified by software and the comment lets it more visible to users.

@bhousel
Copy link
Member Author

@bhousel bhousel commented Aug 8, 2017

Some time ago someone suggested to add a hash tag like #pleasereview to the changeset comment, so we could track it on osmcha. Let me know if I can help on this!

Nice, I'll make sure that when this feature is implemented we will open an issue on OSMCha to support it.

Hashtags in comments are sort of falling out of favor, see #2834. I think they are mostly used by the Missing Maps project for their dashboard. There seems to be general agreement that people would rather see hashtags in a different changeset tag and encourage mappers to write real comments about what they are doing, but there will be some transition period where they still appear in comments.

@bhousel
Copy link
Member Author

@bhousel bhousel commented Aug 9, 2017

wip at #4223

@JamesKingdom
Copy link
Collaborator

@JamesKingdom JamesKingdom commented Aug 17, 2017

Completed in 0ea043b

@HolgerJeromin
Copy link
Contributor

@HolgerJeromin HolgerJeromin commented Aug 30, 2017

iD invented here a new tag.
This tag should be IMO documented on the wiki, as this is designed to be used by other software.

@willemarcel
Copy link
Contributor

@willemarcel willemarcel commented Aug 30, 2017

@HolgerJeromin Thanks for your suggestion. I added it on https://wiki.openstreetmap.org/wiki/Changeset#Tags_on_changesets

@ltog
Copy link
Contributor

@ltog ltog commented Aug 31, 2017

I like the idea of giving new users the possibility to request a review. However, I am missing some key information:

  1. What work has to be done to qualify as a review?
  2. What are the possible outcomes of a review (maybe "good", "needs improvement", "needs revert"?) ?
  3. Who is qualified to do a review?
  4. How can we recognize if a review has been performed? Is it when (any kind of) a changeset comment has been given?
  5. Am I overthinking this?

I'd like to see a list of software that evaluates review_requested=yes tags. @joto evaluates project files (see https://wiki.openstreetmap.org/wiki/Taginfo/Projects ) but AFAIK these are meant for normal tags only, not for changeset tags. Maybe software authors, which support this tag can mention this fact on the wiki?

@HolgerJeromin
Copy link
Contributor

@HolgerJeromin HolgerJeromin commented Aug 31, 2017

@ltog we have no life cycle of a review.
The problem of this is that many persons are reviewing the same with no way to handle situations like "changeset was not good, but all was fixed in later changesets. No need to look at it".

Perhaps osmcha has this internally, but this should work across other QA software tools...

@batpad
Copy link

@batpad batpad commented Sep 1, 2017

The problem of this is that many persons are reviewing the same with no way to handle situations like "changeset was not good, but all was fixed in later changesets. No need to look at it".

My two bits: this information should not live on external review tools but on the osm.org changeset page, which is the commonly understood canonical page for a changeset. I believe discussions on changesets accommodate these use cases just fine. I.e. if someone reviews a changeset, fixes things, they should leave a discussion on the changeset saying "changeset was not good, but all was fixed in later changesets. No need to look at it" for eg. All any external tool needs to do then is surface the current changeset discussions to the reviewer.

It would probably be a good idea for any external review tool to post back any internal taxonomy for tagging / rating changesets as changeset discussions so this information is surfaced in a common place on osm.org. I'm not sure if posting changeset discussions by bots is allowed / encouraged, but I'll create a ticket in OSMCha for this.

tl;dr: I think most of these use-cases are currently handled by the changeset comment tag and changeset discussions.

@HolgerJeromin
Copy link
Contributor

@HolgerJeromin HolgerJeromin commented Sep 1, 2017

@batpad Thanks for your input.
You are right, the life cycle is (with our current software situation) best tracked in the changeset comments.
I would propose to have further discussions about the topic in the linked osmcha tracker.

simon04 pushed a commit to openstreetmap/josm that referenced this issue Sep 4, 2017
floscher pushed a commit to floscher/josm that referenced this issue Sep 4, 2017
floscher pushed a commit to floscher/josm that referenced this issue Sep 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants
You can’t perform that action at this time.