Maintenance Working Group Meeting - 2025/02/27 08:58 EST - Transcript

Attendees

Adolfo Brandes, Awais Qureshi, Feanil Patel, Feanil Patel's Presentation, Jeremy Ristau, Kyle McCormick, Robert Raposa, Sarina Canelake

Transcript

Sarina Canelake: Morning, Robert.

Robert Raposa: Who's this with us? The cat's name. You can't hear me, can you?

Sarina Canelake: They can kind of hear you, but there's a ton of background noise.

Awais Qureshi: All right, everyone.

Kyle McCormick: I wait.

Sarina Canelake: Kyle, do you see that there are two kittens in this?

Adolfo Brandes: will be present.

Robert Raposa: So first question is the background noise equally as bad now or…

Kyle McCormick: No, I do not. Sorry, Robert. Go ahead.

Sarina Canelake: No, it's much better.

Robert Raposa: Google so that's Google Meet in Firefox versus Google Meet in Chrome. Yes.

Sarina Canelake: H annoying.

Sarina Canelake: inappropriate. Business

Feanil Patel: Morning everybody. Okay. Do people have any particular agenda items for today?

Sarina Canelake: I was just going to ask you to change the ownership of this so that we can get the Zapier integration set up,…

00:05:00

Feanil Patel: Yeah, right now I've just been manually moving them, but they've all been public,…

Sarina Canelake: right? But I like the notification in the chat room of…

Feanil Patel: but I can Yeah.

Sarina Canelake: where to find the or

Feanil Patel: Yeah, it sounds good.

Feanil Patel: Any other?

Sarina Canelake: I was also wondering there's an audit of what repos don't have cataloginfo.yaml and I was trying to figure out as I'm doing a bunch of read the docs URL changes like the number of the repos I'm encountering don't have catalog info and…

Feanil Patel: Okay. Yeah.

Sarina Canelake: it's unclear to me is this unmaintained or is there a maintainer that just hasn't set up their catalog info. So, …

Feanil Patel: So, all of that info is in the priority spreadsheet.

Sarina Canelake: for I know that. But it would be easier as I'm making the pull request to not have to refer to that spreadsheet.

Feanil Patel: If there isn't a catalog info file, there's no maintainer.

Sarina Canelake: That's not entirely true. edex toggles is maintained, but doesn't have a catalog info.

Feanil Patel: No, then it's not actually maintained,…

Feanil Patel: the official if the catalog info is not there, then it is not officially maintained. So, Reggie needs to update that or relinquish maintainership.

Sarina Canelake: Okay. Yeah,…

Sarina Canelake: that's might be why Andreas nominated himself to maintain it because it looked unm Yeah,…

Feanil Patel: 

Feanil Patel: Yeah. Yeah. Yeah. Yeah, I think it's just that there's a bit of follow-up required to make sure all the maintainers are doing all the things and that one might have just gotten missed,…

Sarina Canelake: I sent him the links. I've just kind of been going through who's merging the update PRs and assuming that they're the de facto maintainer. So,

Feanil Patel: Yeah. suspect it's just that it was in progress and we're sort of waiting. Yeah, in the spreadsheet it is in progress. but if Reis thinks he maintains that he needs to update the catalog info,…

Sarina Canelake: Yeah, I sent him the maintain column and…

Feanil Patel: I'll ping him.

Sarina Canelake: then the specific how to upload it. I sent the files.

Feanil Patel: Okay,  All right, this is what I'm looking for. Okay, let me share my screen.  Okay, I think a lot of this has been in progress. So, I know Jeremy, you and Kyle have been talking about the videos page and sort of what the current state of that is.

Feanil Patel: So, how is that going to be generally part of your studio front end ticket or does it still need to be tracked here as a conversation?

Jeremy Ristau: The legacy studio front end part of it is done except I don't even really know if we should remove the old version. should we just remove it because nobody else uses it or I'm not totally sure…

Kyle McCormick: Is there an old version of this page?

Jeremy Ristau: what yes.

Feanil Patel: Mhm.

Kyle McCormick: Got it.

Jeremy Ristau: Yeah, it has the drag and drop section at the top and lists videos. So there definitely is an old version of this page. since it is not on by default, it's still needs to go through the deer process because it is available, right? Yeah.

