Talking Drupal #579 - Women in Drupal

November 19, 2026

Today we are talking about Woman, Drupal, and Woman in Drupal with guests Ashleigh Fox, Sinduri Guntupalli, and Rachel Lawson. We’ll also cover Legal as our module of the week.

Listen:

direct Link

Topics

  • Drupal Origin Stories
  • Belonging in Community
  • Role Models and Mentorship
  • Invisible Work in Tech
  • Rethinking Invisible Work
  • Valuing Non-Code Skills
  • Creating Women Leaders
  • Removing Hiring Barriers
  • Rethinking Contribution Credits
  • Recognition Versus Reward
  • Challenging Contribution Assumptions
  • Funding Access With Scholarships
  • Women in Drupal Award
  • Brief description:
    • Have you ever wanted to make users agree to your site's terms and conditions before they can register or log in, and keep a record of who agreed to which version of the terms? There's a module for that.
  • Module name/project name:
  • Brief history
  • How old: created in Oct 2003 by Robert Castelo (robert castelo) of Code Positivem
    • Versions available: 3.0.3 and 4.0.0-beta3, both of which work with Drupal 8.9 through 11
  • Maintainership
    • Minimally maintained, latest release (4.0.0-beta3) was in July 2025, and there's a Drupal 12 compatibility patch in review
    • Security coverage on the stable 3.0.x branch; the 4.0 betas aren't covered yet
    • Test coverage: A few functional tests in the 3.x and 4.x branches
    • Number of open issues: 93 open issues, 39 of which are bugs, a few marked RTBC
  • Usage stats:
    • ~4100 sites
  • Module features and usage
    • Allows for T&C to be updated, and then the user is notified of updates and needs to accept the new version. Module keeps track of who accepted which version(s).
    • Includes a "notes about the changes" user-facing field.
Transcript

[00:00:00] Nic: This is Talking Drupal, a weekly chat about web design and development from a group of people with one thing in common: we love Drupal. This is episode 579, Women in Drupal. On today's show, we're talking about Women in Drupal and Women in Drupal with our guests, Ashley Fox, Sunduri Guntupalli, and Rachel Lawson.

We'll also cover legal as our module of the week. Welcome to Talking Drupal. Our guests today are Ash, Sunduri, and Rachel. Sunduri is an open source enthusiast and positivity advocate. Her path went from civil engineering to development to product management. She now works as a senior developer programs engineer at Dynatrace.

She's on the Drupal Austria board and helps organize Drupal events and won the Women in Drupal award in 2025. Rachel has had the privilege of seeing Drupal from many angles in her 20-year career as a developer, a community organizer, whilst working as community liaison at the Drupal Association, and was helping to organize the mentored core contribution at DrupalCon and many other events across the world.

Her real passion is meeting people and learning about their own experiences in the Drupal community, especially in places and circumstances different from her own. If she can find a way to travel to those people across the world by motorbike, all the better. Ash is the senior marketing manager at Jakala, formerly FFW, working at the intersection of creativity, technology, and digital experience.

Building on FFW's deep roots in the Drupal community, Jakala continues to support initiatives such as the Women in Drupal award, created by FFW five years ago to celebrate and champion the people and diverse voices shaping the community. With a background in content and creative strategy, Ash is passionate about great storytelling, smarter digital experiences, and making technology feel a little more human Ashley, Sunduri, and Rachel, welcome to the show and thank you for joining us.

[00:02:02] Ashe: Thank you. Thanks for having us. Thank you.

[00:02:05] Nic: Quite, quite the intro. I, I have to say, I, I have comments about each of these before we jump in. Um, I find it interesting that you went from engineering, Sunduri, to Drupal, 'cause I did the same thing. My, my training is in plastics engineering. Ooh, cool. Like Mike as well.

Uh, so it's, it's, it's always fun to meet other fellow engineers. And Rachel, I, I don't know if you know this, but we were... A year or two ago we were talking about the first DrupalCon in Asia, and we were talking to, I think, Sarabi, and she was saying how hard it was gonna be to get to Singapore. And I looked up how long it would take.

Uh, you know, in my mind, they're a lot closer together. I'm like, "How far apart can they be?" Yeah. I looked up and it's like a 100-hour drive. I'm like- ... "Okay. Yeah. That's, that's, that's flight only territory" But now I'm imagining you driving your motorbike all the way around, uh, around

[00:02:58] Rachel: the- Well, we'll see what happens next year.

[00:03:01] Nic: Uh, and then A- Ash, I, I'm curious, how, how long is Jkala gonna be Jkala, formerly FFW? It, it's... I feel like you guys have been Jkala for a while now.

[00:03:11] Ashe: Yeah. We ha- I mean, we have, yes. But, um, I think FFW has, um, such a deep history with Drupal- Yeah ... that we, you know, for things like this, it's helpful to mention.

[00:03:22] Nic: Awesome. I'm Nic Laflin, founder at nLighten Development, and today my co-host, my co-host is Emma Harrell, UX lead for Drupal CMS and UX manager for Drupal Core. Emma is the UX lead, and she's also part of the Drupal AI initiative, and organizer of the DrupalCon Higher Education Summit. She's all about making Drupal easier to use and opening up new audiences.

Welcome back to the show, Emma, and thank you for joining us. Thank

[00:03:47] Emma: you. Glad to have you. I'm getting the hang of it now. On, like, episode three, I think. Could be speaking too soon, but.

[00:03:56] Nic: Yeah. It's al- it's always good to hear fresh voices, and it's always sad to see a guest host's, uh, tenure kind of finish. But, um, we've, we've been really happy to have you here.

[00:04:06] Emma: Thank you.

[00:04:09] Nic: All right, and now to talk about our module of the week, let's turn v- turn it over to Mike Anello from Drupal Easy, who is filling in for Martin Anderson-Clutz this week. M- Mike, what do you have for us?

[00:04:19] Mike: Hello, hello. Uh, so this week I have the Legal module. Um, which I even surprised myself, 'cause I thought for sure I was gonna pick an AI-related module, 'cause that's where my head's been at for a couple months.

But, um, I'm in the process of upgrading a Drupal 7 site up to Drupal 11. It's a site I have maintained. I built and I've been maintaining it for more years than I care to calculate. Um, and the Legal module is a module that I have. It's, it's, it's on the Drupal version, Drupal 7 version of the site right now, and I just, um, installed it on the Drupal 11 version o- of the site.

And it's, it's still solid, and it's still, it, it, it still does everything I need. So, um, it basically allows, um, a site builder or site owner to, um, have terms of service, um, that their users have to, you know, do a little checkbox on, um, before they can log in. Um, and the thing that I really like about this module is when those terms of services change, um, the module keeps track of what version each user has agreed to.

And if the terms change, the next time the user logs in, um, they have to click the, the, the checkbox again. Um, and the module has an area of, uh, for, for the, the site owner to put in, like, what's changed. So it's very helpful. Um, it's, it's not just a blind change. It's like, "Hey, we're asking you to, to agree to these again.

Here's why. Here's what's changed between last week and this week." Um, so I really like that functionality, and quite frankly, it's just, I've never had an issue with the module. It's just been rock solid for as long as I've been using it through all the upgrades. Um, so it was created way back. I don't see how this is possible.

Um, let me- I'm gonna double-check this number, 'cause it's... I wrote it yesterday, but now I'm like, I'm looking at the number, and it can't be the year.

[00:06:28] Nic: It's not, it's right.

[00:06:29] Mike: Is it right? It was created in 2003. Um- Wow ... there are probably listeners who have kids that are older, younger than this module. Or, yeah.

They're, th- that's crazy. So Robert Castello, uh, that's his username as well, of code positive. I, I have no idea- Yeah ... if Robert's still active in the comm- Is he still active, Rachel, or not anymore?

[00:06:50] Rachel: Yeah, uh, yeah, absolutely. Yeah.

[00:06:52] Mike: God bless him. Um- Yeah. So currently there is a 3.x branch, which has a full release, and a 4.x branch, which is on beta 3.

Um, both, both of those branches are, uh, work through, uh, 8, uh, Drupal Core 8.9 through 11. Um, I'm using the beta s- the 4.x, uh, version for the site I'm building. Um, it is marked as minimally maintained. That beta 3 was released last year, a little over a year ago in July of 2025. Um, and, uh, there is, looks like there is some, you know, slower movement in the issue queue to get it ready for Drupal 12.

