www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LEGAL-439) Q1 Website Review
Date Fri, 15 Feb 2019 06:51:00 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769000#comment-16769000
] 

Henri Yandell edited comment on LEGAL-439 at 2/15/19 6:50 AM:
--------------------------------------------------------------

Starting with a review of [http://apache.org/licenses/] per Sally's request.

Breaking the page down into sections, with comments:


{code:java}

Introduction: Text seems fine. The links in the first paragraph are unnecessary and confusing,
you wouldn't expect an embedded link to jump you down the page in this way. Technically we
have a trademark assignment as well, which isn't listed here and doesn't allow the 'contributor'
to retain their previous rights.



# Licensing of Distributions

Using the term 'Distributions' may be dated now. We've toyed with "Products" in other parts
of our website and that's more likely to be in the public's lexicon. The first introductory
paragraph stating the software is licensed under the terms of the documents below could be
simpler, and may fall under the bleeding obvious.

### Apache License, Version 2.0 (current)

This text is historic. The sentence regarding the GPL can be removed. The statement that all
packages are implicitly licensed under AL 2.0 unless stated otherwise seems off. It implies
that the lack of a license means the package is under Apache 2.0, which is out of sorts with
the standard position that a lack of a license means no rights are granted. The link to "Applying"
is useful, but the content of that page will need updating as it is also historic.

### Apache License, Version 1.1 (historic) ## \{#1.1}
### Apache License, Version 1.0 (historic) ## \{#1.0}

Also historic, but reasonably so. We could potentially move both of these sections to their
own Old Versions page. 

Rather than using the beginning of this page to talk about software licensing, it's tempting
to move this entire licensing section to its own page. 




# Contributor License Agreements # \{#clas}

* "Desires" is an odd word to use. It encourages negotiation.
* "is available" is vague with regards to a CCLA. 

Again, this whole section could move to a page dedicated to CLAs, or perhaps a page that talks
about the licensing of contributions (which would include many later sections).

# Software Grants

Calling this a Software Grant is quite confusing. It implies Assignment. It's also a bit confusing
how the SGA and a CLA/CCLA work together. Why sign a SGA if you've signed a CLA of some form.

Some soul searching and rewriting would be good here. Can go to a page on licensing of contributions
(see above).


# Submitting License Agreements and Grants

Instructive text. Could go to an instruction page on licensing of contributions (see above).



# Provenance # \{#provenance}

This is an oddly out of place section. It's better placed on a page explaining Apache development
practices re: licensing. Perhaps as an introduction to a revamped resolved.html page.

# Export restrictions

Probably should be in /legal/ rather than /licenses/

# Trademark and Logo Usage 

A bit out of place. It could go in the FAQ, or perhaps we need an overarching context that
shows Trademarks, Legal and Licenses as three parts of one subsite.

# Questions? 

Fair, though it could be written to talk more about contacting legal-discuss@, but please
read the FAQ first. That'll increase random traffic from laziness, so there may be wisdom
in the current setup.
{code}




was (Author: bayard):
Starting with a review of [http://apache.org/licenses/] per Sally's request.

Breaking the page down into sections, with comments:

{noformat}
Introduction: Text seems fine. The links in the first paragraph are unnecessary and confusing,
you wouldn't expect an embedded link to jump you down the page in this way. Technically we
have a trademark assignment as well, which isn't listed here and doesn't allow the 'contributor'
to retain their previous rights.



# Licensing of Distributions

Using the term 'Distributions' may be dated now. We've toyed with "Products" in other parts
of our website and that's more likely to be in the public's lexicon. The first introductory
paragraph stating the software is licensed under the terms of the documents below could be
simpler, and may fall under the bleeding obvious.

### Apache License, Version 2.0 (current)

This text is historic. The sentence regarding the GPL can be removed. The statement that all
packages are implicitly licensed under AL 2.0 unless stated otherwise seems off. It implies
that the lack of a license means the package is under Apache 2.0, which is out of sorts with
the standard position that a lack of a license means no rights are granted. The link to "Applying"
is useful, but the content of that page will need updating as it is also historic.

### Apache License, Version 1.1 (historic) ## \{#1.1}
### Apache License, Version 1.0 (historic) ## \{#1.0}

Also historic, but reasonably so. We could potentially move both of these sections to their
own Old Versions page. 

Rather than using the beginning of this page to talk about software licensing, it's tempting
to move this entire licensing section to its own page. 




# Contributor License Agreements # \{#clas}

* "Desires" is an odd word to use. It encourages negotiation.
* "is available" is vague with regards to a CCLA. 

Again, this whole section could move to a page dedicated to CLAs, or perhaps a page that talks
about the licensing of contributions (which would include many later sections).

# Software Grants

Calling this a Software Grant is quite confusing. It implies Assignment. It's also a bit confusing
how the SGA and a CLA/CCLA work together. Why sign a SGA if you've signed a CLA of some form.

Some soul searching and rewriting would be good here. Can go to a page on licensing of contributions
(see above).


# Submitting License Agreements and Grants

Instructive text. Could go to an instruction page on licensing of contributions (see above).



# Provenance # \{#provenance}

This is an oddly out of place section. It's better placed on a page explaining Apache development
practices re: licensing. Perhaps as an introduction to a revamped resolved.html page.

# Export restrictions

Probably should be in /legal/ rather than /licenses/

# Trademark and Logo Usage 

A bit out of place. It could go in the FAQ, or perhaps we need an overarching context that
shows Trademarks, Legal and Licenses as three parts of one subsite.

# Questions? 

Fair, though it could be written to talk more about contacting legal-discuss@, but please
read the FAQ first. That'll increase random traffic from laziness, so there may be wisdom
in the current setup.
{noformat}

> Q1 Website Review
> -----------------
>
>                 Key: LEGAL-439
>                 URL: https://issues.apache.org/jira/browse/LEGAL-439
>             Project: Legal Discuss
>          Issue Type: Task
>            Reporter: Henri Yandell
>            Priority: Major
>
> Using this Jira issue as a scratch space to review our legal website content. Idea is
to copy any outstanding items to a fresh ticket each quarter. Or come up with a new harebrained
scheme :)
> Feel free to add any todo items.
> Pages under the Legal Committee purview:
>  [https://www.apache.org/legal/index.html]
>  [https://www.apache.org/legal/3party.html]
>  [https://www.apache.org/legal/dmca.html]
>  [https://www.apache.org/legal/ghmon.html]
>  [https://www.apache.org/legal/ramblings.html]
>  [https://www.apache.org/legal/release-policy.html]
>  [https://www.apache.org/legal/resolved.html]
>  [https://www.apache.org/legal/src-headers.html]
> There are also 38 files under https://www.apache.org/licenses/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message