Kyle McCormick: I believe it's listed as one of the many st legacy studio pages to remove. So yeah,…

Jeremy Ristau: When we wrote it, we didn't know that it wasn't on by default, so it's definitely in there. and…

Kyle McCormick: cool. So it

Jeremy Ristau: You mentioned we just leave it in there until a new way of handling additional pages that are plug-in style comes about. so I don't is there anything else to kind of do for this to the task? I guess not.

00:10:00

Feanil Patel: No, I think for this particular task it was that we didn't have enough information. I think we've sort of collected all that information now. So, I think it's good.

Kyle McCormick: So to summarize, the legacy page will go away with the other legacy studio front ends. The new page will go away at least a couple months after there is a way to plug custom pages into front end app authoring.

Feanil Patel: Yeah, I think that sounds right.

Jeremy Ristau: Yeah. or…

Feanil Patel: So, Right.

Jeremy Ristau: the new page stays, but portions that are dependent on the video pipeline become plugins. Yeah. Not the entire page.

Kyle McCormick: That too.

Feanil Patel: Right. Because…

Feanil Patel: if it can be used for uploading videos and people want to do that without using all the VM and Val stuff, that's still available to them. But that'll probably require some sort of product review.

Jeremy Ristau: And we are working to isolate the transcript management outside of the rest of the info for videos.

Jeremy Ristau: So if transcript information is something we want to keep but upload things are not then we could start to tease them out from a UI perspective so they're easier to plug in.

Feanil Patel: All right.

Jeremy Ristau: We can continue to augment the page and its layout to make it easier to have a default version that's available for everybody.

Kyle McCormick: Yeah, my sense is that there is a desire for that transcript management,…

Kyle McCormick: but I'm not close enough to it to know better. yeah, Jenna might know more about that than

Jeremy Ristau: And I think…

Jeremy Ristau: and when we do that, we would just need to know sort of so the issue we run into on our side is that we use the video pipeline for the videos page. We don't use other upload mechanisms. So we might not know all of the info or…

Jeremy Ristau: capabilities that are available. we would just, need someone with that kind of general operator and instance knowledge to help us out to know what to tease out.

Feanil Patel: Right. And Serena,…

Feanil Patel: is there I know you've been sort of working with the educator docs a bunch recently. So is know if there's a good summary of all the video capabilities in those docs that would be a useful source that's up to date

Sarina Canelake: video uploads or how to use the video player or what do you

Feanil Patel: how to manage videos as an author. So video uploads what the experience looks like using YouTube by default and things like that. if it captures that feature.

Sarina Canelake: I'm taking a look right now. I mean,…

Sarina Canelake: I'm sure there's something about using videos, but I'm not sure exact. Yeah.

Feanil Patel: Yeah, that

Jeremy Ristau: or even like the metadata associated with videos like the length and…

Jeremy Ristau: location and things like that. Are those things that have data readily available that we can get from a different place other than the video pipeline stuff like that?

Feanil Patel: Yeah, that's probably not in the docs that Ser is looking at, but yeah, it's also good questions in that space.

Feanil Patel: I'm sure it's in the product spec that didn't get written.

Sarina Canelake: Yeah. …

Sarina Canelake: we're reorganizing docs, but we're not necessarily Here, I'll link this is sort of the overview doc that I found. And there's some related links at the bottom about videos. I think that's all we've got. So, I think maybe that en additional video options is kind of like maybe what you're talking about.

Jeremy Ristau: I'll check this out.

Jeremy Ristau: The add a video might be helpful, too. I'll check it out.

Sarina Canelake: Yeah, I think that the partner course staff docs might have something about the video pipeline.

Sarina Canelake: We didn't migrate, we're obviously not migrating those because those are edex specific. but I don't know when edex sort of got rid of its docs team if that pipeline wasn't available. There might not be comprehensive docs on it.

00:15:00

Feanil Patel: All right.

Jeremy Ristau: Yeah, for this todo I think it's done.  Thank

