Merge pull request #277 from apache/unused
Unused data items
diff --git a/asfdata.yaml b/asfdata.yaml
index e4a59bd..06da33f 100644
--- a/asfdata.yaml
+++ b/asfdata.yaml
@@ -78,11 +78,15 @@
# projects, products, versions, and sources
file: data/eccn/eccnmatrix.yaml
-# used on index.ezmd
-twitter:
- # load, transform, and create a sequence of tweets
- handle: 'TheASF'
- count: 1
+# The following is a work-round, as EZT does not currently
+# support a check to see if a variable is defined
+# Note: currently disabled. Change the following to 1 to enable
+twitter_enable: 0
+# # used on index.ezmd
+# twitter:
+# # load, transform, and create a sequence of tweets
+# handle: 'TheASF'
+# count: 1
# used on index.ezmd
foundation:
diff --git a/content/board/escalation.md b/content/board/escalation.md
index d4ee574..7330e6f 100644
--- a/content/board/escalation.md
+++ b/content/board/escalation.md
@@ -46,7 +46,7 @@
- Issues with Apache Infra should first be escalated to the [Infra Administrator](https://whimsy.apache.org/roster/orgchart/infra-admin) directly. If that is not sufficient, only then escalate to [VP, Infrastructure](https://whimsy.apache.org/roster/orgchart/vp-infra).
-- Any **brand or trademark issues** go to the [Brand Management Committee](https://www.apache.org/foundation/marks/contact) on private lists and cc: the relevant private@ list.
+- Any **brand or trademark issues** go to the [Brand Management Committee](/foundation/marks/contact) on private lists and cc: the relevant private@ list.
- Any issues of **law or from lawyers** go to the [Legal Affairs Committee](https://whimsy.apache.org/roster/orgchart/vp-legal) (on a private list if needed!)
@@ -54,20 +54,20 @@
- Operations issues (fundraising, conferences, etc.) should go to the [President](https://whimsy.apache.org/roster/orgchart/president) and EVP; the [Org Chart](https://whimsy.apache.org/roster/orgchart/) is helpful to see who reports to the President or the Board directly.
-For more pointers, see the [Services Available To Apache Projects listing](https://www.apache.org/board/services). Note that the private members@ mailing list is never the right place to escalate project issues.
+For more pointers, see the [Services Available To Apache Projects listing](/board/services). Note that the private members@ mailing list is never the right place to escalate project issues.
## Exception Cases For Escalation
There are a few rare cases that may be exceptions to the above guide, depending on severity and urgency:
-* Any potentially **disclosed security issue** that is not being addressed: escalating _immediately_ to ensure that the [Security Team is aware of the issue](https://www.apache.org/security/) is OK if other avenues are not working.
+* Any potentially **disclosed security issue** that is not being addressed: escalating _immediately_ to ensure that the [Security Team is aware of the issue](/security/) is OK if other avenues are not working.
- Any **credible threats to personal safety** should be escalated immediately to local law enforcement or emergency personnel. If you are at an ApacheCon or other ASF hosted event, contact the conference organizers or Planning committee as soon as practical by asking any event staff; elsewhere, please contact the ASF's President at president@apache.org.
- Any **legal summons or demands** from legal counsel should be escalated immediately to the [Legal Affairs Committee](https://whimsy.apache.org/roster/orgchart/vp-legal), so that the ASF's counsel can review for action.
-- Serious **code of conduct** violations where you are not comfortable working with the person in question directly may be escalated to the [President or reporting volunteers](https://www.apache.org/foundation/policies/conduct.html) directly.
+- Serious **code of conduct** violations where you are not comfortable working with the person in question directly may be escalated to the [President or reporting volunteers](/foundation/policies/conduct.html) directly.
### Just looking for some general advice on the ASF?
diff --git a/content/board/index.md b/content/board/index.md
index 6e626dc..89e267d 100644
--- a/content/board/index.md
+++ b/content/board/index.md
@@ -95,6 +95,6 @@
### See Also
-* General [How-To information for Apache contributors](https://www.apache.org/dev/).
+* General [How-To information for Apache contributors](/dev/).
* [Five-year Strategic Plan for the Apache Software Foundation](./ASF-5-year-plan-02-21-2018), from 2018
diff --git a/content/board/services.md b/content/board/services.md
index a4ca68d..d3e7e86 100644
--- a/content/board/services.md
+++ b/content/board/services.md
@@ -39,38 +39,38 @@
### Infrastructure Services
-The [Apache Infrastructure team](https://www.apache.org/dev/infrastructure) (Infra) is
+The [Apache Infrastructure team](/dev/infrastructure) (Infra) is
responsible for management and day-to-day system administration and operation
of websites, source control systems, and other infrastructure offered to
-Apache projects, and provides a [guide to developer tools](https://www.apache.org/dev/).
-You can [contact Infra](https://www.apache.org/dev/infra-contact#misdirected)
+Apache projects, and provides a [guide to developer tools](/dev/).
+You can [contact Infra](/dev/infra-contact#misdirected)
and [Infra has many self-serve tools](https://selfserve.apache.org/).
-Example services include: [Subversion and GitBox hosting](https://www.apache.org/dev/services.html#source-repository),
-[Jenkins, BuildBot, and other CI tools like ReviewBoard, Sonar](https://www.apache.org/dev/services.html#build),
-[Hosted VM for each project](https://www.apache.org/dev/services.html#virtual-servers).
+Example services include: [Subversion and GitBox hosting](/dev/services.html#source-repository),
+[Jenkins, BuildBot, and other CI tools like ReviewBoard, Sonar](/dev/services.html#build),
+[Hosted VM for each project](/dev/services.html#virtual-servers).
### Marketing & Publicity
-[Marketing and Publicity](https://www.apache.org/press/#whoweare)
+[Marketing and Publicity](/press/#whoweare)
provides primary communications services for the ASF, and advises Apache
-projects and initiatives on their outreach efforts. You can [contact the Press Team](https://www.apache.org/press/#contact).
+projects and initiatives on their outreach efforts. You can [contact the Press Team](/press/#contact).
-Example services include: [Press releases over the wire for major releases](https://www.apache.org/press/#releases),
-[connections with industry analysts](https://www.apache.org/press/#interviews),
-[Apache feather and Powered By logos for all TLPs](https://www.apache.org/foundation/press/kit/).
+Example services include: [Press releases over the wire for major releases](/press/#releases),
+[connections with industry analysts](/press/#interviews),
+[Apache feather and Powered By logos for all TLPs](/foundation/press/kit/).
### Travel Assistance At ApacheCon
-The [Travel Assistance Committee](https://www.apache.org/travel) exists to
+The [Travel Assistance Committee](/travel) exists to
help those that would like to attend ApacheCon events, but are unable to do so
for financial reasons.
### Conference & Event Support
-The [Conferences team](https://www.apache.org/foundation/conferences)
+The [Conferences team](/foundation/conferences)
organizes official events such as ApacheCon, as well as facilitating third
-party events that Apache PMCs are involved in. You can [contact the Conferences team](https://www.apache.org/foundation/conferences#mailing-lists).
+party events that Apache PMCs are involved in. You can [contact the Conferences team](/foundation/conferences#mailing-lists).
Example services include: running [ApacheCon for all projects](https://apachecon.com/),
and a [central calendar for Apache-related events](https://events.apache.org/).
@@ -81,31 +81,31 @@
The [Apache Security Team](https://security.apache.org) exists to provide
help and advice to Apache projects on security issues and to provide
co-ordination of the handling of security vulnerabilities and CVE issuing.
-Anyone can [submit a security issue](https://www.apache.org/security/#reporting-a-vulnerability).
+Anyone can [submit a security issue](/security/#reporting-a-vulnerability).
Example services include: the [general security@ vulnerability reporting mailing list](https://security.apache.org/projects/),
-and [detailed checklists and help with CVEs](https://www.apache.org/security/committers.html) and handling vulnerabilities.
+and [detailed checklists and help with CVEs](/security/committers.html) and handling vulnerabilities.
### Brand & Trademarks
-The [Brand Management team](https://www.apache.org/foundation/marks/resources)
+The [Brand Management team](/foundation/marks/resources)
collaborates with projects on branding and trademarks. You can
-[contact the Brand Management team](https://www.apache.org/foundation/marks/contact)
-and [report trademark issues](https://www.apache.org/foundation/marks/reporting).
+[contact the Brand Management team](/foundation/marks/contact)
+and [report trademark issues](/foundation/marks/reporting).
-Example services include: [trademark law resources for developers](https://www.apache.org/foundation/marks/resources),
-[approvals for running outside events with Apache brands](https://www.apache.org/foundation/marks/events),
-[trademark registration of your project name](https://www.apache.org/foundation/marks/register#register).
+Example services include: [trademark law resources for developers](/foundation/marks/resources),
+[approvals for running outside events with Apache brands](/foundation/marks/events),
+[trademark registration of your project name](/foundation/marks/register#register).
### Legal
-The [Legal Affairs Committee](http://www.apache.org/legal) is responsible for
+The [Legal Affairs Committee](/legal) is responsible for
establishing and managing legal policies based on the advice of legal counsel
-and the interests of the Foundation. You can [contact Legal Affairs](https://www.apache.org/legal/#communications).
+and the interests of the Foundation. You can [contact Legal Affairs](/legal/#communications).
-Example services include: [answering specific legal JIRAs for project business](https://www.apache.org/foundation/contributing.html#TargetedSponsor),
+Example services include: [answering specific legal JIRAs for project business](/foundation/contributing.html#TargetedSponsor),
a public legal-discussion@ mailing list for general legal chats,
-and the [official FAQ of license compatibility questions](https://www.apache.org/legal/resolved.html).
+and the [official FAQ of license compatibility questions](/legal/resolved.html).
### Fundraising
@@ -113,8 +113,8 @@
is responsible for establishing and managing fundraising activities to
support the operations of the ASF and our projects.
-Example services include: [accepting targeted donations for your project](https://www.apache.org/foundation/contributing.html#TargetedSponsor),
-and the [core donations and sponsorships](https://www.apache.org/foundation/contributing.html) that pay the ASF's bills.
+Example services include: [accepting targeted donations for your project](/foundation/contributing.html#TargetedSponsor),
+and the [core donations and sponsorships](/foundation/contributing.html) that pay the ASF's bills.
### Other Useful Services
diff --git a/content/community-resources/index.md b/content/community-resources/index.md
index 1abbee3..7f967ba 100644
--- a/content/community-resources/index.md
+++ b/content/community-resources/index.md
@@ -7,9 +7,9 @@
| Resource | Details |
|-----------|-------------|
-| [ASF Code of Conduct](https://apache.org/foundation/policies/conduct) | We expect everyone who participates to honor our code of conduct. |
+| [ASF Code of Conduct](/foundation/policies/conduct) | We expect everyone who participates to honor our code of conduct. |
| [ASF Committer Directory](https://people.apache.org/) | An index of projects and committers for every ASF project. |
-| [ASF Memorials](https://apache.org/memorials/) | Valued members we have lost. |
+| [ASF Memorials](/memorials/) | Valued members we have lost. |
| [Apache Local Community (ALC)](https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC) | ALCs are local groups of ASF / open source enthusiasts in towns/cities around the world. |
| [Community Over Code](https://communityovercode.org/) | ASF’s flagship community event in North America, Europe, and Asia. |
| [Community Events](https://events.apache.org/) | Calendar of upcoming community and ASF events. |
diff --git a/content/dev/pmc.md b/content/dev/pmc.md
index bfc2f82..9659822 100644
--- a/content/dev/pmc.md
+++ b/content/dev/pmc.md
@@ -164,6 +164,7 @@
Maintain information about your PMC's composition in the SVN "committers" repository
at [committee-info.txt](https://svn.apache.org/repos/private/committers/board/committee-info.txt) and keep it up-to-date.
Remember to update the LDAP committee group as well.
+This is normally done using the [Whimsy roster tool](https://whimsy.apache.org/roster/committee/).
Be aware of anything currently in incubation at
[incubator.apache.org](https://incubator.apache.org).
diff --git a/content/foundation/contact.md b/content/foundation/contact.md
index 39beaae..b2436dd 100644
--- a/content/foundation/contact.md
+++ b/content/foundation/contact.md
@@ -3,7 +3,7 @@
# Contact Us
-**Before** sending mail to the address below, **make sure** that the information on the [FAQ](https://www.apache.org/foundation/faq) doesn't already address your issue. If it is, the only response you'll receive is a pointer
+**Before** sending mail to the address below, **make sure** that the information on the [FAQ](/foundation/faq) doesn't already address your issue. If it is, the only response you'll receive is a pointer
to that page.
## Project Contacts
@@ -12,22 +12,27 @@
## Security Contacts
-Visit the [ASF Security page](https://www.apache.org/security/) to learn how to report a security vulnerability.
+=======
+Visit the [ASF Security page](https://www.apache.org/security/) to learn how to report a security vulnerability.
+
+## Academic Researchers
+
+To ensure that our communities are respected, and to make it easier for researchers to find the right information, our volunteers maintain a [Research Information Portal](https://apache.org/research/).
## Foundation Directory
| Inquiry | Contact |
| ----------- | ----------- |
-| Technical Support | If you believe you’re experiencing a technical issue, visit the [Technical section of our FAQ](https://www.apache.org/foundation/faq) first before reaching out.|
+| Technical Support | If you believe you’re experiencing a technical issue, visit the [Technical section of our FAQ](/foundation/faq) first before reaching out.|
| Hosting a project with ASF | [Apache Incubator](https://incubator.apache.org/) |
-| Press and analyst inquiries | [Newsroom](https://apache.org/press/) <br> press@apache.org |
-| Sponsorship or donation inquiries | [Foundation Sponsorship](https://apache.org/foundation/sponsorship.html) <br> [Individual Supporters](/foundation/individual-supporters) <br> fundraising@apache.org |
-| Trademarks or service marks including all Apache project names and logos | [Trademark Contacts](https://apache.org/foundation/marks/contact) |
-| Legal and Licensing | [Licensing FAQ](https://apache.org/foundation/license-faq.html) <br> [Legal Affairs Committee](https://apache.org/legal/) |
+| Press and analyst inquiries | [Newsroom](/press/) <br> press@apache.org |
+| Sponsorship or donation inquiries | [Foundation Sponsorship](/foundation/sponsorship.html) <br> [Individual Supporters](/foundation/individual-supporters) <br> fundraising@apache.org |
+| Trademarks or service marks including all Apache project names and logos | [Trademark Contacts](/foundation/marks/contact) |
+| Legal and Licensing | [Licensing FAQ](/foundation/license-faq.html) <br> [Legal Affairs Committee](/legal/) |
| Infrastructure | [Infrastructure Contact](https://infra.apache.org/contact.html) |
| Website | Issues with a specific Apache project's website should go to that project's dev@ mailing list. For issues with the foundation top-level website apache.org or news.apache.org: press@apache.org |
-| DMCA Designated Agent | [DMCA Agent](https://apache.org/legal/dmca.html) |
+| DMCA Designated Agent | [DMCA Agent](/legal/dmca.html) |
| Exports | [Exports](/licenses/exports/) |
| For questions that are not covered above | apache@apache.org |
diff --git a/content/foundation/faq.md b/content/foundation/faq.md
index cf802e3..96cd59c 100644
--- a/content/foundation/faq.md
+++ b/content/foundation/faq.md
@@ -51,7 +51,7 @@
FAQ](license-faq.html). If that doesn't answer them, you may contact our
[Legal Affairs Committee](/legal/).
-We address specific questions about trademarks of The Apache Software Foundation on the [Trademark Policy page](https://apache.org/foundation/marks/).
+We address specific questions about trademarks of The Apache Software Foundation on the [Trademark Policy page](/foundation/marks/).
## Foundation
diff --git a/content/foundation/governance/index.md b/content/foundation/governance/index.md
index b429a16..a77094e 100644
--- a/content/foundation/governance/index.md
+++ b/content/foundation/governance/index.md
@@ -24,13 +24,13 @@
PMCs vote on new committers and PMC members for their project, set per-project policies, and formally vote on software product releases. PMCs report quarterly directly to the board, not to the President.
-**[Executive Officers](https://apache.org/foundation/leadership)**
+**[Executive Officers](/foundation/leadership)**
The board elects a Board Chair (a director) and appoints a standard range of executive officers. Officers are all unpaid volunteers, and serve at the direction of the board in their specific areas of responsibility. Officers are responsible both for managing the Foundations affairs in their specific areas, and for reporting monthly status reports to the board.
Executive officers include a President, Executive Vice President, Secretary, Assistant Secretary, and Treasurer.
-**[Corporate Officers](https://apache.org/foundation/leadership)**
+**[Corporate Officers](/foundation/leadership)**
The board has appointed several officers for corporate-wide functions - this includes Vice Presidents to oversee Brand Management, Conference Planning, Fundraising, Legal Affairs, Marketing and Publicity, Travel Assistance, and Diversity. The board delegates authority to set and execute corporate policy within each officer's specific area of responsibility.
diff --git a/content/foundation/how-it-works/index.md b/content/foundation/how-it-works/index.md
index a58bdd0..48c776b 100644
--- a/content/foundation/how-it-works/index.md
+++ b/content/foundation/how-it-works/index.md
@@ -135,7 +135,7 @@
The board is responsible for management and oversight of the business and
affairs of the corporation in accordance with the foundation
-[Bylaws](bylaws.html). This includes management of the corporate assets
+[Bylaws](/foundation/bylaws.html). This includes management of the corporate assets
(funds, intellectual property, trademarks, and support equipment) and
allocation of corporate resources to projects.
@@ -147,7 +147,7 @@
that the foundation should have, but this was the number of the
first board and it has never changed. The board is elected every year.
-The [board website](https://www.apache.org/foundation/governance/board.html) has more information, the list of the current
+The [board website](/foundation/governance/board.html) has more information, the list of the current
directors, a schedule of meetings, and minutes of past meetings.
### Project Management Committees (PMC) {#pmc}
@@ -163,10 +163,10 @@
has the power to establish rules and procedures for the day to day
management of the communities for which the PMC is responsible, including
the composition of the PMC itself. See further discussion about the role of the
-PMC [chair](https://www.apache.org/dev/pmc.html#chair) and [why chairs are
-officers](https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers).
+PMC [chair](/dev/pmc.html#chair) and [why chairs are
+officers](/foundation/faq.html#why-are-PMC-chairs-officers).
-The [ASF Bylaws](https://www.apache.org/foundation/bylaws.html) (section 6.3) define a PMC and the position
+The [ASF Bylaws](/foundation/bylaws.html) (section 6.3) define a PMC and the position
of chair. Some emails help to clarify:
[here](http://www.mail-archive.com/community@apache.org/msg03961.html) and
[here](http://www.mail-archive.com/community@apache.org/msg04005.html).
@@ -296,7 +296,7 @@
Each project is responsible for its own [project website](https://home.apache.org/committers-by-project.html).
Further information to assist committers, developers, and PMCs is available
-at [ASF Infrastructure](https://infra.apache.org/).
+at [ASF Infrastructure](/dev/).
### Decision Making {#decision-making}
@@ -481,14 +481,14 @@
Along with the Incubator, the foundation has several other
cross-foundation projects. For example, the ASF does not have offices or
-buildings. It's a virtual entity that exists only on the internet, and the [Infrastructure team](../dev/infrastructure.html) manages the
+buildings. It's a virtual entity that exists only on the internet, and the [Infrastructure team](/dev/infrastructure.html) manages the
technical infrastructure that enables it to operate.
Read more about these and other cross-foundation projects on the [Foundation
-Projects](https://www.apache.org/foundation/foundation-projects.html) page.
+Projects](/foundation/foundation-projects.html) page.
The ASF also hosts some foundation-wide mailing lists, which you can learn about
-on the [Mailing Lists](https://www.apache.org/foundation/mailinglists.html) page.
+on the [Mailing Lists](/foundation/mailinglists.html) page.
## In review... {#conclusions}
diff --git a/content/foundation/license-faq.md b/content/foundation/license-faq.md
index d7a425f..0e26870 100644
--- a/content/foundation/license-faq.md
+++ b/content/foundation/license-faq.md
@@ -220,7 +220,7 @@
>
> <span class="link-external"> [Apache License, Version
-2.0](http://www.apache.org/licenses/LICENSE-2.0) </span>
+2.0](/licenses/LICENSE-2.0) </span>
>
This is a free software license, compatible with version 3 of the GPL.
Please note that this license is not compatible with GPL version 2, because
diff --git a/content/foundation/members.md b/content/foundation/members.md
index 5a239df..d7c65f2 100644
--- a/content/foundation/members.md
+++ b/content/foundation/members.md
@@ -5,7 +5,7 @@
ASF Members are those who have proven their commitment to the ASF by contributing to one or more of the Foundation’s projects. We thank them for their ongoing contributions to the Foundation.
-Our Members are similar to stockholders–they elect new Members and may vote for Directors. Membership in The Apache Software Foundation is a privilege and is by invitation only. The [Governance](https://apache.org/foundation/governance/) page provides details on Membership and the nomination process.
+Our Members are similar to stockholders–they elect new Members and may vote for Directors. Membership in The Apache Software Foundation is a privilege and is by invitation only. The [Governance](/foundation/governance/) page provides details on Membership and the nomination process.
<p><a class="btn btn-default mx-10" href="http://home.apache.org/committers-by-project.html#member" role="button">Go to Member List</a>
@@ -110,7 +110,7 @@
| dain | Dain Sundstrom |
| danese | Danese Cooper |
| danhaywood | Dan Haywood | [Causeway](https://causeway.apache.org) |
-| danielsh | Daniel Shahaf | [Subversion](http://subversion.apache.org/), [Infrastructure](http://www.apache.org/dev/infrastructure)|
+| danielsh | Daniel Shahaf | [Subversion](http://subversion.apache.org/), [Infrastructure](/dev/infrastructure)|
| danny | [Danny Angus](http://blog.killerbees.co.uk) | [James](http://james.apache.org/) , [Jakarta](http://jakarta.apache.org/), [Labs](http://labs.apache.org)|
| dashorst | Martijn Dashorst |
| davisp | Paul Joseph Davis |
@@ -194,7 +194,7 @@
| jani | Jan Iversen | |
| jbellis | Jonathan Ellis |
| jbonofre | [Jean-Baptiste Onofré](https://nanthrax.blogspot.com) | [ActiveMQ](http://activemq.apache.org), [Archiva](http://archiva.apache.org), [Aries](http://aries.apache.org), [Bahir](http://bahir.apache.org), [Beam](http://beam.apache.org), [Brooklyn](http://brooklyn.apache.org), [BRPC](http://brpc.apache.org), [Camel](http://camel.apache.org), [CarbonData](http://carbondata.apache.org), [EventMesh](http://eventmesh.apache.org), [Felix](http://felix.apache.org), [Geronimo](http://geronimo.apache.org), [Gobblin](http://gobblin.apache.org), [Guacamole](http://guacamole.apache.org), [Incubator](http://incubator.apache.org), [InLong](http://inlong.apache.org), [jClouds](http://jclouds.apache.org), [Karaf](http://karaf.apache.org), [Liminal](http://liminal.apache.org), [Livy](http://livy.apache.org), [Nemo](http://nemo.apache.org), [Seatunnel](http://seatunnel.apache.org), [Sedona](http://sedona.apache.org), [ServiceComb](http://servicecomb.apache.org), [ServiceMix](http://servicemix.apache.org), [Shiro](http://shiro.apache.org), [Streampipes](http://streampipes.apache.org), [Syncope](http://syncope.apache.org), [Tuweni](http://tuweni.apache.org), [Unomi](http://unomi.apache.org), [Wayang](http://wayang.apache.org)|
-| jcamacho | Jesús Camacho Rodríguez |
+| jcamacho | Jesús Camacho Rodríguez | [Calcite](http://calcite.apache.org/), [Hive](http://hive.apache.org/), [ORC](http://orc.apache.org/) |
| jcorvel | Johan Corveleyn | [Subversion](http://subversion.apache.org/) |
| jeagles | Jonathan Eagles | [Hadoop](http://hadoop.apache.org) ; [Tez](http://tez.apache.org/) |
| jerenkrantz | [Justin Erenkrantz](http://www.erenkrantz.com/) | [httpd](http://httpd.apache.org/) , [APR](http://apr.apache.org/) , [commons](http://commons.apache.org/) , prc , infrastructure|
diff --git a/content/foundation/news.md b/content/foundation/news.md
index d81a3d4..59e8954 100644
--- a/content/foundation/news.md
+++ b/content/foundation/news.md
@@ -3,7 +3,7 @@
# {{title}}
-_Please see our [current listing of News and Announcements](https://www.apache.org/press/#news) for more recent notes._
+_Please see our [current listing of News and Announcements](/press/#news) for more recent notes._
<hr/>
@@ -14,7 +14,7 @@
Announcements](http://mail-archives.apache.org/mod_mbox/www-announce/) or
you can visit [our foundation blog](https://blogs.apache.org/foundation/).
-See the [current listing of News and Announcements](https://www.apache.org/press/#news).
+See the [current listing of News and Announcements](/press/#news).
### 2010 ###
diff --git a/content/foundation/policies/anti-harassment.md b/content/foundation/policies/anti-harassment.md
index 37f357d..adabf7e 100644
--- a/content/foundation/policies/anti-harassment.md
+++ b/content/foundation/policies/anti-harassment.md
@@ -4,7 +4,7 @@
# {{title}}
## Policy Information
-**Please see the [Apache-wide Code of Conduct policy](https://www.apache.org/foundation/policies/conduct), which covers expected
+**Please see the [Apache-wide Code of Conduct policy](/foundation/policies/conduct), which covers expected
behavior within any Apache project's public or private spaces, including email lists.**
The Apache Conference Committee adopted this policy. Its most recent change was on 2011-08-24.
diff --git a/content/foundation/press/kit/c-over-c-logo.png b/content/foundation/press/kit/c-over-c-logo.png
new file mode 100644
index 0000000..6bec381
--- /dev/null
+++ b/content/foundation/press/kit/c-over-c-logo.png
Binary files differ
diff --git a/content/foundation/reports.md b/content/foundation/reports.md
index 2e7bf1f..1f3c705 100644
--- a/content/foundation/reports.md
+++ b/content/foundation/reports.md
@@ -7,8 +7,8 @@
#### Annual Reports
-* [The Apache Software Foundation - Annual Report - FY2022](https://www.apache.org/foundation/docs/FY2022AnnualReport.pdf)
-* [The Apache Software Foundation - Annual Report - FY2021](https://www.apache.org/foundation/docs/FY2021AnnualReport.pdf)
+* [The Apache Software Foundation - Annual Report - FY2022](/foundation/docs/FY2022AnnualReport.pdf)
+* [The Apache Software Foundation - Annual Report - FY2021](/foundation/docs/FY2021AnnualReport.pdf)
* [The Apache Software Foundation - Annual Report - FY2020](https://s.apache.org/FY2020AnnualReport)
* [The Apache Software Foundation - Annual Report - FY2019](https://s.apache.org/FY2019AnnualReport)
* [The Apache Software Foundation - Annual Report - FY2018](https://s.apache.org/FY2018AnnualReport)
@@ -46,4 +46,4 @@
* [The Apache Way to Sustainable Open Source Success](https://s.apache.org/GhnI)
* [The Apache Software Foundation 2018 Vision Statement](https://s.apache.org/zqC3)
* [Foundation Statement –Apache Is Open.](https://s.apache.org/PIRA)
-* [ASF 5-year Strategic Plan](https://www.apache.org/board/plan.html)
+* [ASF 5-year Strategic Plan](/board/plan.html)
diff --git a/content/foundation/sponsorship.md b/content/foundation/sponsorship.md
index 84868a5..3ccadb8 100644
--- a/content/foundation/sponsorship.md
+++ b/content/foundation/sponsorship.md
@@ -106,7 +106,7 @@
Targeted Sponsorship provides the ASF with non-cash contributions aimed at specific activities, projects, or programs, such as donating cloud services, providing legal services, underwriting our flagship event attendees’ expenses, funding project hackathons, and contributing documentation resources.
-Targeted Sponsorships benefit the ASF in addition to funding our general operations. We invite you to [view our guidelines](https://apache.org/foundation/docs/Targeted-Sponsorship-Policy.pdf) to see if Targeted Sponsorship is right for you.
+Targeted Sponsorships benefit the ASF in addition to funding our general operations. We invite you to [view our guidelines](/foundation/docs/Targeted-Sponsorship-Policy.pdf) to see if Targeted Sponsorship is right for you.
## Corporate Giving Programs
@@ -116,6 +116,24 @@
## FAQ
+### What is the ASF’s tax identification number?
+The ASF's tax identification number is 47-0825376.
+
+### Can I just make a one-time donation?
+The ASF appreciates donations of any size and, as we are a US registered 501(c)(3)
+corporation, your donation may be tax deductible. If you are interested in
+donating to the ASF at a different level than sponsorship, see our
+[donation page](/foundation/contributing.html).
+
+### Where can I mail a check?
+Mail your check or money order payable to:
+
+The Apache Software Foundation<br>
+1000 N West Street, Suite 1200<br>
+Wilmington, DE 19801<br>
+
+To receive a tax receipt, include your email address and the name for whom the donation should be credited (your own or the third party if it is a on behalf of someone else).
+
### Where will my sponsorship funds go?
The ASF provides the infrastructure for hundreds of projects - the mailing lists, code repositories, bug tracking systems, etc. A few paid contractors, plus large amounts of volunteer effort, maintain these resources. This, in addition to the large costs of bandwidth and server hardware, constitutes the bulk of the expense of running the Foundation.
@@ -197,11 +215,4 @@
renewal. If renewal does not take place by the renewal date of the sponsorship,
the ASF may remove your logo from the thanks page.
-### Can I just make a one-time donation?
-
-The ASF appreciates donations of any size and, as we are a US registered 501(c)(3)
-corporation, your donation may be tax deductible. If you are interested in
-donating to the ASF at a different level than sponsorship, see our
-[donation page](/foundation/contributing.html).
-
Thanks for your support!
diff --git a/content/index.ezmd b/content/index.ezmd
index 8dffdc5..b60c418 100644
--- a/content/index.ezmd
+++ b/content/index.ezmd
@@ -63,8 +63,12 @@
<a href="https://www.linkedin.com/company/the-apache-software-foundation/">The Apache Software Foundation on LinkedIn</a>, on the ASF's <a href="https://www.youtube.com/c/TheApacheFoundation/">YouTube channel</a>, and on <a href="https://feathercast.apache.org/">Feathercast</a>, the voice of the ASF.</p>
<!-- gm -->
<div class="updates blog-feed">
-<!--
- <article class="card">
+ <!--
+ Exclude the Twitter section from processing.
+ To re-instate, update asfdata.yaml
+-->
+[is twitter_enable "1"]
+ <article class="card">
<div class="content">
<span class="label label-danger">Twitter</span>
<div>
@@ -73,8 +77,7 @@
</div>
<a class="continue" href="https://twitter.com/TheASF">Continue Reading →</a>
</article>
--->
- [for foundation]<article class="card">
+[end] [for foundation]<article class="card">
<div class="content">
<span class="label label-danger">Foundation Blog</span>
<h5><a class="entryTitle" target="_blank" href="[foundation.href]">[foundation.title]</a></h5>
@@ -177,7 +180,7 @@
</div>
</section>
<!-- Apache Featured Projects Section -->
-<section class="bg-gray">
+<section class="bg-gray" data-pagefind-ignore="all">
<div class="container">
<div class="row">
<div class="col-md-12">
diff --git a/content/legal/generative-tooling.md b/content/legal/generative-tooling.md
index 4c87549..c96aaba 100644
--- a/content/legal/generative-tooling.md
+++ b/content/legal/generative-tooling.md
@@ -11,7 +11,7 @@
The Apache-2.0 license, and the Apache Individual Contribution License Agreement, both remind contributors that they are responsible for disclosing any copyrighted materials in submitted contributions that are not their original creation. This is as true when using generative AI tooling, as it is when using materials from public websites or code from other open source projects.
-When disclosing these materials, contributors should also identify the licensing for these materials. The ASF maintains a [3rd Party Licensing Policy](https://www.apache.org/legal/resolved.html) that provides guidance on which licenses are acceptable, along with instructions on the treatment of [3rd Party Works](https://www.apache.org/legal/src-headers.html#3party).
+When disclosing these materials, contributors should also identify the licensing for these materials. The ASF maintains a [3rd Party Licensing Policy](/legal/resolved.html) that provides guidance on which licenses are acceptable, along with instructions on the treatment of [3rd Party Works](/legal/src-headers.html#3party).
While in general, content generated by a non-human (e.g., machine or [monkey](https://en.wikipedia.org/wiki/Monkey_selfie_copyright_dispute)) is not copyrightable, if content consists of some portions generated by AI and other portions authored by a human, the portions authored by a human may be copyrightable.
@@ -19,7 +19,7 @@
> “For example, a human may select or arrange AI-generated material in a sufficiently creative way that “the resulting work as a whole constitutes an original work of authorship.” Or an artist may modify material originally generated by AI technology to such a degree that the modifications meet the standard for copyright protection. In these cases, copyright will only protect the human-authored aspects of the work, which are ‘independent of’ and do ‘not affect’ the copyright status of the AI-generated material itself.”
-These portions authored by a human may simply come from the prompt the human provided or subsequent changes they make. However, a prominent concern with generative AI is the risk of reproducing portions of materials that they were trained on, some of which may be copyrightable subject matter. Thus, a recommended practice when using generative AI tooling is to use tools with features that identify any included content that detects whether suggestions are similar to parts of the tool’s training data, as well as the license of that content.
+These portions authored by a human may simply come from the prompt the human provided or subsequent changes they make. However, a prominent concern with generative AI is the risk of reproducing portions of materials that they were trained on, some of which may be copyrightable subject matter. Thus, a recommended practice when using generative AI tooling is to use tools with features that identify any included content that is similar to parts of the tool’s training data, as well as the license of that content.
Given the above, code generated in whole or in part using AI can be contributed if the contributor ensures that:
@@ -28,7 +28,7 @@
1. The output is not copyrightable subject matter (and would not be even if produced by a human)
2. No third party materials are included in the output
3. Any third party materials that are included in the output are being used with permission (e.g., under a compatible open source license) of the third party copyright holders and in compliance with the applicable license terms
-3. A contributor obtain reasonable certainty that conditions 2(ii) or 2(iii) are met if the AI tool itself provides sufficient information about materials that may have been copied, or from code scanning results
+3. A contributor obtain reasonable certainty that conditions 2.2 or 2.3 are met if the AI tool itself provides sufficient information about materials that may have been copied, or from code scanning results
1. E.g. AWS CodeWhisperer recently added a feature that provides notice and attribution
When providing contributions authored using generative AI tooling, a recommended practice is for contributors to indicate the tooling used to create the contribution. This should be included as a token in the source control commit message, for example including the phrase “Generated-by: <Name of Tool> <Version>”. This allows for future release tooling to be considered that pulls this content into a machine parsable Tooling-Provenance file.
@@ -47,4 +47,4 @@
As with documentation, the above principles would still apply. Though with images being a non textual form, the details quickly become complex. We expect this to continue to be a rapidly evolving area.
## What do we do if a contribution includes AI generated content and some form of tooling has identified materials that have been copied? {#handling-references}
-Refer to the [3rd Party Licensing Policy](https://www.apache.org/legal/resolved.html) as with any other contribution.
+Refer to the [3rd Party Licensing Policy](/legal/resolved.html) as with any other contribution.
diff --git a/content/legal/release-policy.md b/content/legal/release-policy.md
index fe65ed6..e037230 100644
--- a/content/legal/release-policy.md
+++ b/content/legal/release-policy.md
@@ -3,7 +3,7 @@
# {{title}}
-This page documents the ASF policy on software releases. This document is for ASF release managers and [PMC](glossary#PMC) members.
+This page documents the ASF policy on software releases. This document is for ASF release managers and [PMC](/foundation/glossary#PMC) members.
Information [for end-users](https://infra.apache.org/release-download-pages.html#best_practice) is also available.
This document summarizes the <a href="https://infra.apache.org/release-publishing.html">release process</a>.
@@ -538,7 +538,7 @@
below:
This product includes software developed at
- The Apache Software Foundation (http://www.apache.org/).
+ The Apache Software Foundation (/).
N.B. Unfortunately versions of this document prior to 2013-01-30 (r1440650) were incorrect, as they used the phrase:
"developed by" instead of "developed at".
diff --git a/content/legal/src-headers.md b/content/legal/src-headers.md
index 03a88e2..8a24322 100644
--- a/content/legal/src-headers.md
+++ b/content/legal/src-headers.md
@@ -87,7 +87,7 @@
Copyright [XXXX-XXXX] The Apache Software Foundation
This product includes software developed at
- The Apache Software Foundation (http://www.apache.org/).
+ The Apache Software Foundation (/).
</li>
<li id="notice-other">Use the remainder of the NOTICE file to include [required third-party notices][1].
diff --git a/content/licenses/LICENSE-2.0.md b/content/licenses/LICENSE-2.0.md
index b1ec215..c5c3c61 100644
--- a/content/licenses/LICENSE-2.0.md
+++ b/content/licenses/LICENSE-2.0.md
@@ -137,17 +137,16 @@
within Derivative Works that You distribute, alongside or as an addendum to
the NOTICE text from the Work, provided that such additional attribution
notices cannot be construed as modifying the License.
-<br/>
-<br/>
-You may add Your own copyright statement to Your modifications and may
+</li>
+
+</ol>
+
+<p>You may add Your own copyright statement to Your modifications and may
provide additional or different license terms and conditions for use,
reproduction, or distribution of Your modifications, or for any such
Derivative Works as a whole, provided Your use, reproduction, and
distribution of the Work otherwise complies with the conditions stated in
-this License.
-</li>
-
-</ol>
+this License.</p>
<p><strong><a name="contributions">5. Submission of Contributions</a></strong>. Unless You
explicitly state otherwise, any Contribution intentionally submitted for
diff --git a/content/press/index.md b/content/press/index.md
index 750765a..4b69294 100644
--- a/content/press/index.md
+++ b/content/press/index.md
@@ -5,39 +5,40 @@
## Recent News
<p><a class="btn btn-default mx-10" href="https://news.apache.org/" role="button">Go to Foundation Newsroom</a>
+<p><a class="btn btn-default mx-10" href="https://apache.org/foundation/reports" role="button">View Reports</a>
-## Press Release Support
-Press releases that refer to the ASF and/or its projects must be approved by the VP Marketing and Publicity prior to distribution. Please allow for a minimum of 10 business days to complete the review. We are sensitive to internal approval processes and will expedite feedback when possible.
-- The ASF is vendor-neutral and does not provide testimonials that endorse, promote, or advertise the capability, credibility, or quality of any technology, product, or service. Email: press@apache.org - Joint announcements are rarely issued; examples of such releases include instances where a major industry milestone or initiative takes place, or announcing ASF Platinum-level Sponsorships.
-
-* You may request a quote for your ASF-related press release. Quotes may not be included unless approved by the VP Marketing & Publicity.
+## Publicity Guidelines for ASF Top-Level Projects
+ASF top-level projects (TLPs) and their communities are encouraged to actively build awareness of their project and activities through marketing and communications activities such as public relations, email, content, social media, website, and branding. Educational opportunities include Community Over Code, meetups, videos, podcasts, articles, third party conferences, and related community events.
+
+TLP participants are invited to review the guidelines in the <a href="https://cwiki.apache.org/confluence/display/PRESS/Publicity+Guidelines+for+Top-Level+Projects">internal ASF wiki page</a>.
+
+## Third Party Press Release Support
+Press releases that refer to the ASF and/or its projects must be approved by the VP Marketing and Publicity prior to distribution. Please allow for a minimum of 10 business days to complete the review. We are sensitive to internal approval processes and will expedite feedback when possible.
+
+* The ASF is vendor-neutral and does not provide testimonials that endorse, promote, or advertise the capability, credibility, or quality of any technology, product, or service.
+* Joint announcements are rarely issued. Examples of such releases include instances where a major industry milestone or initiative takes place, or announcing ASF Platinum Sponsorships.
+* You may request a quote for your ASF-related press release. Quotes may not be included unless approved by the VP Marketing & Publicity.
* Third-party press releases must not include the ASF boilerplate, dateline location, logo, or media contacts.
-## Publicity Guidelines for Apache Top-Level Projects {#project-guides}
+No formal press releases or announcements can be made by a third party on behalf of an Apache project, e.g., "Company ABC announces new features in Apache Project Name" or mentioning the project as part of upcoming features/support in their own products. Interested parties may issue supporting announcements with pointers to news originated by ASF or the project, e.g. a link to the corresponding mailing list, webpage or blog post.
-Apache projects and their communities are encouraged to actively build awareness of their project and activities through emails, blog posts, tweets, and other means of outreach. Educational opportunities include ApacheCon, MeetUps, videos, podcasts, articles, third party conferences, and related community events.
+## Third-Party Brand Support
+Organizations are responsible for adhering to [ASF trademark policies](https://www.apache.org/foundation/marks/resources). For questions about branding and trademark, please visit [https://apache.org/foundation/marks/contact](https://apache.org/foundation/marks/contact).
-Whilst speaking with members of the media and analyst community, projects must be referred to as "Apache _Project Name_" as per the [ASF Branding Guidelines](/foundation/marks/#guidelines). Be prepared to answer "who uses you?": as a project’s known user base grows, PMCs are welcome to promote their users in a "Powered By" page like the [Apache Hadoop Powered By page](https://cwiki.apache.org/confluence/display/hadoop2/PoweredBy). Create and encourage project supporters to utilize the project’s ["Powered By" logo](/foundation/press/kit/#poweredby). Ensure that the project maintains [**vendor neutrality**](/press/media.html#interviews), particularly when referring to project users.
+The [publicity/brand/communications guidelines created by Databricks](https://apache.org/foundation/press/Project-PR-BrandGuidelines.pdf) serve as a "good practice" model for other ASF-focused organizations to emulate.
-Projects are advised to prepare news announcements and hone their messaging privately within their PMCs (keeping the content confidential to the PMC, and not on dev@, user@ or any other public list or forum) to ensure that the public or press don’t scoop your story before it’s out or publish inaccurate information. At times messaging changes, features are unable to be delivered as intended, testimonials need adjusting, and so on, and it’s best to minimize the chances of your story to get out with incorrect information, or for nobody to recognize your news story because it was covered earlier and is therefore no longer considered newsworthy.
+## Contact Us
+press@apache.org
-Projects should refrain from issuing announcements under embargo. Pre-announcing project features or release dates to members of the media is risky, as not all journalists or outlets honor confidentiality requests in general, or adhere to embargo dates/requirements. Furthermore, many journalists are unable or unwilling to fulfill requests for retractions or corrections. Be aware, be careful.
+## FAQ
+**Can I refer to an individual, organization or community as “founding” an ASF project?** <br>
+Many projects enter the Apache Incubator with a recognized individual founder, group of founders, or corporate entity where the project originated and/or which was responsible for its development/administration.
-Apache PMCs are responsible for the "care and feeding" of a project’s code, community, and communications on a day-to-day basis. Projects are recommended to:
+The ASF is vendor neutral: all ASF projects are overseen by their respective Project Management Committees (PMCs), who guide the project's day-to-day operations. Once a project comes to the ASF, its development and oversight is the responsibility of the project’s PMC and community.
+
+There are no "owners" of any Apache project. Individuals and companies who founded projects that are now under the auspices of the ASF may be referred to as "original creator of Apache Project Name" or "original developer of Apache Project Name." Examples:
+* **Individual’s title.** "Individual’s Name, Apache Member (or Committer) and original developer of Apache Project Name."
+* **Company whose founders or employees are the original creators of an Apache project.** "Company Name, founded by the original creators of Apache Project Name" or "several Company Name team members are the original developers of Apache Project Name."
-- Review and adhere to the Publicity Guidelines for Top-Level Projects as described here
-- Ensure your [project listing and DOAP (Description Of A Project) file](https://projects.apache.org/) accurately reflect what the project is about --be succinct, particularly with the short description (note that the project may fall under one category): this helps those unfamiliar with your project be able to find you. The longer project description should be used as the official project boilerplate ("About Apache _Project Name_") and, for consistency, be included in official news announcements, media briefings, and other applications (the ASF Boilerplate is for Foundation-originating press releases and is **not** to be used in any project announcements);
-- Upload a high-resolution version of your project’s logo at [apache.org/logos/](/logos/);
-- Contact ASF Infrastructure to establish a https://blogs.apache.org/_PROJECTNAME_ project blog directory (and admin/publishing credentials);
-- Request a project interview on [Feathercast, the voice of the ASF](https://feathercast.apache.org/);
-- Gain additional exposure by posting newsworthy project updates and milestones to [announce(at)apache(dot)org](/foundation/mailinglists.html#foundation-announce); these will be added to the Apache Weekly News Round-Ups which is also sent to members of the media and analyst community;
-- Establish a Twitter (and/or other social media) account(s) with a handle that includes "Apache" or "ASF" with the project name and description (example at [https://twitter.com/ApacheAccumulo](https://twitter.com/ApacheAccumulo) ) --share information often, and point to your project Website and mailing list archives where possible;
-- Participate in Media & Analyst Training (held during ApacheCon; complimentary for Apache Committers and Members); and
-- Comply with guidelines for "founding" individuals, organizations, and communities of Apache projects as applicable (detailed below).
-No formal press releases or announcements can be made by a third party on behalf of an Apache project --for example, "Company ABC announces new features in Apache Project Name" (or including it as part of upcoming features/support in their own products). However, interested parties may issue supporting announcements with pointers to official project-originating news providing that a link to the corresponding mailing list(s) and/or blog post is included. Third parties are prohibited from using the official ASF Boilerplate or project boilerplates in their press releases or announcements unless authorized by ASF Marketing & Publicity.
-
-Guidelines for "founding" individuals, organizations, and communities of Apache Projects: many projects enter the Apache Incubator with a recognized individual founder, a group of founders, or a corporate entity where the project originated and/or which was responsible for its development/administration. The ASF is vendor neutral: all Apache projects are overseen by their respective Project Management Committees (PMCs), who guide the project's day-to-day operations. Once a project comes to the ASF, its development and oversight is the responsibility of the project’s PMC and community. There are no "owners" of any Apache project. Individuals and companies who founded projects that are now under the auspices of the ASF may be referred to as "original creator of Apache Project Name" or "original developer of Apache Project Name". Examples: 1) individual’s title --"Individual’s Name, Apache Member (or Committer) and original developer of Apache Project Name"; 2) company whose founders or employees are the original creators of an Apache project --"Company Name, founded by the original creators of Apache Project Name..." or "several Company Name team members are the original developers of Apache Project Name...".
-
-The ASF Marketing & Publicity team is happy to work with organizations as they relate to Apache projects and their overall involvement with the ASF, particularly those with "original developers" status. The [publicity/brand/communications guidelines created by Databricks](/foundation/press/Project-PR-BrandGuidelines.pdf) serve as a "good practice" model for other Apache-focused organizations to emulate.
diff --git a/content/research/index.md b/content/research/index.md
index f4bb8f6..33ef8ec 100644
--- a/content/research/index.md
+++ b/content/research/index.md
@@ -9,20 +9,20 @@
## About The ASF And Our Communities {#about}
-The Apache Software Foundation ("ASF") is based in the United States and is recognized as a 501C3 non-profit charity creating [software for the public good](https://www.apache.org/foundation/). We do this by providing services and support for many software project communities who choose to join the ASF. Thus the ASF is a very broad set of loosely-connected communities, each with their own independence, but following core [policies required by the ASF board](https://www.apache.org/board/). A key feature of ASF project governance is [independence from corporate or outside control](https://community.apache.org/projectIndependence.html).
+The Apache Software Foundation ("ASF") is based in the United States and is recognized as a 501C3 non-profit charity creating [software for the public good](/foundation/). We do this by providing services and support for many software project communities who choose to join the ASF. Thus the ASF is a very broad set of loosely-connected communities, each with their own independence, but following core [policies required by the ASF board](/board/). A key feature of ASF project governance is [independence from corporate or outside control](https://community.apache.org/projectIndependence.html).
-- See the [governance](https://www.apache.org/foundation/governance/) and [org chart](https://apache.org/foundation/governance/orgchart) of the ASF's corporate entity.
-- [The Apache Way](https://apache.org/theapacheway/index.html) is our set of behaviors for community-led projects.
+- See the [governance](/foundation/governance/) and [org chart](/foundation/governance/orgchart) of the ASF's corporate entity.
+- [The Apache Way](/theapacheway/index.html) is our set of behaviors for community-led projects.
- We work on [many publicly archived mailing lists](https://lists.apache.org/) for the [100's of ASF projects](https://projects.apache.org/).
-- All [ASF code is free to use](https://www.apache.org/free/) and provided under [our Apache-2.0 license](https://www.apache.org/licenses/), and we have a [license FAQ](https://www.apache.org/legal/resolved.html).
-- We publish [Board of Directors minutes](https://whimsy.apache.org/board/minutes/) as well as [corporate public records](https://www.apache.org/foundation/records/).
+- All [ASF code is free to use](/free/) and provided under [our Apache-2.0 license](/licenses/), and we have a [license FAQ](/legal/resolved.html).
+- We publish [Board of Directors minutes](https://whimsy.apache.org/board/minutes/) as well as [corporate public records](/foundation/records/).
- The [ASF infrastructure team](https://infra.apache.org/) can **only** answer questions about the ASF's own officially provided services.
## Codes Of Conduct And Communication Etiquette {#conduct}
-Please review the ASF's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) before working in any ASF hosted spaces or communities. The ASF's CoC is derived from a number of other popular open source project codes, and works to ensure all participants can contribute freely and comfortably in ASF spaces. Any serious CoC violations should be [reported to one of our volunteer contacts](https://www.apache.org/foundation/policies/conduct#reporting-guidelines).
+Please review the ASF's [Code of Conduct](/foundation/policies/conduct) before working in any ASF hosted spaces or communities. The ASF's CoC is derived from a number of other popular open source project codes, and works to ensure all participants can contribute freely and comfortably in ASF spaces. Any serious CoC violations should be [reported to one of our volunteer contacts](/foundation/policies/conduct#reporting-guidelines).
-ASF Conferences have their own extended [Anti-Harassment policy](https://www.apache.org/foundation/policies/anti-harassment.html), covering in-person or synchronous online events.
+ASF Conferences have their own extended [Anti-Harassment policy](/foundation/policies/anti-harassment.html), covering in-person or synchronous online events.
Virtually all communication at the ASF is expected to be on our [publicly archived mailing lists](https://community.apache.org/lists.html). We have [general email etiquette guidelines](https://community.apache.org/contributors/etiquette) and [tips on how to use our mailing lists](https://infra.apache.org/contrib-email-tips.html).
