Proposing workstreams #12
Replies: 13 comments 62 replies
-
|
If you are interested in participating in or leading one of these workstreams, please reply on the workstream threads below 👇🏾 |
Beta Was this translation helpful? Give feedback.
-
|
Interested in the |
Beta Was this translation helpful? Give feedback.
-
|
Interested in the |
Beta Was this translation helpful? Give feedback.
-
|
Interested in the |
Beta Was this translation helpful? Give feedback.
-
|
Interested in the |
Beta Was this translation helpful? Give feedback.
-
|
Interested in the |
Beta Was this translation helpful? Give feedback.
-
|
Interested in the |
Beta Was this translation helpful? Give feedback.
-
|
I am mainly a coder and would be interested in tooling workstream when it spins up. As part of that, I am thinking any adopted set of terms deemed non-inclusive as well as suggested replacements that this effort (or others) publishes and maintains would be good to have codified into a standard file format that can be slurrped into various tools and workflows (npm, json, python, etc.). AFAIKT, the dashboard tools so far referenced here from Red-Hat's efforts aren't pitched at that level. |
Beta Was this translation helpful? Give feedback.
-
|
Initial Enterprise/Company Workstream meeting this Thursday Feb 11 at 2 EST - please email andre_p_pellet@dell.com to be added to the invite. |
Beta Was this translation helpful? Give feedback.
-
|
KianaMinkie – Can you send me your email address?
From: KianaMinkie <notifications@github.com>
Sent: Monday, February 8, 2021 1:01 PM
To: inclusivenaming/org
Cc: Pellet, Andre P; Mention
Subject: Re: [inclusivenaming/org] Proposing workstreams (#12)
[EXTERNAL EMAIL]
I'd love to join this workstream too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#12 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASMZGUTI6FBJ4OJACHJRSE3S6AREBANCNFSM4U5TIDWQ>.
|
Beta Was this translation helpful? Give feedback.
-
|
Wrt the SDO workstream:
I’m talking to my colleague Matthew Schnoor today about him stepping up to lead here (e.g. recruiting him 😉)
Perhaps he can tag-team with Joanna.
Best,
Jim
From: Joanna Lee <notifications@github.com>
Sent: Monday, February 8, 2021 5:26 PM
To: inclusivenaming/org <org@noreply.github.com>
Cc: St Leger, Jim <jim.st.leger@intel.com>; Manual <manual@noreply.github.com>
Subject: Re: [inclusivenaming/org] Proposing workstreams (#12)
If this workstream still needs a leader, I am happy to volunteer for this position. I'm a legal counselor to dozens of SDOs. I recently helped a well-known electronics SDO develop an inclusive language policy. I look forward to contributing to this workstream!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#12 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AN6RFBRHW4GCWKVW5WJLBEDS6B6JNANCNFSM4U5TIDWQ>.
|
Beta Was this translation helpful? Give feedback.
-
|
@celestehorgan Hi -- I intended to join the language workstream. I've filled out the Doodle form for scheduling and hope to attend the upcoming kickoff. Just letting you know since I don't see my name on the list (@MonicaRush). If there's anything else I need to do please LMK. Thank you, Celeste! |
Beta Was this translation helpful? Give feedback.
-
|
All -- I think we've solved our initial goals (identifying the workstreams and leads, doing some recruiting for each, and starting to kickoff meetings). If you're on Slack, here are the channels... Pillar / vertical workstreams:
Program / horizontal workstreams:
If you're not on Slack, you should join us! I'm going to lock and close this discussion, but questions/comments/concerns can be directed to:
Details on our communication platforms can be found here: https://inclusivenaming.org/get-involved/ Looking forward to all of the work we'll get to do together! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As we grow the Inclusive Naming Initiative, we want to ensure that members are aligned with areas that:
The leadership team is opening this discussion thread to formally propose workstreams!
As you'll come to notice, I tend to draw many ideas from work in the Kubernetes Community.
Here, I'll liken the proposed workstreams to the various types of Special Interest Groups (SIGs):
Our proposed workstreams are as follows:
Domain-specific
Each of the domain-specific workstreams will be focused around building process within the named domain:
Open Source
Lead(s): @justaugustus / @celestehorgan
Members:
Company
Lead(s): @andrepellet
Members:
Standards Developing Organizations (SDOs)
Lead(s):
Members:
Program Management
Program Management workstreams focus on cross-Initiative efforts.
Language
Purpose: Researching language, reviewing/approving recommendations
Lead(s): @celestehorgan
Members:
Community & Tooling
Purpose: Welcoming/directing new contributors, managing new contributions
Lead(s):
Members:
Marketing
Purpose: Spreading the word, advertising, and content production
Work items:
Lead(s): @xmulligan / @pritianka
Members:
Administration (restricted membership)
Purpose: Identity management
Work items:
Lead(s): @justaugustus / @edwarnicke
Members:
cc: @celestehorgan @edwarnicke @pritianka @xmulligan
Beta Was this translation helpful? Give feedback.
All reactions