Feanil Patel: Yeah, I mean that's a starting point and hopefully we can get more information from the product side. Yeah, I think so too.  Yeah, I have marked it as done. I have not ticketed up the front end base transition for platform road map, but I'm planning on doing a bunch of ticket writing stuff later this week, today and tomorrow. Jeremy, Do you have any new information on the name affirmation repo and

Jeremy Ristau: Nothing other than that is comfortable making it public.

Feanil Patel: All right. in that case,…

Jeremy Ristau: Yeah. and…

Feanil Patel: maybe the ball's back in my court to sort of review and make sure that that's something that might be I think today now that would be a product question of do they want it?

Jeremy Ristau: then the technical steps is it just an axim engineering ticket or something?

Feanil Patel: Is there Yeah. Yeah. at that point it's just an excellent engineering ticket.

Jeremy Ristau: Yep.

Feanil Patel: I think you or Simon saying that you wish to transfer it and then the mechanics of that I think that today that would be the …

Jeremy Ristau: And are you implying with your product statement that there would need to be a product proposal written to have this added and everything?

Feanil Patel: I think so. I'm looking at others for sort of either confirmation or disagreement read of that's how we add features to the platform today and…

Jeremy Ristau: I can certainly find out.

Feanil Patel: if we're moving this into the open edex and sort of promising to find a maintainer for it that feels like the correct pathway to go through. Yeah, that's fair.

Kyle McCormick: Is this something that's already enabled in the OpenX platform?

Feanil Patel: Is it on by default? I think we need more information. are there internal sort of product docs that you can share about what that feature is and what it does?

Feanil Patel: All right. I put a to-do in there for checking in for next time. about that specifically. I'm going to mark this one as done for now.  And then any updates on the other dependencies brand and brace.

Jeremy Ristau: No. The braise one started a conversation between a few teams. the brand one is, I think, more about finding someone who can do the work. So, they're all in different states in progress, I guess I would say.

Feanil Patel: Next was for me to start adding some efforts to the repos that are left. I haven't started this yet, but I did do a review of the repos to sort of start looking at what a good estimate would be, but none of this data is in that spreadsheet yet. the last couple of times this has happened, I've just been walking people through what's available and what needs to happen to them. So, I'm going to start making that data more public, but they're going to be estimations. So, I'm not sure how valuable they're going to be for people until I actually just do it.

00:20:00

Feanil Patel: And then it's like Yeah.

Robert Raposa: This is an idea. I don't know if that walk through could be recorded and would be helpful to anyone or if it's different for every repo or anything, but just an idea.

Feanil Patel: Yeah. It's not yet, I think, because that it's tuned to the experience level of the people that are there and…

Robert Raposa: Okay.

Feanil Patel: what they need to know.

Robert Raposa: You Got it.

Feanil Patel: But so I think some sort of estimate would be useful for the things that are left to help people make decisions, but also people have been reaching out and we've been talking sort of directly based on what their team's capabilities are and that maybe makes a little bit more sense. So we've been sort of playing it by ear for an update on that though I think we just passed the 70% mark on repositories that are maintain files that are up to date and in them and as far as I know responsive maintainers and toggles is not one of them. It is not. So that's super exciting. I think we're moving at a really good clip.

Feanil Patel: the stuff that's left some of it is things that we want to deprecate and some of it is things that are extremely small X blocks that are useful but not super costly to maintain. So a lot of the major bigger parts of the code base do have clear maintainers which is really code lines of code probably we have a much higher percentage than by just repository account. super cool. Kyle, I believe you made a post about your Is this the Django?

Kyle McCormick: Nope. Not yet.

Feanil Patel: This is where the Django settings are.

Kyle McCormick: Is that …

Feanil Patel: Okay. Yeah.

Kyle McCormick: I thought that was a Xbox extraction.

Feanil Patel: It is for the Xlock extraction Django setting. But you merge that PR

Kyle McCormick: What? VR

Feanil Patel: that's linked here or…

Feanil Patel: that you close the issue rather. This is the issue link there and then you need to make post done.

Kyle McCormick: Right, the Django settings are in there.

Kyle McCormick: I haven't made a post saying please toggle these to false if you don't want to get the extracted blocks by default. We're not imminently going to be turning any of those on by default,…

Feanil Patel: Yeah. Yeah.

