[preMEP] Mozart-Oz Patch Repository

[Christian Schulte]

Hi all,

I just have a question (maybe I'm dumb): what problem is supposed to be
solved? how does the proposed repository help in solving that problem? who
is going to solve the problem?

Cheers
Christian

--
Christian Schulte, http://www.imit.kth.se/~schulte/ 

-----Original Message-----
From: mozart-hackers-bounces at ps.uni-sb.de
[mailto:mozart-hackers-bounces at ps.uni-sb.de] On Behalf Of Fred Eisele
Sent: Friday, July 29, 2005 6:08 PM
To: mozart-hackers at ps.uni-sb.de
Subject: [preMEP] Mozart-Oz Patch Repository


This is a proposal for an informational MEP.

Reference:
http://www.mozart-oz.org/pipermail/mozart-hackers/2004/002119.html

"It began as a complement to the expert-written Nupedia on January 15,
2001." ... "The status of Wikipedia as a reference work has been
controversial, and it is both praised for its free distribution, free
editing and wide range of topics and criticized for alleged systemic biases,
preference of consensus to credentials, deficiencies in some topics, and
lack of accountability and authority when compared with traditional
encyclopedias."
-- http://en.wikipedia.org/wiki/Wikipedia

"Nupedia was characterized by an extensive peer-review process designed to
make its articles of a quality comparable to professional encyclopedias.
Nupedia wanted scholars to volunteer content for free."
-- http://en.wikipedia.org/wiki/Nupedia

 The discussion http://www.vendian.org/oz/wiki/index.cgi?Governance
illustrates 
the problem nicely.
The discussion itself presumes that what is needed is a system not unlike
Nupedia. That is, where changes are governed, managed, controlled, released,
pr oven, etc. The posting of the discussion on a wiki illustrates one reason
why that level of control is important (the link was vandalized (I rolled it
back)). The problem is that very few (any?) MEP have been submitted.

=======================
The Proposal:

Create a distributed change management system where:
- each 'patch' is independently and multiply certified.
- each 'system' is that collection of patches meeting specific certification
requirements =======================

Preliminary Discussion/Explanation:

This system would be created separately from the current system. For detail
on what constitutes a patch see http://www.darcs.net/manual/node8.html
There would be different types of patch certification:
1) Committee (mozart-oz board, iso, ansii, etc.)
2) Submitter (anonymous or signed) 
3) Distribution (debian, red hat, windows, os/X, etc.)
4) Optimization (i386, Pentium, cell, etc.)
5) Management (notify when child patch created)
6) Organizational (business, colleges, governments, etc.)

The default patch set would be mozart-oz board certified patches. A patch
set would be composed of other patch sets, composed of patches selected by
their certifications.

There is currently a similar activity going on with WikiMedia:
http://meta.wikimedia.org/wiki/Article_validation_feature

Peace

____________________________________________________________________________
_____
mozart-hackers mailing list
mozart-hackers at ps.uni-sb.de      
http://www.mozart-oz.org/mailman/listinfo/mozart-hackers