<p></p>
<p>This depends on what the end result should look like. If we say "modify the map" implicitly includes "post changeset comments", and add a new permission that only permits posting changeset comments, we would introduce a bit of a duplication. This may be somewhat confusing to users. If we're okay with that duplication, then there will be no impact on cgimap.</p>
<p>The option to introduce <em>two</em> new permissions and deprecate the exiting "modify the map" permission would be closer to the idea of separating "post a comment" into a new permission. From a design pov, this is cleaner, as different permissions don't overlap. It involves much more work, and also requires changes to CGImap (because it needs to know the new permission to allow write operations), and also editors like JOSM.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/2631#issuecomment-686372012">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLJ5MAE5MLNVJYSUFCLSD5PFVANCNFSM4NFGNPHA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AAK2OLIGEM25IAXIRMTSD3TSD5PFVA5CNFSM4NFGNPHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFDUTJLA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/2631#issuecomment-686372012",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/2631#issuecomment-686372012",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>