text
stringlengths
0
2.46k
[840.52 --> 840.82] Okay.
[841.48 --> 845.74] Well, we talked about having terms of service, uh, to some degree, like a, if you want to
[845.74 --> 849.52] be a maintainer, et cetera, or you are a maintainer, or you want to bring on a contributor,
[849.52 --> 853.16] a term of service. So what you're saying is if you need to leave or you need to step
[853.16 --> 861.66] away, the social construct should be plan for successor, invite a successor, have some
[861.66 --> 864.90] sort of plan, like just don't leave your station abandoned.
[865.62 --> 866.48] And I agree with that.
[866.56 --> 866.80] Right.
[867.00 --> 869.70] That would be great if you didn't abandon, especially if other people are using it.
[870.24 --> 874.14] But I agree with that as well. Like it's much easier to get people to step up to positions
[874.14 --> 876.18] in your project if you're clear about what they are.
[876.46 --> 876.60] Right.
[876.86 --> 877.06] Yeah.
[877.06 --> 882.56] Hey, if you submit five pull requests and I, you know, I pretty much accepted them unchanged
[882.56 --> 887.16] and you're always there when I send you an email or a DM, like then I'm willing to consider
[887.16 --> 888.46] you for this role.
[888.90 --> 894.48] Right. And if you accept it when you leave, which is cool, please help me find somebody
[894.48 --> 895.26] who might be suitable.
[895.90 --> 896.64] That would be a good cause.
[896.64 --> 899.92] And the please might be more you have to versus just simply please.
[900.14 --> 901.12] Can you say that though?
[901.12 --> 907.62] Well, I, well, what I'm asking, I guess, is like, should we, there's, there's no perfect
[907.62 --> 913.46] way to do this, but maybe the version that gets deployed in most cases, like if you accept
[913.46 --> 919.14] the position on a project that has, I don't know, some usefulness, some threshold of usefulness
[919.14 --> 923.70] and you are a crucial person because you've accepted a role as a maintainer.
[923.70 --> 924.00] Yeah.
[924.50 --> 926.94] Maybe you agree to mentor a certain number of people or something.
[927.34 --> 928.08] Yeah, exactly.
[928.70 --> 934.38] Something, something that says I care about my team, my other maintainers and this project
[934.38 --> 936.96] enough to accept the role because I like it.
[936.96 --> 943.78] But also if I need to step away, some sort of responsibility to ensure non-breakage, you
[943.78 --> 943.96] know?
[944.20 --> 948.20] So one of our, our GitHub students, you know, the students that's in GitHub education shared
[948.20 --> 953.60] with me a tip that he learned yesterday, which was instead of write, you know, someone submits
[953.60 --> 958.74] an issue instead of just writing code and solving it and doing your own pull request and closing
[958.74 --> 958.98] it.
[959.26 --> 963.50] They suggested writing out like the whole problem and how you saw the solution.
[963.50 --> 966.80] And they say it would take as long as just solving it, but writing it up and describing
[966.80 --> 971.04] it and then putting it out there for someone else to be able to pick up is a good way to
[971.04 --> 972.16] like grow your project.
[973.02 --> 973.98] Don't repeat yourself.
[974.16 --> 978.98] That's so forward thinking though, you know, it's just like it requires discipline and forethought.
[979.24 --> 981.94] It's hard to do that all the time where you're just like, well, I could just fix it real
[981.94 --> 982.20] quick.
[982.38 --> 984.42] Especially if you like writing code and you like your project.
[985.22 --> 986.26] I like to write code.
[986.36 --> 988.18] I do not like to write prose very much.
[988.66 --> 990.20] I started this because I like coding.
[990.66 --> 991.94] I'm just going to code this up real quick.
[991.94 --> 994.76] But you do that over and over and over again.
[994.86 --> 998.40] Eventually it's just a recipe for disaster, you know, as your, as your life changes, as
[998.40 --> 999.44] your desires change.
[1001.02 --> 1005.04] But you can write prose for the problems that are kind of boring to you and then save the
[1005.04 --> 1006.30] interesting ones for yourself.
[1006.86 --> 1007.08] Yeah.
[1007.76 --> 1009.12] Just don't tell anybody that's what you're doing.
[1010.80 --> 1012.30] Here's a bunch of boring issues, guys.
[1012.42 --> 1013.36] You guys handle those.
[1013.42 --> 1014.36] I'll take all the fun stuff.
[1014.38 --> 1015.00] I'll take the fun stuff.
[1015.50 --> 1017.52] It might not work to grow your project.
[1017.52 --> 1023.86] Companies can now contribute to open source via GitHub sponsors in new ways, not just credit
[1023.86 --> 1024.26] cards.
[1024.92 --> 1026.54] POs, larger checks, et cetera.
[1027.84 --> 1030.78] What's the state, I guess, the next major thing for sponsors?
[1030.90 --> 1031.64] What are you working on?
[1031.72 --> 1035.76] What is the sponsors team or this new leadership?
[1036.04 --> 1037.94] What's the next plan for GitHub sponsors?
[1037.94 --> 1038.38] Yes.
[1038.74 --> 1038.98] Yes.
[1038.98 --> 1041.32] I think there's still features we can add in the products.
[1041.48 --> 1045.26] Like we talked about, like being able to see all your dependencies and all those dependencies
[1045.26 --> 1047.50] and, you know, contribute with like one click.
[1047.64 --> 1048.88] You know, there's things like that we can add.
[1049.18 --> 1052.04] But we also have a couple other programs that we're experimenting with and we're bringing
[1052.04 --> 1053.32] them into, you know, one group.
[1053.92 --> 1057.70] So we have, we have a accelerator program that's going on right now.
[1057.78 --> 1058.82] It's a 10 week program.
[1059.02 --> 1061.92] We have 20 people in it in this round, $2,000 a week.
[1062.18 --> 1063.70] And they meet a couple times a week.
[1063.74 --> 1064.84] They get like mentorship.
[1065.16 --> 1066.22] They get to meet each other.
[1066.22 --> 1068.98] And these are people that want to take their project to the next level.
[1069.50 --> 1071.88] And so we're, we're figuring out like, what do they need?
[1071.98 --> 1073.02] What can we offer them?
[1073.02 --> 1077.40] And then hopefully what can we build into sponsors and the GitHub product to help all
[1077.40 --> 1079.44] maintainers who want to take their project to the next level?
[1079.64 --> 1079.74] Yeah.
[1080.30 --> 1084.62] We also have GitHub funds because it's really hard to get venture capital money when you
[1084.62 --> 1088.06] are writing your, your company's code in open source.
[1088.52 --> 1090.72] Venture capitalists like to think you have secret sauce.
[1091.26 --> 1096.18] And so we have GitHub fund that actually funds open source software projects that
[1096.18 --> 1097.74] are companies, startup companies.
[1098.34 --> 1101.72] And that's GitHub proper that funds it or they're pulling together other people's money?
[1101.84 --> 1102.16] How does it work?
[1102.16 --> 1105.18] It's a partnership with Microsoft's M12 venture capital fund.
[1105.54 --> 1105.90] Okay.
[1106.24 --> 1107.76] How do those projects get selected?
[1107.90 --> 1109.04] Is it an application?
[1109.30 --> 1111.52] Is it, who gets funded?