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

Changeset Comment #31

Open
cliffordsnow opened this issue Aug 29, 2021 · 3 comments
Open

Changeset Comment #31

cliffordsnow opened this issue Aug 29, 2021 · 3 comments

Comments

@cliffordsnow
Copy link
Contributor

I leave a lot of changeset comments when I review new mappers work. I review all new edits even if not specifically requested. I don't always leave a changeset comment but I often just leave a editing tip, like to square buildings and sometime asking for the user to make a specific change.

Like the Welcomed button we could add a made changeset comment and received a reply button.

@jbelien jbelien added this to the Version 2.0 milestone Aug 30, 2021
@jbelien
Copy link
Member

jbelien commented Sep 3, 2021

I indeed think it's a good idea to comment the first changeset(s) of a new mapper.
But I think adding a second "welcomed" toggle is not really necessary.

You can use the "welcomed" toggle as you please. For Belgium it could mean "a welcome message has been sent" and for Washington State mean "a welcome comment has been left of the first changeset(s)".

You can also use the notes on a mapper profile in the welcome tool to specify you left comment(s) on the changeset(s).

@cliffordsnow
Copy link
Contributor Author

How about a check box in the changeset info box. Something like

Changeset 12345678
September 3, 2021
Added a bunch of stuff

[ ] Changeset Comment

@cliffordsnow
Copy link
Contributor Author

If the information is saved in a dataset, we could gather some statistics.

@jbelien jbelien removed this from the Version 2.0 milestone Oct 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants