text stringlengths 0 2.46k |
|---|
[2377.78 --> 2380.64] Is your pull request backlog getting bigger or smaller? |
[2380.98 --> 2386.10] Are you responding to pull requests and issues more, more quickly or is it taking you more |
[2386.10 --> 2386.52] time? |
[2386.64 --> 2391.46] So I like to look at trends over time and I like to look at metrics in the context of |
[2391.46 --> 2397.66] projects because individual projects have, you know, certain ways of working and certain |
[2397.66 --> 2399.46] things that impact the metrics. |
[2399.46 --> 2401.56] And unless you're part of the project, you don't know. |
[2401.56 --> 2408.66] So, you know, for example, if I work on a project and it's, you know, we're cutting a huge release |
[2408.66 --> 2412.52] that, you know, has a bunch of breaking changes, there's probably going to be some weird things |
[2412.52 --> 2413.90] in the metrics associated with that. |
[2414.04 --> 2418.20] So, you know, pull requests are getting the backlog while you get everything together for |
[2418.20 --> 2419.26] the release, for example. |
[2420.18 --> 2425.86] I was talking to a friend at Google, Sophia Vargas, and she does a lot of analysis on things |
[2425.86 --> 2426.92] like Kubernetes. |
[2426.92 --> 2432.34] And some of the metrics that she was looking at it made just no sense because the way Kubernetes |
[2432.34 --> 2434.80] works is you've got bots that do all the things, right? |
[2434.90 --> 2437.58] So like you have bots that respond to things automatically. |
[2437.88 --> 2442.28] The bots close the issues automatically after a certain amount, you know, they go stale, |
[2442.36 --> 2442.94] they close them. |
[2443.32 --> 2446.88] So there's all this like bot activity that she was looking at data and she's like, this |
[2446.88 --> 2447.54] makes no sense. |
[2447.74 --> 2450.38] And she went and talked to some people and they were like, oh yeah, because that's the |
[2450.38 --> 2450.70] bots. |
[2450.90 --> 2451.50] That's what they do. |
[2451.50 --> 2451.86] Yeah. |
[2452.76 --> 2453.66] It's normal to them. |
[2453.78 --> 2457.30] But unless you understand that, you can't interpret like the, it doesn't tell you anything |
[2457.30 --> 2460.34] about the health of the project unless you understand what's going on within the project. |
[2460.66 --> 2460.86] Yeah. |
[2461.34 --> 2464.70] So it's a hard job then, I guess, to quantify. |
[2465.62 --> 2470.18] And so when you say you like to look at trends, you're basically measuring the health of the |
[2470.18 --> 2472.70] project relative to its past health. |
[2474.66 --> 2475.72] Why is that beneficial? |
[2475.72 --> 2482.68] I guess just to see where they're headed or, um, I guess who, I don't want to say who |
[2482.68 --> 2485.10] cares, but like who's actually, who, who cares? |
[2485.78 --> 2491.84] Who's the person who, or the org or the entity that says, I care about the future health of |
[2491.84 --> 2493.14] this, this project. |
[2493.34 --> 2494.94] Is it foundations? |
[2495.28 --> 2496.06] Is it individuals? |
[2496.22 --> 2499.26] Like I would come to it as an individual and think this is why I'd want to score. |
[2499.26 --> 2503.40] Or it's because like my, my question is, do I want to get involved in this project? |
[2503.48 --> 2504.74] Do I want to use this thing? |
[2505.44 --> 2506.64] How's the health of the community? |
[2506.76 --> 2513.42] You know, I look at the, uh, GitHub pulse tab, the insights, not super useful, but it's |
[2513.42 --> 2513.76] there. |
[2513.94 --> 2514.30] Right. |
[2514.34 --> 2518.08] Cause I'm trying to gauge, is this a dependency that I'm willing to take on perhaps? |
[2518.26 --> 2522.76] So that'd be like one angle into caring about the community health of a project, overall |
[2522.76 --> 2523.14] health. |
[2523.54 --> 2528.30] And so I would like to see like, well, I mean, trends would be useful, but if it's starting |
[2528.30 --> 2534.04] from a really bad place and it's trending up, but it's like still maybe not the nicest |
[2534.04 --> 2534.84] place to hang out. |
[2534.84 --> 2535.20] Yeah. |
[2536.52 --> 2537.60] Long winded question. |
[2538.28 --> 2540.78] Like who are the users of your information? |
[2540.78 --> 2541.22] I guess. |
[2541.26 --> 2541.96] Who's the end user? |
[2542.68 --> 2542.84] Yeah. |
[2542.90 --> 2543.66] So it depends. |
[2543.82 --> 2546.78] I think, I think all of those people are end users of metrics. |
[2546.78 --> 2547.20] Right. |
[2547.20 --> 2552.44] And so, so part of the reason that I look at trends is because, um, from, let's just |
[2552.44 --> 2553.86] talk about from a VMware perspective, right? |
[2553.86 --> 2554.82] From a company perspective. |
[2554.98 --> 2555.18] Sure. |
[2555.30 --> 2560.66] I want our maintainers to look at the projects and use the project health metrics to decide |
[2560.66 --> 2562.56] where they need to improve. |
[2563.12 --> 2567.96] So, you know, if they're responding to pull requests really quickly, um, then that's, |
[2568.00 --> 2568.42] that's great. |
[2568.56 --> 2571.82] But if they're never closing any of those pull requests, maybe that's where they need |
[2571.82 --> 2572.26] to focus. |
[2572.26 --> 2575.06] So it gives them, it gives them a place to focus. |
[2575.20 --> 2575.50] Sure. |
[2575.50 --> 2579.68] And the reason I like to focus on trends is because what I don't want is somebody getting |
[2579.68 --> 2583.82] all hung up because they're, you know, their number is going down, but maybe it's going |
[2583.82 --> 2587.16] down less quickly or it's, it's improving in some way. |
[2587.24 --> 2590.60] So they're already, they've already made some improvement and I don't want people getting |
[2590.60 --> 2595.08] hung up on just like the number because the numbers less than it was last month or whatever. |
[2595.30 --> 2597.78] I want them to think about whether they're already improving. |
[2597.94 --> 2599.84] Is there something else they can do to improve? |
[2599.84 --> 2604.04] And then I think, you know, when you're new to a community and you're trying to decide |
[2604.04 --> 2607.34] whether you want to participate in a community, I think those are a whole different set of |
[2607.34 --> 2607.92] health metrics. |
[2608.12 --> 2612.32] Like, yeah, I mean, I think that's things like, is anybody actually using this thing? |
[2612.56 --> 2612.74] Right. |
[2612.78 --> 2614.42] I don't want to contribute to something nobody uses. |
[2614.76 --> 2614.86] Right. |
[2615.14 --> 2618.82] Um, are there lots of other people contributing to all of those contributors work at the same |
[2618.82 --> 2620.52] company and I don't work for that company? |
[2620.54 --> 2622.18] Am I even going to be welcome in this project? |
[2622.44 --> 2626.40] So I think there's a lot of things that you look at depending on, on what your goals are as |
[2626.40 --> 2629.70] a contributor and depending on what kind of project you want to contribute to. |
[2629.84 --> 2631.08] How do you represent this data? |
[2631.24 --> 2636.60] Is it on a website and I can go to like a certain domain and a certain org name and a |
[2636.60 --> 2637.42] certain project name? |
[2637.56 --> 2640.16] Like, is it like GitHub URL structure to get to this data? |
[2640.52 --> 2644.30] How do you, how can I go and find my projects that I'm interested in as data? |
[2644.40 --> 2645.38] How can I find that information? |
[2646.04 --> 2646.54] Um, yeah. |
[2646.60 --> 2650.38] So you, you kind of have to, if you're talking about it from a chaos perspective, you kind |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.