Um, and quite honestly, it, um, I, I will probably end up getting involved in that if, if I don't see it moving forward, um, in the next couple months. Um, security covered, yes, for the 3.x version, not for the 4.x version because it's still in beta. There's not a full release. Um, and there are a few functional tests in both the 3.x and 4.x versions, uh, of the module.

Um, I wouldn't call it full test coverage, um, but looking at the tests briefly, it does seem like it's testing the basic functionality, um, which, which is, you know, probably fine for the vast majority of the use cases Um, 93 open issues, 39 of them are bugs. A few of them are marked RTBC. I kinda get the sense that this is the kind of, uh, contrib module that, um, the maintainers are looking at.

You know, they're diving into the issue queue maybe every few months and push the ball forward a little bit, and then go away for a few months, um, which is fine as long as we get, we can get a full release and, and, and there's no major bugs. Um, about 4,100 sites are reporting being, uh, using this module.

Um, and like I said, I, I've, I've used it for a lot of years, and no issues whatsoever. Um, and just for this type of thing, it's solid. Um, I will say what I would love to see, and this kind of is maybe going off the reservation a little bit, I'm a big fan of a, a site called Termageddon, which, um- Oh ... it's, it's a service that will help you keep your privacy policy and your terms of condition automatically updated as the landscape, the, the legal landscape changes.

Um, I would love to see some type of integration in this so that as that changes, might, maybe that triggers the legal module to re-ask and things like that. But, um, yeah, I, I feel like terms and conditions and privacy policy for a lot of sites are... And maybe I'm moving into opinion territory, so I'll quickly stop talking after this.

Um, a lot of times it's, "Hey, we need a privacy policy" during the site build, and it gets written, and then it just sits there and doesn't get-

[00:09:50] Nic: Link up.

[00:09:51] Mike: Yeah. So.

[00:09:52] Nic: I, I, I want to point out one thing before, um, before I talk about the module itself. Yeah. So the, this module says that it was created on October 3rd, 2003, like you, you pointed out.

But this, so this might be the oldest module where we actually know the date that it was created because, I don't know if you know this, but before the project module was created, modules were just on the site. There wasn't, like, a date. Right. And September 28th, 2003, was the date that they were all moved to the project module.

So most really old modules all were created on September 28th, 2003.

[00:10:29] Mike: Okay. Please, please, please tell me you had to look that up and you did not have that know- ... that knowledge off the top of your brain.

[00:10:35] Nic: I, I looked up the specific date that it happened, 'cause I didn't remember it was September 28th, but I knew it was very close to that.

[00:10:41] Mike: Wow.

[00:10:41] Nic: Um-

[00:10:42] Mike: It's impressive ... '

[00:10:43] Nic: cause I've, I've been looking at it a lot Can you be on

[00:10:45] Rachel: my team at tri- Drupal trivia?

[00:10:47] Mike: Yeah,

[00:10:48] Rachel: no

[00:10:49] Mike: kidding. Bringer right there.

[00:10:50] Nic: May- maybe. Um, I, I will say, too, I, I didn't know this module existed. I'll have to take a look at it. I've built this functionality myself. Um, I think the one question I would have is how easy is it to see the audit trail?

Um, for a particular user

[00:11:07] Mike: I believe there is. It ships with a view

[00:11:10] Nic: Oh, okay

[00:11:11] Mike: That has, um, if I recall correctly without having to type and look it up, that shows, uh, each user. It's a view of users, and it shows the version of the terms and condition that they have, um, agreed to, the most recent version.

[00:11:27] Nic: Okay

[00:11:28] Mike: So it kind of- Yeah, the-

[00:11:31] Nic: Yeah.

Yeah. The, the use case I had for it was, um, a client has software, some of it's paid licenses and some of it's free trials, and the free trials had to sign an EULA to, like, confirm that they would use it in concordance with the free license or the demo license rather. And they, they had the same requirement.

They need to see when somebody signed it, they need to re-sign it if it changed, et cetera. So it was... It's kind of... I, I wonder if we could just build it on top of the legal module- Yeah ... and not have to maintain all that logic.

[00:12:04] Mike: That seems like that'd be a beneficial, um, investigation for you.

[00:12:08] Nic: Yeah.

Absolutely.

[00:12:09] Mike: Yeah

[00:12:11] Nic: All right. Thank you, Mike, for dropping in for Martin, who we also saw this weekend, uh, in person, which is always nice. Um, if listeners wanted to connect with you or suggest a module of the week, what's the best way for them to do that?

[00:12:25] Mike: Um, I'm Ultimike pretty much everywhere, Drupal, Slack, uh, most of the social medias.

Um, but if you do have a specific request for module of the week, um, I would say reach out to Martin. Um, he's everywhere on Slack as well, or the email address for the show, which is [email protected].

[00:12:43] Nic: Yep, absolutely. Perfect. Thanks, Mike. All

[00:12:47] Mike: right. Thanks. Good to see everyone. Have fun.

[00:12:49] Sinduri: Thanks. You too.

Bye.

[00:12:52] Nic: All right. Let's jump right into our topic. Um, I, I mentioned this before we started recording, but for our listeners, I think we're gonna take, uh, a slightly different, um... Give me one second. Um, we're gonna take a slightly different approach, and I think this show is gonna be a little bit more of a, a round table.

Um, so we're going to be talking about kind of your... We're gonna start by talking about you guys' Drupal story and how you got in. So maybe, Emma, you can kick things off. How did you get into Drupal, and what kind of kept you around?

[00:13:31] Emma: Uh, so I got into Drupal as a content editor when I was using it at my place of work, and I was kind of intrigued by the system.

And I put in a talk on a bit of a wild card, uh, like answered a call for speakers for the DrupalCon Prague, and it got accepted. So that was my first sort of... I feel like I skipped the, the sort of initiation of camps and whatnot that some people do, and I just went straight into the full con. So that was, like, four days, um, immersion, and I was lucky.

I had a very good friend, um, Billy, who accompanied me at that DrupalCon, and he introduced me to a lot of people. And I followed up afterwards and, yeah, just kind of grew a network. Um, y- you know, cliche, but I don't even know if I came for the code actually. I came because of the curiosity, but the community certainly, like, I just found places I could be useful.

Um, and I still do. Um- Yeah ... so that's kind of what kept me, keeps me invested in it. Um-

[00:14:39] Nic: Awesome.

[00:14:40] Emma: Yeah.

[00:14:40] Nic: How, how, how about you, Rachel? What, um, how did you get started in Drupal, and why are you still here?

[00:14:48] Rachel: Um- ... I started, actually, I was, I, I was seconded into a marketing department of, um, a pharmaceutical company for a while.

And, uh, I wanted a agency in the UK to do something, and I was trying to explain what I wanted. Uh, and I- they really would not give me what I wanted, and I just experimented, downloaded stuff off the internet, and tried it out, and ended up, by random more than anything, choosing Drupal. I, but ... And then they actually used it.

They actually then said... They took me literally when I said, "Here, I want something like this." They took me literally, and then used Drupal themselves, which is kind of interesting. But they, they, they did manage it. Uh, and then I just got involved. I went to DrupalCon London for, uh, based upon that from work.

And, um, yeah, yeah, I... The thing I did there that really helped me get to know people was I volunteered. I just joined the volunteer list, and that is such a big deal when you go to DrupalCon. Just join the volunteer list and you will get to meet people. Not only that, but people think you actually know stuff as well, even though-

you really don't. I,

[00:16:09] Nic: I've heard the same about having a podcast.

Uh, A- Ashley, how about you? When, when did your Drupal journey start, and kind of what's kept you around?

[00:16:19] Ashe: So mine is maybe a little bit different, because, uh, so I work in a marketing department, and I moved into, so FFW, then Jekula- Yeah ... uh, about three years ago. So I joined, and it's been a really interesting, uh, like, learning curve for me.

Before that I spent quite a lot of time in financial services, and then before that I was in agencies and other creative places. So then when I came into Drupal, that's... it's, it's a learning curve to, uh- So I have to learn all these terms and understand it, um, and explain that to other people. So yeah, so it's been great, because I think...

