text
stringlengths
0
2.46k
[4722.16 --> 4722.82] So that's why I'm there.
[4723.04 --> 4724.36] So what is it you do there then?
[4724.48 --> 4724.76] Particularly.
[4725.20 --> 4725.48] Yeah.
[4725.58 --> 4725.72] Yeah.
[4725.84 --> 4726.34] I'm not.
[4726.48 --> 4726.64] Yeah.
[4726.64 --> 4727.84] I'm director of community.
[4728.02 --> 4728.28] Okay.
[4728.56 --> 4731.68] So that means that we're, you know, handling meetups.
[4731.78 --> 4735.48] We're doing things like our community forums, our real time communities, that kind of thing.
[4735.52 --> 4739.92] Trying to bring together practitioners of open source data infrastructure broadly, whether
[4739.92 --> 4744.24] we offer it on our platform or not, to kind of come together and talk about the problems
[4744.24 --> 4747.16] that they're having and some of their pain points and some of their tips and tricks and
[4747.16 --> 4747.72] stuff like that.
[4747.76 --> 4750.32] Because it's a really fascinating thing to be part of.
[4750.86 --> 4754.54] And, you know, a lot of people don't realize that there are open source alternatives for like
[4754.54 --> 4756.56] data warehousing or some of these other challenges.
[4756.64 --> 4757.14] So, yeah.
[4757.30 --> 4758.14] So that's why I'm in it.
[4758.48 --> 4760.30] Do you interface with the Ospo by any chance?
[4760.56 --> 4760.76] Yeah.
[4761.06 --> 4761.24] Yeah.
[4761.32 --> 4761.50] Okay.
[4761.60 --> 4761.74] Yeah.
[4761.78 --> 4764.16] I mean, with the caveat, I'd only been there like three weeks.
[4764.28 --> 4764.80] So like, who knows?
[4764.90 --> 4765.20] But yeah.
[4765.56 --> 4765.76] Yeah.
[4765.80 --> 4767.08] The Ospo people are amazing.
[4767.22 --> 4770.46] And it reminds me a lot of the work that we did at Acquia around Drupal, right?
[4770.46 --> 4774.12] It wasn't called an Ospo, but it was very much like, what's the best thing for this
[4774.12 --> 4774.72] project?
[4775.22 --> 4775.48] Right.
[4775.66 --> 4779.58] That's the thing we have to focus on, whether or not it's good for the business as a whole,
[4779.70 --> 4782.72] because those are, they're separate, but hopefully there's a Venn diagram, but they
[4782.72 --> 4784.30] could be separate and competing concerns.
[4784.88 --> 4786.84] Every Ospo has a level of maturity.
[4786.94 --> 4788.28] What do you think yours is at?
[4788.32 --> 4792.38] Without calling it immature, like what level are they fighting against?
[4792.38 --> 4795.46] Honestly, I don't know if I'm qualified to say that, but I mean, they're in the to-do
[4795.46 --> 4795.84] group.
[4796.24 --> 4797.70] They're a member of the OpenSSF.
[4797.76 --> 4800.16] So I feel like they are, they're doing the right things.
[4800.22 --> 4801.34] They're contributing in the right ways.
[4801.56 --> 4801.62] Right.
[4801.74 --> 4804.66] And they're also employing, you said, Kafka maintainers and stuff like that.
[4804.74 --> 4804.90] Yeah.
[4805.00 --> 4805.20] Yeah.
[4805.30 --> 4805.56] Yeah.
[4805.86 --> 4809.44] And yeah, there's like Postgres, a couple of people, there's like, you know, from different,
[4809.72 --> 4814.14] like, you know, again, they want to make sure that the technologies that we rely on for
[4814.14 --> 4815.12] our customers stick around.
[4815.48 --> 4815.66] Right.
[4815.68 --> 4818.74] And I think that that's really awesome because not, they wouldn't have to do that, right?
[4818.74 --> 4822.02] They could just sell the stuff and not give back, but they're choosing to do it.
[4822.12 --> 4822.48] So, yeah.
[4823.36 --> 4823.64] Cool.
[4823.96 --> 4827.68] But on the maintainership thing, yeah, I do think that that is a general problem.
[4827.70 --> 4831.80] That people need to think about is like right now you're in this, you love it.
[4832.16 --> 4835.86] You know, you could do this the rest of your life, but realistically your life's going to
[4835.86 --> 4837.26] change over the course of your life, right?
[4837.26 --> 4837.46] Right.
[4837.72 --> 4840.60] You maybe, you know, get, you know, different hobbies.
[4840.72 --> 4842.56] Maybe your interest in technology's changed.
[4842.62 --> 4843.78] Maybe you have a kid, whatever.
[4844.22 --> 4844.42] Yeah.
[4844.50 --> 4847.38] And so it's really important to think about that as you're maintaining your product
[4847.38 --> 4850.60] and your project to make sure that you're, you're thinking about who's going to take
[4850.60 --> 4853.78] that on when you have to step away so that you can step away when you need to.
[4854.04 --> 4854.18] Yeah.
[4854.18 --> 4854.48] Yeah.
[4854.48 --> 4858.54] One of the themes for me, I didn't put it in my notes actually.
[4858.62 --> 4863.50] One of the themes for maintainer or for maintainer month and maintainers, I believe, is like
[4863.50 --> 4867.82] essentially finding a way to step back, finding a way to have succession planning and stuff
[4867.82 --> 4868.26] like that.
[4868.46 --> 4871.92] Do you, as part of your leadership, talk at all about that?
[4872.22 --> 4876.74] Like that kind of maturity of a maintainer and supporting folks that, to anti-burnout essentially.
[4876.74 --> 4877.14] Yeah.
[4877.14 --> 4877.26] Yeah.
[4877.58 --> 4877.94] Yeah.
[4878.06 --> 4883.10] So we, we do things like have what are called, oh my God, what is the word?
[4883.40 --> 4884.12] This is so bad.
[4885.62 --> 4886.66] Ah, provisional.
[4886.80 --> 4887.20] That's the word.
[4887.30 --> 4888.20] Provisional maintainers.
[4888.34 --> 4892.70] So we find people that are kind of active and doing the right things in the right subsystems.
[4892.80 --> 4896.58] We'll kind of find those people, pull them in and say, hey, would you like to become
[4896.58 --> 4897.44] a provisional maintainer?
[4897.44 --> 4902.06] A provisional maintainer doesn't get commit access necessarily, but they are allowed to
[4902.06 --> 4906.32] like make, okay, this RTBC, sorry, reviewed and tested by community patch.
[4906.38 --> 4908.02] It's like, it's gone through the review process.
[4908.26 --> 4911.66] This patch is good to go and they can escalate it to committer to actually commit it.
[4911.74 --> 4914.64] And after they've done that for a little bit of time, then we do give them commit access,
[4914.90 --> 4917.58] but maybe just to their own subsystem and not the whole of core.
[4917.78 --> 4919.40] And then later they kind of grow into that.
[4919.40 --> 4920.72] So we have like a progression model.
[4921.18 --> 4926.34] What we're also exploring is the idea of term limits on a committer as well.
[4926.34 --> 4929.78] Um, because, uh, terms and term limits, I should say.
[4929.88 --> 4933.70] So terms meaning you're not signing up to something for life necessarily.