Closed Bug 1600148 Opened 4 years ago Closed 4 years ago

2019 Updates for CPG Governance Pages

Categories

(www.mozilla.org :: Pages & Content, enhancement, P2)

Product:
www.mozilla.org
Component:
Pages & Content
Version:
Production
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: eirwin, Unassigned)

Details

Hello,

I would like to request the following:

  1. A new mozilla.org page to replace our current Community Hotline landing page (which is on Splash and Splash is going away).
  2. Updates to the Community Participation Guidelines Page
  3. Updates to the 'How to Report Page'

These changes are documented here: https://docs.google.com/document/d/1Uvex8CNAXAFizQNFw_wGZw-2o1t6PI7IEm3KyqClTd8/edit

There are two small process changes as part of these updates:

  1. we remove inclusion@mozilla.com alias for questions (because of unmanageable spam), and replace with cpg-inquiries@mozilla.com
  2. We start logging changes to CPG in a flat/Github file rather than promising updates to a mailing list.

I need Shoshana and Mitchell to sign off, before moving forward with actual content changes.

Mitchell has approved adding 'caste' as a supported group (so no blocker there), talking to Shoshana next week.

Shoshana has also signed off,

Adding in L10N Driver, how do we launch with all languages?

Flags: needinfo?(pmo)
Priority: -- → P2

As a timeline we want this updated before All Hands

@eirwin, there are two pages associated with CPG policies:

1). https://www.mozilla.org/en-US/about/governance/policies/participation/
2). https://www.mozilla.org/en-US/about/governance/policies/participation/reporting/

Languages: de, es-ES, fr, hi-IN, ja, pt-BR, zh-TW.

The Bedrock team is the one implementing the changes. Localization takes over once the update is set up. Due to the tone of language is more legal oriented, we will send the pages to our localization vendor to complete the update. I am adding Eric to add this to the team's dashboard.

Let me know if we continue supporting the same languages or we want to expand it to more. What is the time line to release the update

Flags: needinfo?(pmo)

Thanks!

I consulted our team, who believe we should have CPG translated in Top 10 Firefox languages (which represent 90% of FF users) + Arabic Indonesian and Taiwanese (where we have big communities).
https://docs.google.com/document/d/166A9CyI1rWM1UBxrZTzIF5-6oJnVOmOP4MteRlJeUMY/edit

I say this no knowing how much additional work that would be. Or cost center for vendor .

Also adding Tara should she have an opinion on language priorities for staff.

Flags: needinfo?(trobertson)

I like the idea of adding caste, but think some education and communication would need to happen around this for it to be meaningful.

Flags: needinfo?(trobertson)

Thanks Tara, as part of this release, I'll have a small comms plan, outlining changes and the reason we're adding caste, based on my notes here from Thenmozhi Soundararajan. (https://docs.google.com/document/d/1-lm_2xmZepTxOVsL4EWlL68_FsN2IAd-BA-8-sOmcHM/edit), and anything else you would like to add. I'll update the bug with this comms plan when I have it.

Any resources to make that part of an educational offering would be out of scope of OI resourcing capacity.

Here is my communications plan - please provide feedback by January 8th.

https://docs.google.com/document/d/1ocJlVem_5oMGFSWjSU8hfpPt3SCsxwMUG7IeqvET9Eo/edit#

We will be improving translation list
from: de, es-ES, fr, hi-IN, ja, pt-BR, zh-TW.

To: de, es, fr, ru, pt, it, ja, zh-TW, zh-CN, pl, nl, hi, id, ar

Flags: needinfo?(trobertson)
Flags: needinfo?(nukeador)
Flags: needinfo?(lharris)

HI Erik

We would like to publish these before the next All Hands. And Peiying requires the first copy in bedrock to begin localizing is that possible?

Flags: needinfo?(erenaud)

@Emma,
1). Both participation and reporting docs are in bedrock so we need them both ready for localization.
2). For the locale list, because how mozorg is set up, es will be in es-ES and populate to es-* variants, and pt will be in pt-BR and populate to pt-PT.