So I've worked on Women in Drupal for the last three years as well, the award. Um, which- Okay ... has been fantastic. It's been such a nice experience. And the thing that's sort of kept me is the, the passion behind the Drupal community is kind of unlike any other really, and it's, it's kind of infectious. So when you meet people, when you go to DrupalCon and you talk to people and you're like, "Wow, okay," everybody is so passionate, and I love that.

[00:17:22] Nic: Awesome. Uh, and we'll talk about the Women in Drupal Award a little bit more later, I think, 'cause I, I have, uh, I have some specific questions about that too. But before we do that, Sunduri, how, how did you get involved in Drupal and, and why are you still around?

[00:17:36] Sinduri: Uh, so I had like a big story. Like, uh, I will try to keep it short, but, uh, I moved to Vienna and I was trying to learn German, but I always wanted to become a programmer.

I just thought I was not smart enough. So I was like learning German, learning programming. It felt like programming was the answer. And then COVID happened and I didn't think. Yeah. Thank you, Rich. And, uh, COVID happened, I didn't think I was gonna find a job. And then Klaus Bruder, uh, he offered me a job on LinkedIn.

I did an interview and thankfully got the job. And, uh, like everybody's saying, the community is what made me stay. Um- Mm ... people are passionate and people are really nice. And also, I don't think we don't talk about this enough, although Drupal developers don't get enough money, they are s- like one of the smartest people in the world.

And, uh, we are just like really passionate and just staying it. Unfortunately, I don't work in the Drupal community anymore, but, uh, Emma, my first DrupalCon was also Prague, and I didn't know anybody back then. And, uh, so-

[00:18:36] Nic: Mm-hmm ... that was very interesting. How, how, how is the German coming too? Is that

[00:18:40] Sinduri: successful?

Everything that's

[00:18:45] Nic: All right,

[00:18:47] Sinduri: we-

[00:18:48] Nic: All right, we can move on. Um, okay. So, uh, Rachel, maybe we could start the next question with you this time. So- Yeah ... was there, was there a moment in time where you kind of realized that you belonged in the community, or were maybe the only woman in the room and still felt, um, included?

What kind of made the difference there? Or how, uh, what's something- I think in t- ... can, kind of keep in mind?

[00:19:11] Rachel: In terms of being truly made to feel welcome, there was a particular moment. Um, I was with Jesse Beach. We went to... I'd already, you know, kind of got involved in the Drupal community a little bit. But in terms of actually really thinking, "Yeah, this is where I belong," it was a moment in DrupalCon in Prague, don't even ask me the year.

Where I was with Bes- Jesse Beach, and I hadn't really done much in the way of code contribution at that point. I'd just kind of run around, enjoyed myself. But, um, the... She said, "Do you want to come along? We're gonna go the day before. Acquia have got a room. We'll go up and, uh, get stuck in." And I, I kind of went up, and there was every...

There was a load of Acquia people sat in the room. So there was Angie, Angie Byron, web chick. There was quite a few others. I, and obviously Jesse I was with. Um, and it was, everyone was really welcoming. But also, even though I was, I don't want to say a nobody, but, you know. So I wasn't, I wasn't really known for having real particular stuff to bring to the party at that stage.

Um, they wanted to know what I thought on everything, and actually listened. Uh, I seem to rem- seem to remember me and Angie having a very long discussion about responsive tables in Drupal 8, or the upcoming Drupal 8 at that time. Uh, I still think I was right. Uh, but, but, uh, yeah, yeah. It was that made to feel as though my, my, my opinion mattered.

Okay. And it, and, and actually take, you know, just taken at face value as somebody who's worth listening to and finding out, and it made such a difference

[00:21:17] Nic: Yeah, I think being, being heard is I mean, it's key, right? Um, Em- Emma, do you, do you have a moment that kinda stands out to you, too?

[00:21:28] Emma: Um, I think so. It would've been sort of after Prague, I got a bit more confidence that some of the things I was, like, raising about Drupal, because I guess I was coming to it from an editor, like, feeling a bit stupid.

Why is it kind of confusing? And then I started speaking to other people, and they b- they were kind of nodding, going, "No, we need to simplify it. If we want new people to join the community, if we want people who are not already very familiar with Drupal to learn it, you know, there are things that we can do to make it easier."

And so I started a small group looking at Drupalism, just looking at terminology and how we could try and demystify that a bit for folks. And I did a BoF. I can't remember which DrupalCon it was, and quite a few people came, and that sort of made me feel, okay, I have, like, I have something here. I have a, a group of people to sort of work with me on this.

Um, and yeah, even though that piece of work was kind of bigger than all of us really, and still is, it's still... I guess for me it felt like I was tapping into something the community wanted, and that made me feel, um, included and, like, that I could, you know, that together we can make a difference. Yeah.

Which is, like, Drupal all the way through, right? So yeah.

[00:22:49] Nic: Yeah.

[00:22:49] Emma: I think that was mine.

[00:22:51] Nic: S- Sunduri, how, how about you? What, what's a moment that stands out to you as a, a time that the community helped you realize, like, you belong, you're part of the community?

[00:23:01] Sinduri: Uh, I would start with a bad example because, like, uh, when I first wanted to create my Drupal issue for a, a code thing, it took me 45 minutes to write the issue.

I was so scared that, uh, I'm doing something wrong and people are gonna judge me, and I didn't know the community back then, so I was, like, really scared. Uh, but I think, uh, it wasn't a moment, but, uh, even when I first, uh, contributed to Mountain Camp, an event there, I didn't know anybody. I think I met, like, one or two people, but I didn't know anybody.

And by the end of the event, I was like, "This is my space. This is my happy place." And for me- Mm-hmm ... uh, it wasn't a moment, but it was just, like, by the end when I was leaving I was like, just this is my space, and that was it.

[00:23:41] Nic: Hm. Mm. Awesome. How about you, Ashleigh? How did you... Did, did you have a moment that stands out?

[00:23:47] Ashe: Not really a moment, but more, like, I would say a collection of observations over time of, like, seeing, um, lots of people in the community, like, broadly how people sort of support and champion each other, and then also having some really good, um, female role models as well, which is important to me personally, too.

So I think, like, over time you just see more instances of things, and you meet more people, and you work with more people, and it sort of adds up to think, actually, this is a, a nice space to be in.

[00:24:15] Nic: Uh, I mean, I think mentorship and having people to look up is- kind of so important. So Ashley, like who, who are some of the role models that you're talking about, and, uh, w- what are things that if they're trying to be that, um, mentor, what are things they should keep in mind when bringing on new people?

[00:24:34] Ashe: So I mean, I can only speak to you from a broader sort of marketing perspective, so it's a little bit different for me. But I think having like, um, an inclusive environment and strong women in like leadership roles as well within the company is good. So even if you don't have specific mentoring with them, you can see these people doing things, um, and achieving things and, and taking up space in these roles, and I think that's really positive.

[00:24:58] Nic: Hm. How about, uh, how about you, Emma? I think- Who, who are your role models in the Drupal community?

[00:25:04] Emma: Well, I have to say watching... And again, initiating into Drupal and seeing the Women in Drupal Awards be part of that and seeing like a whole room of people clapping a woman up on stage and just, you know, it- there's no clearer message that, you know, there is a place for you.

Uh, you know, and women are celebrated in Drupal is a very, like a very clear message from the community about how inclusive it is. Um, and so yeah, like the, the people who I saw win it, Christina Chamias, um, Pam Berown, who are then I, you know, I've, I've got to work with since then, um, has, you know, you benchmark yourself against, um, people like that.

So I think, yeah, that, that's what I'd say to that really.

[00:25:49] Nic: Awesome. How about you, Rachel? Who, who do you look up to in the Drupal community?

[00:25:54] Emma: And obviously Rachel and Sunduri- ... I look up to. Oh, stop. That's why I asked them to come onto this episode to sort of, yeah. Sorry, Rachel.

[00:26:03] Nic: I was wondering which one of you was gonna be the first one to call

[00:26:05] Emma: out.

Yeah, I know.

[00:26:10] Rachel: I, I... Who do I look up to? It, it, it, it's, it's the people who spend time. It would... The same, uh, the same as, uh, Angie at Web Chick did. The people who, uh, who are in positions where they can take actions and spend the time, uh, to, to listen and to, and to do things and, and, and, and kind of help. So yeah, Angie, uh, Jessxjm, absolutely look up to them completely.

