#167 Update council legal page
Merged 2 years ago by bcotton. Opened 2 years ago by jlovejoy.
Fedora-Council/ jlovejoy/council-docs jl-council-legal-page  into  main

@@ -11,7 +11,7 @@ 

  ** xref:policy/guiding-policy.adoc[Guiding Policy]

  ** xref:policy/policy-change-policy.adoc[Policy Change Policy]

  ** xref:policy/edition-promotion-policy.adoc[Edition Promotion Policy]

- ** xref:policy/legal.adoc[Legal Statements]

+ ** xref:policy/legal.adoc[Legal & Licensing Policies]

  ** xref:policies.adoc[Additional Policies]

  * Council Procedures

  ** xref:procedures/welcome.adoc[Welcome to Council]

@@ -1,58 +1,3 @@ 

- == International Restrictions

+ == Legal & Licensing Policies

  

- By contributing to and/or downloading Fedora content,

- you acknowledge that you understand all of the following:

- Fedora software and technical information may be subject to

- the U.S. Export Administration Regulations (the "EAR") and

- other U.S. and foreign laws and may not be

- exported, re-exported or transferred

- (a) to a prohibited destination country under

- the EAR and

- the U.S. Department of Treasury,

- Office of Foreign Assets Controls

- (currently

- Cuba,

- Iran,

- North Korea,

- Syria,

- and

- the Crimea Region of Ukraine,

- subject to change as posted by the United States government);

- (b) to any prohibited destination or to any end user

- who has been prohibited from participating in U.S. export transactions by

- any federal agency of the U.S. government; or

- (c) for use in connection with the design,

- development or production of

- nuclear, chemical or biological weapons,

- or rocket systems, space launch vehicles, or sounding rockets,

- or unmanned air vehicle systems.

- You may not contribute to Fedora or

- download Fedora software or technical information

- if you are located in one of these countries or otherwise

- subject to these restrictions.

- You may not provide Fedora software or

- technical information to individuals or

- entities located in one of these countries or

- otherwise subject to these restrictions.

- You are also responsible for compliance with

- foreign law requirements applicable to the import,

- export and use of Fedora software and technical information.

- 

- Fedora software in source code and binary code form are publicly available

- and are not subject to the EAR in accordance with §742.15(b).

- 

- === Note

- 

- Export rules are very hard and very complicated.

- 

- Sponsors (or any other contributors) in Fedora

- should not make any effort to determine a contributor's

- nationality, country of origin, or area of residence.

- If a potential contributor independently (and explicitly) reveals their

- nationality, country of origin, or area of residence, and that

- nationality, country of origin, or area of residence

- is in one of the export

- restricted countries

- (as listed above)

- then they are required to bring that information

- to the attention of Fedora Legal.

+ For various legal and licensing policies related to Fedora, please see https://docs.fedoraproject.org/en-US/legal/ 

Instead of a bare URL, let's put in an xref (e.g. ..please see the xref:legal::index.adoc[legal documentation])

\ No newline at end of file

Add link to Fedora-legal docs section
remove export policy and add link to correct/updated one on Fedora-legal docs
rename page
rename link to page in Nav

Signed-off-by: Jilayne Lovejoy

Instead of a bare URL, let's put in an xref (e.g. ..please see the xref:legal::index.adoc[legal documentation])

Metadata Update from @bcotton:
- Request assigned

2 years ago

Looks good to me. I can fix the URL/xref issue I mentioned above post-merge.

I'll leave this open until early next week in case another Council member has comments.

Changing my vote to a weak -1 – I'd prefer that we delete the page in Council docs, update the navigation sidebar to link to the new page, and use :page-aliases: to redirect traffic at the old URL to the new one in the Legal docs.

I agree with @jflory7. Might as well delete the page and do the redirect.

The main argument for keeping the page is if we want to contextualize the link to the Legal docs. But we can add that later if there's context we want to add.

I'm going to go ahead and merge this and then immediately follow up with a deletion and a PR to the legal docs to add the alias.

Pull-Request has been merged by bcotton

2 years ago