GITHUB-6452 - Remove VZ/VZM references

Author: rgisrael

.DS_Store

@@ -4,12 +4,12 @@ title: code-of-conduct
 nav_exclude: true
 ---
 
-# Verizon Media Open Source Code of Conduct
+# Yahoo Open Source Code of Conduct
 
 ## Summary
 This Code of Conduct is our way to encourage good behavior and discourage bad behavior in our open source projects. We invite participation from many people to bring different perspectives to our projects. We will do our part to foster a welcoming and professional environment free of harassment. We expect participants to communicate professionally and thoughtfully during their involvement with this project. 
 
-Participants may lose their good standing by engaging in misconduct. For example: insulting, threatening, or conveying unwelcome sexual content. We ask participants who observe conduct issues to report the incident directly to the project's Response Team at opensource-conduct@verizonmedia.com. Verizon Media will assign a respondent to address the issue. We may remove harassers from this project. 
+Participants may lose their good standing by engaging in misconduct. For example: insulting, threatening, or conveying unwelcome sexual content. We ask participants who observe conduct issues to report the incident directly to the project's Response Team at opensource-conduct@yahooinc.com. Yahoo will assign a respondent to address the issue. We may remove harassers from this project. 
 
 This code does not replace the terms of service or acceptable use policies of the websites used to support this project. We acknowledge that participants may be subject to additional conduct terms based on their employment which may govern their online expressions.
 
@@ -41,16 +41,16 @@ Participants remain in good standing when they do not engage in misconduct or ha
 * **Don't disrupt.** Sustained disruptions in a discussion.
 
 ### Reporting Issues
-If you experience or witness misconduct, or have any other concerns about the conduct of members of this project, please report it by contacting our Response Team at opensource-conduct@verizonmedia.com who will handle your report with discretion. Your report should include:
+If you experience or witness misconduct, or have any other concerns about the conduct of members of this project, please report it by contacting our Response Team at opensource-conduct@yahooinc.com who will handle your report with discretion. Your report should include:
 * Your preferred contact information. We cannot process anonymous reports.
 * Names (real or usernames) of those involved in the incident.
 * Your account of what occurred, and if the incident is ongoing. Please provide links to or transcripts of the publicly available records (e.g. a mailing list archive or a public IRC logger), so that we can review it.
 * Any additional information that may be helpful to achieve resolution.
 
-After filing a report, a representative will contact you directly to review the incident and ask additional questions. If a member of the Verizon Media Response Team is named in an incident report, that member will be recused from handling your incident. If the complaint originates from a member of the Response Team, it will be addressed by a different member of the Response Team. We will consider reports to be confidential for the purpose of protecting victims of abuse. 
+After filing a report, a representative will contact you directly to review the incident and ask additional questions. If a member of the Yahoo Response Team is named in an incident report, that member will be recused from handling your incident. If the complaint originates from a member of the Response Team, it will be addressed by a different member of the Response Team. We will consider reports to be confidential for the purpose of protecting victims of abuse. 
 
 ### Scope
-Verizon Media will assign a Response Team member with admin rights on the project and legal rights on the project copyright. The Response Team is empowered to restrict some privileges to the project as needed. Since this project is governed by an open source license, any participant may fork the code under the terms of the project license. The Response Team’s goal is to preserve the project if possible, and will restrict or remove participation from those who disrupt the project. 
+Yahoo will assign a Response Team member with admin rights on the project and legal rights on the project copyright. The Response Team is empowered to restrict some privileges to the project as needed. Since this project is governed by an open source license, any participant may fork the code under the terms of the project license. The Response Team’s goal is to preserve the project if possible, and will restrict or remove participation from those who disrupt the project. 
 
 This code does not replace the terms of service or acceptable use policies that are provided by the websites used to support this community. Nor does this code apply to communications or actions that take place outside of the context of this community. Many participants in this project are also subject to codes of conduct based on their employment. This code is a social-contract that informs participants of our social expectations. It is not a terms of service or legal contract.
 

Code-of-conduct.md

@@ -29,4 +29,4 @@ We only seek to accept code that you are authorized to contribute to the project
 
 ## Code of Conduct
 