Um, re- very much so. Um, but I've, I've got to say, Sunduri, you talking about that sort of the fear of taking that action, uh, it's real. And it affects, it affects us. It affects a, many of us. Um, and it's a real, it's a real- Staying in it. I think if there's one thing that mentors can do, whoever they are, who- whoever thinks that they're in a position where they can say something, is just to encourage people.

I think probably the most effective, the most impactful thing I did in the whole time that I was community liaison at the DA was What I described as giving permission and saying, "Yes, go do that thing."

[00:27:37] Emma: Mm.

[00:27:37] Rachel: Uh, even though I was in no position to, to give that position, that permission, and the permission had no meaning whatsoever.

Yeah? Just someone saying, "Yes, that's a good idea. Go do it," made so many things happen, um, over that time. Um, you know, I, I remember having a call with, uh, I think it was Will in it. Uh, I can't remember who was in the call, but, um, um, they were talking about making the Drupal Swag Shop, yeah? And they were saying- Oh, yeah

"We should have a Drupal Swag Shop." And I was like, "Great. When you gonna start?" And that type of conversation. And they did it, yeah? They completely did it. Uh, because they're just waiting to... They're just waiting for someone to say, "Go do it." Yeah. I then had to explain- Yeah ... to my boss why, what, what was going on, but

because I, I said yes before actually checking. But

[00:28:36] Ashe: So I actually have you on video saying that as well, because, um, I took some videos of, um, some of the women at DrupalCon Rotterdam, and I have Rachel saying, "Go do it. Don't wait for permission." Oh. "Go do that thing." And I

[00:28:48] Rachel: was- Yeah, no,

[00:28:50] Ashe: so it was... Yeah ... what does it make the other day.

And I was like, "Yeah."

[00:28:52] Rachel: Yeah, absolutely. Don't wait for permission, but a lot of- Yeah ... people want to hear it. So- Yeah, exactly ... if you are in any way able to give that permission-

[00:29:00] Sinduri: Mm-hmm ...

[00:29:00] Rachel: even if you're not technically able, just do it anyway. Turn around to people and say, "Yeah, go do it." And the same goes with just making that first issue.

Go do it. But please, you have permission to do it. I spend ages saying- ... no one, not- nothing bad's gonna happen from making an issue.

[00:29:19] Nic: Yeah. A- and I mean, that's one of the strengths of the community. It's not just that the community's so positive, but we also ha- we do have the community health working group and team-

[00:29:27] Sinduri: Yes

[00:29:28] Nic: that if, if somebody is out of line, we have processes to manage that. It's not just all... You know, obviously not everybody is always, uh, cheerful online or, or helpful. But we have the mentors, and we have the guardrails to make sure the community is healthy. So I think for most people, the experiences that you're, you're sharing, hopefully their first time contributing or creating an issue or whatever that is, hopefully is, is, is positive.

Uh, Sundari, uh, before we move on to the next section, um, who, who are your role models in, in the Drupal community? Who do you look up to?

[00:30:02] Sinduri: Obviously all the three women here and additionally. Uh, Emma, uh, stole my line. But yeah. Right. Uh, additionally Bardi, Jess, uh, Surbhi, everybody I think, uh, who shows some kind of strength, but more than that, kindness and, uh, mentorship.

Yeah. I think, uh- Yeah ... just showing, uh, sharing a random word, what Rachel is saying, like, uh, supporting people, just showing kindness to be and to support them. I think that is, uh, everybody who does that is a role model for me.

[00:30:32] Nic: Awesome. Okay, so we're gonna move on to the next section of the show, which is titled The Woman and In- and the Invisible Work, which, uh, brought to mind, I, I think it was intentional, but it brought to mind there's a fantastic book called Invisible Woman by Dr.

Carolina, I think. I, I-- We'll have a link in the show notes. It, by the way, it is the most cited book I've ever read. Like, every single, every other sentence has a footnote linking to a study. Um, I, I highly re- it's, a-as Emma said before the show, it's not a happy read. I think it's a, an important read. Um, one of the things that really stood out to me, though, is just how much kind of the world depends on the term, you know, what's termed invisible work, work that is kind of expected by community and by organizations to happen but is not paid and not recognized.

Um, and traditionally, most of that work happened is, is made by women, not entirely, but the book was focusing on women, so it talked a lot about that as well. Um, so with that frame in mind, what are some of the biggest challenges, you know, women still face when trying to start or build a career in technology?

Maybe Emma, you can, uh-

[00:31:58] Emma: I can, yeah. I can go. I think-

[00:31:59] Nic: Kick it off ...

[00:32:00] Emma: definitely, definitely I think an entry point is doing some of those invisible tasks. But, and women tend to take them up, I think for several reasons. Firstly, we say, "Okay, I can do that, and I'm in my comfort zone." And we might edit ourselves out of roles that, you know, we think we need some support with for, for reasons like Sunduri alluded to.

I don't want to feel stupid here. I, I'm not sure I'm good enough, that kind of thing. It, it becomes a sort of self-fulfilling prophecy, if I can put it that way. So I think that is- Yeah ... definitely a challenge. Um, and that I think can be addressed by sort of recognizing that that work is necessary and it's valued and it, um, it doesn't have to just be done by women.

But I think that, that women tend to gravitate towards that. I think the other reason for, for kind of doing that is because that role isn't in the limelight. So because if the limelight involves people that we can't see are like us, you know, it's a sort of human, um, response to go, "Oh, I don't belong here.

You know, this is all men or th- there are no women here or there's nobody I can relate to here." Um, so I think that is, is a challenge, um, being able to see yourself, um, in a leadership position, in a position, um, like a, an equivalent role as men perhaps, um, in te- not just in Drupal, but in technology and like, um, yeah, more broadly I think.

[00:33:30] Nic: A- and it, it might be worth mentioning too what types of things we're talking about too, right? So for example, um, a lot of the work that the book is talking about, it talks about stuff at home, right?

[00:33:41] Emma: Yeah.

[00:33:41] Nic: But if we're looking at, if we're talking about specifically, um, you know, building a career, a lot of the work that happens at companies is al- also falls into this category.

Things like from more social pieces like planning birthday parties for everybody in the office to scheduling meetings and making sure everybody knows that they're supposed to show up to, uh, following up on email. You know, uh, some of that's project management stuff, but a lot of it is following up people that aren't the project manager.

Um, so it's, it's work that if it didn't happen, the company would fall apart. Um, but nobody's, um... you know, you might, uh, you might get recognition if a project finishes early, but you're not, you know, nobody's getting called up on stage and getting award for making sure everybody knew that which meeting they were supposed to attend showed up, right?

Um, so th- that's the kind- Yeah ... of work that I think some, some of the types of work that we're talking about here.

[00:34:39] Emma: Yeah, 100%. Sorry, Rachel, I think you were gonna speak.

[00:34:45] Rachel: I'm gonna have to h- I've got a problem with the term invis- invisible work, invisible contribution. And it, it's- the more I think about it, it, it's really problematic.

'Cause if you think that there's con- If you're thinking that there is contribution that is invisible, you're not looking in the right places. Yeah? Mm. And I, I think this is, this is the problem, is we have a lot of people who ... Every community has them, to be honest. It's not that the work is invisible, it's that a significant proportion of the people in that community are not looking at it- Recognize

and appreciating it. Yeah? Yeah. It's just as valuable. It's needed. In fact, actually, no, it's more valuable, because the other work won't get done otherwise. So- Mm ... you know, we've, we've got a huge amount of things that people call invisible work, that a lot of the stuff that goes on at the Drupal Association, uh, is invisible.

The things that the community working group do, it's, it's, it's called invisible. They're not invisible. Um, they are available. People are not going and looking. Now- I think they're

[00:36:03] Sinduri: not recognized ...

[00:36:05] Rachel: that, that's, that's ... If, if you think- If all you appreciate is code contributions, you're missing out on most of the community's con- work.

[00:36:24] Nic: I'm, I'm curious, what, what do you think about instead of... Uh, and Drupal, I think, is in a slightly unique situation because Drupal does recognize things specif- 'cause th- there's a lot of stuff Drupal could do better. It's not perfect. Um, but for example, like camp organization and con organization- Yeah ... is explicitly recognized, which in more traditional tech fields isn't really.

