Kalle asked (via IRC) that I should send him the assignment papers from GNU. Since the ssh key on this computer had not been transfered to gnu I had to do that first and wait for access....
well, here I am. And more importantly, the requested papers are attached:
/hesa
.... when scopying the files from fencepost.gnu.org I created a dir. I called it copyass and realised only now how awkard the name was ;)
Henrik Sandklef wrote:
Hi all,
Starting point:
Xnee is a piece of software written by me. Copyright belongs to me.
Jon wrote some lines of code for Xnee. Jon is Norwegian. Jon's code was written in Sweden.
Question
To transfer Jon's copyright to me I need to write a copyright assignment.
The assignment used in GNU is US centric (e.g there's no "ideel upphovsrätt" over there).
Can I (still) use the GNU assignment paper? .. or should I write a new one?
/hesa
Sweden mailing list Sweden@fsfeurope.org https://mail.fsfeurope.org/mailman/listinfo/sweden
Copyright Assignment Administration
located at: /gd/gnuorg/assign.admin
Table of Contents
1. FSF's policy on copyright assignment 2. Overview of the assignment process
3. Applications and files used by the Assignment Administrator 3.1 RT Application 3.2 Copyright.list 3.3 Copyright Spreadsheet 3.4 Assignment Templates 3.5 Maintainers.txt
4. Issuing an assignment 4.1 What happens prior to the request for an assignment? 4.2 Explanation of the completed questionnaire 4.3 Responding to the request for an assignment 4.4 Producing the assignment 4.5 Issuing the assignment
5. Receiving assignment and disclaimer forms 5.1 Updating copyright.list 5.2 Copying and filing 5.3 Completion of the assignment
6. Miscellaneous
1. FSF's Policy on Copyright Assignment
FSF's Legal Counsel, Eben Moglen, states the importance of the assignment process for the Free Software Foundation:
'Under US copyright law, which is the law under which most free software programs have historically been first published, there are very substantial procedural advantages to registration of copyright. And despite the broad right of distribution conveyed by the GPL, enforcement of copyright is generally not possible for distributors: only the copyright holder or someone having assignment of the copyright can enforce the license. If there are multiple authors of a copyrighted work, successful enforcement depends on having the cooperation of all authors.
In order to make sure that all of our copyrights can meet the record keeping and other requirements of registration, and in order to be able to enforce the GPL most effectively, FSF requires that each author of code incorporated in FSF projects provide a copyright assignment, and, where appropriate, a disclaimer of any work-for-hire ownership claims by the programmer's employer. That way we can be sure that all the code in FSF projects is free code, whose freedom we can most effectively protect, and therefore on which other developers can completely rely.'
2. Overview of the Assignment Process
Currently, the assignment correspondence workload is managed through the use of the RT ticketing application, which captures and displays email correspondence. Most often the Contributor sends an initial email to the Assignment Administrator, requesting an assignment. The email includes a completed questionnaire supplied by the Maintainer of the gnu program. This questionnaire is designed to supply the information required to compile and issue the assignment. The assignment is then drafted and snail mailed to the Contributor. An email is also sent to the Contributor that may include an employer disclaimer, depending upon the answers contained in the questionnaire. Upon receipt of the assignment the Contributor reads and signs the document and returns it to the FSF. Once the assignment has been received and signed on behalf of the FSF, the next step is to update the filing system. Firstly the details of the assignment are recorded in a computer file 'copyright.list', which is the master list of all the FSF's assignment records. Then the original assignment is photocopied and filed. The Contributor and Maintainer are then both contacted informing them that the assignment process is complete. The Maintainer needs to be contacted so that they are free to incorporate the changes of the Contributor into the gnu program, being unable to do so before the assignment process is complete. Finally a thankyou letter and a copy of the paperwork is snail mailed to the Contributor.
3. Applications and Files used by the Assignment Administrator
3.1 RT Application (http://rt.gnu.org/). This application captures in a 'Copyright' queue, all correspondence emailed to the Assignment Administrator, and is the primary system through which communications are undertaken. RT creates a search able index and archives all assignment correspondence, and allows for the structured management of the work load. The main screen of the Copyright Queue is the search screen showing all 'New' and 'Open' matters. The program provides each request a unique identification number (Ticket Number). The following email addresses are captured by RT and listed in the Copyright queue: assignments@fsf.org; fsf-records@fsf.org; copyright-clerk@fsf.org.
3.2 Copyright.list (located on 'fencepost') - This document contains an abridged list of all assignments and disclaimers held by the FSF; it is the master list. The list is presented in a strict format that MUST be followed precisely. It is open to the community and is used frequently by the Maintainers to check that the Contributor has in fact made the assignment.
3.3 Copyright-Spreadsheet (located in the Assignment Administrators Home Folder) - The spreadsheet allows for the Administrator to have a summary of the progress of the assignments. Furthermore, it allows for the reporting of various statistics as they relate to the assignment process, e.g. number of assignments processed in a given time period, average time taken to process assignments.
3.4 Assignment Templates - Only approved standard assignment text should be used by the Administrator. These texts are held in templates and include detailed instructions for their use. There locations are listed here (all located on 'spider'):
/office/Forms/Copyright/Forms and Templates/assign.changes.manual
/office/Forms/Copyright/Forms and Templates/assign.future.everything
/office/Forms/Copyright/Forms and Templates/assign.image
/office/Forms/Copyright/Forms and Templates/assign.joint.separate
/office/Forms/Copyright/Forms and Templates/assign.logo
/office/Forms/Copyright/Forms and Templates/assign.manual
/office/Forms/Copyright/Forms and Templates/assign.translation.manual
/office/Forms/Copyright/Forms and Templates/corpassign.USE(past only)
/office/Forms/Copyright/Forms and Templates/corpassign.future(past & future)
/office/Forms/Copyright/Forms and Templates/corpassign.program
/office/Forms/Copyright/Forms and Templates/empdisclaim.program
/office/Forms/Copyright/Forms and Templates/newassign.changes (past only)
/office/Forms/Copyright/Forms and Templates/newassign.future.(past & future)
/office/Forms/Copyright/Forms and Templates/newassign.program.individual
/office/Forms/Copyright/Forms and Templates/template.disclaimer (this is for an individual to disclaim their Intellectual Property Interest in some work)
3.5 Maintainers.txt (located on 'fencepost') - This lists Maintainers of the gnu programs.
4. Issuing an Assignment
An assignment is issued in response to a request from a Contributor. That request comes in the form of a completed questionnaire emailed to the Assignment Administrator.
4.1 What happens prior to the request for an assignment? The following is an exert of Information For Maintainers from maintain.txt, also located at http://www.gnu.org/prep/maintain_toc.html
'If you maintain an FSF-copyrighted package, then you should follow certain legal procedures when incorporating legally significant changes written by other people. This ensures that the FSF has the legal right to distribute the package, and the standing to defend its GPL-covered status in court if necessary.
Before incorporating significant changes, make sure that the person who wrote the changes has signed copyright papers and that the Free Software Foundation has received and signed them. We may also need a disclaimer from the person's employer.
To check whether papers have been received, look in `/gd/gnuorg/copyright.list'. If you can't look there directly, fsf-records@gnu.org can check for you. Our clerk can also check for papers that are waiting to be entered and inform you when expected papers arrive.
The directory `/gd/gnuorg' is found on the GNU machines; if you are the Maintainer of a GNU package, you should have an account on them. Contact accounts@gnu.org if you don't have one. (You can also ask for accounts for people who help you a large amount in working on the package.) In order for the Contributor to know person should sign papers, you need to ask for the necessary papers. If you don't know per well, and you don't know that person is used to our ways of handling copyright papers, then it might be a good idea to raise the subject with a message like this:
Would you be willing to assign the copyright to the Free Software Foundation, so that we could install it in program? or Would you be willing to sign a copyright disclaimer to put this change in the public domain, so that we can install it in program?
If the Contributor wants more information, you can send per `/gd/gnuorg/conditions.text', which explains per options (assign vs. disclaim) and their consequences.
Once the conversation is under way and the Contributor is ready for more details, you should send one of the templates that are found in `/gd/gnuorg'. This section explains which templates you should use in which circumstances. Please don't use any of the templates except for those listed here, and please don't change the wording.
Once the conversation is under way, you can send the Contributor the precise wording and instructions by email. Before you do this, make sure to get the current version of the template you will use! We change these templates occasionally--don't keep using an old version.
For large changes, ask the Contributor for an assignment. Send per a copy of the file `/gd/gnuorg/request-assign.changes'.
For medium to small changes, request a disclaimer by sending per the file `/gd/gnuorg/request-disclaim.changes'.
If the Contributor is likely to keep making changes, person might want to sign an assignment for all per future changes to the program. So it is useful to offer per that alternative. If person wants to do it that way, send per the `/gd/gnuorg/request-assign.future'.
When you send a `request-' file, you don't need to fill in anything before sending it. Just send the file verbatim to the Contributor. The file gives per instructions for how to ask the FSF to mail per the papers to sign. The `request-' file also raises the issue of getting a copyright disclaimer from the Contributor's employer.'
***END OF REPRINT***
4.2 Explanation of the completed questionnaire
The 'request-' file issued by the Maintainer, as outlined in 4.1, directs the Contributor to send an email to the Assignment Administrator. That email, a completed questionnaire, is captured by the RT application.
Sometimes, a Contributor is not referred by a Maintainer, and instead contacts the FSF directly. In that case, one should send a copy of: /office/Forms/Copyright/Forms and Templates/Maintainer.mistrained.instructions.
If we receive a request for an assignment outside of the RT application then one should create a ticket for the request in the RT through the 'create a ticket function', and then proceed as normal. This ensures that RT contains a complete record of assignments.
A Contributor is an individual who assigns their work on a gnu program to the FSF. A Maintainer is one who manages a gnu program, incorporating the work of the Contributor into the program.
The following is a an explanation of the questionnaire with a description of the relevance of the headings and answers that must be evaluated by the Assignment Administraor:
Subject: The subject line of the email should contain the full
legal name of the contributor. If there is any doubt about the name, then this should be raised immediately.
REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES This tells you what
type of assignment form is called for. The list of templates is shown in 3.4. The most frequently requested assignment is one to cover past and future changes.
[What is the name of the program or package you're contributing to?]
This question is included to determine to which GNU package the individual will be contributing.
[Did you copy any files or text written by someone else in these
changes? > Even if that material is free software, we need to know about it.] This is included to ensure that the assignment will be valid and that no others can claim ownership to the work.
[Do you have an employer who might have a basis to claim to own >
your changes? Do you attend a school which might make such a claim?] This is included to ensure that no others can claim the work of the Contributor; if there is an employer or university in the picture then in the responsive email to the Contributor one must include a employer/university disclaimer and instructions for its completion. The employer/university disclaimers are sent via email.
[For the copyright registration, what country are you a citizen of?]
This question is needed pursuant to copyright law and is recorded in copyright.list
[What year were you born?] Individuals under eighteen (18) years of
age cannot make a binding contract (which is what an assignment is) without a disclaimer by the parents or legal guardian. (see: III.F.vii)
[Please write your email address here.] This is for contact and
copyright.list purposes.
[Please write your postal address here.] This is so we can contact
the individual with the assignment paperwork
[Which files have you changed so far, and which new files have you
written > so far?] This is included for inclusion in copyright.list and as a means of providing the Maintainer with a easy way of learning of the current work of the Contributor
4.3 Responding to the Request for an Assignment
The Administrator initially records the RT application number, Last Name, Software Package, and date of first contact in the copyright-spreadsheet. Following review of the answers contained in the Contributor's email a determination as to whether the FSF will issue the assignment is in order.
If there are concerns about the need for disclaimers or about additional information, then send the Contributor an email in order to clarify the situation, note any thoughts or questions using the comment feature on RT.
As a general rule assignments are issued only for gnu programs. To see if the instant issue is an exception to the general rule check with Bkuhn or RMS. As mentioned above, there are precise guidelines that a program must fulfill in order to be accepted as a gnu program. If the program is not a current gnu program then refer them to maintainers@gnu.org, for investigation and evaluation.
Before issuing the assignment and assuming that one does not currently have an encyclopedic knowledge of gnu programs, one must then check to see if the assignment is for a valid program. There are three places one can check on information about a programs nature.
- Maintainers.list - copyright.list. - Free Software Directory - http://www.gnu.org/directory/.
IMPORTANT: Never alter the language of an assignment template without joint approval from RMS and legal counsel.
There is a listing of alternative text previously approved for corporate assignments, located at: home/tedt/office/Forms/Copyright/Forms and Templates/prior.app.lang. This listing of alternative text shows what legal counsel has previously deemed acceptable.
IMPORTANT: Each new request for altered text must still be sent to RMS for approval, even if legal counsel has approved the text, as there may be a political issue at stake.
4.4 Producing the Assignment
The following outlines the steps to produce a typical assignment form covering a Contributors 'Past & Future' work:
Call up the appropriate assignment template for the type of assignment as listed above in section 3.4. In this instance: /office/Forms/Copyright/Forms and Templates/newassign.future
Add the last name and RT ticket number in the upper right hand corner of the template (for future referencing and filing purposes)
In the 1st paragraph of the text (three lines from beginning) locate the space for the full legal name of the Contributor, and insert that text
Enter the name of the program/package that the assignment is for in the title of the text, next to the word 'ASSIGNMENT' (i.e. ASSIGNMENT - GNU Emacs)
Enter the name of the program/package in the para. 1. (a) on the 3rd line
If the Contributor is a minor then include the following text at the end of the assignment form:
Agreed: [relative signature] Nature of relationship to Contributor (ex:mother, father, etc):
IMPORTANT : A parent or guardian may sign the form. It is important to have the nature of the relationship on the form ("Parent", "Father","Mother", "Guardian").
Be sure to advise the Contributor that we will want them to sign another form once they turn 18 (assuming this is a "past and future changes" form that is being signed). When the form is completed, the clerk should insert a warning in copyright.list that another form will be needed and state the Contributor's status as a minor. Also warn the Maintainers that they should not accept future changes from this person after their 18th birthday.
Save the file using the following naming convention: year(4 digit).last name (contributor).package name.assignment type (p=past; f=future; pf=past&future i.e. 2003.Smith.Emacs.pf).
If there are multiple same-last names for the same package then include after the last name the first initial of the Contributor, thus 2003.Smith.J.Emacs.pf
Print the text of the assignment onto FSF letter headed paper.
4.5 Issuing the Assignment
An email confirmation should be sent via RT to the Contributor. This informs them that they will shortly receive the assignment paperwork and further instructions in the post. If applicable the email should also include the text and instructions for an employer disclaimer. The steps taken to issue the assignment are described here, together with actions taken within the RT application :
Click the [Reply to email] icon in RT.
Change status of ticket from "new" to "stalled." - this status change allows the to do list to be manged, since a ticket listed as stalled does not show on ones search screen. When correspondence comes in related to the ticket the status of the ticket is automatically changed from 'stalled' to 'open' and reappears on the search screen notifying the Administrator that further action needs to be taken.
Change classification of ownership on RT from unowned to owned by you.
Insert email text
- If there is no disclaimer needed then use: home/tedt/office/Forms/Copyright/Forms and Templates/standard.response.
- If there is an employer or university disclaimer then use: home/tedt/office/Forms/Copyright/Forms and Templates/standard.response&empdisclaimer
Compile the assignment form, instruction letter (located in file folder labeled Assignment Instruction , #9 FSF addressed envelope, stickers and promotional materials in regular envelope for mailing.
If the mail is INTERNATIONAL then stamp envelope with the airmail letter post stamp located in the mailing center.
Post the assignment, and lastly update "Action Taken" and "Outstanding Question" in the copyright-spreadsheet, as required.
5. Receiving Assignment and Disclaimer Forms
The following indicates the process for handling incoming assignment forms:
Dating - Upon receipt of an assignment or disclaimer form, stamp it with the received-date stamp
Signing %G–%@ Check that the assignment has been properly signed and dated by the Contributor. Check if an employer disclaimer is outstanding. If it is, then place the assignment in $(B!H(BAwaiting Disclaimer$(B!I(B folder. If the assignment is on FSF letterhead then place assignment in the "To Sign" folder for Bkuhn's signature. If the assignment is not on FSF letterhead hold the letter for signature by RMS, reading through the assignment noting any deviations from the standard text, to aid in RMS's review.
5.1 Updating Copyright.list
After the assignment has been signed, the next step is to update copyright.list. The three main types of records listed here are assignments, translation disclaimers and disclaimers (both individual and employer). The format of the list is designed to allow for easy searching and the creation of reports based on the data, thus the strict adherence to the format detailed below is ESSENTIAL.
Assignment Format:
PACKAGE NAME (capitalized) [one tab space] First & Last Name [one tab space] Year- Month-Date [one tab space] Date Signed by Contributor ---new line-- Description of assignment [use previously established wording for description] --new line-- Email address of contributor
EMACS John Doe USA 1947 2003-08-01 Assigns past and future changes. jd@email.com
If the Contributor has already made "changes" or created "new" files [this is determined by examining the answer to the last question in the Contributor's email], then these must be included on copyright.list; the format is as follows:
EMACS John Doe USA 1947 2003-08-01 Assigns past and future changes. (changed: 1st change [enter] 2nd change [enter] last change [enter] New: 1st new [enter] last new) jd@email.com Software Disclaimer Format:
PACKAGE NAME (capitalized) [one tab space] Name of Disclaimer [one tab space] Year- Month-Date one tab space] Date signed Description of disclaimer [use previously established wording for description]
EMACS Sleepycat Software, Inc. 2003-08-16 Disclaims changes or enhancements to free software already in existence and up to two years after date of disclaimer made by John Doe.
- If the disclaimer applies to all free software then use ANY for package name
- If the disclaimer applies to multiple GNU packages, then list them all
Individual Disclaimer in Software:
PACKAGE NAME (capitalized) [one tab space] First Last Name [one tab space] date disclaimer signed email address
EMACS Jon Doe 2003-07-10 Disclaims all intellectual property interest in changes and enhancements. jd@debian.org
Translation Disclaimer Format:
TRANSLATIONS [one tab space] Name of translator [one tab space] year- month-date Disclaimer. {one space} [language abbreviation] Email Address
TRANSLATIONS Polly Lingual 2003-08-01 Disclaimer. [fr] polly@lingual.fr
- check http://www.loc.gov/standards/iso639-21/englangn.html for listing of language abbreviations (the 2nd column shown contains the proper codes to use).
Once entered, copy text and insert into the body of an email which should be sent (with a brief description in the subject header of what the material is) to translations@iro.umontreal.ca
5.2 Copying and Filing
Copy the original document as follows:
for each ASSIGNMENT received make two (2) photocopies for each DISCLAIMER received make three (3) photocopies for each TRANSLATION received make three (3) photocopies. Documents are filed under YEAR and then alphabetically by LAST NAME.
Assignments Forms:
The original document goes in the fireproof file cabinet located in the third floor office. Of the two photocopies, one is sent to the Contributor and the other is filed alphabetical by Last Name in the assignment duplicates file. These duplicates are regularly removed off-site and stored, currently, with Novalis.
Disclaimers:
File the original disclaimer behind the corresponding assignment in the fireproof file cabinet. Of the three photocopies, one is sent to the Contributor, a copy goes in the assignment duplicates, and the final photocopy goes in the disclaimer duplicates file filed under the last name of the Contributor or if the Contributor is a corporation under the corporation's name.
Translations:
The original document goes in the fireproof file cabinet. Of the three photocopies, one is sent to the Contributor, a copy goes in the assignment duplicates, and the final copy is filed by last name in the disclaimer duplicates file.
5.3 Completion of the Assignment
Email the Contributor and Maintainer to confirm the completion of the assignment process.
When replying change the RT ticket status from stalled to resolved. This will archive the correspondence.
The subject heading of that email should also be changed so that it reads "[Contributer name] assigns [TYPE OF ASSIGNMENT] to [NAME OF PROGRAM]" (i.e. Jane Doe assigns past and future changes to Emacs)
The body of the thank you email can be found at: home/tedt/copryrightlistofficedocs/finalemail Mark a carbon/courtesy copy of the email to the package Maintainer
The package Maintainer can be found by searching Maintainers.txt.
At the bottom of the "thank you email" be sure to include the summary of useful information for the maintainer about the contributor; name of Contributor, contact email address, and description of the work completed.
The final mailing to the Contributor should include a photocopy of the assignment, disclaimer, or translation as well as a thank you letter, located on spider at:
/office/Forms/Copyright/Forms andTemplates/standard.thankyou
5.4 Miscellaneous
Questions %G–%@ A list of frequently asked questions about the assignment process, text used in assignments/disclaimers and other random things, is contained in a file on spider:
/office/Forms/Copyright/assignments.faq
Merging Tickets - If multiple RT numbers are created in response to what is actually a single matter, then use the merge function to combine all the tickets to create a master RT ticket.
The Copyright-Spreadsheet uses notations in its Status Columns:
AR - awaiting receipt of documents Sign - to be signed by appropriate official to file - copyright.list updated, final email sent, copy mailed filed - filed! res - non-assignment matter completed missing - documents outstanding
Disclaimer Updating - The Assignment Administrator must review the list of disclaimers within copyright.list, noting all disclaimer's that have lapsed and seek new disclaimers from the relevant Contributor.
Maintainers should be notified of lapsed disclaimers and warned not accept any contributions until the paperwork is updated.
Stalled List - The Assignment Administrator must periodically go through the stalled listing of RT tickets. This ensures completion of outstanding paperwork by the Contributor.
The way to assign copyright to the Foundation is to sign an assignment contract.
Below is the assignment contract that we usually use. You would need to print it out, have an appropriate person sign it, and snail it to:
Copyright Clerk Free Software Foundation 59 Temple Place, Suite 330 Boston, MA 02111-1307 USA ASSIGNMENT
For good and valuable consideration, receipt of which is acknowledged, <such and such corp> (the "Assigner"), hereby transfers to the Free Software Foundation, Inc. (the "Foundation") its entire right, title, and interest (including all rights under copyright) in the computer program <name> (the "Program"), subject to the conditions below. The work hereby assigned shall further include any future changes and/or enhancements hereafter made by the Assigner and transmitted by the Assigner to the Foundation for the Foundation's use. It shall include any accompanying documentation files and supporting files as well as the actual program code.
The Foundation grants the Assigner a non-exclusive irrevocable license back, royalty-free, to use the Program without restriction.
For the purposes of this assignment, a work "based on the Program" means any work that in whole or in part incorporates or is derived from all or part of the Program.
The Foundation agrees that all distribution of the Program, or of any work "based on the Program", that takes place under the control of the Foundation or its agents or assignees, shall be on terms that explicitly and perpetually permit anyone possessing a copy of the work to which the terms apply, and possessing accurate notice of these terms, to redistribute copies of the work to anyone on the same terms. These terms shall not restrict which members of the public copies may be distributed to. These terms shall not require a member of the public to pay any royalty to the Foundation or to anyone else for any permitted use of the work they apply to, or to communicate with the Foundation or its agents in any way either when redistribution is performed or on any other occasion.
The Foundation agrees that any program "based on the Program" offered to the public by the Foundation or its agents or assignees shall be offered in the form of machine-readable source code, in addition to any other forms of the Foundation's choosing. However, the Foundation is free to choose at its convenience the media of distribution for machine-readable source code.
The Foundation agrees to give or send the Assigner, upon reasonable prior notice and payment of a fee no more than twenty times the cost of the necessary materials and postage, a copy of any or all of the works "based on the Program" that the Foundation offers to the public or that it has offered within the past six months, or that it distributed for the first time within the past six months. For works that are programs, the machine-readable source code shall be included. Such a request shall detail whether the Assigner wishes to receive all such works or specific works. The choice of works to request may affect the cost and therefore the fee.
The Assigner hereby agrees that if it has or acquires hereafter any patent or interface copyright or other intellectual property interest dominating the Program (or use of the same), such dominating interest will not be used to undermine the effect of this assignment, i.e. the Foundation and the general public will be licensed to use, in the Program and its derivative works, without royalty or limitation, the subject matter of the dominating interest. This license provision will be binding on the assignees of, or other successors to, the dominating interest, as well as on the Assigner.
The Assigner hereby represents and warrants that it is the sole copyright holder for the Program and that it has the right and power to enter into this contract. The Assigner hereby indemnifies and holds harmless the Foundation, its officers, employees, and agents against any and all claims, actions or damages (including attorney's reasonable fees) asserted by or paid to any party on account of a breach or alleged breach of the foregoing warranty. The Assigner makes no other express or implied warranty (including without limitation, in this disclaimer of warranty, any warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE).
For the Assigner, <name and title> <signature and date>
ACCEPTED: FREE SOFTWARE FOUNDATION - Thanks for contributing to the GNU project!
Bradley Kuhn, Executive Director
[Please write your snail address here, so I can snail a copy back to you.]