-We encourage inclusive and professional interactions on our project. We welcome everyone to open an issue, improve the documentation, report bug or ssubmit a pull request. By participating in this project, you agree to abide by the [Verizon Media Code of Conduct](Code-of-Conduct.md). If you feel there is a conduct issue related to this project, please raise it per the Code of Conduct process and we will address it.
+We encourage inclusive and professional interactions on our project. We welcome everyone to open an issue, improve the documentation, report bug or ssubmit a pull request. By participating in this project, you agree to abide by the [Yahoo Code of Conduct](Code-of-Conduct.md). If you feel there is a conduct issue related to this project, please raise it per the Code of Conduct process and we will address it.

Contributing.md

@@ -1,6 +1,6 @@
-# Verizon Media Open Source Guide
+# Yahoo Open Source Guide
 
-The Verizon Media Open Source guide project is a public version of the internal guide used at Verizon Media to help engineers navigate our policies and services.
+The Yahoo Open Source guide project is a public version of the internal guide used at Yahoo to help engineers navigate our policies and services.
 
 We make this guide public out of our belief that sharing code and content brings out our best while inviting others to help us get better. If you have edits, suggestions, or questions about this guide, please open an issue on this project. If you'd like to fork this guide and use it at your company, please do so but we'd love to know about it too. 
 
@@ -14,9 +14,8 @@ This guide is built using GitHub Pages with Jekyll and the Just the Docs theme.
 
 Please refer to [the contributing.md file](Contributing.md) for information about how to get involved. We welcome issues, questions, and pull requests.
 
-## Maintainers
-- Ashley Wolf: awolf@verizonmedia.com
-- Gil Yehuda: gyehuda@verizonmedia.com
+## Temporary Maintainer
+- Robert Israel: risrael@yahooinc.com
 
 Thank you to Megan Leney and Ben Pearson for helping us refine this guide.
 

README.md

@@ -17,4 +17,4 @@ search_enabled: true
 heading_anchors: true
 
 # Footer content appears at the bottom of every page's main content
-footer_content: "Copyright Verizon Media. Content licensed under CC-BY-4.0"
+footer_content: "Copyright 2021 Yahoo Inc. Content licensed under CC-BY-4.0"

_config.yml

@@ -7,7 +7,7 @@ has_children: false
 
 # Accepting Contributions to Open Source Projects
 