Um, but I'm, I'm curious about your, uh, about the terminology because, you know, words have power and make it easier to talk about things. What do you think... Would it be more accurate to talk about unpaid, as unpaid labor or unrecognized work? Like, if we're not gonna call it invisible work, what... And obviously you don't have to-

[00:37:05] Rachel: I, I, I'm quite passionate on this.

No. But I don't want, I don't want to, I don't want to... I wanna be careful that I don't end up speaking forever on this, and maybe we should come back and do a whole section on this. But it, it, it's, um, there's loads of stuff that goes on. It is unpaid. Some of it is unpaid labor. Some of it is just hard work that just needs to be done and might not be fun.

Yeah. Absolutely. Yeah. Some of it is fun. Some of the non-code work is fun. Some of it isn't. Um, yeah, that's true, but you could say that about the code work as well.

[00:37:46] Nic: Uh, Ashley or Sunduri, anything you'd like to add?

[00:37:51] Ashe: Only that really I think to make a community a great one you need a lot of different skill sets.

And I think it's just worth bearing in mind that maybe not everybody has the same skill set as you, but everybody's valuable within that, um, to make things happen. So I think it's, I mean, just recognizing people around you and the value they bring really and just being appreciative of that

[00:38:13] Nic: Awesome. So A- Ashley, I think, you and Emma said something that kind of sparked something for me.

Like, it, it's been really, really refreshing seeing Tiffany take over as the interim CEO. Um, just, like, the fresh ideas that she's coming up with. I, I'm really excited to see what the next, you know, five or six months bring for the Drupal Association. But you had mentioned, Ashley, I think, about having more roles for leadership for women.

What, what are things that, um... What do you think companies should be doing maybe systemically to provide those opportunities for more technical leadership or more senior roles, um, for women or other under- underrepresented communities?

[00:39:00] Ashe: That's a tough question because there's no simple answer to this.

[00:39:05] Nic: Yeah. Solve all the world's problems right now, go. That's what,

[00:39:09] Sinduri: that's what we do. I love that. So glad I joined.

[00:39:12] Ashe: No, I think, I think it's hard, um, because I think every organization is different, every community is different. Like, there are lots of ways you could possibly go about this. But I think, um, one thing we could really do is more advocacy for people when they're not in the room as well.

And sort of speaking about those people who are experts in their field. They are good at this, they are good at that, "Oh, you should speak to such and such," or, you know, people who have your back and raise awareness about you when you're not there necessarily as well. Um, and start sort of promoting just, just because they deserve recognition or just because they have good ideas and they can be part of a discussion.

[00:39:49] Nic: Yeah. You just- I think- You just reminded me of one of the things in the book actually, which kind of combines something that Sunduri and Rachel said, which is so- many times, um... I think many times women will self-edit themselves out of an opportunity. Like, if there's an- Oh, yeah ... internal promotion.

[00:40:05] Sinduri: Yeah.

[00:40:06] Nic: Yep. Yeah. Sometimes all it takes is telling them, "Hey, you, you would be good for this job. You should apply."

[00:40:11] Sinduri: Yeah.

[00:40:11] Nic: And the truth is they're probably overqualified compared to the other candidates. Yeah. But, um, they'll self-edit themselves, so maybe, maybe keep an eye on internal promotions, and, you know, sending those notes out, uh, can be helpful.

[00:40:25] Emma: If I could come in there as well, Nic. I think, like, companies that recognize barriers that prevent women from applying, you know, like confidence issues or whether it's flexible working that would prevent a woman applying- Yeah ... because of other res- like, care responsibilities, not just the women but, you know, any, um, you know, how can you be more inclusive?

Think about the things that might prevent people applying. Like, oh, I don't meet all the gr- job criteria, or I'm lacking in confidence or... Um, I, I think, like, it's really refreshing when you see an advert that acknowledges that and actively sort of stretches out to recruit women, underrepresented, um, people from the community.

The other thing I think, and I'm kind of conscious, is that- Anybody can be a leader, and you can encourage anybody. You don't have to be a CEO to be a leader. But Tiffany obviously , you know, has the opportunity to, to put some brilliant messages out there, and she is doing that and really changing the narrative.

But it can happen bringing somebody in and just giving them a small piece of Drupal to, like, have control over. Like, maybe they run a series of meetings. Maybe they do guest hosting for three times. You know, just things. There are lots of things that you can do to give people a little bit of control, and this doesn't apply just for women.

It... But it just then bolsters the confidence, inspires a kind of can-do thing, and that I... You know, I love that about our community because there really is a place that anybody can come in, but not just do a thing, but also can kind of grow and spread into, into whatever part you want. So I, I, you know, I don't do this enough, but I would like to, to see more of that happening, not just women championing women, but anybody championing anybody really.

Um-

[00:42:11] Rachel: Yeah.

[00:42:12] Emma: Yeah.

[00:42:13] Sinduri: Yeah. Uh, uh, uh, uh, to add to that, I think it's also important, like, uh, where people are not hiring women in junior positions. You will never get a mid-level or a C-level person if you're not actually hiring the person. Uh, for example, Klausie I know specifically looked for a woman when he was hiring for the position and, uh, um, thankfully I got the job.

But, uh...

have the chance to even like, uh, experiment with myself. So I think like, uh, even, like, giving people a chance, and then mentoring them, and then getting them there. But the first thing, uh, the basic chance I think is also really important.

[00:42:56] Nic: All solid advice, I think. A- and that's something that I, I think that's actionable advice that anybody can take too, right? Make sure that you're expanding who you're thinking of when, when you're looking to promote somebody. E- even if it's not, like, a job promotion, I mean, just promote work that somebody's doing or promote an opportunity for somebody.

[00:43:16] Rachel: I mean, 50% of your clients are women, and if you don't have women in... a significant number of women in your decision-making positions, then you're not gonna be a- make decisions that cover 50% of your clients.

[00:43:34] Nic: I mean, a couple of the things that really blew... Not to keep coming back to this book. Sorry. But a couple of things that really blew my mind is that it took, I forget what position she had, but it was a C-suite.

One of the C-suite, um, people at Google got pregnant, and it took somebody in the C-suite getting pregnant to realize that maybe, just maybe, an office with, like, 30,000 people should have a couple of parking spots- ... at the entrance for pregnant women. Like, you're telling me that nobody at Google was pregnant in the five years before, like, she got preg- Like, come on.

And like you said, if there were-

[00:44:15] Rachel: This is Google we're talking about. Exactly.

[00:44:17] Nic: Yeah. The... But like you said, if there were, if you have women in your decision-making, um-

[00:44:23] Ashe: Yeah ...

[00:44:24] Nic: anywhere near the decision-making, like, these are things that become immediately apparent and can be... And it's not like it's causing... It, it's something that helps them, and it doesn't cause any problem for anybody else.

It's like, what, five spots at the entrance? Like, you know, that they have, you know, 30,000 spots in their parking garage or whatever. Um, so let, let's move on to the, to the next thing. So I... You know, Drupal, a- as, as we talked about with the contribution credit, one of the thing... I think it's one of the shining jewels of the Drupal community, the fact that they recognize, um, contributions both in code and outside of code.

Um, it's one of the few communities, it's... I think it's actually one of the only communities that has a contribution credit system, period. But what are, what are some of the things that we should be thinking about and looking for to provide credit that don't get credit today? 'Cause like we said, we... You get credit for organizing.

Maybe not enough credit, but you get credit for organizing. Tiffany added the new category for kind of what you do, I think, Ashley, which is marketing Drupal. Are there other areas that we should continue to explore, um, providing credit, like actual credits on your drupal.org profile for?

[00:45:39] Emma: Do you know, I think they do exist, but, uh, to Sunduri's point about, like, 45 minutes panicking about how you put an issue together, it's, like, just making it easier, um, to pick.

And, and maybe we need to do a better job, and I'm very guilty of this. Instead of just doing a thing, you know, put together an issue or add to your... 'Cause there's a contribution credit record now that you can use, but it, it is... And, you know, I know it's another thing. If you're contributing to something, you do the thing, and you move on.

I do anyway. I'm, I'm pretty lazy about, like, cataloging credits and such. But if you don't do that, then you don't, you know, make that known that other people who might be doing exactly the same thing for another issue or another initiative, you know, that it makes it invisible. You know, it does kind of it doesn't actually show that it's a thing.

