[OSM-dev] Measuring the current state of play wrt new contributor terms

andrzej zaborowski balrogg at gmail.com
Tue Aug 10 00:11:10 BST 2010


Hi,

On 9 August 2010 23:27, Jim Brown <jim at cloudmade.com> wrote:
> and for each row/object type show:
>
> # objects in db as of last update
> # tags in db as of last update
> # objects totally clean (all editors in the history have accepted)
> # objects initial editor accepted
> # objects clean so far (no editors have refused)
> # objects initial editor refused (entire object may be lost)
> # objects with partial data loss (one or more editors have refused, but not
> the first one)
> # tags totally clean (all editors in the history have accepted)
> # tags initial editor accepted
> # tags clean so far (no editors have refused)
> # tags initial editor refused (entire tag series may be lost)
> # tags with partial data loss (one or more editors have refused, but not the
> first one)

It may be more readable if instead of making separate categories for
"accepted" and "not refused" you'd have two values for every category:
the min and max.  Min would assume that all undecided will accept and
max would assume that all as yet undecided will refuse (or do
nothing), the two numbers should be slowly getting closer

Cheers



More information about the dev mailing list