Closed Bug 29613 Opened 25 years ago Closed 24 years ago

Mozilla contributor form needs changes to legal wording

Categories

(mozilla.org :: Miscellaneous, task, P1)

Product:
mozilla.org
Component:
Miscellaneous
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nelson, Assigned: mitchell)

References

Details

There are several problems with the "CVS Contributor Form". 1. Section 5. Cryptography, is completely wrong now that the export regs have changed. It needs to be fixed. We cannot checkin any actual crypto code into OpenNSS until this is fixed. (I just crossed this section out completely before I signed the form.) 2. Section 1. There needs to be an alternative to the paragraph that begins "Contributors's Mozilla.org account username..." The alternative needs to allow a contribution without getting a CVS account at all. It needs to allow the contributor to designate another person who already has a mozilla CVS account to act as the contributor's agent or proxy, to check-in the contribution on the contributor's behalf. It needs to draw a clear distinction betweent the "Contributor" (who is responsible for "Ownership", "Identification" "legal code" etc.) and the agent who merely checks it in. 3. Section 3, identification, needs an added provision that allows the person who checks in code as the agent for another to clearly identify who the "Contributor" is, so that the real Contributor will be responsible for his contribution, and not the agent who does the checkin. Until this is fixed, I won't be able to checkin any code for Paul Kocher or others who've agreed to contribute code, but who don't want to actively become mozilla CVS users.
Raising to P1. This is urgent for OpenNSS.
Priority: P3 → P1
Status: NEW → ASSIGNED
This is a dup of bug 28955. But since it's got more detail, I'll close 28955 instead.
*** Bug 28955 has been marked as a duplicate of this bug. ***
Trying to figure out how to word section 5 so we're protected re (1) notifications to gov't required; and (2) change in regs. Bob, In general I think we need to require people to tell us when they add crypto. That way if we learn that we can or need to give notice only for crypto, we'll know where to look. I don't know if this is needed for the open nss project, where maybe we'll assume that it's all crypto. But we will need to know if people add crypto elsewhere. Like maybe in Bugzilla, which someone has already asked about. Or if some other crypto module arrives. maybe we should say something like: you'll tell us when you add crytpo to any module, or add an ew module containing crypto. thoughts?
mitchell: ping? Gerv
> maybe we should say something like: you'll tell us when you add crytpo to any > module, or add an ew module containing crypto. thoughts? yup, sounds good. You have to define when this has to happen. Before the checkin prevents that it gets forgotten, but has the potential to hold development up.
This needs to happen before check-in. Unfortuanate if it holds up development, but we can't have crypto stuff in the tree we don't know about.
So, is this fixed now, or are we still using the old contrib. form? Gerv
There's a new revision of the CVS contributor form that's been circulated, but it hasn't replaced the old form in http://www.mozilla.org/hacking/CVS-Contributor-Form.ps so, no, it isn't fixed yet.
Is the circulated form a draft, or is this lack of replacement merely website inertia? Gerv
While you're at it, please use HTML for the new form, perferably actually with a real <form> (it doesn't have to post anything, just provide the placeholders).
The new form has been done for a while, but apparently was not posted; Dawn is working on this. It is not in HTML because we ned to get it back unchanged, and using pdf is a generally accepted way legal departments do this. I know it's a pain.
Well, then, at the very minimum, double or triple space the lines that have blanks to be filled it, so that a human can print (or sign) in the space provided.
And please make sure, the PDF loads fine in gv (ghostview). Some PDF do, some don't. (Dunno, what the difference is.)
New form says: "[Committer will notify mozilla.org, if his account has been compromised]; until such notice Committer will be presumed to have taken all actions made through Committer's account.". I don't know, what "presumed" means legally, but I think, that's unfair. E.g. here in Germany (dunno about USA), if you lose your credit card, you have to notify the bank. For all actions before that, the card holder is liable up to 50$. Everything else pays the bank. Also: "[mozilla.org must approve] Code which may, under casual inspection, appear to be cryptographic." This means, mozilla.org has to approve most Mozilla code ;-P . Seriously, this is a bit vague.
s/pays/is paid by/
Dawn, Thanks for sending me a copy of the proposed new "Committer Form". It seems like a huge step in the right direction. The spacing of the lines with blanks seems very adequate. Thanks. There's one thing about it that I think MUST be fixed, however. The .PDF file is 1.89 Megabytes long for a single page. That's WAY too big, IMO. I suspect the program that makes the .pdf file can make it smaller. If that's the best (smallest) that the PDF maker program can do, then I suggest you try making a .GIF or .JPEG image of the page instead. I tried using Communicator's built-in JPEG converter to convert a screen capture of the page image to a JPEG image. At "medium quality" the .JPG is 252KB. At "High quality" it's 664KB, or only 1/3 of the pdf file size.
The reason the file is so big is that I saved the fonts as outlines which I thought would help avoid problems for people with broken pdf readers. But I guess that's unnecessary. I am assuered that embedded fonts in postscript is a perfectly normal thing. I'll resave this and it should be a normal size.
the latest version is here: http://dsl081-068-125-sfo1.dsl-isp.net/mozilla/hacking/CVS-Contributor-Form.pdf its still too large but removing the word "draft" reduces it to a reasonable size.
a new contributor form has been checked in. its still larger than i'd like it to be, but it works. The smaller version didn't work with ghostscript. In any case, the wording of the document is all set, so marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.