Tracy Kuhrt: Welcome everybody to the December, the eighth Hyper Ledger Technical Oversight Committee call.
Tracy Kuhrt: as everyone who's on this call is aware of 2 things that we must abide by. The first is the antitrust policy. Notice that it is currently displayed on the screen.
Tracy Kuhrt: and the second is our code of conduct which is link in the agenda.
Tracy Kuhrt: All right. So for our agenda today we have the standard announcement: the Deaf Weekly Developer Newsletter goes out each Friday.
Tracy Kuhrt: if you would like to include anything in that newsletter, please leave a comment for consideration at the link that is, in the agenda
Tracy Kuhrt: as far as meetings for the holidays. I thought we should probably cancel
Tracy Kuhrt: the 20 s, the 20 ninth, and the fifth to make sure that everybody who is on holiday I can enjoy those holidays and not have to worry about the technical oversight committee. Call
Tracy Kuhrt: I'm not sure whether we'll have content for next week, and we'll decide that next week as to whether or not we have one next week. But I definitely for the the holidays. I'd like to make sure that we cancel those meetings
Tracy Kuhrt: any other announcements that anybody on the call has
Tracy Kuhrt: a root.
Arun S M: This so this is regarding Hyper ledger, blockchain, Explorer Project, which was recently deprecated or end of life cycle, I guess.
Arun S M: And there has been interest in multiple
Arun S M: among multiple community members. So it is going to be
Arun S M: like people are looking into adding certain features to that project, and seeing
Arun S M: and further improving the project and bringing it back to life. So there is going to be a
Arun S M: discussion tomorrow.
Arun S M: Hey? Damn
Arun S M: Eastern time!
Tracy Kuhrt: And the calendar link is where, exactly for people who might be interested in joining that
Arun S M: right. I need to work with David and getting it up on the calendar link.
Tracy Kuhrt: Okay.
Tracy Kuhrt: Okay? And then yeah,
Tracy Kuhrt: I think if I understand correctly that the the code base has been moved to the Labs area. So it's currently a a lab in that project.
Tracy Kuhrt: and if that would like to come back to be a top level project at some point in the future it will have to go through the
Tracy Kuhrt: project. Proposal process.
Arun S M: Agree.
Yup.
Arun S M: Okay. So if you know of anybody else who is interested in the project. Please bring them to the call tomorrow.
Yeah.
Tracy Kuhrt: alright, thanks.
Tracy Kuhrt: Any other announcements that anybody would like to make.
Tracy Kuhrt: I don't see any hands.
Tracy Kuhrt: Nobody coming off mute, so i'll take that, as they know, as far as quarterly reports. We did have the cello report come in
Tracy Kuhrt: this week.
Tracy Kuhrt: I did not see
Tracy Kuhrt: any comments on that. I'm just opening it now, just to make sure that nothing new has come in overnight that I may have this.
Tracy Kuhrt: no, it looks like the only comment here is from from David Boswell. about
Tracy Kuhrt: social media post and marketing for the one release that's coming out. Looks like we still do have a number of Toc members that have yet to review the document. So we'll you know, book to see if there's anything that comes out there. Any questions, though, that anybody does have from that particular
Tracy Kuhrt: project, report the cello project report.
Jim Zhang: Hey, Tracy? I I did have a question on the documentation
Jim Zhang: and the like. There of was the same comments from their last report. I still didn't see much update in that in that area. So I just putting another comment in there.
Tracy Kuhrt: Okay, and it's that there needs to be more documentation for the cello project. Do you think, before the the one that releases what you're asking for?
Jim Zhang: Yeah, yeah, what what thing there is completely lacking. If i'm a newcomer trying to pick up travel, I just can't figure out anything.
Tracy Kuhrt: Okay.
Tracy Kuhrt: probably. Have you in the learning materials working group. Has anybody been working with the cello folks on
Tracy Kuhrt: any sort of documentation or anything there? Has that come up or not?
Bobbi Muscara: no, it hasn't but David and I had a meeting this week about how we're going to change learning materials, working group to help support that more with a task force, and one of them will be that documentation task force.
Tracy Kuhrt: Okay.
Tracy Kuhrt: alright thanks, Bobby
Bobbi Muscara: didn't need to put you on the spot there, but I I know you had helped some other projects in the past. I didn't know this one was one that had come up or not. No, but that documentation working group was going to support all those efforts to make it simple and work together with us to help them attain the documentation they need to get newcomers on boarding easily.
Tracy Kuhrt: Okay.
Tracy Kuhrt: and Jim when we get there. This might be a
Tracy Kuhrt: a best practice that we want to add to the checklist.
Tracy Kuhrt: As we are thinking about documentation.
Jim Zhang: Yeah, it it was kind of my my my subtle way to say
Jim Zhang: they need to really drastically improve documentation to declare one.
Tracy Kuhrt: Yeah.
Tracy Kuhrt: okay, okay.
Bobbi Muscara: I'll reach out folks this week and set something up to get started.
Jim Zhang: Yeah, I appreciate it, Bobby.
Tracy Kuhrt: That's great. Thanks. Probably
Tracy Kuhrt: all right any other comments about cello At this point
Tracy Kuhrt: alright, I will note that the Firefly also did come in early this week. So I did include the link there on the agenda. We'll definitely include it next time
Tracy Kuhrt: as well. But just a yi! That one did come in
Tracy Kuhrt: if you Haven't had a chance to look at it yet. Please do so.
Tracy Kuhrt: And I guess I can ask the question because it does look like a a good number of people have already taken a look at that. Are there any comments or questions about the Firefly report at this point
Tracy Kuhrt: alright, resounding now.
Tracy Kuhrt: So so last week we had talked about a couple of things one we had talked about the different task forces and closing those out
Tracy Kuhrt: and one of the items that came up when we were talking about the project Help
Tracy Kuhrt: task force was
Tracy Kuhrt: potentially creating a checklist where we would move some of the
Tracy Kuhrt: questions that we have in the project reports to some sort of spreadsheet and maybe try to include some of the project. Health
Tracy Kuhrt: type things into this particular
Tracy Kuhrt: sort of
Tracy Kuhrt: checklist of Yes, no. Do we have these things that are included?
Tracy Kuhrt: I I started this with the list of the things that we have done in the past.
Tracy Kuhrt: in the past year, right? We've created the common repository structure we've created the maintain our guidelines, and we've approved the inclusive naming proposal. And so I basically included all of the items from the there, Whether or not they were, must or should.
Tracy Kuhrt: They are included here. for most of these I
Tracy Kuhrt: specified whether they were required or recommend it. but not all of them. maybe I need to go back and do that for the ones I missed.
Tracy Kuhrt: there. But, you know these these items. None of them should surprise us, as we have approved these things in the past.
Tracy Kuhrt: but I did want to have a discussion and see if there were other things that we should be adding to this list.
Tracy Kuhrt: i'm happy to, you know. Take those notes and and start to add them here. directly in the document.
Tracy Kuhrt: Any thoughts, things that we should add to this list.
David Enyeart: I don't have things to add, but i'll just say I like it.
David Enyeart: and a all in one location is very convenient, and I wish this had existed previously. So.
David Enyeart: it looks like it's pretty inclusive of the things we already have. I can't think of anything new, but I think this would be a good thing going forward, and we'll add to it
David Enyeart: as we think of things.
Tracy Kuhrt: Yeah. And and Dave and others, the what I was thinking here is that we would probably create a separate tab for each of the projects. that would be a copy of this template
Tracy Kuhrt: right, and as we as when we add things to the template, we would also add them to the individual project
Tracy Kuhrt: Tabs, so that again one place to go to to see.
Tracy Kuhrt: you know. do our projects support the best practices? If so, where can you find that? so that it's it's also somewhat of a
Tracy Kuhrt: appendix or an index, I guess, is the right way to say that right? That that basically allows people to quickly find the information, so that if they're interested in, say, becoming a maintainer of one of the projects they can go find out. What? How, what does that take? And how do I, how do I become a maintainer? What are the steps I have to go through?
Tracy Kuhrt: so yeah, I think that's kind of the idea here.
Tracy Kuhrt: Peter.
Peter Somogyvari: quick suggestion that i'm ever made a change to. This will be okay if
Peter Somogyvari: I move
Peter Somogyvari: It's the the
Peter Somogyvari: information into its own column. So let's feel tripled by it.
Tracy Kuhrt: sure. Yeah, we can definitely do that.
Okay?
Peter Somogyvari: And then once I do that, i'll have a few ideas for optional stuff, but nothing to add on the required
Peter Somogyvari: from
Tracy Kuhrt: Okay.
Kamlesh Nagware: So I think maybe information about the Lts releases
Kamlesh Nagware: It' be added.
Kamlesh Nagware: And the other thing I even
Kamlesh Nagware: couple of open source project I have seen so
about the
Kamlesh Nagware: Okay. Now.
Kamlesh Nagware: the project implementation, like it was the real time on the production implementation of the particular open source project.
Tracy Kuhrt: So
Tracy Kuhrt: do you have a list of
Kamlesh Nagware: Yeah. Yeah. So so like, for example, if you see any for them, I suppose if you go to any open source projects
Kamlesh Nagware: they mentioned about like who are using
Kamlesh Nagware: this particular project
Kamlesh Nagware: Wouldn't: be.
Tracy Kuhrt: Yeah.
Tracy Kuhrt: Okay, sean. If you scroll down, I am editing, as we speak. So yeah, at the bottom, I added this question: do you have a list of production? Uses
Tracy Kuhrt: to the the document.
Tracy Kuhrt: the camel
Tracy Kuhrt: I also added, your Lts release piece as well on line 25.
Tracy Kuhrt: All right, are you?
Arnaud J Le Hors ("Arno"): Yes, hi! I mean I see what's been said before. This would be great to have, for sure it feels like
Arnaud J Le Hors ("Arno"): I wish you could populate some of this automatically. But,
Arnaud J Le Hors ("Arno"): my question really is, how do you deal with the fact that many projects, if not all.
Arnaud J Le Hors ("Arno"): have multiple repositories?
Arnaud J Le Hors ("Arno"): Are we going to just focus on the main one or
Tracy Kuhrt: good question, Arnold. I have that same question in my head, and I don't know a good answer to that. I really appreciate thoughts here. Right?
Tracy Kuhrt: I I mean in my mind, there's
Tracy Kuhrt: 2 ways that come to my mind of how we can deal with this
Tracy Kuhrt: one is that we have a separate tab for each repo. I think this is going to make this a very long spreadsheet.
Tracy Kuhrt: and that that may be too overwhelming for people.
Tracy Kuhrt: maybe I have a third way. We could create a separate one for each project, and then have repo
Tracy Kuhrt: specific questions and project-specific questions. Right?
Tracy Kuhrt: we could the the third option, which was my original second option was, we do it for project.
Tracy Kuhrt: and in the location column we have multiple locations, one for each repo.
Tracy Kuhrt: so yeah, I think those are the 3 that come to mind. But i'm like
Tracy Kuhrt: would love to hear your thoughts on what you think is best. And if there's a fourth or fifth option that might be better.
Yeah, I mean, I
Arnaud J Le Hors ("Arno"): So I don't claim to have the right answer. Either. That's why I bought it that it it crossed my mind, I think you know, practically speaking.
Arnaud J Le Hors ("Arno"): at least as a first step focusing on the main repository.
Arnaud J Le Hors ("Arno"): It seems like you are reasonable
Arnaud J Le Hors ("Arno"): thing to do.
Arnaud J Le Hors ("Arno"): I think otherwise. It's getting very quickly overwhelmed.
Arnaud J Le Hors ("Arno"): I think it's better to
Arnaud J Le Hors ("Arno"): less information that that we can keep, you know, accurate. Keep it up to date. Then trying to encompass everything, and then
Arnaud J Le Hors ("Arno"): you know it's going to become obsolete before you know. And then it. This is the whole
Arnaud J Le Hors ("Arno"): purpose.
Arnaud J Le Hors ("Arno"): noting how people use these. So they're aware.
Arnaud J Le Hors ("Arno"): And maybe
Arnaud J Le Hors ("Arno"): maybe there's something that needs to be done at the project. They've also that
Arnaud J Le Hors ("Arno"): you know.
Arnaud J Le Hors ("Arno"): I see
Arnaud J Le Hors ("Arno"): I i'm taking the outlook, so I will join.
Arnaud J Le Hors ("Arno"): But
Arnaud J Le Hors ("Arno"): you know, I wonder if it's up to the project to point to the the repo, and that provide additional information
Arnaud J Le Hors ("Arno"): to some degree. You can see this out by just the name. Usually you can find that out.
Arnaud J Le Hors ("Arno"): Maybe more can be done.
Arnaud J Le Hors ("Arno"): There you go
Arnaud J Le Hors ("Arno"): of the project tomorrow.
Tracy Kuhrt: Yeah. And and
Tracy Kuhrt: I don't know, because you've said that I guess a fourth option that has just now come to mind is.
Tracy Kuhrt: what if we required this in the reading
Tracy Kuhrt: for each of the repost.
Tracy Kuhrt: or it
Tracy Kuhrt: pointer to this from the remaining
we're basically
Tracy Kuhrt: The information existed as an index to the project, so that people knew where to find things within that particular repo.
Tracy Kuhrt: okay, a room.
Arun S M: hey? Thanks, Tracy. So I was looking through this list, and thanks for aggregating in one place. I am. I like it to be in one place now that I say this least.
Arun S M: So thinking of some of the bigger projects are some of the projects that have wider scope
Arun S M: it, it could be as simple as, for instance, let's say, for example, for instance.
Arun S M: a a repository that may get contributions from multiple
Arun S M: folks
Arun S M: in each interested in some aspect of it some few folks interested in
Arun S M: on the let's say, bringing up of a Testament.
Arun S M: whereas few of them could be interested in writing samples on the chain code different languages
Arun S M: having.
Arun S M: I know, like private team is doing good job, but
Arun S M: maybe we can recommend
Arun S M: another file called something like owners
Arun S M: which the chromium, like defined earlier.
Arun S M: which allows us to define older level ownership right?
Arun S M: We can say that there can be reviewers and reviewers can who specializes on that particular field, or that either it could be that part of
Arun S M: I mean that folder of a project, or in that part of a project.
Arun S M: and then approval is only when they approve. It goes into
Arun S M: the main base.
Tracy Kuhrt: Yup.
Tracy Kuhrt: and that would be an Owner's file would be recommended, I think right?
Arun S M: Right? It's not a mandate. it it. Yeah, I command it.
Yeah.
Tracy Kuhrt: Okay.
Kamlesh Nagware: So I think like, i'm not just point right there. There are multiple projections of projects. Maybe we can also have we having a list of some projects.
Kamlesh Nagware: so it will easily be identifiable to the people like with project related to which
Kamlesh Nagware: particular repose.
Kamlesh Nagware: So, for example, I'm. Supposed to the fabric having a multiple of it, could be included in the
Kamlesh Nagware: A in the
Tracy Kuhrt: Okay.
Nathan George: on this sheet it seems like it's important for us to to to call out, but most of these are required on a per repo basis. Even if you try to save energy, you still have to have something there for either a legal compliance, reason, or because, if it's not there You're probably not doing. The activity in indicates like doing the testing or
Nathan George: implementing the conventions. And so you know, one of the hopes is that as we get our lymph linting tool
Nathan George: kept up to speed, is it? It's very easy for us to to run this against the repositories and get a picture overall of where the project is at
Nathan George: because they there there is going to be a constant struggle to keep some of these things up to date. And one of the things that's important when project decides to make lots of sub repositories is that they understand upfront what they're signing up for. because I think one of the things that happens is often the sub project is kind of a matter of maintainer convenience.
Nathan George: or it's a matter of you know it. It's just more easier to use the pro the programming language tools. If I don't have to worry about more than one programming language in the same repo. and they don't realize all of these things. end up duplicated as a result.
Tracy Kuhrt: I agree, i'm not sure what specific change, if any we need to make to this to reflect that
Tracy Kuhrt: me, too.
Nathan George: I just wondered if in required and recommended if there's something we can call out about whether they can link or whether they have to duplicate the content
Nathan George: Couple of these we could probably just link from one to the other, and I know we've had that debate at Nauseum and the repository structure and the Maintainer guidelines. So it may be that just the content that's in that linked document is enough.
Tracy Kuhrt: Yeah. completely understood. I think.
Tracy Kuhrt: if I remember correctly, and we'd have to open it. but I think in the
let me see if I can open it here and just take a look at it.
Tracy Kuhrt: I think in the Maintainer's guidelines we have.
Tracy Kuhrt: Was it? The Maintainer's got. My, no, it was the common repository structure and the common repository structure. We do have
Tracy Kuhrt: a comment I remember about
Tracy Kuhrt: these files must contain specific comment. it's specific content. so I think the license, the code of conduct and the security
Tracy Kuhrt: are the 3 that we list as must requires a specific content.
Tracy Kuhrt: is that
Tracy Kuhrt: is that what we should be marking then is those 3 as these require specific content?
Tracy Kuhrt: and then the other files are the variable content ones.
Nathan George: Yeah, I just wonder if where we say for you. File required
Nathan George: we we could put a note in this in this list. It's just. It's really nice as a maintainer to have something like this spreadsheet where I can just go.
Nathan George: but just go through and make sure each thing is is ready to go, because it makes the pull request a lot easier to follow if I
Nathan George: can get them all through at the same time.
Tracy Kuhrt: Yeah, yeah, it is the
Tracy Kuhrt: security. I just said I'm.
Tracy Kuhrt: and my brain obviously is not awake yet. This one security, license and current contact that are the the ones that are special.
Tracy Kuhrt: Maybe maybe the reason that my brain is not able to keep those in my head is because
Tracy Kuhrt: a security and license where is the code of conduct? Here we go.
Tracy Kuhrt: so these 3 are the ones that are special, If you will.
Tracy Kuhrt: I'm. Just gonna mark them. Highlight them in some way. So
Tracy Kuhrt: we remember that we need to do something special with these.
Tracy Kuhrt: Okay, thank you, Nathan, for that.
Tracy Kuhrt: I will make sure to do that
Tracy Kuhrt: any other comments anything else we should add. Jim, I feel like what I want to add around documentation is
Tracy Kuhrt: something like. Do you have tutorials
Tracy Kuhrt: on use to reflect kind of the comment you made about the cello one? Are there other sorts of documentation that people think is extremely important to make sure that
Tracy Kuhrt: that exists for our projects.
Jim Zhang: Yeah, I'm kind of torn a little bit here. I I feel like a a active project will naturally have good documentation, because that's the only way to get the community
Jim Zhang: to be able to pick it up and use it.
Jim Zhang: if it If If your project is lacking basic documentation, it's a sign that nobody cares about it.
Jim Zhang: so that's that's kind of what's in my head. So
Jim Zhang: maybe we can say best practices is having good documentation. But really, if you don't have that, how can you be? the effective project?
Tracy Kuhrt: Yeah. So I added,
Tracy Kuhrt: okay, I obviously have no idea how these sheets.
Tracy Kuhrt: I added, do you have documentation as one right? It's very possible that some of our projects that are in incubation. Haven't gotten to the documentation yet, so that will end up being a no
Tracy Kuhrt: And then I added the second question of tutorials on use.
Tracy Kuhrt: I I want to.
Tracy Kuhrt: I want to avoid the use of the word good, because it's very subjective. What good means.
Tracy Kuhrt: and i'd like to be more specific if we could. If If there's other things that we think are necessary in the documentation
Tracy Kuhrt: that would make it good in our mind.
Tracy Kuhrt: right. what what does that really mean to us?
Tracy Kuhrt: So all right.
Arun S M: yeah, maybe i'm overlooking it. but
Arun S M: I feel like as a developer when I first time see any of the code bases i'm like, unless I know the code base.
Arun S M: I may be interested in knowing how to build it locally how to test it of my test environment.
Arun S M: So I know there is a testing code
Arun S M: point which is put as recommended.
Arun S M: I'm.
Arun S M: I'm. Just not sure if it considers the build and test
Arun S M: if that's what it meant to be.
Arun S M: It's like that in this row number 19.
Tracy Kuhrt: Yeah, no,
Tracy Kuhrt: that is truly testing code. So I added lines 31 and 32 here. do you have
Tracy Kuhrt: build instructions, probably in your documentation.
Tracy Kuhrt: and then
Tracy Kuhrt: the second one.
Tracy Kuhrt: Do you have documentation to help a contributor understand the code base?
Tracy Kuhrt: I think that's what you're asking for. Is it a room.
Arun S M: Sure maybe not the code base at least to build instructions, if possible, because there could be let's say
Arun S M: some of them. Some of the projects would be using, make, find some of them could be using
Arun S M: a rest place is once i'm
Arun S M: they could have multiple flags in there, and as a first time contributor. I may understand how the programming language works.
Arun S M: but I may not be able to comprehend the the
Arun S M: multiple options which are provided in in those files
Arun S M: unless I know about the project right? So maybe they should be an option. So if you are a development, if you are building
Arun S M: if you are contributing, and here is how you can build locally.
Arun S M: It allows you us to gain confidence that you have tested.
Arun S M: and it gives you confidence that
Arun S M: you are able to build it.
Tracy Kuhrt: Yep.
Tracy Kuhrt: Okay.
Tracy Kuhrt: Poppy.
Bobbi Muscara: So with the documentation task force our goal and hopefully will be finished by the end of the year is to get some recommendations for projects and incubation to take their Github repositories and put them through
Bobbi Muscara: these templates and have user docs. And again. I completely agree with everyone who said that the documentation is direct. Reflect on how the project is loved. So, depending on how much work went into describing steps in the Github is is
Bobbi Muscara: as good as your documentation when you say the only thing that I have a question on is when you say, you are more talking about how to tutorials.
Bobbi Muscara: I'm not sure how you could get the community all to do that in a uniform way unless you supply a template that each project has to do for that specific reason.
Tracy Kuhrt: Yeah, I I think that tutorials are going to be very dependent on
Tracy Kuhrt: the project at hand. Right? I think it's important to have those tutorials. But I don't think it's necessary to reflect what type of tutorials, if you will.
Tracy Kuhrt: Okay? Other thoughts.
Tracy Kuhrt: Alright.
Arun S M: Yeah. I know. I'm not supposed to use the check here by type.
Arun S M: I could. I just wanted to paste the link. So this is
Arun S M: some kind of documentation that I was
Arun S M: talking about.
Arun S M: Personally, this benefited me when
Arun S M: I mean long back when I started contributing to this project.
Tracy Kuhrt: Okay.
Tracy Kuhrt: Any other
Tracy Kuhrt: thoughts, anything else we should add to this
Tracy Kuhrt: Peter the
Tracy Kuhrt: the column you requested the required recommended is this kind of the idea that you had there.
Peter Somogyvari: Yeah, that works
Tracy Kuhrt: that works.
Tracy Kuhrt: You had something else in my
Peter Somogyvari: my first idea will be slightly different.
Peter Somogyvari: But
Peter Somogyvari: this is perfect. It it serves the purpose. It's a it makes the data structural
Peter Somogyvari: just the same way.
Peter Somogyvari: So it wasn't it wasn't a job
good.
Tracy Kuhrt: thanks to either.
Tracy Kuhrt: alright, so i'll clean this up a bit. I think you know some of these other things that we had that our mark jet as recorded recommended.
Tracy Kuhrt: i'll check the whatever we document it when we document it, say the maintenance guidelines or the
Tracy Kuhrt: common repository structure, and make sure that they
Tracy Kuhrt: have, whether or not it's a required or recommended
Tracy Kuhrt: some of these new things that we just added, i'm i'm guessing these are all recommended practices, since we just kind of added them. they weren't things that we thought were necessarily required.
Tracy Kuhrt: but happy to to be told that you think something should be required. If
Tracy Kuhrt: if it should be
Tracy Kuhrt: okay, so for the moment i'll make them all recommend it.
Tracy Kuhrt: And then, if for some reason, at some point in the future we decide that they should be required. We can have that discussion
Tracy Kuhrt: any other thoughts on this before we close this topic.
Peter Somogyvari: so I think it's a great idea.
Peter Somogyvari: Gary thumbs up plus one.
Arnaud J Le Hors ("Arno"): so maybe you said it before, and I it so what's the plan now? I mean, what how do you go at feeling out all this data?
Tracy Kuhrt: Yeah. So
Tracy Kuhrt: Oh, no. I thought I could maybe potentially take a first stab at this by going through for the different projects and marking whether or not they exist, and where I found them.
Tracy Kuhrt: and then anything that's left blank. Turn that over to the
Tracy Kuhrt: the projects to allow them to update it
Tracy Kuhrt: or change it, as the case may be. If if I got it wrong for some reason.
Tracy Kuhrt: Does it sound like a an appropriate next step?
Arnaud J Le Hors ("Arno"): Well, if you're willing to do the work, I don't think it is, you know, Jack, but I think it's a bit unfair. I don't know why you would have to carry the load here. We have people from different projects, even within the Tsc. Alone. I think it should be spread around, so that at least one per
Arnaud J Le Hors ("Arno"): one person for project volunteers to do it for their own project.
Arnaud J Le Hors ("Arno"): and then there may be some that for which we don't have anybody.
Arnaud J Le Hors ("Arno"): Maybe we can
David Enyeart: that would work, or we could just say for the next quarter reports. Please fill out the initial spreadsheet.
Okay.
Tracy Kuhrt: I'm happy to do either way. If somebody wants to volunteer to fill it out. Now, that's great.
Tracy Kuhrt: I'm not going to force anybody to do that. But I I do think yeah, definitely. I want in the next quarterly report.
Tracy Kuhrt: If it hasn't been filled out, or it's partially filled out for the the projects to complete that.
David Enyeart: Tracy, i'll volunteer to do it to do fabrics
David Enyeart: first here. Yeah. So we have a
David Enyeart: precedent.
Tracy Kuhrt: Alright, i'm gonna I'm gonna change that link that I have right now. It's coming, only i'm gonna change it to editor
Tracy Kuhrt: so that anybody can go ahead and edit the the document going forward.
Jim Zhang: So, Tracy, we'll have
Jim Zhang: this as ongoing or just one time
Jim Zhang: capture
Jim Zhang: it zooming. Some projects may not have all of them checked.
Jim Zhang: Do we want them to progress? So eventually they have all of them checks.
Tracy Kuhrt: I I think that would be ideal, Jim, right as we do get to a place where they are all checked.
Tracy Kuhrt: I think it
Tracy Kuhrt: the the more that people and projects. let's say, the the more that projects have checked these, I think the the more advanced they are.
Tracy Kuhrt: I think there's you know, potentially a question of
Tracy Kuhrt: and this was not something I did. But maybe we also want to look at the incubation incubation. Exit criteria and see if there's any other things here that
Tracy Kuhrt: might be good questions to include.
Tracy Kuhrt: that would also tell us where the projects are currently being incubated. Whether or not it's is getting close to to being
Tracy Kuhrt: something that they would request to go active.
Tracy Kuhrt: so yeah, I don't think this is a one time thing. I think
Tracy Kuhrt: you know. The the problem that we have is that once people fill it out, they think they're done.
Tracy Kuhrt: but things change in the projects, right? New repos are added.
Tracy Kuhrt: you know,
Tracy Kuhrt: people, you know.
Tracy Kuhrt: may may do things differently in the code, right? They They may have changed some stuff.
Tracy Kuhrt: Some of these will definitely feel like they're static. But I think there is the need for us to, you know. Look at this ever so often and make sure that things are up to date.
Jim Zhang: Yeah, that's how i'm thinking about it as well. So given that it's probably a good idea just to tie this up with the quarterly report.
Jim Zhang: either Expand this the section where we do the
Jim Zhang: the the yes and no
Jim Zhang: checklist
Jim Zhang: or link link to this
Jim Zhang: from that section.
Jim Zhang: and we can also, clarify what does require mean? what does not doing? The require. intel.
Jim Zhang: Would that just prevent me from graduating, or there's other other consequences?
Tracy Kuhrt: I yeah, I think.
Tracy Kuhrt: So. 2 things, Jim. One on the project reports. What I thought i'd do is replace the current section that we have
Jim Zhang: to ask the Yes no questions, and just replace it with a
Tracy Kuhrt: pointer to this document. so that people
Tracy Kuhrt: can check their
Tracy Kuhrt: project to make sure that it's up to date
Tracy Kuhrt: right
Tracy Kuhrt: and then related to whether or not, a project has not completed a required step. I think that is the time at which we
Tracy Kuhrt: become a bit noisy with with them as the Toc. And we we say, when are you going to do this?
Tracy Kuhrt: I know I've seen that a lot in the project reports
Tracy Kuhrt: in the past right where
Tracy Kuhrt: where it's been the case that
Tracy Kuhrt: a particular
Tracy Kuhrt: project, Hasn't
Tracy Kuhrt: completed something maybe in the inclusive language statement or something, and and usually a question comes out right in that project report when I'm going to do it, or
Tracy Kuhrt: why haven't you done this? And I think that's there's still the appropriate type of steps for us to be taking.
Jim Zhang: Yeah, Cool Sounds good.
Tracy Kuhrt: all right.
Tracy Kuhrt: Any other volunteers for anybody who would like to
Tracy Kuhrt: volunteer for any of the projects.
Jim Zhang: Yeah, I'll, I'll do the Firefly one.
Tracy Kuhrt: Okay, thanks, too.
That's
Tracy Kuhrt: alright. Any other volunteers anybody want to take on any of the other projects.
I
Peter Somogyvari: and that will
Tracy Kuhrt: and double. Okay.
Tracy Kuhrt: Thanks, Peter.
Tracy Kuhrt: Anyone else.
Tracy Kuhrt: No. Okay. Great.
Tracy Kuhrt: So
Tracy Kuhrt: the the the link is now editable. So if you do open it again, you should be able to see that you can edit it.
Tracy Kuhrt: I have nothing else on the agenda, for today. Does anybody else have anything they would like to bring up
David Enyeart: in terms of logistics. What was the idea to create a tab for each project?
David Enyeart: Yes, or a column? A Tab.
Tracy Kuhrt: Yeah.
David Enyeart: Okay, Which is just basically a copy of the Template.
Tracy Kuhrt: Any other topics for discussion today?
Tracy Kuhrt: No? Okay.
Tracy Kuhrt: Well, then, I appreciate that.
Tracy Kuhrt: I maybe just one comment before I let you guys go. I know you guys were all excited where you hit that button.
Tracy Kuhrt: the the Tsc. I think we said this last time with the Coc. Election is currently in the hands of the governing board. so we're expecting results back from that in a week, probably early next week, I think, is is the timeline for that.
Tracy Kuhrt: So
Tracy Kuhrt: how we will let people know once those results are final
Tracy Kuhrt: as far as the the new Tfc. That's coming in
Tracy Kuhrt: one of the things I was thinking we might do for a toc call next week is.
Tracy Kuhrt: if we do have the results potentially, we'll get some of the new joiners to come in, and we could potentially have a discussion on
Tracy Kuhrt: You know, a transition type discussion where the people who are
Tracy Kuhrt: are leaving the the Toc.
Tracy Kuhrt: Would, you know, provide some thoughts and insight into
Tracy Kuhrt: things that they've done. And I would like to, you know, see, maybe being continued in the next year, and then maybe some
Tracy Kuhrt: input from the new Tlc members as far as
Tracy Kuhrt: what it is that they'd like to accomplish in the next year.
Tracy Kuhrt: So
Tracy Kuhrt: all up for when when the final results actually come in, if it shows up in time or not. But that's that's kind of the current thinking and kind of what's happening
Tracy Kuhrt: with the toc election.
Tracy Kuhrt: All right, so that's all I have. Jim, you did come off me. Did you have a question?
Tracy Kuhrt: No, I was ready to say, thanks to Jason. Alright, great. yeah. So that's it. I will let you guys actually hit the lead. But now so thanks again. For your thoughts and your discussion today.
Jim Zhang: Yeah, thanks. Tracy.
Jim Zhang: Thanks, bye, bye, bye, bye.