the hivemind
codex
The hivemind's codex is the basic set
of rules
governing the operation of the hivemind. The codex is changed by
occasional
evolutions
proposed on the hivemind mailing list.
The
hivemind's current codex
Definition of the hivemind
- The hivemind is made up of the hivemind
mailing list subscribers
Purpose of the hivemind
- The hivemind will sustain itself
- The hivemind will benefit its participants
- The hivemind will attempt to make contact
with other like-minds
Joining and leaving the hivemind
- Anyone may join the hivemind by subscribing
to the hivemind mailing list
- By subscribing to the hivemind mailing
list, participants agree to adhere to the hivemind codex
- Anyone may leave the hivemind at any time
simply by unsubscribing from the hivemind mailing list
Codex evolution
- Any changes to the hivemind codex must be
proposed on the hivemind mailing list as "evolutions".
- Proposed evolutions must be accompanied by
a reason for the proposal.
- It is recommended that each evolution be
reposted one week after its original posting date.
- Proposed evolutions may only (and must
explicitly):
- (i) add points to the codex,
- (ii) modify existing points in the codex,
or
- (iii) remove points from the codex
- Expressions of support for or objections to
an evolution may be voiced for up to two weeks after the initial
posting of the evolution.
- Evolutions can only be supported in total
or objected to in total. It is not possible to partially support or
object to an evolution. A new, modified evolution should be posted
instead.
- Each person, other that the proposer, may
submit either one supporting vote or one objecting vote.
- Proposed evolutions do not come into effect
until they have received at least one supporting vote.
- Proposed evolutions do not apply if three
or more people object to the evolution.
- For each person actively supporting an
evolution, the number of objections is reduced by one.
The hivemind mailing list
- The hivemind mailing list is for the
general discussion of issues relevant to the hivemind
- The list is not appropriate for spam or
forwarding of unrelated mail
- The list is not appropriate for irrelevant
advertising of products or services
- Basic rules of netiquette should be
followed when posting to the list
Intellectual property
- Any posts to the hivemind mailing list
become the intellectual property of the entire hivemind. Members of the
hivemind may freely quote, use or recycle any intellectual property
belonging to the hivemind. Except in the case where the poster
specifically wishes to retain copyright or wishes to draw attention to
existing copyright in which case the passage must be clearly marked,
eg. (c) or copyright withheld etc.
- The hivemind's intellectual property may not be used in such a way that it will harm the hivemind,
or members of the hivemind.
Evolutions
of the hivemind
Evolutions are listed in reverse
chronological
order (newest first). The status field indicates whether or not the
evolution
is currently in effect.
Evolution #12
Status:
In effect
Date
proposed: 2005-06-08
Proposer:
Ant Brooks
Supporters:
Sean McDonald, Johan Pretorius, George Barnett
Objectors:
None
It was proposed that the following
point be added under the heading of intellectual property:
Evolution #11
Status:
In effect
Date
proposed: 2000-07-15
Proposer:
Ant Brooks
Supporters:
Alicia Woolf
Objectors:
None
It was proposed that the entire
evolution section of the codex be replaced with the following:
- Any changes to the hivemind
codex must be proposed on the hivemind mailing list as "evolutions".
- Proposed evolutions must be
accompanied by a reason for the proposal.
- It is recommended that each
evolution be reposted one week after its original posting date.
- Proposed evolutions may only
(and must explicitly):
- (i) add points to the codex
- (ii) modify existing
points in the codex
- (iii) remove points from
the codex
- Expressions of support for
or objections to an evolution may be voiced for up to two weeks after the initial
posting of the evolution.
- Evolutions can only be
supported in total or objected to in total. It is not possible to partially support
or object to an evolution. A new, modified evolution should be posted
instead.
- Each person, other that the
proposer, may submit either one supporting vote or one objecting vote.
- Proposed evolutions do not
come into effect until they have received at least one supporting vote.
- Proposed evolutions do not
apply if three or more people object to the evolution.
- For each person actively
supporting an evolution, the number of objections is reduced by one.
Evolution #10
Status:
Superceded by evolution #11
Date
proposed: 2000-07-13
Proposer:
Antoine Van Gelder
Supporters:
Jon Tullett, Ivo Vegter (point 1)
Objectors:
Ivo Vegter (remaining points)
The following was proposed:
- Any evolution must be
accompanied with the reason for its existence.
- This evolution shall be
applied retroactively to all existing evolutions.
- Any evolution can be
challenged on the basis of its given reason and modified or deleted as appropriate.
- The reason for this
evolution's existance is to avoid the inevitable inertia that sets in with any formal
system as its constituent components lose relation to the real world over
time.
Evolution #9
Status:
Superceded by evolution #11
Date
proposed: 2000-07-06
Proposer:
Ivo Vegter
Supporters:
Werner, Steve Murray
Objectors:
None
The following was proposed:
- If an evolution is proposed,
it should be posted publically to the hivemind mailing list. Any proposed evolution
must be repeated one week after its initial posting. Supporting votes and
objections will be entertained for two weeks from the date of the first
posting. Should no comment at all be made within two weeks after the initial
posting, the proposed evolution will be adopted.
Evolution #8
Status:
In effect
Date
proposed: 1999-01-26
Proposer:
Ant Brooks, modified by Jeff Fletcher and Matthew French
Supporters:
Matthew French
Objectors:
None
It was proposed that the following
point be added to the purpose section of the hivemind codex:
- The hivemind will attempt to
make contact with other like-minds
Evolution #7
Status:
Superceded by evolution #11
Date
proposed: 1999-01-26
Proposer:
Ant Brooks
Supporters:
None
Objectors:
None
It was proposed that the following
point be added to the evolution section of the hivemind codex:
- Two weeks after any
evolution is proposed, existing supporting votes or objections may no longer be changed
and no new votes may be counted.
Evolution #6
Status:
In effect (an equivalent email address is now used)
Date
proposed: 1998-06-12
Proposer:
Norma Laburn
Supporters:
Lucio de Re, Matthew French
Objectors:
None
It was proposed that the default
reply-to of the hivemind mailing list be set to all@hivemind.net.
Evolution #2a
Status:
In effect
Date
proposed: 1998-06-11
Proposer:
Norma Laburn
Supporters:
Roger Hislop, Damian Costa, Ant Brooks
Objectors:
None
The following modification to the
hivemind codex was proposed:
Intellectual property
- Any posts to the hivemind
mailing list become the intellectual property of the entire hivemind. Members of the
hivemind may freely quote, use or recycle any intellectual property
belonging to the hivemind. Except in the case where the poster specifically
wishes to retain copyright or wishes to draw attention to existing copyright
in which case the passage must be clearly marked, eg. (c) or copyright
withheld etc.
Evolution #5: Disciplinary Procedure
Status:
Not in effect
Date
proposed: 1998-06-11
Proposer:
Matthew French
Supporters:
None
Objectors:
Norma Laburn
It was proposed that if a person
feels that someone be removed, they post a public message with the subject:
"Request removal of ". The body of the message should contain the reasons for the
request, even if they are obvious.
Then a vote should be taken, where
a result of 75% or more for the removal will result in the person being "dismissed"
from the list.
Evolution #4: Voting
Procedure
Status:
Not in effect
Date
proposed: 1998-06-11
Proposer:
Matthew French
Supporters:
None
Objectors:
Ant Brooks
My proposal is that when an issue
is called to vote (such as a change to the hivemind codex) that one week should
pass before the result is made final.
Evolution #3a
Status:
Superceded by evolution #11
Date
proposed: 1998-06-11
Proposer:
Lucio de Re
Supporters:
Damian Costa
Objectors:
None
It was proposed that the hivemind
codex be modified so that all proposals for evolutions are not applicable until
they have received at least one public
supporting vote on the hivemind
mailing list.
Evolution #3
Status:
Superceded by evolution #11
Date
proposed: 1998-06-08
Proposer:
Lucio de Re
Supporters:
Andras Salamon, Roger Hislop, Norma Laburn
Objectors:
None
It was proposed that all proposals
for evolutions are not applicable until they have received at least one supporting
vote.
Evolution #2
Status:
In effect
Date
proposed: 1998-06-08
Proposer:
Ant Brooks
Supporters:
Tim Robinson
Objectors:
Carsten Knoch
It was proposed that the following
section be added to the hivemind codex:
Intellectual property
- Any posts to the hivemind
mailing list become the intellectual property of the entire hivemind. Members of the
hivemind may freely quote, use or recycle any intellectual property
belonging to the hivemind.
Evolution #1
Status:
In effect
Date
proposed: 1998-05-27
Proposer:
Ant Brooks
It was proposed that the hivemind
adopt the following codex:
hivemind codex
Definition of the hivemind
- The hivemind is made up of
the hivemind mailing list subscribers
Purpose of the hivemind
- The hivemind will sustain
itself
- The hivemind will benefit
its participants
Joining and leaving the hivemind
- Anyone may join the hivemind
by subscribing to the hivemind mailing list
- By subscribing to the
hivemind mailing list, participants agree to adhere to the hivemind codex
- Anyone may leave the
hivemind at any time simply by unsubscribing from the hivemind mailing list
Evolution
- Any changes to the hivemind
codex must be proposed on the hivemind mailing list as "evolutions"
- Any proposed evolutions take
place automatically unless three people object to the evolution
- For each person actively
supporting an evolution, the number of objections is reduced by one
The hivemind mailing list
- The mailing list is for the
general discussion of issues relevant to the hivemind
- The list is not appropriate
for spam or forwarding of unrelated mail
- The list is not appropriate
for irrelevant advertising of products or services
- Basic rules of netiquette
should be followed when posting to the list