Kyle McCormick: but it is good to leave it there so that I do it soon.

Feanil Patel: Sounds good. Serena, is this offboarding information in the onboarding docs done?

Sarina Canelake: Yeah, that's Yep.

Feanil Patel: We'll mark that off and then I'll do this now that all of the new people onboarded. I'm going to make this post to get people to take a look at the things that are straggling in X platform. Kyle, this is another post about breaking changes and…

Kyle McCormick: Yeah, this was to kick off a new conversation about…

Feanil Patel: Right.

Kyle McCormick: how we handle breaking changes in general and whether every single one is a deer ticket and if it's not then How do we communicate them?

Feanil Patel: Right. How do we define them?

Kyle McCormick: If people want this to happen soon I think I need to relinquish it. I just cannot take this on a te timeline.

Feanil Patel: Okay. Mhm.

Feanil Patel: Maybe I'll mark this off for now because part of this is that there's a rewrite of the deer of the deer a web that's in progress and perhaps we can sort of post that and this conversation at the same time. Let me just mark this as I'll go update the owner of this to me because the deer oaf is in my court. and then nice.

Kyle McCormick: Mhm. Okay.

Kyle McCormick: And then the next one, the act is ready to work right now. So I will do that.

00:25:00

Feanil Patel: Okay, mark that as done. And then I've still not made these tickets for the CIR work, but I will do that soon.

Sarina Canelake: I will note phenal that…

Feanil Patel: Right. Okay.

Sarina Canelake: if your repo has not experienced a push in three months the cron jobs are cancelled. So there we could put a axom engineering to just go update all the crrons for the unused repos. Yeah.

Feanil Patel: So there so it might be No. No. I mean I think this is even So this is kind of a tricky situation where it's like if you're doing regular package updates then you wouldn't have this problem in the first place because those PRs would serve as the master test PRs. So now that we know this about…

Feanil Patel: how cron is not sufficiently independent activity

Sarina Canelake: We could put a crown for every nine 10 weeks in those repos as well that are just go to the settings and…

Sarina Canelake: affirm that you want the cron to keep running which is a dumb solution but is this I have done that exactly

Feanil Patel: Right. Right.

Feanil Patel: We have prior art for that dumb solution. All right. I'll think about that.  Then I might change the approach on this because one of the things about is if we can automate merging requirements PRs that pass all the tests instead of having a human do them which would keep master sort of regularly building and as long as the merges happened there would be activity on the repo and also it reduces people's maintenance burdens.  So, I wonder if pushing that higher strategic change is the better option.

Sarina Canelake: I think that makes sense. Are there repos that would get this build that don't experience pushes to master?

Sarina Canelake: That's just for ones that would get the updates PRs.

Feanil Patel: I think it's …

Feanil Patel: if there are any repositories that are not doing regular sort of make upgrades they should and if you're doing a regular make upgrade there between the certify package and a couple of other packages that update common the time zone package most repositories have updates pretty regularly or pip and…

Feanil Patel: setup tools themselves have updates regularly. So they're likely to have an update. There's a caveat here because in order for the automerge to work correctly, you have to have required checks turned on in a sane way. so we have to go make sure required there's a little bit more of sanitizing and…

Sarina Canelake: Right, right,…

Sarina Canelake: right. Gotcha. Okay.

Feanil Patel: sort of a better approach for required checks where we don't have to constantly be updating checks in a repo by having what we do in platform where we have one or two that collect the success of a lot of other ones. so there's a little bit of technical fix figuring out that needs to happen for that. So this seemed like an easier option but now I'm not so sure.  It's like approaching complexity where it might be worth it just to do the correct thing with requirements updates auto.

Kyle McCormick: At risk of rabbit holeing on a specific thing you mentioned, is the reason we have to keep fiddling with what checks are required because the check name changes when we upgrade Python.

Feanil Patel: the checkman changes based on the matrix like all the items.

Kyle McCormick: Got it. Okay. Yeah.

Feanil Patel: And I think I haven't seen any solutions to that other than having a sumitive check that that ensures that all the other checks passed before it passed and…

Kyle McCormick: Yeah. I guess we could put new and…

