-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add role description for l10n-drivers in community roles document #125
Comments
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
Expectations
@Delphine @flodolo @peiying2 @TheoChevalier thoughts? |
Not on expectations, but minor suggestion on responsibilities: 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:
|
@TheoChevalier
Reach is definitely better. I'll go with that one. Thanks!
@Delphine
Here's an example:
Responsibility (the what):
- Mentor the growth of l10n communities.
Expectation (the how):
- Help the community organize events to recruit and train localizers.
Is that helpful?
Yeah, I agree that "respond positively" isn't an accurate wording. I'll have to think more on that.
…On Wed, Jun 20, 2018 at 12:52 PM, Delphine Lebédel ***@***.*** > wrote:
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?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#125 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB1yZFU_RPHS7bt5wUtjEqShEeDlz_mSks5t-poJgaJpZM4Uveyg>
.
|
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."
project -> organization?
Evaluate openly? 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”
I think we should make this project oriented instead of product oriented. 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 |
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
Expectations
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":
|
Yes, I second everyone, very well put together.
Delphine's comments, though detailed, but very concrete for people outside
our team to understand, especially the 2nd and 3rd bullet.
…On Thu, Jun 21, 2018 at 10:31 AM, Delphine Lebédel ***@***.*** > wrote:
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?)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#125 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFzumTYgrxvwo2s7GLjEXskHu4NyffRBks5t-9hagaJpZM4Uveyg>
.
|
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.). |
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? |
L10n-drivers is the name of the Mozilla staff on the l10n team.
El lun., 25 de jun. de 2018 13:23, LucyeoH <notifications@github.com>
escribió:
"Respond to reports of CPG violations within the community." <- @emmairwin
<https://github.com/emmairwin> I'm wondering if this should be something
like "respond to or escalate reports of CPG violations within the community
as appropriate".
I like that wording. It's what I was going for, but yours is better :-)
… 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?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#125 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB1yZP_jMVS4hwIhmFx-wCwbco68CZeUks5uATjCgaJpZM4Uveyg>
.
|
It might be helpful to know about this doc we are creating (which will be
updated when we have a new system)
https://github.com/mozilla/diversity/blob/master/Draft-%20REPORTING.MD
…On Mon, Jun 25, 2018 at 12:59 PM, gueroJeff ***@***.***> wrote:
L10n-drivers is the name of the Mozilla staff on the l10n team.
El lun., 25 de jun. de 2018 13:23, LucyeoH ***@***.***>
escribió:
> "Respond to reports of CPG violations within the community." <-
@emmairwin
> <https://github.com/emmairwin> I'm wondering if this should be something
> like "respond to or escalate reports of CPG violations within the
community
> as appropriate".
>
I like that wording. It's what I was going for, but yours is better :-)
> 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?
>
> —
> You are receiving this because you were assigned.
> Reply to this email directly, view it on GitHub
> <https://github.com/mozilla-l10n/localizer-documentation/
issues/125#issuecomment-400065368>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AB1yZP_jMVS4hwIhmFx-
wCwbco68CZeUks5uATjCgaJpZM4Uveyg>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#125 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADsynxFnPoJS1fjXWZAKlFHTMqM7YN_ks5uAUE7gaJpZM4Uveyg>
.
--
-- Emma Irwin
|
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. |
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 ).
The text was updated successfully, but these errors were encountered: