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.
-
|
I'm interested in helping with this workstream |
Beta Was this translation helpful? Give feedback.
-
|
I’d like to help here. . |
Beta Was this translation helpful? Give feedback.
-
|
I'm interested in helping with the Open Source workstream |
Beta Was this translation helpful? Give feedback.
-
|
Definitely interested in helping in open source |
Beta Was this translation helpful? Give feedback.
-
|
I would also like to participate in the open source workstream |
Beta Was this translation helpful? Give feedback.
-
|
Interested in the |
Beta Was this translation helpful? Give feedback.
-
|
Hi Stephen, as discussed - I am happy to lead this effort and organize a follow up to better define this workstream. |
Beta Was this translation helpful? Give feedback.
-
|
I am interesting in signing up for this one |
Beta Was this translation helpful? Give feedback.
-
|
I'm interested in this one |
Beta Was this translation helpful? Give feedback.
-
|
I am interested in this work stream |
Beta Was this translation helpful? Give feedback.
-
|
Feel free to add me for this one! |
Beta Was this translation helpful? Give feedback.
-
|
Interested in the |
Beta Was this translation helpful? Give feedback.
-
|
I would like to work on the SDO stream, focusing on IETF. |
Beta Was this translation helpful? Give feedback.
-
|
I work with many SDOs and would like to participate in this workstream |
Beta Was this translation helpful? Give feedback.
-
|
I would like to work on the SDO stream. |
Beta Was this translation helpful? Give feedback.
-
|
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! |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I'm joining this workstream and I volunteer to serve as co-lead with Joanna. |
Beta Was this translation helpful? Give feedback.
-
|
Interested in the |
Beta Was this translation helpful? Give feedback.
-
|
I would like to participate in this workstream |
Beta Was this translation helpful? Give feedback.
-
|
I'd love to join the |
Beta Was this translation helpful? Give feedback.
-
|
I'm interested in language workstream as this is what we're doing now at my company. |
Beta Was this translation helpful? Give feedback.
-
|
I'm interested in this work stream as a secondary interest or equal to Intake. |
Beta Was this translation helpful? Give feedback.
-
|
I'd love to join this workstream too. |
Beta Was this translation helpful? Give feedback.
-
|
Interested in the |
Beta Was this translation helpful? Give feedback.
-
|
This would be my second choice; I've been involved in ietf newcomer's stuff for several years, and give the tutorials, e.g. |
Beta Was this translation helpful? Give feedback.
-
|
I am interested in the |
Beta Was this translation helpful? Give feedback.
-
|
I'm interested in this work stream but would recommend it be relabeled as "Community" to encompass a member's experience with on boarding and learning. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Spoke with some of the leads (@celestehorgan @pritianka @edwarnicke @xmulligan) today and we're going to update this workstream name to Lots of great discussion has already been happening (#12 (comment), #18, #14) and it sounds like both @markcmiller86, @edwarnicke, and @smokris (just to name a few in addition those who have already mentioned) are interested in this effort. With that reframing, who else is interested in the |
Beta Was this translation helpful? Give feedback.
-
I'll maintain interest here with the new framing |
Beta Was this translation helpful? Give feedback.
-
|
Interested in the |
Beta Was this translation helpful? Give feedback.
-
|
I am interested in |
Beta Was this translation helpful? Give feedback.
-
|
I can definitely help here. |
Beta Was this translation helpful? Give feedback.
-
|
For everyone that wants to help with marketing, please join the #ws-marketing channel in slack so we can start organizing there |
Beta Was this translation helpful? Give feedback.
-
|
Would love to participate here! |
Beta Was this translation helpful? Give feedback.
-
|
I'd love to join this workstream! |
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.
-
|
@markcmiller86 Any interest in doing CI usable static-analysis style checkers? |
Beta Was this translation helpful? Give feedback.
-
|
Sure. |
Beta Was this translation helpful? Give feedback.
-
|
Excellent! I've mostly been hanging out in Go lately, and using golangci-lint ... and it looks like it would be quite doable to write a plugin for that to cover inclusivenaming issues as part of CI static analysis :) What would be your preferred language to start with, and what is its static analysis culture like? |
Beta Was this translation helpful? Give feedback.
-
|
Preferred language? Probably English 😆. Well, I wish I was one of those types that had a large number to choose from. I don't know Go. I can do perl, bash or python pretty well. I figure no on is interested in the first two. So, probably python is best. OTOH, I would not want to let my limited programming language knowedge to somehow wind up being a deciding factor in what is chosen. |
Beta Was this translation helpful? Give feedback.
-
|
See here: #12 (reply in thread) |
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.
-
|
Sure. I'm using a personal address for this project: Thanks! |
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.
-
|
Fantastic, Jim. Thank you. If Matthew is open to leading I would be delighted to collaborate with him. Best, |
Beta Was this translation helpful? Give feedback.
-
|
Hi @JimStLeger @mschnoor-intel @joannalee333 - I'd like to join this workstream :) Sorry I am a bit late in raising my hand. Let me know if I've missed anything. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, kdannels! It isn't too late. Please join us in Slack and we'll bring you up to speed. |
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.
and others
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