Feanil Patel: having that be required. yeah.

Kyle McCormick: old in the matrix instead of 312 and 311 and then have logic in the test that but now we're just fixing weird things with weird things.

Feanil Patel: Yeah. So people have thought about this and there's definitely some prior art around combining doing a summary of tests so that they can do a requirement across a matrix and have the matrix change. but I haven't had time to sort of test or go deep into that.

Feanil Patel: If other people are interested in that, please let me know and I'm happy to provide my context and somebody could do the research. But right now with the crown stuff getting more complicated, I wonder if that's just the better option. Jeremy, you asked a question in chat about sort of like ensuring phase one maintain actions were done. I think in general I do follow up on all of the ones where I know there's been a nomination. This edex toggles regious one I just missed and was not in the list of things to follow up on.

00:30:00

Feanil Patel: and it sounds like Serena's already followed up, but I'm going to make sure that that's on my list of things that at the top there is in progress and I actually do check in on on a pretty regular basis to figure out if there's a nomination that needs to happen or if it's waiting on them to put the catalog file in or all of that.  But this is the thing I'm doing is I think very initial and I think there's a sort of longer tail question of how do we ensure that the requirements updates are actually merging we don't have that as a piece of data that we're tracking right now and I think we're going to need to invest in some of that validation of health metrics as maintainers.

Feanil Patel: …

Feanil Patel: I think we're sort of now starting to approach, we've crested over the finding maintainers and I think now we're trying we're approaching it's time to figure out how to sort of make sure maintenance is happening.

Jeremy Ristau: And I guess my higher level question is this a maintenance working group or…

Jeremy Ristau: is it a maintainership working group? And when you say we are doing things,…

Jeremy Ristau: do we Axom or do you mean this working group? and we All right. So the accountability for maintainership lives inside of this working group's remmit.

Feanil Patel: Yeah, my expectation would be this working group.

Feanil Patel: Yeah, that's my expectations. and ation path for if we need help. But I think we have sort of enough permission and sort of responsibility here that we can sort of start making the

Feanil Patel: if we're seeing people not actually maintaining things like we have sufficient sort of authority to start asking questions.

Jeremy Ristau: Sounds good.

Jeremy Ristau: It was more of a where does the ownership lie kind of question helps. Thanks.

Robert Raposa: I haven't really gotten into or used repo health, but …

Robert Raposa: I think that's basically the intent of it is to define things. and then we never got to a place of what's actually important in there but it sounds like we have the beginning of that possibility proposed.

Feanil Patel: Yeah. Yeah.

Feanil Patel: And I know and I have a do to chat and get a review of the current state of repo health. if others are interested for those don't know who are watching reporting repo health is a set of tools that collects repository metrics across all of the repositories in the organization. and it essentially does this by running little tests on the repository to determine various sort of attributes about it. I think it's extremely flexible and we could totally use it to do things like have

Feanil Patel: get a list of the last requirements update that merged on any given repo and then see which ones are sort of like the age of different PRs on a repo and things like that and start using it to track some of the metrics we would determine are important for maintenance health but I think we need to determine what those metrics are because right now repo health has a ton of information it is indirectly relevant but not directly. I think getting some sort of summarization and some sort of simplification of data that we care about is going to be important.

00:35:00

Feanil Patel: I'm gonna Yeah.

Robert Raposa: Are there edex platform topics?

Robert Raposa: I was just noting that it's 9:35. Okay.

Feanil Patel: 

Feanil Patel: Yeah. Yeah. Yeah. Yeah. I was just going to say I think I'm going to put a next time topic for metrics of maintenance health and maybe next week let's try to talk if you guys can think about sort of what are the things you would want to know about a repo to know that it's like being maintained or is wellmaintained. and that could be a starting point for a topic of do we have this information? How do we collect this information? How often do we want to look at this information?

Feanil Patel: I think there's some defined in there…

Jeremy Ristau: I think those are probably defined in the maintainer responsibilities sheet wik  Thank you, man.

Feanil Patel: but a lot of it is more abstract and if we want to sort of track concrete health we need to sort of do that translation you are making sure that the repository is up to date. What does that actually mean? I think the translation is that means you're actually merging and releasing it regularly for things that are libraries or that you're merging requirements pers for things that are services and doing that translation of the ideological stuff…

