Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.cis.okstate.edu!newsfeed.ksu.ksu.edu!news.mid.net!sbctri.tri.sbc.com!newspump.wustl.edu!gumby!newsxfer.itd.umich.edu!news.mathworks.com!bloom-beacon.mit.edu!senator-bedfellow.mit.edu!usenet
From: mycroft@zygorthian-space-raiders.mit.edu (Charles M. Hannum)
Newsgroups: comp.unix.bsd.netbsd.misc
Subject: Regarding the agreement (was Re: followup from censored port-i386@Netbsd.ORG)
Date: 04 Jul 1996 20:40:28 -0400
Organization: Massachvsetts Institvte of Technology
Lines: 142
Message-ID: <el2k9wjh6rn.fsf_-_@zygorthian-space-raiders.MIT.EDU>
References: <DERAADT.96Jun23070919@zeus.theos.com>
<DERAADT.96Jun24082701@zeus.theos.com>
<x7dpw6doi0t.fsf@glacier.MIT.EDU> <4revjl$fva@panix2.panix.com>
<DERAADT.96Jul3235828@zeus.theos.com>
NNTP-Posting-Host: zygorthian-space-raiders.mit.edu
X-Newsreader: Gnus v5.2.22/Emacs 19.30
Just to clear up a few misconceptions regarding the infamous
`agreement'...
1) The idea for the agreement came originally from Chris, during a
phone call with Theo. That Chris indicated we were going to write one
before consulting the other members of `core' was a mistake on his
part. Or perhaps he didn't, and Theo misinterpreted it that way;
since I don't know the contents of the call, I have no way to be sure
of this. In fact, the first mention of it by Theo in the `core' list
archives refers to some private communication from Chris that I have
never seen.
2) Theo has repeatedly lambasted us about it on the basis that the
agreement was ridiculous and (in my words) degrading and insulting.
In short, the agreement would have been equivalent to `I will be nice.
- X. X. X.' To quote Chris, `The point of an agreement of the one
such as i proposed is to make it clear -- to everybody -- what the
policy is for project-associated behaviour standards.'
In fact, such an agreement doesn't exist. I am largely responsible
for that. I find it extremely insulting, and I would personally
refuse to sign it. Even if I wanted to, I would therefore be obliged
not to ask anyone else to.
3) If you actually *read* the current agreement (included below),
you'll see that it is nothing more than a (mostly necessary) piece of
legal bookkeeping.
4) As for why it took so long to generate, that's mostly because there
were some internal problems in the `core' group. These problems have
been resolved. If other people were given accounts during that time,
all I have to say is:
a) Too bad. The NetBSD project is not run by bureaucracy.
b) Legal agreements are between legal entities. Before the
NetBSD Foundation existed, there was no tangible legal entity to
act as the counterparty to the agreement.
> Who hasn't signed it yet?
That's private business between the NetBSD Foundation and said
parties, and it will *not* be discussed with other people.
The text of the actual agreement follows.
-----8<-----snip-----8<-----snip-----8<-----snip-----8<-----snip-----8<-----
NetBSD Developer's Agreement
Section I - Definition of terms
For the purpose of this document the following terms are defined:
(a) `The Developer' is defined as someone to whom a NetBSD
Developer's Account has been granted. The Developer
is considered to be a representative of The NetBSD Foundation
when conducting NetBSD Foundation business and/or development
efforts.
(b) `Core' is defined as the group known as the NetBSD Core Group,
acting as an agent of The NetBSD Foundation.
(c) `The Repository' is defined as the collection of source code
and historic records contained in the NetBSD master source
repository.
(d) `Commit' is defined as the act of adding to, removing
from, or otherwise altering the contents of The Repository.
(e) `Tainted source code' is defined as source code for which
redistribution by either The Developer or The NetBSD Foundation
would be unlawful.
(f) `The NetBSD Project' is defined as development or any other
activity related to the NetBSD operating system.
Section II - Purpose of a NetBSD Developer's Account
NetBSD Developer's Accounts are granted for the purpose of developing,
maintaining, advising, and otherwise improving the NetBSD Project.
A NetBSD Developer's Account provides:
(a) access to some or all of the private NetBSD mailing lists,
internal documentation, and internal planning and
strategy of The NetBSD Foundation, and
(b) access to The Repository and NetBSD distribution mechanisms.
Section III - Responsibilities of The Developer
The Developer has the following responsibilities:
(a) The Developer will not disclose information private
to the NetBSD Foundation with out the explicit prior permission
of Core. Private information is defined as information
that is accessible to The Developer but is not available
to the general public, or previously private information that
was released in violation of the agreement by anyone.
(b) The Developer will not commit tainted source code to
The Repository.
(c) As a NetBSD Foundation representative, The Developer will
conduct himself accordingly when carrying out Foundation
business or development efforts.
(d) The Developer may not redistribute a particular piece
of source code or diffs between two pieces of source code
(heretofore referred to as `The Code') obtained from
The Repository if:
(1) redistribution of The Code by either The Developer
or the NetBSD Foundation would be unlawful, or
(2) Core has requested that The Developer not
redistribute The Code.
Section IV - Agreement between The Developer and The NetBSD Foundation, Inc.
I, the under-signed, accept the privileges and responsibilities associated
with having a NetBSD Developer's Account as outlined above in Sections
II and III. I understand that either myself or The NetBSD Foundation
reserve the right to terminate this agreement and my NetBSD Developer's
Account at any time. After termination of this agreement by either party,
clauses III(a), III(b), and III(d) shall remain in effect.
_____________________________ ________________________________
(print name) (signature and date)
-----8<-----snip-----8<-----snip-----8<-----snip-----8<-----snip-----8<-----
--
- Charles M. Hannum
Director, The NetBSD Foundation