Add role description for l10n-drivers in community roles document
Closed this issue · 19 comments
l10n_community_roles.md needs to have a section describing how the l10n-drivers are accountable to the community in terms of their responsibilities and expectations (see this discourse comment from @MikkCZ ).
I'm struggling a bit to properly define the expectations placed upon us by the community. I have the responsibilities covered, but could use some feedback. Here's what I have:
Responsibilities
- Mentor new l10n communities through the process of launching a new localized Mozilla product.
- Communicate project updates and participation invitations in primary communications channels, like the dev-l10n mailing list and IRC.
- Respond to reports of CPG violations within the community.
- Create and guarantee a safe, collaborative space for all communities.
- Work with l10n communities to increase the user base for their localizations.
- Perform technical validation of contributions from the community to determine whether to ship contributions.
- Create and maintain tooling that promotes a healthy and simple localization workflow for the community.
- Recognize outstanding contributions made by the community.
- Promote translation and localization best practices within the project.
Expectations
- Promote the growth and health of each l10n community.
- Represent and advocate for the needs of the l10n community to the Mozilla organization.
- Respond positively to ideas for l10n improvements from the community.
- Utilize open communication channels at every opportunity.
@Delphine @flodolo @peiying2 @TheoChevalier thoughts?
Not on expectations, but minor suggestion on responsibilities: user base > reach, maybe? Not sure user base would work well for an advocacy campaign, for instance.
And I think my brain still struggles to differentiate the two categories… Will try to find other examples online
Yes I admit I still have a hard time understanding the difference between "Responsibilities" and "Expectations" (and although it's been explained to me a few time). Are "Expectations" just a sort of high-level summary of the "Responsibilities", and that should encompass them all? I feel like I'll be able to answer better once I get a better understanding of these definitions :)
Other than that:
- "Respond positively to ideas for l10n improvements from the community." -> should this be more "Review and apply when possible ideas for etc."? I wonder if "respond positively" sounds like we're going to adopt just any idea that comes up, no matter what (maybe it's just because I'm not a native English speaker that I understand it this way). I feel like we should rather say something along the lines that we'll always respond, then review/analyze, and finally apply when possible. Thoughts?
Mentor new l10n communities through the process of launching a new localized Mozilla product.
I think this could be more generic (new products for all, new locales): "Mentor new and existing l10n communities through the process of launching localized Mozilla products."
Promote translation and localization best practices within the project.
project -> organization?
Respond positively to ideas for l10n improvements from the community.
Evaluate openly?
Possible ideas for responsibilities, not sure how to word them:
- Making sure products are properly localizable (strings review, open to all locales, etc.)
- Avoid overload/burnout by balancing requests, and identifying alternative solutions to localization products. Thinking mostly about using MT, agencies, asking to move deadlines, etc.
Possible ideas for responsibilities, not sure how to word them:
You meant expectations? If I understood the definition correctly, this seem to be more “how“ than “what”
- Making sure products are properly localizable (strings review, open to all locales, etc.)
- Avoid overload/burnout by balancing requests, and identifying alternative solutions to localization products. Thinking mostly about using MT, agencies, asking to move deadlines, etc.
I think we should make this project oriented instead of product oriented.
Also open to all locales → open to as many locales as possible? (since this usually depends on resource, platform availability, strategic decisions on a project, etc)
I’m also wondering if this wouldn’t be implicit in the “promote the health of the community” and “advocate for the needs of the l10n community” points
You meant expectations? If I understood the definition correctly, this seem to be more “how“ than “what”
I think you're right. The distinction is still really confused in my head 🦄
There's definitely overlap between some of the points (e.g., isn't the CPG part covered by the next point about "safe community"?), but some are worth being called out explicitly.
Ok, new draft incorporating your feedback. Thoughts?
Responsibilities
- Mentor new and existing l10n communities through the process of launching localized Mozilla projects.
- Communicate project updates and participation invitations in primary communications channels, like the dev-l10n mailing list and IRC.
- Respond to reports of CPG violations within the community.
- Work with l10n communities to increase the reach of their localizations.
- Perform technical validation of contributions from the community to determine whether to ship contributions.
- Create and maintain tooling that promotes a healthy and simple localization workflow for the community.
- Recognize outstanding contributions made by the community.
- Promote translation and localization best practices within Mozilla.
Expectations
- Promote the open, collaborative processes within each l10n community.
- Represent and advocate for the needs of the l10n community to the Mozilla organization.
- Evaluate ideas for l10n improvements from the community openly.
- Utilize open communication channels at every opportunity.
- Prevent localization from being an obligation by balancing requests and resources to respect community time and availability.
Thoughts? I would also be interested in input from @MikkCZ to see if this is meeting his own expectations.
Looks good to me 👍
Same here, thanks!
This looks really good to me, thanks Jeff!
I don't know if this is diving into too much details, but I was also thinking under "Responsibilities":
- Give early feedback on code and strings to developers - and fix when necessary - to prevent localization issues
- Act as a point of contact for questions from localizers regarding localizable content
- Advocate for more culturally and linguistically friendly features to Product Management (maybe this is already represented by the "Represent and advocate for the needs of the l10n community to the Mozilla organization." under Expectations?)
Advocate for more culturally and linguistically friendly features to Product Management (maybe this is already represented by the "Represent and advocate for the needs of the l10n community to the Mozilla organization." under Expectations?)
I would say it’s implied, but if we’re adding it I would replace Product Management with something that works for all PMs
I was wondering if there should be something about facilitating connections to Mozilla outside of l10n (e.g. getting in touch with people working on specific projects, find who to talk to for specific questions, etc.).
Thoughts? I would also be interested in input from @MikkCZ to see if this is meeting his own expectations.
Thanks for sharing the proposal, +1 from me. I think it's time to put it in the docs and ask for feedback from a broader forum of all localizers.
"Respond to reports of CPG violations within the community." <- @emmairwin I'm wondering if this should be something like "respond to or escalate reports of CPG violations within the community as appropriate".
Sorry I've lost track of some elements of this are we also going to have some messaging around how someone can become an l10n driver?
Updated the doc with feedback from this issue and will close it now. If any additional changes need to be made, please file a new issue.