Feanil Patel: which is in the OAP and to the concrete stuff that people would do day as a proxy at least of …

Feanil Patel: because I think some things are going to be hard you are doing a good job with the documentation it's like we Yeah.

Kyle McCormick: We could have an LLM tell us that,…

Kyle McCormick: I'm only half ironic right now.  We might be able to do that.

Jeremy Ristau: just have write it for you.

Feanil Patel: Yeah. Yeah. Yeah. we can certainly have an element if it thinks it has an opinion, but I don't know if it's a good opinion or a bad opinion.

Jeremy Ristau: I mean there's at least minimums right there's a readme there the dependabot is enabled right …

Feanil Patel: Yeah. Yeah. Yeah. Exactly. Yeah. Right.

Jeremy Ristau: how old are requirements PRs when was the last time touched stuff like that exactly…

Feanil Patel: And issues, when was the last time an issue was responded to? …

Jeremy Ristau: how stale are

Feanil Patel: how many…

Jeremy Ristau: Good start at least.

Feanil Patel: how stale are the issues? Yeah. Exactly. So these are specific metrics that will sort of are indicative cumulatively the health of the repo necessarily because there are reasons why they could be off. Yeah. Exactly. yeah, are there edex platform topics people want to talk about?

Kyle McCormick: I'll give an inform on the status of the setting simplification. which I'll link in the chat, now that this is merged, Fineil and I have one more PR to merge in the short term to remove redundancies from CMS settings. We've done this before for LMS settings. So this is the same thing on the CMS Other than that, we will keep the parent issue up to date, but Fine and I are both pretty busy with other projects and this is on our back burners. So, you might see long periods of time between PRs, but they will be following the plan in the ADR and…

Kyle McCormick: we'll keep the issue up to date as we slowly move through it. And we're also accepting any volunteers who are interested in helping with the setting simplification since it's pretty well speced out at this point. So, just let us know…

Feanil Patel: Yeah. And…

Kyle McCormick: if that's something you have concerns about or…

Feanil Patel: then yeah and…

Kyle McCormick: interested in helping

Feanil Patel: the next phase of it I think is very approachable and it's much lower risk set of changes. it's updates to common based on all of the things that we've learned in the ies where production.py in fact was just overriding the defaults in So the defaults in common are just false or incorrect. so we want to be able to push those defaults up into common so that if you look at common you in fact do look at the default values of settings that are in our system.

Robert Raposa: I'm wondering too…

Robert Raposa: if it's the next phase is it a per setting thing where people could literally clean up a little bit at a time or it's a big thing that has to happen all at once.

Feanil Patel: I mean,…

Feanil Patel: you could do that. The amount of energy you will spend doing that versus doing all 30 or 50 settings is not going to be that much different. I would just do the whole thing.

Robert Raposa: Got it. And I just more meant …

Robert Raposa: hey, if someone's working with a setting and they fix that one thing and …

Feanil Patel: Yeah,…

Feanil Patel: yeah, yeah.

Robert Raposa: is that a useful activity or not?

Feanil Patel: Yeah, yeah. I mean it certainly can be but I think doing the whole thing the hard part as Kyle and I have discovered is not the action of getting the settings moved…

00:40:00

Robert Raposa: Got it.

Feanil Patel: but the validation and evaluation steps that come afterwards because the settings files are one of these things that are fairly difficult to test with unit tests right now until we make all of these changes.  Nice. Yeah. but if people have other questions on this, definitely please reach out to us. If you want to help but don't know where to get started, please reach out.

Feanil Patel: Hopefully we're starting to get to the point where it's a lot easier to reason about what the values of things are before YAML touches them at least. and easier to evaluate sort of defaults and things across various platforms. Anybody have anything else? Yeah. Okay,…

Jeremy Ristau: I got a late update. It's not really about edex platform, but begs just got back to me and was like, "This might be hard.

Feanil Patel: that sounds good. if he wants to what I would suggest I think this is maybe useful as a deer and then he can change the dates on the deer and use it as a way of communica moving forward. Is that useful or is that just extra paperwork?

