"If editing in a community (blue) or collaborative (purple) country you shall use a descriptive edit summary"
Comment from Ūdilugbulgidħū on 8 December 2016 at 16:15
Very good rule. Hardly any effort required, but saves a lot of time for other people.following things up.
Comment from Luciano on 9 December 2016 at 04:11
It's a great suggestion, except that many users don't seem to care about any rules whatsoever, including much more important ones related to verisimilitude and respecting other users' work. I think it might be hoping too much to expect users to conform to another rule which might be deemed fairly low priority in comparison to other rules.
Having said that, I've also always felt a little bit unclear, myself, about what information is useful in an edit summary. I tend to use my own shorthand to organize my summaries, but that shorthand is undoubtedly opaque to other users. Is there a standard (e.g. at OSM) for what information should be put in an edit summary?
Speaking as a "devil's advocate", isn't it obvious from whatever was actually done in the edit, what the intentions of the editor were, and isn't the changeset id number sufficient to identify it if it needs to be discussed later on?
Comment from PColumbus73 on 9 December 2016 at 13:41
In regards to collaborative territories, I think the owners of these territories should institute rules they believe are in the best interests for their territory. Whether it be more closely monitored like the Ardisphere, or more free-for-all like Drevet was before I took over. I agree that having summary notes would be nice to have for a territory owner to have a quick glance at the work being done in their territories.
I think the 'blue' territories could be subdivided by experience level. For instance, Commonia is pretty much the training ground for new mappers, so I think it's a little unfair to expect that Commonia should conform to the rest of the OGF world (I tend to think of that area as tribal lands). However, a blue territory like Gobrassanya would cater to more advanced mappers (and have more rules applied there).
Comment from wangi on 10 December 2016 at 00:37
Anything helps really in an edit survey. It's pretty common for a large bounding box to show for the change (due to long road or coastline ways), but the edits are just in one small bit of it.
Perfect situation is when the edit summary tells a story from commit to commit.
But mostly meant a bit tongue in cheek.
Comment from Luciano on 10 December 2016 at 05:39
Actually, I think it might be valuable to the OGF community to put together some kind of OGF:Edit_Summary informational/instructional page, where we could develop our own community standard and have something to point new users towards...
Anyone interested in taking that on? I think this would be one example of something that would best be taken on by someone with actual OSM experience (i.e. not me).
Comment from wangi on 11 December 2016 at 18:08
I'll pull something based on https://wiki.openstreetmap.org/wiki/Good_changeset_comments
* First item
* Second item
1. First item
2. Second item