-The Verizon Media Open Source Program Office (OSPO) provides services to help engineers at Verizon Media prepare code for external publication, promote projects, and build open source communities. If you are interested in open source collaboration, we are here to help. To get an overview of our program, visit the OSPO Welcome Page intranet page, chat with us on our internal Slack channel (#opensource), or send an email to ospo@.
+The Yahoo Open Source Program Office (OSPO) provides services to help engineers at Yahoo prepare code for external publication, promote projects, and build open source communities. If you are interested in open source collaboration, we are here to help. To get an overview of our program, visit the OSPO Welcome Page intranet page, chat with us on our internal Slack channel (#opensource), or send an email to ospo@.
 
 This page addresses topics related to accepting contributions into our projects. 
 

assets/VZM-OSG-Web.jpg

@@ -7,13 +7,13 @@ nav_order: 3
 
 # Contributing to Open Source Projects
 
-The Verizon Media Open Source Program Office (OSPO) provides services to help engineers at Verizon Media prepare code for external publication, promote projects, and build open source communities. If you are interested in open source collaboration, we are here to help. To get an overview of our program, vist the OSPO Welcome Page intranet page, chat with us on our internal Slack channel (#opensource), or send an email to ospo@.
+The Yahoo Open Source Program Office (OSPO) provides services to help engineers at Yahoo prepare code for external publication, promote projects, and build open source communities. If you are interested in open source collaboration, we are here to help. To get an overview of our program, vist the OSPO Welcome Page intranet page, chat with us on our internal Slack channel (#opensource), or send an email to ospo@.
 
 This page highlights the steps you'll take when it comes to contributing company code as an existing open source project managed by someone else. 
 
 ### Step Zero: Planning for Success
 
-We encourage Verizon Media engineers to contribute to projects we rely upon. We seek to be good open source citizens. If you find a bug, or can make some code better, we want to enable you do it. However, we want you to be aware of some concerns that you should keep in mind. Most of the time, these will not come up. Given the number of projects we work on, the number of engineers we have, and the complexity of some projects, we occasionally run into blocking issues.
+We encourage Yahoo engineers to contribute to projects we rely upon. We seek to be good open source citizens. If you find a bug, or can make some code better, we want to enable you do it. However, we want you to be aware of some concerns that you should keep in mind. Most of the time, these will not come up. Given the number of projects we work on, the number of engineers we have, and the complexity of some projects, we occasionally run into blocking issues.
 
 Please read the guidelines below. If none of these issues are relevant to your pull request, then go ahead and contribute to an open source project. You do not need to get approval for every pull request. The overhead involved in these approvals is not worth it. That said, if the issues below are relevant, or if you have **any** concerns about your contribution, ask us. We're here to help you.
 

docs/accepting/accepting.md

@@ -11,18 +11,18 @@ Some projects require us to keep records of who we've authorized to contribute t
 
 ## Contribute to Google Projects
 
-Google requires corporate contributors be listed on a list that Verizon Media's OSPO maintains with Google. To contribute to a Google Open Source Project, complete the following steps:
+Google requires corporate contributors be listed on a list that Yahoo's OSPO maintains with Google. To contribute to a Google Open Source Project, complete the following steps:
 
 1. Go to your Github [Emails](<https://github.com/settings/emails>) Settings page on your personal GitHub account.
-1. Add your verizonmedia.com email address as either a primary or backup email address. This helps Google's Bot determine that you are a Verizon Media employee and your contribution to their project is therefore authorized by our OSPO. Note: You can make your email address private if you like. We ask that you remove it when you leave Verizon Media.
-1. Use your verizonmedia.com email address for any contributions to Google projects that you make on behalf of Verizon Media. For example, for projects that use git for source control, use the ``git config`` command to set your email address.
-1. Request to be added to the GoogleGroup whitelist for Verizon Media contributors to Google open source projects.
+1. Add your yahooinc.com email address as either a primary or backup email address. This helps Google's Bot determine that you are a Yahoo employee and your contribution to their project is therefore authorized by our OSPO. Note: You can make your email address private if you like. We ask that you remove it when you leave Yahoo.
+1. Use your yahooinc.com email address for any contributions to Google projects that you make on behalf of Yahoo. For example, for projects that use git for source control, use the ``git config`` command to set your email address.
+1. Request to be added to the GoogleGroup whitelist for Yahoo contributors to Google open source projects.
 
 Once we add you to the list, you'll be able to contribute to Google's projects.
 
 ## Contribute to Apache Software Foundation (ASF) Projects
 
-Verizon Media has dozens of active participant positions in [Apache](https://www.apache.org/) projects. Some employees are Project Management Committee (PMC) members, chairs, or committers. Apache requires contributors to sign CLAs. For details, see Apache's [contributor](https://community.apache.org/contributors/) page. Currently, we contribute to Apache Druid, Hadoop, HBase, Hive, OMID, Oozie, Pig, Phoenix, Pulsar, Spark, Storm, Tez, and Traffic Server (and probably others too).  
+Yahoo has dozens of active participant positions in [Apache](https://www.apache.org/) projects. Some employees are Project Management Committee (PMC) members, chairs, or committers. Apache requires contributors to sign CLAs. For details, see Apache's [contributor](https://community.apache.org/contributors/) page. Currently, we contribute to Apache Druid, Hadoop, HBase, Hive, OMID, Oozie, Pig, Phoenix, Pulsar, Spark, Storm, Tez, and Traffic Server (and probably others too).  
 
 Before contributing to an Apache project:
 1. Open a Jira ticket to request authorization to sign the CLA.
@@ -40,7 +40,7 @@ To contribute to [OpenStack Foundation](https://https://www.openstack.org/) Foun
 
 ## Contribute to OpenID Foundation
 
-To contribute to [OpenID Foundation](https://openid.net/foundation/) projects, open a JIRA ticket and include your manager's name and project name you are contributing to, along with a brief description of your contribution goals. We will review your request with the Verizon Media Identity team. Once approved to contribute:
+To contribute to [OpenID Foundation](https://openid.net/foundation/) projects, open a JIRA ticket and include your manager's name and project name you are contributing to, along with a brief description of your contribution goals. We will review your request with the Yahoo Identity team. Once approved to contribute:
 
 1. You sign the [OpenID Individual Contributor License Agreement (ICLA)](https://openid.net/intellectual-property/contribution-license-agreement/) and the [OpenID Corporate Contributor License Agreement (CCLA)](https://openid.net/intellectual-property/contribution-license-agreement/)
 1. Upload the signed ICLA and CCLA to the JIRA ticket.
@@ -57,7 +57,7 @@ The OpenID Foundation also sponsors working groups. Before signing an Intellectu
 
 ## Contribute to CNCF  
 
-To contribute to [Cloud Native Computing Foundation](https://cncf.io) projects, open a JIRA ticket and include your manager's name and project name you are contributing to, along with a brief description of your contribution goals. We will review your request with the Verizon Media Omega team. Once approved to contribute:
+To contribute to [Cloud Native Computing Foundation](https://cncf.io) projects, open a JIRA ticket and include your manager's name and project name you are contributing to, along with a brief description of your contribution goals. We will review your request with the Yahoo Omega team. Once approved to contribute:
 
 1. Sign the [CNCF Individual Contributor License Agreement (ICLA)](https://identity.linuxfoundation.org/?destination=node/285/employee-signup). Please add your signed ICLA to the JIRA ticket.
 1. We will update the CNCF [Corporate Contributor License Agreement (CCLA)](https://identity.linuxfoundation.org/?destination=node/285/organization-signup).

docs/contributing/contributing.md

@@ -7,7 +7,7 @@ parent: Launching Mobile Apps
 
 # Publishing Binaries 
 
-The Verizon Media Open Source Program Office (OSPO) provides services to help engineers at Verizon Media succeed with open source. If you are interested to learn more about open source, we are here to help. To get an overview of our program, vist the OSPO Welcome Page intranet page, chat with us on our internal Slack channel (#opensource), or send an email to ospo@.
+The Yahoo Open Source Program Office (OSPO) provides services to help engineers at Yahoo succeed with open source. If you are interested to learn more about open source, we are here to help. To get an overview of our program, vist the OSPO Welcome Page intranet page, chat with us on our internal Slack channel (#opensource), or send an email to ospo@.
 
 This page highlights issues engineering teams need to know about open source code in their binary apps. 
 

docs/contributing/recordkeeping.md

@@ -7,13 +7,13 @@ has_children: true
 
 # Launching Mobile Apps
 
-The Verizon Media Open Source Program Office (OSPO) provides services to help engineers at Verizon Media succeed with open source. If you are interested to learn more about open source, we are here to help. To get an overview of our program, vist the OSPO Welcome Page intranet page, chat with us on our internal Slack channel (#opensource), or send an email to ospo@.
+The Yahoo Open Source Program Office (OSPO) provides services to help engineers at Yahoo succeed with open source. If you are interested to learn more about open source, we are here to help. To get an overview of our program, vist the OSPO Welcome Page intranet page, chat with us on our internal Slack channel (#opensource), or send an email to ospo@.
 
 This page highlights issues Mobile App and SDK engineering teams need to know about open source code in their apps. 
 
 ### Step Zero: Planning for Success
 
-Mobile apps that Verizon Media publishes must include 3rd party notices listing relevant open source license information. We usually make this available in a menu selection near the app's Terms of Service and Privacy Policy text, in a Settings or About menu. We call this _Credits_ whereas some apps list these as _Notices_, _Third Party Notices_, or _Open Source Credits_.
+Mobile apps that Yahoo publishes must include 3rd party notices listing relevant open source license information. We usually make this available in a menu selection near the app's Terms of Service and Privacy Policy text, in a Settings or About menu. We call this _Credits_ whereas some apps list these as _Notices_, _Third Party Notices_, or _Open Source Credits_.
 
 Mobile app teams get the contents of the Credits file from our build system. Please use that file. Some teams manage their own credits-file creation process, which the OSPO can help audit for accuracy. In cases we publish a 3rd party app, the vendor must supply the notices. In cases we are providing an app for another entity to publish, we must supply the notices to the customer.