Jeremy Ristau: I'm guessing you're asking everyone but me…

Jeremy Ristau: because we have an internal ticket to do this now. So I don't Okay.

Feanil Patel: If you have an internal ticket,…

Feanil Patel: it's fine.

Jeremy Ristau: Yeah. Yeah.

Feanil Patel: I'll put a reminder for following up on it.

Jeremy Ristau: I think if I said, "Hey, Brian, would you also make a depper?"

Jeremy Ristau: he would go, "That sounds like extra paperwork, but it's not for him,…

Feanil Patel: Yeah. Yeah.

Jeremy Ristau: " So,…

Feanil Patel: Yeah. Yeah. I think the sort of correlary to that question is anybody else using the brace client in the platform today?

Jeremy Ristau: yeah. Right.

Feanil Patel: And that is what the deer would discover.

Sarina Canelake: Yeah, I mean to an extent if you already have an internal ticket, you could just copy the text of the internal ticket and put it in a deer. it feels a little like extra paperwork. It also feels like a way of communicating. And when we're starting to draw up the release notes, we do pull from the deer tickets and we do pull from the product tickets as well to kind of communicate in the release notes what's changed.

Sarina Canelake: But we also look at the pull requests and the breaking changes commits. So, I'm kind of like wishy-washy, I think, on the whole issue.

Feanil Patel: Yeah. Yeah.

Feanil Patel: Yeah. Almost actually, more than the deapper, just an announcement that we're going to make this is fine because I'm realizing the repo is public. If other people want to install it when it is not installed by default, they simply can, which is like the state they're in right now, except that they are forced to install it because it's in the default install. So, never mind.

Feanil Patel: I don't think we need that big word,…

Kyle McCormick: And if we and…

Kyle McCormick: if we pull the breaking change commits in to the release notes,…

Feanil Patel: right? Yeah,…

Kyle McCormick: then this will make it to the release notes.

Feanil Patel: I think that should be fine.

Sarina Canelake: Yeah, I think that should be fine as

Feanil Patel: More paperwork.

Jeremy Ristau: I mean this will become a private dependency though.

Feanil Patel: Is the repo going to become private?

Jeremy Ristau: Yeah I don't think that for braise we would be moving it to open edex. Yeah.

Feanil Patel: No. moving into the open edex or versus leaving the repo private in the edex or even if you make it private in the future the version that is currently public will remain public. So if other people are I was still using that they can still use the version of the code that they have been able to use up until now. it just will, stop getting updates from edex, which is a precarious dependency to have in your business anyway.

Kyle McCormick: Fine, if they make the repo private right now on the edex side,…

Feanil Patel: Yeah. Is that true?

Kyle McCormick: then it won't be available to people unless they use the internet archive. Should we clone this to open edex unsupported?

00:45:00

Feanil Patel: Is that true or is it I thought when public repos went private the public repos were still available on GitHub that might be…

Kyle McCormick: Didn't think so, but …

Feanil Patel: because I thought there was a mechanism there but maybe they've removed that and…

Feanil Patel: I'm thinking of an old mechanism that was there.

Jeremy Ristau: can co-pilot.

Kyle McCormick: test this.

Feanil Patel: Yeah. We can just test it. Yeah. Yeah.

Kyle McCormick: If it does go fully private, one thing we can do is just clone this to open unsupported so that people can always use it if they need it.

Feanil Patel: I'd love to do that as a before it goes fully private if we know when that's going to be.

Jeremy Ristau: Great things to support having a deer ticket so we can have this conversation inside of the ticket. Yeah.

Feanil Patel: Yeah. Yeah. Yeah. Yeah.  All also Thanks, Scott. So, we'll at least have a snapshot of right now. Mhm.

Kyle McCormick: And we can sync that up until the point where it goes private.

Feanil Patel: Anything else? Okay. All right. thank you everybody. and we'll talk to you next time. and if you'll see you in the working group Slack. Hey

Robert Raposa: Thanks everyone.

Jeremy Ristau: Awesome. Thanks. See you.

Sarina Canelake: Hey

Meeting ended after 00:47:05 👋

This editable transcript was computer generated and might contain errors. People can also change the text after it was created.