On Thursday 14 November 2002 06:36 pm, Erik Moeller wrote:
Propose a scheme that allows this, can be kept reasonably clean and implemented in an easy to use fashion, and I'll look at it. Alternatively, root for my team certification proposal, because it allows just that.
Regards,
Erik
Hm. Your idea for team certification on the one hand and Larry's Sifter idea combined with my idea of having multiple Sifters with different foci sound like compatible ideas to me.
Different certification teams would simply belong to different one click Sifters (each Sifter project would have to be Wikipedia registered in order to use the one click article upload function -- they would also have to respect Wikipedia policies and conventions or risk losing their registration).
-- Daniel Mayer (aka mav)
Hm. Your idea for team certification on the one hand and Larry's Sifter idea combined with my idea of having multiple Sifters with different foci sound
like compatible ideas to me.
Indeed, and it's good that Larry is moving forward with his Sifter project. But I do not like the idea of having many different Wikipedia forks, because these will, per definitionem, only be selections of articles, whereas I would simply like to have information *within* Wikipedia that Team FOO has certified revision BAR as BAZ. This wouldn't mean that you would no longer be able to look at uncertified (unstable by the software analogy) articles. You would just get information that a previous revision has been certified by a team in your trusted team list if that's the case.
This clearly requires more changes to the Wikipedia code than the Sifter idea, but if we introduce team certification at all, I propose it should be done under a scheme integrated in Wikipedia.
Regards,
Erik
wikipedia-l@lists.wikimedia.org