Video summary
The Neurodiversity community is celebrating the official acceptance of their new community hub session for CubeCon in Salt Lake City, scheduled to take place in November 2026. Following this confirmation, the team is finalizing the schedule and preparing specific exercises for attendees, including a neuroinclusive social contract activity designed to help create self-autonomous and accountable teams. This upcoming event marks a significant milestone after a year of dedicated work by the group, serving as a platform to gather real-world feedback from the community before they return to Europe in 2027 with an officially published best practices document. The atmosphere is one of excitement and anticipation, with organizers noting that the current quiet period is merely a "silence before the storm" before a surge of new information and updates following the conference.
A central focus of the meeting was the collaborative refinement of the neurodiversity best practices document, where members like Pashant contributed their own experiences and notes regarding onboarding procedures. The team emphasized that this process is not about determining who is right or wrong, but rather a collective effort to brainstorm, iterate, and ensure clarity for everyone involved. They plan to incorporate all feedback received during the Salt Lake City event into the document, aiming to polish and publish it by March of the following year. This iterative approach ensures that the guidelines remain relevant and effective, drawing directly from the lived experiences of the community rather than theoretical assumptions.
For those interested in contributing beyond documentation, such as through coding or technical improvements, the speakers provided clear guidance on how to get involved with the CNCF ecosystem. They recommended exploring the Kubernetes repository for issues tagged for new contributors and suggested joining Tactical Advisory Groups within CNCF Slack channels that align with specific interests like security or infrastructure. Additionally, they highlighted cloudnative.dev as a resource for finding "good first issue" tickets, making it easier for newcomers to start contributing technically. The group offered personal support through dedicated Slack channels where maintainers and ambassadors can guide individuals based on their comfort levels and preferences, ensuring that technical contributions are accessible to all members of the neurodiverse community.
The meeting concluded with an invitation for asynchronous participation, acknowledging that some members may prefer sharing ideas via notes rather than speaking live due to personal or professional constraints. The organizers reassured everyone that all contributions, whether spoken or written, are valued and will be treated as part of a collective knowledge base without necessarily attributing specific points to individuals. As the group prepares for their next gathering in October, they encouraged continued engagement through Slack channels and expressed gratitude for the active participation of members like Ryan, who stepped up to co-lead the initiative. The session ended on a positive note, reinforcing the community's commitment to inclusivity, collaboration, and the shared goal of building a more accessible future for neurodiverse individuals in technology.
Read the full video transcript
I want to say that we are pretty
excited. Our community hub session got
accepted. Uh we are just spending the
the last minute uh scheduling. Um and
we'll hear back from the committee
regarding that. Uh but yeah, we we got
confirmed for at least one uh 60-minut
session. Uh and we'll definitely be
there for for everybody who will be
present in Salt Lake City at CubeCon,
Salt Lake City. Um
we have uh exercises prepared for you.
So definitely uh nice a nice uh session.
Uh what else? Um definitely will I mean
uh congratulations to Ryan. He's the new
co-lead uh of neurodyiversity
probably like you were like oh isn't he
already? But yeah, so he's he's really
been active and yeah, it's it's uh very
intuitive that he's joining us and thank
you Green as well for
>> Thanks for stepping up. Um Ryan, I know
like I said, I I historically haven't
been able to be here because my day job
doesn't allow for it really. So I
appreciate you stepping up.
>> No worries. Yeah, it's good to see you
finally and um hopefully get to a
CubeCon and connect in person with
that'd be great.
Yeah, maybe uh Profant I don't know if
you have any questions. I know you've
been uh in a couple of meetings before
and we are discussing actually you added
some contributions if I'm not mistaken
to the the guidelines we're trying to
create we are trying to create for
neurodeiversity. Um
if you want we can go through those and
um check your your latest notes.
>> Yeah I or add some my own experience in
that docs.
>> Exactly. Uh
so let's just open that one.
So, did you add them directly to the
neurodiversity best practices? Because
I'm just opening the document now and I
cannot see those. I just painted it in
the chat.
Yeah. Pashant. Um, do you know where
those updates went in?
>> Yeah.
>> Yeah, I share the
link on
neurody diversity page uh Slack channel.
>> Okay, let me go back.
>> Yeah, it's
>> it's uh here and this right.
Yeah, the link you paste in the chat is
correct link and at the bottom onboard
onboarding.
Uh the last uh thing
in the last I have had my
I think there isue with my internet.
Wait.
Yeah, I mean uh we can we can share
that's that's fine. We could share the
screen or I could share whoever wants.
So we were talking about this uh
particular
doc.
Hi there. Welcome.
>> Hello. Thank you.
Yeah. Uh I mean Pashan please I mean
feel free to let us know what you added.
We can discuss it right now. I mean we
have plenty of time. So
>> yeah I have added this line uh
>> uh at the bottom there is a topic on on
boarding best practices.
>> Okay.
>> Uh point one two.
>> Mhm.
uh the board planted I have added in the
docs.
>> Perfect. Okay. Basically this last
section on boarding best practices.
Okay.
>> Yeah. Yeah.
>> Yeah.
>> Yeah. Um exactly. I mean what we hope to
do with the session we have um at Salt
Lake City and obviously with everything
we have been doing in the last year um
is to complete this uh best practices
document um we'll take like all the
nodes and everything added here uh and
then we could work nicely and then and
and finally start like let's say an
official document and so so um right now
because obviously We were like once we
get to the confirmation the final
schedule in for Salt Lake City, we'll
start
creating the the dock for this uh
community session hub session. Um and
definitely after we come back from Salt
Lake City, we'll start adding here uh
based on what we had this feedback from
the community there. Uh and then
obviously we have all all these kind of
monthly meetings to to keep editing,
adding and uh having something to be
published hopefully by next CubeCon. Uh
so like this we can already have uh have
our own page for neurodyiversity before
CubeCon uh Europe next year in 2007.
So if you have any ideas Deborah
yourself or anybody just feel free to
keep sorry to keep adding in in this
document
um and from then onwards we'll um we'll
start uh
just uh polishing all all the steps
uh how get verified if I add something
in the docs it's how get I get verified
if it's uh correct or something need to
improve and all something like that.
>> Well, this is why we'll keep uh using
this meeting to work together.
Um so like I said with the because we
are expecting this CubeCon Salt Lake
Salt Lake City to get the I say like the
final feedback not the final feedback
but it will be nice to have like after
one year of running the neurodyiversity
group to have this feedback and then
we'll add all um yeah all the notes that
we have uh taken during this time. It's
not about being right or wrong. We would
just be present and keep brainstorming
and and see for example to avoid
obviously repetition to sound um clear
no sound okay for everyone. So we'll use
our common sense and uh just stick to
the points that uh we learn from the
community. You are the community. So uh
that that's good. It's not I think about
being right or wrong or but together we
will kind of like work it out together
how how to best deliver this to
officially and publish it.
So you're not alone in essence brush and
we will do this together as a as an
exercise
uh from November onwards and keep
reiterating up to uh hopefully we'll
have it already by by March next year
published.
>> Okay.
>> Yeah. And thank you for these these are
really good contributions. Yeah. Part of
what we're doing uh with one of our
sessions in CubeCon in Salt Lake City
coming up in November is the
neuroinclusive social contract exercise.
essentially just how to create self-
autonomy um self-accountable teams um if
you're familiar with the self social
contract at all and we'll kind of use
these examples that you have um to kind
of benchmark against and kind of see
what what survive or what get iterated
on. So these will be you know invaluable
as we go into that u CubeCon here in
North America. So we'll let you know the
result of that. Yeah. So thank you.
Sorry, I'm on mute. So, um obviously we
want to keep hearing from Async. Uh I
mean from from people like online or
async. If you have any experiences that
you want to share, uh obviously if
you're not,
I'm going to say if you don't feel
comfortable discussing them live, it's
fine. We can add them as notes. Um but
uh it would be nice to have like even if
you have like an experience uh at your
workplace or with something that you
implemented, we discussed this a number
of times uh maybe with your friends or
with some acquaintances. Um or you
participated to another gathering that
was neurode divergent like or something
like that. Uh and you have some ideas
from there that you like to to introduce
to to this group. uh you could put it
down as notes and we are happy to take
it like this. The the notes are not
necessarily coming back to you. So
they're not traceable in the sense that
you know I added that you added that but
they're like a collective uh way of um
adding ideas
and uh definitely uh we could use them
for sure.
So yeah, uh I mean if you have anything
else to add, just let us know. Uh
obviously we don't want to
uh keep you from adding anything or if
you want to to we can call it a day if
we don't have any ideas to talk about.
Um just let's not forget Ryan maybe for
the recording to make um a screenshot.
You make a screenshot of of the people
present. We can use this for
the recording.
We can smile.
>> One, two, three.
All right, perfect. Hey, we nailed it.
>> Thank you. Uh, and yeah, I mean, thank
you so much for for coming again to the
to the sink. Um, right now it's looking
like, you know, it it might be a bit um
silent or like that, but don't worry, it
will ramp up is one of those like the
silence before the storm kind of moment.
So, uh, yeah, we'll be pretty active u
soon with with more information after
Salt Lake City.
>> Wonderful.
Yeah, Pashan, Deborah, any any last
thoughts? Uh, not to put you on the
spot. You don't have to come off at all,
but if there's anything else you wanted
to talk about, feel free. Um, otherwise,
yeah, we will get the comm uh, excuse
the community hub schedule out soon. Uh,
so we'll know the sessions for sure that
we have coming. So, we'll be able to
give the community more updates as to
what we're going to be talking about and
where you can contribute ahead of time
as well.
>> Okay. Uh Hmon asks if there is any
technical part where we can also
contribute
>> uh to uh that's a great question and to
this neurodyiversity group in general
merge forward like just technical
contributions in the CNCF um
>> okay
>> oh so maybe I didn't rephrase the
question again say that again
>> mean uh if uh if I want to contribute
more than docs like coding and all.
>> I would recommend going to the
Kubernetes repo and seeing what is
tagged for um issues that are tagged for
new contributors and there's always
something to pick up. If you are in the
CNCF Slack or the Kubernetes Slack, um
there's also tactical advisory groups
you can join whatever of those interests
you and they usually have their issues
also tagged good for new contributors. I
would recommend joining that.
>> Yeah, really good answer.
>> Yeah, to support that, to make it
easier, there's something called
cloudritor.dev. Take a look at that.
That categorizes everything as good
first issue. That's an awesome spot to
start. So,
>> so um I mean I mean I can always uh ping
you you are already in neurodyiversity.
I could ping you the one second the tag
operation resilience I'm part of. Uh
that's accepts the technical
contributions. Let me just give you the
slack channel. Uh but there's also so
much more um not only this tag but like
the whole tag security infrastructure
and so on. Uh just just join our one of
these channels. Uh the people will be
happy to guide you through it depends on
obviously your your preferences as well.
And we have so many ACNCF ambassadors
and and maintainers etc. And we'll be
able to to guide you exactly where you
feel more comfortable.
Yep. Deborah, how about yourself? Um, do
you want us to ask any question can be
about merge for world or beyond like one
native in general?
>> Um, honestly none for now. I'm still
honest I'm still just trying to um get a
grasp of um everything CNCS merge
forward. So yeah, I'm just getting the
knowledge.
>> Excellent. Yep. Thank you so much. Yeah.
Well, uh I mean if you don't have any
questions, I mean it's okay for you to
to wrap it up for today now
and we'll see each other in in October,
but feel free to to ping us anytime in
the Slack channels and yeah, we'll be
available async.
>> Wonderful.
>> Thanks.
>> Enjoy our days and nights. Yeah, we'll
see you later.