[Protecting Maps] Subsystem maintainer like approval process
Hi,
I've recently found waze and am quite interested in editing the map.
With my new view, I found a possible area of improvement.
The behaviour I'm currently observing, is that in order to get a change to be made at all, an editor can only touch roads that are its level, or lower.
That means a rank 1 editor can edit all roads at rank 1, and potentially harm those roads.
Also, edits to higher ranked roads can not be made, when a new situation has recently been formed.
The current solutions to this are either a rank change request, which then lowers the rank required to edit a road (which then potentially allows other lower ranked editors to damage that section of road) or to have a higher ranked editor make the change for you (which damages the lower ranked editor in its points).
The system I'm proposing is slightly different and is much like the Linux kernel development model.
In my proposal, I'd suggest allowing edits to be made to any road by all editors (regardless of rank). However, when the time for applying those edits comes, rather than immediately applying the edits, it would be wise to send the proposed change to an editor with appropriate permissions for review.
The advantages of this system would be as follows:
1) Lower ranked editors would be able to make a more meaningful contribution
2) Road ranks wouldn't have to be lowered in order to allow lower ranked editors to edit (enhances safety)
3) Lower ranked editors would be barred from making harmful edits.
4) Lower ranked editors can still notify higher level editors without making a report on site (after all, whilst driving we need the eyes on the road and the hands on the wheel).
The disadvantage would be:
1) Higher ranked editors would potentially see a whole bunch of edits up for review by rank 1 editors.
As an additional side feature, the higher level editors would get points for allowing or denying these edit reviews, in order to encourage the processing of edits up for review, in turn lowering the number of edits up for review.
I've recently found waze and am quite interested in editing the map.
With my new view, I found a possible area of improvement.
The behaviour I'm currently observing, is that in order to get a change to be made at all, an editor can only touch roads that are its level, or lower.
That means a rank 1 editor can edit all roads at rank 1, and potentially harm those roads.
Also, edits to higher ranked roads can not be made, when a new situation has recently been formed.
The current solutions to this are either a rank change request, which then lowers the rank required to edit a road (which then potentially allows other lower ranked editors to damage that section of road) or to have a higher ranked editor make the change for you (which damages the lower ranked editor in its points).
The system I'm proposing is slightly different and is much like the Linux kernel development model.
In my proposal, I'd suggest allowing edits to be made to any road by all editors (regardless of rank). However, when the time for applying those edits comes, rather than immediately applying the edits, it would be wise to send the proposed change to an editor with appropriate permissions for review.
The advantages of this system would be as follows:
1) Lower ranked editors would be able to make a more meaningful contribution
2) Road ranks wouldn't have to be lowered in order to allow lower ranked editors to edit (enhances safety)
3) Lower ranked editors would be barred from making harmful edits.
4) Lower ranked editors can still notify higher level editors without making a report on site (after all, whilst driving we need the eyes on the road and the hands on the wheel).
The disadvantage would be:
1) Higher ranked editors would potentially see a whole bunch of edits up for review by rank 1 editors.
As an additional side feature, the higher level editors would get points for allowing or denying these edit reviews, in order to encourage the processing of edits up for review, in turn lowering the number of edits up for review.
Re: [Protecting Maps] Subsystem maintainer like approval pro