Um, and we talked a little bit about organizing camps and the work that goes on behind the scenes in terms of mentoring and contribution that's associated with the cons. If we broke down all those different types of small jobs that happen, there, there's a ton of things there that we could be recognizing, um, people for.

Just anything that facilitates getting people together to work on Drupal, you know, th- there's a lot that just falls into, to those categories, and those are really, um, necessary. Um, but they don't fit the shape of a, like, a standard issue. Um-

[00:47:11] Nic: Yeah.

[00:47:12] Emma: But-

[00:47:13] Nic: I, I mean, for, to, to your point, like, I think as an organizer, I think we get one credit from putting together a camp.

And- Yeah ... I mean, usually there's... We usually have meetings every other week for six months leading up to it- Mm-hmm ... and once a week for a month leading up to it, give or take. Um, uh, and, and the, the truth is sometimes with code that happens, too. Like, I've, I've had code contributions where I've worked half an hour on it, and I've gotten a credit, and I've had code contributions where I literally spend 100 hours and get- Yeah

one credit. Um, so it, there's some variability there as well. But yeah, it might be interesting to see if there's a way to provide... Maybe it's per meeting you provide a credit or something. Um-

[00:47:58] Rachel: So I was somewhat involved, for want of a better description, in creating the, the, um, non-code, uh, projects on Drupal.org.

Um, because we wanted to do, um, exactly this type of thing and allow people to record, uh, non-code, uh, contributions. And it was inspired by the work that the Drupal diversity and inclusion, uh, group were doing at that time. They started doing it- Okay ... where they were giving contribution credits in an issue, uh, i- in an issue every week.

Um, and then we started doing that with the core contribution mentoring group. Um, and then it, it- Okay ... it's grown from there, and it's started to come into camps and so on. How you organize that, how you decide to give, uh, to create issues and to give contribution is up to you. There's no one telling you what you should, um, credit.

How many issues. Yeah. Whatever. There isn't a, there isn't a number. So if you think there is a piece of work that should be credited, credit it. Yeah? Yeah. The... No one, no one's saying you get one per event. Now, no, no, if you want more than that, then do it.

[00:49:22] Nic: Hmm. I'll, I'll bring it up with the team. I mean, we, we- Yeah

oh, actually, we're in a bit of a sticky situation with the podcast right now, 'cause we provide credit for all our guests and guest hosts. Mm-hmm. But with the new promotional credits, the DA wants to- I see ... credit us through that, which would be great, but we're also trying to figure out what to do because that means that we can't credit on the podcast.

Uh- So, like, we can't do double credit, right? We don't, we don't want duplicate credits. Um, so we're, we're actually talking about it internally, trying to figure out what we're gonna do there, 'cause it... I mean, both option... I, I, I do get some satisfaction from crediting all of our guests and guest hosts. Um, and, and it's a good record to see who, you know, who's been on the podcast.

So we're, we're still talking with the DA about that. Um, before we move on, uh, uh, do you guys wanna add something else? I don't know, I don't know if I gave everybody a chance to-

[00:50:16] Sinduri: I, I wanna say one thing. Credit... I, I love credits. I love getting credits and it's gives me a happy space. But, uh, does it really affect people to want to contribute more?

Especially people who are not working for a company who wants credits. Um- I have no right answer ...

[00:50:33] Nic: S- speaking for myself, I think it's one of the reasons why my contribution has increased so much. I mean, my-- I'm a freelancer. My company doesn't really get benefit from having credits, but just seeing the numbers go up it, uh, you know, it's satisfying to see.

So, you know, I, I don't think, um, I got a lot of satisfaction in the work that I was doing, the code-level stuff that I was doing. But I, I don't know if I would've sustained it if I didn't have the kind of gamified credit system, right?

[00:51:04] Sinduri: Um- But personally, it makes me very happy to get the credits. Yeah. But I just want to understand, like, if for different, uh, other people, how would it affect when they're doing the work?

Does credit system, uh, make them

[00:51:18] Nic: happy? Yeah. What do you guys think?

[00:51:21] Rachel: I want to keep mine for a bit.

[00:51:22] Emma: Yeah. I, when I first started, I didn't realize it was a thing, I'll be honest. So I would just attend meetings for a while, and then all of a sudden I got a notification saying, "You've been credited." You know how you get one on your email when you've made an account?

[00:51:39] Nic: Yep.

[00:51:39] Emma: Um, I do- where I'm conscious is, like, so that made me feel good, and then sort of thinking how do you encourage new people to contribute? I think it's don't ask them if you want to be credited. Like, just default do it. So, and again, note to self, when I, um, the Higher Ed Summit for DrupalCon Europe was a new thing for Rotterdam this year.

I got a team together. Have I credited them? No. Sorry, guys- ... but I will do it. I will do it, and I've said it. I've made a pledge publicly. But, uh, you know, because it, it, it's, it just says thank you, and thank you costs nothing, you know? And that, that sort of thing is what the community's good at. Um, to, to, and, you know, it's everybody likes a thank you.

So I feel whether your company requires it, whether it doesn't, it's just, it, it's a nice thing. Um- Yeah ... but I don't really have an exact answer to the, you know, what you're raising, Nic, where it is a very difficult thing to do equitably because it very much depends on the project, the initiative, like how it's divided up.

I ca- I've had credits for attending, like you, a single meeting, and then credits for organizing a whole thing. Um, but I think as long as, as long as there's something, um, it doesn't need to be perfect. And, you know, again, we're an open source community. If we can see a better way of doing it in a particular project, like ask the person who's awarding the credits or make a suggestion because there's ways that, that things can be, um, changed, um, a- and c- and can evolve, uh, to, to be more inclusive and, um-

[00:53:24] Nic: Yeah

[00:53:24] Emma: you know, congratulating those, uh, contributions.

[00:53:31] Nic: Oh, go ahead, Nic ...

[00:53:31] Rachel: go on, I'm gonna have to do it. Okay. So there's, contribution credits come down to two different things. And for each end user, they, they mean different things. There's recognition and there's reward. So you've got recognition. It's, it's a way of saying thank you, as Emma says, and saying, "Actually, this person's done something really good."

Uh, and we should always, always be doing that for everything that's a benefit to the community, whether it's some code, whatever, it doesn't matter. Just saying thank you through doing a contribution credit is an amazing thing to do. It's really great. The other aspect is reward, and actually being able to give something that has value to people.

Now, the value changes depending on who you are and what you do. So somebody who's a freelance developer, either front end or back end, contribution credits have very specific value because they're saying, "Hey, this person can do all of these things." They can sell. That is their CV, or resume in, in the US.

Mm. It, it, it is a part of saying that. The same for an agency. If you are, through your, the way that you are credited, saying that you are working for an agency, uh, you can give value to that agency because you're making the agency look good for potential clients.

[00:55:13] Nic: Yeah.

[00:55:13] Rachel: And this i- this is a another great thing It would, I would love, 'cause I, I work for an end user, uh, these days.

Uh, an end user organization. So we, we don't, we don't sell our work, our Drupal work. It's an internal thing. So, um, the value doesn't exist as such. Yeah, there isn't a resale value for those, for those contribution credits. However, it helps us show a list of what we've been involved in, which then helps us understand learning and development of team, et cetera.

Yeah. So each of these things has value in a different way for different actors, for want of a better description. Yeah. But-

[00:56:04] Nic: Yeah.

[00:56:06] Rachel: It,

[00:56:07] Nic: I, I, I think it's interesting 'cause, like, to go ... Put a finer point on that maybe. Like, if you're an individual, you can use it when you're looking for a job, right? Yeah. It's an easy way.

Like, when we were ... Um, I just went through an RFP process with a client. So I have a client, they wanted to do a rebuild, which was a little bit bigger than I could do individually, so we did an RFP with several different agencies, and one of the things that we did is looked at all those agencies on drupal.org and see, uh, both how many credits the agency had, but what the breakdown was between their em- employees, right?

'Cause again, if, if an agency- Yeah ... has 1,000 credits, and 1,000 of those credits happen with one person, and that one person isn't gonna be on the team, uh-

[00:56:50] Rachel: Exactly ... that,

[00:56:50] Nic: what,