@Eric, I would like to see the strings extracted by mid January so we can be sent to agency for localization before all hands. Due to the language and tone in these docs, we have sent them to our agency to provide the translation. Communities will have time review the content once they are delivered in Pontoon.

Flags: needinfo?(nukeador)

@emma I suggest with the new email alias we use something like cpg-inquiries [at] mozilla.com to avoid web crawlers from adding this alias to all the spam lists as well.

Flags: needinfo?(lharris) → needinfo?(eirwin)

Emma - I don't have access to the source/changes document (I've requested that in gdocs) so this request is effectively blocked.

For the stated requirements, I have the following questions (please ignore them if they're in the source/changes doc):

  • A new mozilla.org page to replace our current Community Hotline landing page (which is on Splash and Splash is going away).
    Q - What is the desired URL for this new page?

  • Updates to the Community Participation Guidelines Page
    Q - What is the URL for this page?

  • Updates to the 'How to Report Page'
    Q - What is the URL for this page?

  • There are two small process changes as part of these updates:

  • we remove inclusion@mozilla.com alias for questions (because of unmanageable spam), and replace with cpg-inquiries@mozilla.com
    Q - is this included in the change document?
    We start logging changes to CPG in a flat/Github file rather than promising updates to a mailing list.
    Q - is this included in the change document?

  • I need Shoshana and Mitchell to sign off, before moving forward with actual content changes.
    Q - Have both Shoshana (it looks like she has in Comment2) and Mitchell provided their final approvals of the content?
    Q - Are there any other stakeholders that need to provide input (is their a RASCI associated with this project?)

Flags: needinfo?(erenaud)

@eric, the info on the URLs for CPG and Report pages are included in comment #4.

Hi @eric, sorry for the delay - back from holidays. I have granted you access, and my responses to your questions below (which many I think will also be answered in the doc):

A new mozilla.org page to replace our current Community Hotline landing page (which is on Splash and Splash is going away).
Q - What is the desired URL for this new page?

I think based on the current naming conventions for the CPG, and How to Report:

https://www.mozilla.org/en-US/about/governance/policies/participation/
https://www.mozilla.org/en-US/about/governance/policies/participation/reporting/

It should be:

https://www.mozilla.org/en-US/about/governance/policies/participation/reporting/community-hotline

Updates to the Community Participation Guidelines Page
Q - What is the URL for this page?

https://www.mozilla.org/en-US/about/governance/policies/participation/

Updates to the 'How to Report Page'
Q - What is the URL for this page?

https://www.mozilla.org/en-US/about/governance/policies/participation/reporting/

There are two small process changes as part of these updates:

we remove inclusion@mozilla.com alias for questions (because of unmanageable spam), and replace with cpg-questions@mozilla.com
Q - is this included in the change document?

Yes - also please see change from inquries@mozilla.com to cpg-questions@mozilla.com

We start logging changes to CPG in a flat/Github file rather than promising updates to a mailing list.
Q - is this included in the change document?

https://github.com/emmairwin/cpg/blob/master/CHANGELOG.md

I need Shoshana and Mitchell to sign off, before moving forward with actual content changes.
Q - Have both Shoshana (it looks like she has in Comment2) and Mitchell provided their final approvals of the content?

Yes both have approved.
Q - Are there any other stakeholders that need to provide input (is their a RASCI associated with this project?)
All stakeholders have been notified. I can update if there are any emergency/last minute blockers, but there are no so far.

Flags: needinfo?(eirwin)

As an update I have confirmed that the staging version of the following pages fully meet the request:

We will do a soft-launch (website update, no comms) in the next day or two depending on the team's ability, and send out comms sometime before All Hands (all in RASCI will be consulted on that content before it goes out).

Flags: needinfo?(trobertson)

@Emma, the three pages for all the requested locales are now on production (live). The next step is to have the communities review them is they choose to do so.

This request is complete.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.