Thanks for the well written starting point, Daniel!

> I have listed three general ideas for getting things started, and I
welcome even more ideas with an open heart and mind. Perhaps this is a
topic that is better off separated into a "communications strategy"
document of its own? Would anyone be willing to help with that?
I'm happy to lead or co-lead. The website is in dire need of an update,
which I'm also happy to pledge time to as part of comms.

*Regarding acronyms: *As a marketer, I typically recommend using a term
that is most globally recognized vs a less recognized term (even if the
latter is more appropriate). In this case, it's DEI:
https://trends.google.com/trends/explore?q=dei,edi&hl=en. [Note: Even if
EDI includes something _other_ than the intended term in this search, DEI
is ahead by a large enough margin that it becomes moot].

The reasoning is that the term with the most usage is what most people will
universally understand right away, even if there's a better or more
accurate term available. It's a unnecessary hurdle if someone needs to
search the web for what "EDI" means before opening a survey link, reading a
blog post etc. That's the marketing POV.

*Regarding the survey: *In addition to what's on the Wiki, I would also
love to understand what ASF projects are doing to support DEI today. We
might uncover outstanding programs or workflows we can learn from and share
with others as best practice examples (and ask them to write blog posts for
the ASF blog, for example). I'm happy to lead or co-lead drafting an
internal survey leveraging my experience with survey design. I had helped
Katia (previous VP) with marketing the last survey (wearing ASF M&P hat),
so also know a bit about how that was run with OSU and Bitergia (though
others here may have been more directly involved with its creation).


On Thu, Mar 20, 2025 at 7:32 AM Jarek Potiuk <ja...@potiuk.com> wrote:

> >
> > Let me quickly jump in and say that the idea of a BoF session in
> > Minneapolis is not intended to exclude any other offline async
> > discussions or brainstorming that we do. The primary purpose would be
> > visibility for the EDI community and getting more people involved with a
> > physical presence, utilizing the benefits of a physical meeting.
> >
> > We can and should definitely have discussions and meetings prior to
> > this, both on this mailing list, and hopefully through online roundtable
> > sessions where we can flesh out ideas and principles prior to any
> > physical presence at any conference.
> >
>
> ACK - that's what I thought and understood as well, just the "Reboot"
> suggested that this will be the point in time (and space actually) where we
> press the button and start seriously doing stuff :) . So I just wanted to
> clarify it :)
>
>
> > I have listed three general ideas for getting things started, and I
> > welcome even more ideas with an open heart and mind. Perhaps this is a
> > topic that is better off separated into a "communications strategy"
> > document of its own? Would anyone be willing to help with that?
> >
>
> I would but not leading nor spending more than review, comments
> suggestions, occasional meetings - more dragged into this than leading any
> efforts. Not after Airflow 3 is out. I foresee a LOT of energy and focus of
> mine (and the whole Airflow community) will be very, very laser-like in the
> next 2-3 months,  and I also already have 4 security / airflow related
> events planned for me to go to in the coming 4 months (2 in US, 1 in Poland
> one in Germany) where I either speak or MC the conference. But I expect
> that to subside afterwards. I consider The fall events should be much
> lighter - CoC as a lightweight load despite leading two tracks and
> mentoring in a third one and Airflow Summit is pretty much on auto-pilot
> thanks to Software Guru) and I will be happy to spend more time then.
>
> So if you look for a follower that might turn into one of the leaders
> later, count me in.
>

Reply via email to