[00:56:51] Rachel: what's that say? Yeah. I mean, we've, we've ju- we've just done an RFP, and we didn't consider any organizations who did not have a significant presence on drupal.org.

[00:57:01] Nic: Yeah. It ... And I, I, I think it works even for the end user organization, like you said, because if I'm, if I'm responding to an RFP and I see that organization has a bunch of credits, it's like, okay, they're tied to the community. They, you know, they know how Drupal works. They know the ethos of giving back, of using c-

Like, you don't have to do the whole extra sa- sales pitch of like, "Hey, we use Contrib because it's vetted by the commun-" You know what I mean? Like, they already know that kind of stuff, so you know how to approach them. Um, okay. So I th- I think now is a good time to kinda move on to the next, the next section.

I... By the way, I might do like... I like how you broke this into different- ... different sections of the show. It makes, uh, it makes for... Maybe we'll, I don't know, maybe we'll adopt that for, for the show moving forward. Um, so we'd like to kind of acknowledge some assumptions that, uh, people make, I think, and talk about maybe breaking some barriers to, um, get more contribution from, from women.

Um, so, uh, Ashley, maybe we can start with you. What are some assumptions that we kinda make on how people take part in Drupal, um, maybe around, uh, available time, travel arrangements or funding? Um, what are some assumptions that we make that we should maybe revisit?

[00:58:34] Ashe: I guess for me this could come back to some of the earlier things as well of like, uh, responsibilities that are on people that we maybe don't consider, and then we just assume that maybe people are in a similar position to us and things like this. And I think that can be a bit tricky because we're all different.

We've all got very different lives going on. So I think in terms of assumptions, it's nice to think that everybody can be as involved as you might wanna be But maybe not everybody can at the moment in time. So if people, and utilizing connection networks and things like this, um, to do things as a community is probably one of the, the best ways we can support each other even when things are different.

[00:59:18] Nic: You, you said, uh... When you say connection network, that, that sounds like it might mean something specific. Is that-

[00:59:24] Ashe: No, I'm just

[00:59:25] Nic: saying- Or is it- I mean, like- Oh, okay ...

[00:59:27] Ashe: if I wasn't part of the Women in Drupal award, I wouldn't know Emma. Yeah. I wouldn't know Rachel. I wouldn't know

[00:59:31] Nic: Mary. Ah, okay. Like,

[00:59:32] Ashe: making these connections are really valuable, and I think, like, if there's...

So say there was something, I mean, obviously I don't develop anything, but say there was a project that

[00:59:41] Sinduri: I heard of that I thought

[00:59:42] Ashe: somebody else could actually be a really good fit on, and I don't have the, the time or the capacity to engage in that, then I can be like, "I know somebody who would be perfect for this or who may really want to get involved."

So I think it's still about championing other people. Um, and then, yeah, just trying to, to do what you can when you can

[01:00:03] Nic: How about you, Sunduri? Anything, anything you'd like to add about that? What are some assumptions that maybe people make around contribution that we should revisit?

[01:00:12] Sinduri: Uh, I think it's more about, uh, uh, integrating.

Like the, uh, for example, like, uh, events. Uh, coming to DrupalCon, we assume that companies will pay for, uh, us to go there. Nic, you're a, a freelancer, so you know you have to pay for your own stuff to go to an event. And I think, like, all of us are nodding. So I'm guessing all of us are paying for our own self.

And I think, like, that is something we forget, that it can get really expensive really fast for normal people. So basically all my savings go for Drupal events. That's all. Like, my vacation time goes for Drupal events. And, uh, a- additionally, we also assume people have free time. Like for example, I am privileged where I don't have children, and I spend time for evenings and weekends on Drupal event stuff.

But people have families, people have lives. And, uh, we assume like, "Oh, why they're not doing enough?" But they have a l- they have a family that they have to take care of. So- Yeah ... I think those are like, um, multiple different factors which we forget then, yeah

[01:01:11] Nic: How about

[01:01:11] Emma: you,

[01:01:11] Nic: Emma?

[01:01:12] Emma: I think there's a ... I do have children, and I ... They have been, like I have favored Drupal over them sometimes. But I have ... They're teenagers, so, you know, I'm kind of always- Oh, yeah ... riding the waves. I think sometimes I'm, when I'm needed, it's by Drupal, and like the majority of the time it's like, "Talk to the hand, mom."

Um, but so I think, I think it's knowing that about people. And this is, this can be tricky because people don't always want to talk about their personal circumstances and such. But I think it's just respecting people. If people leave early in a meeting, then that's absolutely fine. Uh, but it's just kind of, i- it's making sure that they're not gonna lose out.

So if we re- Yeah ... like for example, in that instance, record the meeting, take transcripts, follow it up on Slack so that if somebody does have to like run and drop for the school run, and this can apply to, you know, any parents, it's not just, just women. Um, then, uh, you know, it's just thinking that through and trying to not let that be something where they're missing out.

And I guess similarly to Sunduri's point, don't ... Uh, like if, if people can't travel to a Drupal event, then make sure that's not when the main thing is gonna happen. You know- Yeah ... make sure that there can be an online call that other people can, um, participate in. Um, and yeah, just not, just not assuming. I mean, the, one of the great things about Drupal is, you know, the international flavor.

It does-

[01:02:40] Mike: Right ...

[01:02:41] Emma: make us question what time zone are people in? How is it, is it evening for them? Is it morning for them? And then get a sense of, of how people's days are, are panning out. So I think, I think all of that, um, contributes to sort of like not making assumptions and, and just asking and being polite.

You know, and, um, we have mechanisms to try and work all of this out so that people can, can contribute, whether it's asynchronous, whether it's synchronous, and there's lots of ways.

[01:03:12] Nic: Yeah, I think most, most initiatives in Drupal have an asynchronous, like, 24-hour meeting in Slack. Which, which is, I mean, in itself is making an assumption that, uh, you know, they have access to Slack, which is a proprietary software, and the internet.

I mean, it... Although it is pretty hard to collaborate remotely without internet access, so I think that's kind of a baked-in assumption. But al- also it, it, it, a lot of times having an actual meeting where you're talking to people can be more productive than an asynchronous meeting, 'cause sometimes you have to have some back and forth, and if everything is asynchronous...

I, so I think some initiatives, I think, I think the CLI and Core initiative did this, where they have an asynchronous meeting- Mm ... every week, and then I think once a month they have a synchronous meeting. Um, but, and I think even UX, I think, has two separate meetings, one in two different time zones. I, I know I've joined, um, the call that you and Christina put on sometimes- Yeah

to ask, to, to ask questions. So yeah. All, all, all sorts of ways to, to contribute. Uh, Rachel, anything you'd like to add before we...?

[01:04:19] Rachel: Yeah. I mean, I, I really like the asynchronous meetings. I think they're, they're a great, uh, innovation actually. I'm really pleased. But if there's one thing that we could really be looking at, it's taking a long, hard decision to really step up on scholarships to in-person events.

[01:04:42] Sinduri: Yes.

[01:04:42] Rachel: And w- we, we, we, we do them to an extent at the moment. So DrupalCon, we will see probably about 1% to 2% scholarships to, to attendees ratio.

[01:05:01] Nic: Hm.

[01:05:04] Rachel: We need to change that by orders of magnitude, um, because that's how we get to events the people who make a difference. Um, and how we get to events people who are not necessarily totally bought into Drupal right now.

Um, so it, us making a significant change to that, and I don't know the answers how, uh, makes a difference. I mean, I remember when... I, I, I'm sure you, you, you all remember, uh, lockdown, uh, during COVID, and we couldn't have DrupalCon in person. Well, we had it online, and I was at the DA at the time, and I, I kind of got onto the subject of scholarships, and I s- we kind of worked out that scholarships didn't cost us anything.

[01:06:06] Sinduri: Hmm.

[01:06:07] Rachel: Yeah? Um, and we were able to offer access to the event to orders of magnitude more people. In fact, I think to, to the... it was either the first one or the second one, we held 178, I think it was, scholarship places.

[01:06:26] Nic: Oh.

[01:06:27] Rachel: And we... I... There, there will be a Drupal Association blog post on it if you want to look it up.

Um, we offered places, and they were taken up by loads of people in all sorts of parts of the world. SheCode Africa supplied a load, uh, a- and, and so on. Imagine that in person, if we were actually able to make it so that a significant mo- gr- significantly greater number of people were able to come to events.

