"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "CONTRIBUTING" between
RPerl-5.000000.tar.gz and RPerl-5.002000.tar.gz

About: RPerl is an optimizing compiler for the Perl 5 programming language (converting Perl 5 source code into C++).

CONTRIBUTING  (RPerl-5.000000):CONTRIBUTING  (RPerl-5.002000)
<<<=== OVERVIEW ===>>> <<<=== COPYRIGHT CONTRIBUTIONS ===>>>
[ BEGIN, RPERL FAMILY COPYRIGHT ASSIGNMENT AGREEMENT ]
By contributing to this repository, you agree that any and all such Contribution
s and derivative works thereof shall immediately become part of the RPerl Family
of software and documentation, and you accept and agree to the following legall
y-binding terms and conditions for all Your present and future Contributions:
1. Definitions.
"You" or "Your" shall mean the copyright owner, or legal entity authorized by th
e copyright owner, that is making this Agreement. For legal entities, the entit
y making a Contribution and all other entities that control, are controlled by,
or are under common control with that entity are considered to be a single Contr
ibutor. For the purposes of this Agreement, "control" means (i) the power, dire
ct or indirect, to cause the direction or management of such entity, whether by
contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the o
utstanding shares, or (iii) beneficial ownership of such entity.
The "RPerl Family of software and documentation" (hereinafter the "RPerl Family"
) is defined as all copyrightable works identified as "part of the RPerl Family"
immediately following their copyright notice, and includes but is not limited t
o the RPerl compiler, the MathPerl suite, the PhysicsPerl suite, the SciencePerl
suite, other RPerl application suites, application programming interfaces betwe
en RPerl and any other technology, and all associated RPerl software.
"Team RPerl" is defined as all duly-authorized contributors to the RPerl Family,
including You after making Your first Contribution to the RPerl Family under th
e terms of this Agreement.
"Team RPerl Leadership" is defined as all duly-authorized administrators and off
icial representatives of the RPerl Family, as listed publicly on the most up-to-
date copy of the RPerl.org website.
"Contribution" shall mean any original work of authorship, including any changes
or additions or enhancements to an existing work, that is intentionally submitt
ed by You to this repository for inclusion in, or documentation of, any of the p
roducts or services which are part of the RPerl Family (hereinafter the "Work").
For the purposes of this Agreement, "submit" or "submitted" means any form of
electronic, verbal, or written communication sent to Team RPerl Leadership, incl
uding but not limited to communication on electronic mailing lists, source code
revision systems, and issue tracking systems that are managed by, or on behalf o
f, Team RPerl Leadership for the purpose of discussing and improving the Work, b
ut excluding communication that is conspicuously marked or otherwise designated
in writing by You as "Not a Contribution".
2. Assignment of Copyright. Subject to the terms and conditions of this Agreeme
nt, and for good and valuable consideration, receipt of which You acknowledge, Y
ou hereby transfer to the individual named William N. Braswell, Jr. with a prima
ry place of residence in Cedar Park, Texas, USA (hereinafter "Braswell"), Your e
ntire right, title, and interest (including all rights under copyright) worldwid
e in all Your Contributions. The Work hereby assigned shall also include any fu
ture versions of these or any other Contributions hereafter made by You. Any de
rivative works of this Contribution prepared by You or Team RPerl shall be solel
y owned by Braswell and shall remain part of the RPerl Family.
You hereby agree that if You have or acquire hereafter any patent or interface c
opyright or other intellectual property interest dominating the software or docu
mentation contributed to by the Work (or use of that software or documentation),
such dominating interest shall not be used to undermine the effect of this assi
gnment, i.e. Braswell and all subsequent licensees shall be licensed to use, in
that software or documentation and their derivative works, without royalty or li
mitation, the subject matter of the dominating interest. This license provision
shall be binding on Your heirs, assignees, or other successors to the dominatin
g interest, as well as on You.
You hereby represent and warrant that You are the sole copyright holder for the
Work and that You have the right and power to enter into this legally-binding co
ntractual agreement. You hereby indemnify and hold harmless Braswell, his heirs
, assignees, or other successors and Team RPerl Leadership, the officers, employ
ees, and agents of any organization under the control of Braswell or owned in ma
jority by Braswell, against any and all claims, actions or damages (including at
torney's reasonable fees) asserted by or paid to any party on account of a breac
h or alleged breach of the foregoing warranty.
3. Grant of Patent License. Subject to the terms and conditions of this Agreeme
nt, You hereby grant to Braswell and to recipients of software distributed by Br
aswell a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocab
le (except as stated in this section) patent license to make, have made, use, of
fer to sell, sell, import, and otherwise transfer the Work, where such license a
pplies only to those patent claims licensable by You that are necessarily infrin
ged by Your Contribution(s) alone or by combination of Your Contribution(s) with
the Work to which such Contribution(s) was submitted. If any entity institutes
patent litigation against You or Braswell or Team RPerl Leadership or any other
entity (including a cross-claim or counterclaim in a lawsuit) alleging that you
r Contribution, or the Work to which you have contributed, constitutes direct or
contributory patent infringement, then any patent licenses granted to that enti
ty under this Agreement for that Contribution or Work shall terminate as of the
date such litigation is filed.
4. You represent that you are legally entitled to assign the above copyright and
grant the above patent license. If your employer(s) or contractee(s) have righ
ts to intellectual property that you create that includes your Contributions, th
en you represent that you have received official written permission to make Cont
ributions on behalf of said employer(s) or contractee(s) and that they have waiv
ed in writing all such rights for your Contributions to the RPerl Family and tha
t all such written permission(s) and waiver(s) are attached to your first Contri
bution, or that said employer(s) or contractee(s) have executed Team RPerl's Emp
loyer Copyright Disclaimer Agreement and it is attached to your first Contributi
on.
5. You represent that each of Your Contributions is Your original creation and i
s not subject to any third-party license or other restriction (including, but no
t limited to, related patents and trademarks) of which you are personally aware
and which are associated with any part of Your Contributions.
6. You agree to submit written notification to Team RPerl Leadership of any fact
s or circumstances of which you become aware that would make the representations
of this Agreement inaccurate in any respect.
[ END, RPERL FAMILY COPYRIGHT ASSIGNMENT AGREEMENT ]
<<<=== LEGAL OVERVIEW ===>>>
All RPerl Family software and documentation is legally copyrighted by original R Perl creator William N. Braswell, Jr. All RPerl Family software and documentation is legally copyrighted by original R Perl creator William N. Braswell, Jr.
To maintain the legal integrity and defensibility of the RPerl Family of softwar e and documentation, all contributors to the RPerl Family must assign copyright ownership to Mr. Braswell, thereby empowering him to pursue legal action against those who attempt to violate any RPerl Family copyright, license, or other inte llectual property rights. To maintain the legal integrity and defensibility of the RPerl Family of softwar e and documentation, all contributors to the RPerl Family must assign copyright ownership to William Braswell under the terms of the RPerl Family Copyright Assi gnment Agreement above, thereby empowering him to pursue legal action against th ose who attempt to violate any RPerl Family copyright, license, or other intelle ctual property rights.
This is the same strategy used by the Free Software Foundation for many GNU soft ware projects, as explained below: This is the same strategy used by the Free Software Foundation for many GNU soft ware projects, as explained below:
Why The FSF Gets Copyright Assignments From Contributors Why The FSF Gets Copyright Assignments From Contributors
By Professor Eben Moglen, Columbia University Law School By Professor Eben Moglen, Columbia University Law School
Copyright © 2001, 2008, 2009, 2014 Free Software Foundation, Inc. Copyright © 2001, 2008, 2009, 2014 Free Software Foundation, Inc.
The quoted text below is not modified, and is licensed under a Creative Commons Attribution-NoDerivs 3.0 United States License. The quoted text below is not modified, and is licensed under a Creative Commons Attribution-NoDerivs 3.0 United States License.
http://www.gnu.org/licenses/why-assign.en.html http://www.gnu.org/licenses/why-assign.en.html
http://creativecommons.org/licenses/by-nd/3.0/us/ http://creativecommons.org/licenses/by-nd/3.0/us/
"Under US copyright law, which is the law under which most free software program s have historically been first published, there are very substantial procedural advantages to registration of copyright. And despite the broad right of distrib ution conveyed by the GPL, enforcement of copyright is generally not possible fo r distributors: only the copyright holder or someone having assignment of the co pyright can enforce the license. If there are multiple authors of a copyrighted work, successful enforcement depends on having the cooperation of all authors. "Under US copyright law, which is the law under which most free software program s have historically been first published, there are very substantial procedural advantages to registration of copyright. And despite the broad right of distrib ution conveyed by the GPL, enforcement of copyright is generally not possible fo r distributors: only the copyright holder or someone having assignment of the co pyright 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 recordkeeping and other requirements of registration, and in order to be able to enforce the GPL m ost effectively, FSF requires that each author of code incorporated in FSF proje cts 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 ." In order to make sure that all of our copyrights can meet the recordkeeping and other requirements of registration, and in order to be able to enforce the GPL m ost effectively, FSF requires that each author of code incorporated in FSF proje cts 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 ."
<<<=== COMMITMENT TO FREE & OPEN SOURCE SOFTWARE ===>>> <<<=== COMMITMENT TO FREE & OPEN SOURCE SOFTWARE ===>>>
Mr. Braswell is committed to maintaining the free-and-open-source software (FOSS William Braswell is committed to maintaining the free-and-open-source software (
) basis of the RPerl Family. FOSS) basis of the RPerl Family.
If your RPerl Family contribution is accepted and merged into an official RPerl
Family source repository, then your contribution is automatically published on G
ithub with FOSS licensing, currently the same terms as Perl itself (your choice
of Artistic or GNU GPL licenses).
<<<=== ASSIGNMENT AGREEMENT ===>>>
The file named ASSIGNMENT.pdf contains the copyright assignment agreement. Plea se print the file on one page of paper, then use blue ink to clearly write your full legal name twice (both at the top and bottom), write the date, and sign you r signature. You may then submit the fully-executed ASSIGNMENT document either in original paper form via snail mail, or a high-resolution digital scanned copy via e-mail. If possible, please execute (sign) the ASSIGNMENT document in the presence of an official Notary Public, and have them notarize the appropriate ar ea at the bottom of the document. If your RPerl Family contribution is accepted and merged into an official RPerl Family source repository, then your contribution is automatically published onli ne with FOSS licensing, currently the same terms as Perl itself (your choice of Artistic or GNU GPL licenses).
<<<=== EMPLOYER DISCLAIMER ===>>> <<<=== EMPLOYER COPYRIGHT DISCLAIMER AGREEMENT ===>>>
The file named EMPLOYERS.pdf contains the employer disclaimer agreement. If you are employed, and either your job involves computer programming or you have exe cuted an agreement giving your employer rights to the software you create, then we must also receive a fully-executed copy of the EMPLOYERS agreement, using the same blue-ink signing and notarization method as the ASSIGNMENT document descri bed above. Please have the EMPLOYERS agreement signed by a vice president or ge neral manager in your organization. The file named EMPLOYERS.pdf contains the Employer Copyright Disclaimer Agreemen t. If you are employed or work as an independent contractor, and either your jo b involves computer programming or you have executed an agreement giving your em ployer or contractee rights to the software you create, then we must receive a f ully-executed copy of the EMPLOYERS agreement. Please print the file on one pag e of paper, and use blue ink to clearly write the entity's full name and address , followed by your full legal name. Then, have a vice president or general mana ger in your organization use blue ink to write the date, their full legal name a nd organizational title, and sign their signature. You may then submit the full y-executed EMPLOYERS document either in original paper form via snail mail (pref erable), or a high-resolution digital scanned copy via e-mail. If possible, ple ase execute (sign) the EMPLOYERS document in the presence of an official Notary Public, and have them notarize the appropriate area at the bottom of the documen t.
<<<=== OTHER CONTRIBUTORS ===>>> <<<=== OTHER CONTRIBUTORS ===>>>
If any other people have written software source code or documentation as part o f your RPerl contribution, then they and their respective employers must also al l sign and submit their own copies of the ASSIGNMENT and EMPLOYERS agreements. If anyone other than yourself has written software source code or documentation as part of your RPerl Family contribution, then they must submit their contribut ions themselves under the terms of the RPerl Family Copyright Assignment Agreeme nt above, and their respective employer(s) or contractee(s) must also all sign a nd submit their own copies of the Employer Copyright Disclaimer Agreement.
Please be sure you DO NOT STUDY OR INCLUDE any 3rd-party or public-domain intell ectual property as part of your RPerl contribution, including but not limited to : source code; documentation; copyrighted, trademarked, or patented components; or technical concepts. In other words, don't copy someone else's work and don't study someone else's work while doing your own. All your work must be 100% ori ginal. Please be sure you DO NOT STUDY OR INCLUDE any 3rd-party or public-domain intell ectual property as part of your RPerl Family contribution, including but not lim ited to: source code; documentation; copyrighted, trademarked, or patented compo nents; or technical concepts. In other words, don't copy someone else's work an d don't study someone else's work while doing your own. All your work must be 1 00% original.
<<<=== RECOGNITION ===>>> <<<=== RECOGNITION ===>>>
Once we have received all necessary assignment agreements and employer disclaime r agreements, then we will begin the process of reviewing any software pull requ ests you have submitted through the official RPerl repository on Github. Upon m erging of your pull request(s), you will automatically be listed by Github as on e of the official RPerl contributors, and you will also be manually added to the AUTHORS file. Once we have received your contribution under the terms of the RPerl Family Copy right Assignment Agreement above, as well as any necessary Employer Copyright Di sclaimer Agreement(s), then we will begin the process of reviewing any software pull requests you have submitted through the official RPerl Family repositories. Upon merging of your pull request(s), you should automatically be listed in th e repository as one of the official Team RPerl contributors, and you will also b e manually added to the AUTHORS file.
<<<=== SUBMISSION ===>>> <<<=== SUBMISSION ===>>>
When you are ready to submit the signed agreement(s), please answer the followin g 12 questions about yourself and your RPerl contribution, then include your ans wers in the body of your e-mail or on a separate sheet of paper in snail mail, a nd send it all to one of the addresses below. When you are ready to submit the signed agreement(s), please answer the followin g 12 questions about yourself and your RPerl Family contribution, then include y our answers in the body of your e-mail or on a separate sheet of paper in snail mail, and send it all to one of the addresses below.
1. Full Legal Name 1. Full Legal Name
2. Preferred Pseudonym (or "none") 2. Preferred Pseudonym (or "none")
3. Country of Citizenship 3. Country of Citizenship
4. Date of Birth (spell full month name) 4. Date of Birth (spell full month name)
5. Snail Mail Address (include country) 5. Snail Mail Address (include country)
6. E-Mail Address 6. E-Mail Address
7. Names of RPerl Files Modified (or "none") 7. Names of RPerl Family Files Modified (or "none")
8. Names of RPerl Files Created (or "none") 8. Names of RPerl Family Files Created (or "none")
9. Current Employer (or "none") 9. Current Employer(s) or Contractee(s) (or "none")
10. Does Your Job Involve Computer Programming? (or "not applicable") 10. Does Your Job Involve Computer Programming? (or "not applicable")
11. Does Your Job Involve an IP Ownership Agreement? (or "not applicable") 11. Does Your Job Involve an IP Ownership Agreement? (or "not applicable")
12. Name(s) & Employer(s) of Additional Contributors (or "none") 12. Name(s) & Employer(s) of Additional Contributors (or "none")
Snail Mail Address: Snail Mail Address:
RPerl Project RPerl Project
c/o William Braswell c/o William Braswell
608 S. Cougar Ave. [ CONTACT VIA E-MAIL BELOW FOR STREET ADDRESS ]
Cedar Park, TX, USA, 78613 Cedar Park, TX, USA, 78613
E-Mail Address (Remove "NOSPAM." Before Sending): E-Mail Address (Remove "NOSPAM." Before Sending):
william.braswell at NOSPAM.autoparallel.com william.braswell at NOSPAM.autoparallel.com
THANKS FOR CONTRIBUTING! :-) THANKS FOR CONTRIBUTING! :-)
 End of changes. 12 change blocks. 
22 lines changed or deleted 128 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)