Yeah? Um- Yeah ... all those people at the moment who cannot participate, able to participate and grow the community

[01:07:11] Nic: So I'm, I've been curious since the intro about the Woman in Drupal award. Uh, Ashley, I think you might be in a good position to talk a little bit about that award. Can, can you tell us what goes into, um, nominating, selecting, providing the award? Mm. We ... You know, tell us a little bit about the Woman in Drupal award.

[01:07:33] Ashe: So it's ultimately, from my perspective, about visibility and about recognizing women for the work they do. Um, and so there are so many brilliant women doing brilliant things in Drupal, and it's just a way to sort of share their story a bit and give that recognition more widely, um, within the community.

And it doesn't really end with the recognition of the person on stage because it's what happens after. Um, and it's interesting because when I spoke to a lot of the women, uh, this year at DrupalCon, it was ... That they were saying, "Oh, I felt really inspired seeing this person on the stage, and I felt really inspired hearing about that person's journey."

Which is lovely because

[01:08:13] Sinduri: they don't know

[01:08:14] Ashe: them,

[01:08:14] Sinduri: they just have

[01:08:15] Ashe: seen, like, a snapshot of them for a short period of time, um, and have been able to come away with something that maybe inspires them to push more and to do more and to maybe get their own nomination one day. Um, which is really great. So we, um, encourage people to nominate people from all different, um, worlds within Drupal.

So we did initially have categories. And this year we removed them, which I was super happy about because it made it a lot easier for people to nominate. Because I think the categories were a little bit of a barrier sometimes- Mm ... in terms of who could be what. Um, and as the award grew, we knew that we needed to make it more accessible.

We wanted to not put any limits to who could be nominated. Um, so this year was great, I think, because we had, um, a pool of people nominated and then we have a jury, uh, which is usually the previous winners from the year before. And they come together and they make the decision of who they think, um, should, should win.

And there are three winners that we have for this award, 'cause despite us removing the categories we didn't want to limit the number of winners either. So we were able to shine a light on three women every year. Um, and it's, it's really positive. And from a marketing perspective, it's lovely because you get to see the storytelling element of this.

And it's ... The awards give you a platform, but what we do with those stories afterwards is also really important.

[01:09:43] Nic: Is, is there a good webpage that kind of tells that story or...?

[01:09:48] Ashe: Yep. So, um, we've actually got one in the, in the resources that you're gonna share. So, uh, I wrote a blog for this year for the Women in Drupal Award this year, and the reason I've shared that is because there's some really lovely pictures of Emma, Rachel, and Sunduri also, uh, on stage.

Rachel is thrilled about it, as you can see. But, um, yeah, it's, it's lovely because you get to see us in action, and you get to hear a bit about it. And we also had some of my colleagues there, um, who gave a great speech at the start, um, talking about opening doors for people, um, within whatever industry you're in really.

Um, so yeah, so please do take a look at the blog, and you can see some of the pictures, and, um, get to know a bit more. But we do have a page, uh, as well every year that we update on Drupal.org as well about the Women in Drupal Award.

[01:10:38] Nic: All right. Awesome. I'll take a look

[01:10:43] Emma: It's, um, I think the other thing to note about the Women in Drupal award is that it's peer nominated.

So- Mm-hmm ... anybody can nominate anybody. And, um, Ash and I, um, without... previously I think it was define, build-

[01:10:58] Sinduri: Scale ...

[01:10:59] Emma: um, yes, scale. Um, so if you felt, I... She's doing brilliant work in the Drupal community, she's, it, you know, I want to, to recognize her. You would have to then think, does she fit into this category?

But without that, now, you know, going forward anybody can nominate any woman they've worked with. Yeah. So I guess call to action for the community, if you've got a woman that's in a team or initiative that you're in, just kind of, you know, recognize those contributions, and when the call comes out, uh, for next year, then-

[01:11:32] Nic: Mm-hmm

[01:11:32] Emma: um, you know, y- you can just fill in a form, um, and it can be then considered, um, by, um, as Ash says, the, the previous winners, which I think is a really nice... For me, I won it in 2025 along with Sunduri, and I didn't realize that it, you know, I didn't really understand the full process until I got to be on the jury for this year's winners.

Um, so then you sort of get to see the lovely things that people have written about, uh, like nominees for this year. Um, and, um, and it's so hard to select three- Yes ... winners because you, you almost want... But then to a point, I think people have a, a moment in the Drupal community of recognition and, you know, it, it will come and, and again, I didn't, I haven't had a full sort of experience of the process, but people are nominated year on year and so, you know, um, that's kind of noted as well because there are people, uh, obviously from Jacala who recognize names that are coming up over and again because a- as the previous year's winners, you just get to see the sort of- Yeah

nominations for that year. Um, but yeah, it's, um-

[01:12:46] Ashe: We also have Baddy and Kit who are consistent- Baddy and Kit ... with the jury year as well, so they know- They do ... as well who's been nominated before, which is great. Um, and we also removed this year, so, um, speaking about more broadly giving credit to other roles and things within the community- Mm-hmm

we removed the need for a Drupal profile, a Drupal.org profile to be nominated because-

[01:13:06] Nic: Oh, interesting ...

[01:13:07] Ashe: before, like there are some people, say you work in HR, you can still be nominated. You're still part of the community. You're still, you know- Yeah ... it doesn't matter what you do, what role you do, you can still be nominated.

Um, but obviously somebody, say, from HR- Interesting ... is probably not gonna have one of those profiles. So that was just another barrier that we wanted to remove

[01:13:26] Nic: Hmm. That's interesting. Yeah, we, I mean, obviously we don't require a drupal.org account to be on the show either, but it, it always makes me a little sad when I can't give them the specific credit, uh-

to show up on their page. So may- maybe, maybe you can ask them to create it afterwards if they're, uh, if they're nominated. Um, well, all right. We are, uh, running out of time, so, um, I don't think we, uh... I'm gonna do a, a really quick round. Is there anything that we didn't discuss today that you think would be, uh, uh, a good way to highlight women in Drupal outside of the award?

Um, what's a good way to, to promote somebody doing amazing things? Is there a- any last thoughts?

[01:14:18] Rachel: If people are doing amazing things, thank them publicly. Do it publicly. Yeah.

[01:14:25] Nic: That sounds good. Well, Ashley, Sunduri, Rachel, and Emma, thank you for joining us. And Emma, thank you for joining us for the last three weeks.

Thank you for having me. Uh, don't... Always happy to have you guys. Thank you. Uh, you can reach out to us on the Drupal Slack in the Talking Drupal channel, or email us with, @[email protected]. If you'd like to promote your Drupal event, sponsor an episode, or become a guest, you can visit talkingdrupal.com and click the buttons in the sidebar.

And thank you patrons for supporting Talking Drupal. Your support has kept us talking for 579 episodes.

[01:15:01] Ashe: Wow.

[01:15:02] Nic: All right. Ashley, if our guests wanted to get in touch with you or had any questions, what's the best way for them to do that?

[01:15:08] Ashe: They can find me on LinkedIn, Ashley Box.

[01:15:12] Nic: Awesome. And Sunduri, if our listeners wanna get in touch with you, what's the best way for them to do that?

[01:15:17] Sinduri: Drupal org Slack, Drupal Switzerland Slack, Drupal Austria Slack, and LinkedIn.

[01:15:23] Nic: Awesome. And Rachel, how about you?

[01:15:26] Rachel: Uh, you can find some links to contact me on rachelnorfolk.me.

[01:15:31] Nic: Perfect. And Emma, how can people get in touch with you? You can

[01:15:34] Emma: get me on Drupal Slack, uh, just Emma Hall

[01:15:39] Nic: Perfect. And you can find me pretty much everywhere @nicxvan, N-I-C-X-V-A-N.

And- Do I get to say

[01:15:47] Emma: that- Yes, you do ... if

[01:15:48] Nic: you've

[01:15:48] Emma: enjoyed listening, we've enjoyed talking. Thank you.

[01:15:52] Nic: Yes. Thank you so much.

[01:15:53] Ashe: Thank you.

[01:15:54] Nic: See you next week.

[01:15:55] Ashe: Thanks, Amazee.

[01:15:56] Emma: Thank you.