Tracy Kuhrt: All right. Welcome everybody. It's February. Welcome to February. Second
Tracy Kuhrt: Hyper, Ledger, Technical Oversight Committee call, as you are probably all aware.
Tracy Kuhrt: 2 things that we must divide by on this call. The first is the antitrust policy
Tracy Kuhrt: that is currently displayed on the screen.
Tracy Kuhrt: and the second is our code of conduct which is linked in the agenda.
Tracy Kuhrt: So for our agenda today we have some announcement.
Tracy Kuhrt: If who's ever sharing would take us to the agenda? That would be great.
Tracy Kuhrt: Thank you. So the first one is the standard one, the Dev Weekly developer Newsletter that goes out each Friday. If you have something that you would like to include in that
Tracy Kuhrt: Newsletter. Please leave a comment on the Wiki page that is linked in the agenda.
Tracy Kuhrt: the second one. So last week we approved project reports being submitted via Github
Tracy Kuhrt: Ryan. I worked on basically getting. I did all the old reports and got them migrated over to Github.
Tracy Kuhrt: I set up some a default template for the project reports.
Tracy Kuhrt: We've actually had our first project report submitted on Github. So in the future, if you are somebody who Files
Tracy Kuhrt: project reports. Github is the place for those.
Tracy Kuhrt: The third announcement that we have is
Tracy Kuhrt: that the Hyper Ledger Mentorship program has kicked off.
Tracy Kuhrt: So we're currently looking for mentorship project proposals.
Tracy Kuhrt: and if you do have a project proposal, please submit that
Tracy Kuhrt: prior to March fifteenth.
Tracy Kuhrt: we will be having men come and talk to us
Tracy Kuhrt: in a couple of weeks to
Tracy Kuhrt: tell us more about what the Hyper Ledger Mentorship program is, and also to
Tracy Kuhrt: put a call out for people who would be willing to review the different for project proposals that come out to
Tracy Kuhrt: get the
Tracy Kuhrt: ones that we think are
Tracy Kuhrt: kind of match. The criteria that the mentorship program has.
Tracy Kuhrt: So that's in a couple of weeks. But in the meantime, if you do have a project
Tracy Kuhrt: mentorship project that you would like to propose. Please do so
Tracy Kuhrt: all right. Any other announcements that anybody has.
Tracy Kuhrt: Okay, not seeing any him. So anybody else coming off mute. I will take that as a.
Tracy Kuhrt: So as far as quarterly reports, we are still waiting on the earth to report to come in.
Tracy Kuhrt: We did, as I mentioned. Get the Hyper ledger statute
Tracy Kuhrt: coming in on Github.
Tracy Kuhrt: So I link here in the agenda about the Pr. And a rendered version of that report for you to take a look at.
Tracy Kuhrt: I think, as of this morning, and i'm sure somebody might have snuck in since last time I looked. But when I looked there were, I think, 6 people who had had a chance to review that, and we're still waiting on 5 others to take a look at that.
Tracy Kuhrt: So please do take a look at that report.
Tracy Kuhrt: The Hyper Ledger Areas report came in last week
Tracy Kuhrt: and
Tracy Kuhrt: was
Tracy Kuhrt: reviewed by, I think, the majority of us, but any questions on any of the Quarterly reports.
Tracy Kuhrt: Okay, another rezoning, though. So we do also have some upcoming reports. Today we have the Indie and the Non cred that are also due.
Tracy Kuhrt: and then we have a hyper ledger. You know how that's coming to you next week.
Tracy Kuhrt: so we will look forward to receiving those
Tracy Kuhrt: all right. So for discussion items. We have 2 discussion items. The first one is something that I added Yesterday, since we were moving other things to Github.
Tracy Kuhrt: I was curious. If we wanted to also move these meeting agendas to Github.
Tracy Kuhrt: and then the the other agenda item that we have is the task force proposals.
Tracy Kuhrt: I will say that there are a number of
Tracy Kuhrt: Poc members who have not put their name anywhere, and I don't know if that's because you're not interested, or you Just Haven't
Tracy Kuhrt: completed the
Tracy Kuhrt: the task to add your name to any of those task forces
Tracy Kuhrt: definitely important to do that. So if you want to do that here
Tracy Kuhrt: while we're while I'm wasting a bit of time. Please do do that so that we can make sure that we know which ones we want to prioritize.
Tracy Kuhrt: But let's have a discussion about the first agenda item.
Tracy Kuhrt: Do we want to move meeting agendas to Github? Or do we want them to stay out of the Wiki.
Tracy Kuhrt: So if you wouldn't mind opening up the proposal there, whoever is sharing the screen
Tracy Kuhrt: on the the meeting agenda to Github.
Tracy Kuhrt: so yeah, like I said.
Tracy Kuhrt: as far as
Tracy Kuhrt: other things that we're moving to Github into basically that hyper ledger. Org
Tracy Kuhrt: wanted to see if we wanted to move the meeting minutes there.
Tracy Kuhrt: specifically having the poc chair create a request
Tracy Kuhrt: to add the meeting agenda
Tracy Kuhrt: during the Toc meeting, having the pr modified to include any of the attendees that we have.
Tracy Kuhrt: And then, after the Poc meeting.
Tracy Kuhrt: why, I think you have a comment about the recordings.
Tracy Kuhrt: and then just going through the process of getting approvals and getting that merge to to Github.
Tracy Kuhrt: So why did you want to comment on that? The recordings piece?
Tracy Kuhrt: It came off mute, but
Tracy Kuhrt: we don't hear you.
Ry Jones: Okay, there. Okay.
Ry Jones: The the recordings are obviously not too large to host on. Get up.
Ry Jones: I was thinking
Ry Jones: for other reasons. I've been looking into where we can store big stuff doesn't change. Archive Org
Ry Jones: is a free place to host big things that don't change.
Ry Jones: So I was thinking about using archive org.
Ry Jones: But i'm not married to that.
Ry Jones: The other thing that we could do is to continue to upload those to the wiki and
Ry Jones: point to the Wiki.
Ry Jones: I don't have strong feelings either way.
Tracy Kuhrt: Okay.
Tracy Kuhrt: I think the the main concern is that we want to put them some place where we want them.
Tracy Kuhrt: so that we need to go back and listen to them.
Tracy Kuhrt: I remember just recently we had a question come up about some decision that we had taken. And Why did we take that?
Tracy Kuhrt: We we dug through the recordings right to listen to kind of our reasoning. So I want to make sure that wherever we put the recordings. We're not going to lose them.
Ry Jones: Right? Which sounds very reasonable.
Tracy Kuhrt: Yeah.
Tracy Kuhrt: Title.
Timo Glastra: Yeah, it is it? Just like for the poc meetings? This? Or is it like more? As also to try for more general, because all the other working groups and stuff is hosted on on the Wiki? Like? Is there a a bigger plan behind this, or is it just like for this specific meeting?
Tracy Kuhrt: Yeah. So this is specifically for the Toc meeting. So if if you take a look and go to to to Hyper ledger.org.
Tracy Kuhrt: you will see that we're we're starting to move things over there that are specifically right related to the
Technical Oversight Committee.
So we have all the governing documents. We have.
Tracy Kuhrt: the guidelines that we've developed over the years information for us as members who we are as as well as what do we? What are we responsible for? And then the project updates that we just moved over.
Tracy Kuhrt: So my thought was that we would have kind of a fifth.
Tracy Kuhrt: that down here that was the meeting minutes
Tracy Kuhrt: to to really have them all in one place.
Timo Glastra: Okay, yeah, I think, for for the auto meetings, like what I think, what
Timo Glastra: most of the benefits of using the the Hyper ledger Wiki also
Timo Glastra: always lost. There is the collaborative features of it, and that multiple people can add links and take notes at the same time. But i'm not sure how how relevant it is.
Timo Glastra: The Poc meeting notes.
Tracy Kuhrt: Yeah, it's a good point, you know. I think there's been a couple of times when we have done some collaborative editing on some documents on the Wiki
Tracy Kuhrt: during this meeting. Very few, I think I can probably count on one hand the number of times that we've done that
Tracy Kuhrt: so probably not as important as maybe some of those other meetings, but
Tracy Kuhrt: is something that yeah, it's worth considering.
Tracy Kuhrt: Anybody else have any thoughts on this.
Tracy Kuhrt: Bobby?
Bobbi Muscara: So I just have a question. So as a foundation, are we moving away from confluence? Is that like the goal of this, or is it because
Bobbi Muscara: a lot of the other
Bobbi Muscara: special interest groups and all those part of the trainings, or get them familiar with the Wiki Page and i'm just curious if that's
Bobbi Muscara: a trend moving away from confluence as again a hyper ledger foundation.
Ry Jones: I'm: i'm gonna say no.
Ry Jones: So
Ry Jones: the my original desire behind moving a bunch of stuff to get a bunch of historical stuff to Github
Ry Jones: was that we lost some of the foundational documents for hyper ledger.
Ry Jones: like we don't have the original Saw Tooth proposal anywhere that I can find. There are a couple of other documents that are missing.
Ry Jones: so I want to preserve those
Ry Jones: and the same thing for the
Ry Jones: for the meeting.
Ry Jones: Sorry for the project updates
Ry Jones: in the Wiki. There is no
Ry Jones: like anyone can go in
Ry Jones: and
Ry Jones: edit these pages on the Wiki, so we don't know who actually reviewed what?
Ry Jones: At what time.
Ry Jones: So that was why I wanted to move project ports over.
Ry Jones: and the the Tsc. Sorry, the Toc
Ry Jones: being agendas are something else that we, some of them, are are lost to time.
Ry Jones: So I for those items.
Ry Jones: I I want those there
Ry Jones: is Hyper Ledger moving away from confluence.
Ry Jones: No.
Tracy Kuhrt: and why? I will add to your point about
Tracy Kuhrt: things being modified after the fact. So last year we had some meeting minutes where
Tracy Kuhrt: people were going through and trying to clear up their backlog of tasks that they had to
Tracy Kuhrt: to review right for the project report. But
Tracy Kuhrt: in a lot of
Tracy Kuhrt: in more than one case I did see that people checked themselves as having attended a Toc meeting; that they did that at 10,
because we didn't.
Tracy Kuhrt: We didn't remove that as a task item for them. So you know, I think there is a
Tracy Kuhrt: there is some
Tracy Kuhrt: information that is in the Wiki that is not actually correct.
Tracy Kuhrt: based on the the Toc meeting so very similar to what you see with the project reports potentially being
Tracy Kuhrt: modified or checked off. I I don't know how many times I've had somebody like unchecked. The fact that I've reviewed a a project report. But
Tracy Kuhrt: you know there there's a similar sort of issue that exists with the Tlc meetings today.
Tracy Kuhrt: Jim.
Jim Zhang: Sorry, Can you find that unmute button? I think it just takes some getting used to us? There was at least 2 incidents in the past year where I needed to update the agenda, so I would have to
Jim Zhang: in the new process.
Jim Zhang: make a poor request to the agenda for that to be merged
Jim Zhang: and ready for the meeting.
Jim Zhang: Just for you. It's a bit funky, but I I I can see the benefit of doing this versus Wiki
Jim Zhang: for like archiving and and tracking purposes. So I i'm willing to give it a try. But I think you know it's in terms of the convenience. I I think there's definitely a loss of that. But at least for myself, I'm: i'm willing to give this a 5
Tracy Kuhrt: yeah question. And another
concerning that.
Tracy Kuhrt: I think, is is worthwhile to have brought up. So
Tracy Kuhrt: think about whether or not you
Tracy Kuhrt: Hmm. Add it to the agenda in the past, and whether or not that
Tracy Kuhrt: seems like it's a potential concern for you other people, obviously besides zoom. So, Marcus: yeah. So it's just a for a quick follow up. I I assume the Tm. Toc members will be made at least the writer access, so we can
Jim Zhang: make a pull request directly
Jim Zhang: on on this repository rather than having to fork to our own.
Ry Jones: I I think that's undecided
Ry Jones: right.
Ry Jones: My guess is yes.
Ry Jones: I I
Ry Jones: How is it today? I I can't tell you I'll stop my head. What? How it's set up.
Ry Jones: How could it be Exactly as you said
Ry Jones: I, I would just need to change the permissions to make it that way, and
Ry Jones: basically do the auto branch create thing when you want to pick an edit.
Jim Zhang: Great cool. Thanks, Ryan. That's it for me.
Tracy Kuhrt: Thank you. I think the other thing we might consider is whether or not a drop Pr. Would allow you to edit it directly
Tracy Kuhrt: to edit the files that were were added.
Tracy Kuhrt: or alternatively, just to make the use the suggestion, option, right to suggest, adding or or modifying
Tracy Kuhrt: A, and then having the person.
Tracy Kuhrt: the chair. Who created it right, except that suggestion.
Tracy Kuhrt: Marcus.
Marcus Brandenburger: Yes, thanks. So I absolutely see the benefits of of maintaining the history of those documents a little bit better. Maybe we should consider putting this later on a blockchain instead of Github.
Marcus Brandenburger: Not just joking. Have you also considered to use the Github Riki, which I guess, is a little bit easier to maintain when multiple people would like to add things quickly.
Marcus Brandenburger: But I also, because I can also see the additional overhead of I mean adding addition to this pending pr.
Marcus Brandenburger: depending on on the personal preferences. How to use Kit, I guess.
Marcus Brandenburger: and
Marcus Brandenburger: and that could be complicated.
Marcus Brandenburger: The my experience with the
Marcus Brandenburger: All right.
Marcus Brandenburger: the proposals, or the
Marcus Brandenburger: what you just mentioned, Tracy, When you suggest a change. If, then the Pr. Create, you accept
Marcus Brandenburger: those some times this results in an awkward
Marcus Brandenburger: merge issues. This is my experience.
Marcus Brandenburger: So did you try the get a Wiki for some other
Marcus Brandenburger: things like that? That.
Tracy Kuhrt: Yeah, some more, because I've used. I'm using a github with you right now with another project.
Tracy Kuhrt: I think the reason so. So there were those were 2,
Tracy Kuhrt: I mean. I can take it back. That was one of the 2 options that I considered. One of the 3 options I guess I considered was the wiki that the concern I have with the Wiki, and I don't know if it's the case, but I don't think we can show the wiki on a Tsc. That hyper ledger, that one
Tracy Kuhrt: alright.
Tracy Kuhrt: Yeah, that that was, I think, my concern there. Then the second one, also the same concern that I can considered, and throughout was just creating an issue
Tracy Kuhrt: that we could track the meeting agenda on again. We can't display the issue on Tlc. That hyper ledger.org, which is why I went to this
Tracy Kuhrt: a process of Pr.
Tracy Kuhrt: Which yeah is a is a bit more challenging, but
Tracy Kuhrt: would allow us to to display those
Tracy Kuhrt: on a Tlc. That we led to that one.
Marcus Brandenburger: Okay, I see.
Marcus Brandenburger: But so so your personal preference would be, I mean, going this
Pr. Route
Marcus Brandenburger: in in terms of I mean, if you think about the the additional get overhead you need to do.
Marcus Brandenburger: I mean for the Vicki, you can do everything in the border
Marcus Brandenburger: for creating a Pr. You have to do something in the terminal
Marcus Brandenburger: depending on personal preferences of kit.
Tracy Kuhrt: Yeah. So for for me, I guess I don't.
Tracy Kuhrt: I don't necessarily
Tracy Kuhrt: care whether or not we move over to the Pr. Or we stick with confidence. But it was. Are we trying to to move everything over. So therefore let's make this a
Tracy Kuhrt: suggestion that question, and see what people think right. Like. If you guys decide this is the worst idea in the world, Tracy. I'm perfectly happy to say great. Let's close it and move on
Tracy Kuhrt: right. I I really i'm really not tied to. Whether or not we have to do this or not.
Tracy Kuhrt: I'm, you know, presenting it as there are reasons to do it.
Tracy Kuhrt: I'm i'm not tied to one way or the other.
Aleksandr Petrosyan: if I may. I just like to comment about the get over. Really, this is nothing.
Aleksandr Petrosyan: Github offers quite a few facilities for doing things in line, so to speak, and there's a little bit of automation in the web. Ui! That can be done. If not, it can be self hosted at least partially when it's script that removes the overhead entirely.
Aleksandr Petrosyan: The issue is that people
Aleksandr Petrosyan: large amounts of people, and Hyper Ledger has a lot of contributors, is with a lot we want people spending extra time doing this.
Aleksandr Petrosyan: I'd also raise that confluence as a very different syntax, meaning that if we have the technical proposals in how can be, and it is in mark that I'm. Transforming it into a format in which we could also host it on the hypervisor Wiki
Aleksandr Petrosyan: is comparable to writing the thing from the ground.
Aleksandr Petrosyan: So the fact that the poor request allows us to use the lockdown syntax might actually save people time
Aleksandr Petrosyan: not counting that we can also remove the get overhead by custom solution.
Aleksandr Petrosyan: So in any respect
Aleksandr Petrosyan: it's it's reasonable.
Aleksandr Petrosyan: I think, that the cool request workflow has more advantages
Aleksandr Petrosyan: in terms of
Aleksandr Petrosyan: develop a convenience. Let's just say
Aleksandr Petrosyan: just a comment.
Alright Thank you.
Tracy Kuhrt: I appreciate that
Tracy Kuhrt: any other thoughts or comments on this.
Tracy Kuhrt: Do we think we want to vote on this.
Tracy Kuhrt: and if we do, is there somebody who would like to make a motion?
Jim Zhang: I can motion to pass this.
Tracy Kuhrt: Alright thanks, Jim. Do we have a second
Marcus Brandenburger: 1 s?
Tracy Kuhrt: Okay. I I know, Marcus. I think you were on when you were the other one a second.
Thank you for that.
Tracy Kuhrt: All Righty, let's do a let's do a voice vote, because i'm not sure that everybody is behind this. And so I want to make sure we we know where we stand.
Ry Jones: Give me a roll call, vote, vote.
Tracy Kuhrt: Thank you.
Ry Jones: Okay on the matter before the Toc. Or run.
Yes.
Ry Jones: Bobby.
Bobbi Muscara: No.
Ry Jones: David.
David Enyeart: Yes.
Ry Jones: Jim.
Jim Zhang: Yes, Marcus.
Marcus Brandenburger: Yes, Peter.
Tracy Kuhrt: I guess.
Ry Jones: Team of
Timo Glastra: Yes.
Ry Jones: Tracy.
Tracy Kuhrt: Yes.
Rama.
Ramakrishna V: Yes.
Ry Jones: okay. The eyes have it
Tracy Kuhrt: alright.
Great.
Tracy Kuhrt: All right. So let's move on to the tax.
Tracy Kuhrt: of course.
Tracy Kuhrt: issues that we've created. Let's see if we've got some updates behind me.
Tracy Kuhrt: So I think we'll just go through these one by one and see if we've got any support for these. Looks like with the supported projects we have
Tracy Kuhrt: myself who is signed up so that's probably not one we're gonna prioritize
Tracy Kuhrt: for the badging life cycle.
Tracy Kuhrt: We have Rama and Bobby, who've signed up for that one
Tracy Kuhrt: for the next one. Here the security artifact
Tracy Kuhrt: task force.
Tracy Kuhrt: We have
Tracy Kuhrt: Marcus Arnold and Hart.
Tracy Kuhrt: I have signed up
Tracy Kuhrt: security vulnerability we have
Tracy Kuhrt: for the onboarding.
Tracy Kuhrt: We have Bobby, you sign up to be a leader and myself and Bobby as
Tracy Kuhrt: participates
Tracy Kuhrt: for the documentation. Bobby has also signed up to be a leader, and we have Rama and myself as participants, plus obviously Bobby.
Tracy Kuhrt: the project best practices, Roma and myself.
Tracy Kuhrt: And then
Tracy Kuhrt: for the last one here the best practices.
Tracy Kuhrt: Tomorrow you snap right in there, I mean Marcus
Tracy Kuhrt: and Dave and Kimo.
Tracy Kuhrt: So just looking at that. Yeah, Roma, you have a question.
Ramakrishna V: No, just a comment. I believe Peter is on vacation this week, so he may sign up for some of these many returns. I know I did discuss with them about documentation, so he might be interested in joining that one.
Tracy Kuhrt: Okay, Great. Thank you for that. And I know Steven also mentioned in his chat to the Hyper Ledger
Tracy Kuhrt: for this meeting that he was going to update the documentation and the pipeline ones for that.
Tracy Kuhrt: Now.
Tracy Kuhrt: did we have everybody on the call.
Tracy Kuhrt: every T. Oc. Number on the call, sign up for task forces, or do we have to add
Tracy Kuhrt: anybody to any of these task forces to to make sure that we've got a complete list.
Jim Zhang: Hey, Tracy? I just added myself to 2 of them.
Tracy Kuhrt: Okay? Which to Jim?
Jim Zhang: That was security artifacts, signing and best practices for projects.
David Enyeart: Okay, great. Thank you.
David Enyeart: Okay, Great.
Arun S M: To add myself, I'll be adding after this call, that is, i'll. I think, heart also mentioned on the chart that
Arun S M: it can be anybody outside the Tuesday as well.
Tracy Kuhrt: Yes, for sure, for sure anybody outside the Tsc. Can can sign up, or are there specific ones that you're thinking about adding your name to, so that we can get kind of an accurate count. So
Tracy Kuhrt: where people are at?
Arun S M: Yes, so i'll be signing up for security, both the task forces and on the ongoing content.
Arun S M: These 3 are
at least.
Arun S M: But i'll I will go through, and I to
Tracy Kuhrt: That's fine. That's right. Thank you. Okay. Anybody else who hasn't had a chance or not in after I went through those.
Tracy Kuhrt: Okay. So based on that, I think where we're at is for sure, the onboarding content and the documentation
Tracy Kuhrt: and the security
Tracy Kuhrt: task force
Tracy Kuhrt: seems to be, and I think it was the vulnerability disclosure one heart that you said you want it to prioritize.
Hart Montgomery: Yes, Tracy, that was my opinion, since I've sort of done some background on that one with the open Ssf.
Hart Montgomery: But if you know if there's massive momentum towards another one, you know we we could start with that one, too.
Tracy Kuhrt: Okay?
Tracy Kuhrt: Alright, and then I think
Tracy Kuhrt: the other one that might have had a lot.
Tracy Kuhrt: Yeah, it was the project best practices. Maybe you signed up for later. Okay, that's why I didn't touch your name. I was looking at the list
Tracy Kuhrt: instead of the leader, so great, so
Tracy Kuhrt: I know that we have leaders for the
Tracy Kuhrt: documentation on boarding and best practices.
Tracy Kuhrt: I don't think we necessarily have a leader, a room, are you? Still.
Tracy Kuhrt: I know you were the leader for the security task force previously. Is that something that you're still interested in doing or not?
Arun S M: Yes, I
Tracy Kuhrt: Okay, great.
Tracy Kuhrt: So I think we've got kind of the 4 out of the 8, which is kind of where we want it to end up
Tracy Kuhrt: any objections or thoughts that I miss something as I was going through there, that we should have been focusing on besides those for
Tracy Kuhrt: okay.
Tracy Kuhrt: So I guess what i'd like to do, and and is to continue kind of the process that we had
Tracy Kuhrt: last
last year
Tracy Kuhrt: where we spend
Tracy Kuhrt: It's the first half an hour of the poc calls
Tracy Kuhrt: on poc topics, assuming we have any
Tracy Kuhrt: and the rest of the time on
Tracy Kuhrt: the task force
Tracy Kuhrt: discussions now, by doing that.
Tracy Kuhrt: since we have 4, that means that we have meetings at least once a month for these task forces.
Tracy Kuhrt: but that does not preclude us from having meetings in between the time that
Tracy Kuhrt: the poc. It's discussed at the Poc.
Tracy Kuhrt: Right? So if you want to have off cycle meetings.
Tracy Kuhrt: you can have off cycle meetings.
Tracy Kuhrt: If you're not.
Tracy Kuhrt: then it's that probably could take you a bit longer to get through some of these tasks.
but
Tracy Kuhrt: I think it's really important that
Tracy Kuhrt: it not only be a
Tracy Kuhrt: a toc meeting that we're discussing these, but that work it's done outside of that as well.
Tracy Kuhrt: So with that, I I think the the idea here would be to create some sort of order for going through these.
Tracy Kuhrt: and I don't know if any of the leaders would like to volunteer to step up first.
Tracy Kuhrt: Yeah, Roma Question.
Ramakrishna V: Yes, quick question in the past. Do you have? Have you started separate discussion for each of these so people can discuss?
Tracy Kuhrt: Yes, yes, we have, and we can do that again. We can create task force channels for each of these, so that people could have
Tracy Kuhrt: their offline discussions there. As well as
Tracy Kuhrt: you know any sort of meetings that they might have
Tracy Kuhrt: Bobby?
Bobbi Muscara: Well for the documentation and the onboarding, the learning materials, working group kind of has stepped up the members to help out with that along with David, and I believe that the plan is to maybe meet
Bobbi Muscara: where the learning materials development working group used to meet for those 2 task forces, and maybe put like on boarding on one Monday, and then the documentation on another, and then report back to the Tsc. I would say in in like 2 or 3 months
Bobbi Muscara: for the final report on which everyone is closest. And then.
Bobbi Muscara: after that, 2 more months report on the next one.
Bobbi Muscara: If that makes sense, I can put that in a document
and
Bobbi Muscara: solidify that
schedule.
So yeah, Bobby, I think it's great to to meet on the off
Tracy Kuhrt: to Oc. Meetings. I think that's perfect. I do think that it's worthwhile to bring back the discussion, so on a more frequent basis to the poc, so that any input that the poc might have can be.
Tracy Kuhrt: And before right things are finalized, if you will
Tracy Kuhrt: right or even help, because I I think it's important that
Tracy Kuhrt: that the Tsc. Is is involved in these topics as well.
Bobbi Muscara: Would you suggest? Well, I guess there's right now. 4 or 5 task force. Would you suggest that they rotate weekly? So every week one of the task force catches the Toc up on what's happening?
Tracy Kuhrt: That's correct. So Exactly. I think there's 4, right? I think we've got
Tracy Kuhrt: the security vulnerability disclosure. They're actually all
Tracy Kuhrt: kind of together, the onboarding content the documentation and the project best practices.
Tracy Kuhrt: So Number 48, 47, 46 and 45,
Tracy Kuhrt: as they're gonna see here.
Tracy Kuhrt: And so what I would like to do is create an order for those to come into the Poc. Right? We can start with the security vulnerability disclosure.
Tracy Kuhrt: have discussions in the Toc as well as their offspring.
Tracy Kuhrt: Then the next week would be maybe the onboarding content, and so on, and so forth.
Tracy Kuhrt: Right?
Bobbi Muscara: Sounds good.
Tracy Kuhrt: Is there? Is there a preference for where we want to start? Or Shall we just say those are the order that we're gonna go in
Tracy Kuhrt: no preference? Okay, let's call that the order that we're gonna go through these in and at the Tc.
Tracy Kuhrt: So, definitely i'll create some channels
Tracy Kuhrt: for us to discuss these items.
Tracy Kuhrt: If you are the leader of these task forces and you are going to set up a a meeting
off cycle.
Tracy Kuhrt: or when you would be coming into the Toc and discussing.
Tracy Kuhrt: I let that channel know, so that people can join
Tracy Kuhrt: and
Tracy Kuhrt: participate in those discussions.
Tracy Kuhrt: Also, if you're the leader of these task forces, make sure I capture the information properly.
Tracy Kuhrt: so that
Tracy Kuhrt: if there's something that we're supposed to be delivering on that I didn't capture, or
Tracy Kuhrt: you think I overstepped, and what we're supposed to be delivering on. Please fix that so that it's correct
Tracy Kuhrt: questions.
Tracy Kuhrt: comments.
Tracy Kuhrt: Okay.
Tracy Kuhrt: Any other topics that anybody would like to discuss today.
Tracy Kuhrt: is there?
Tracy Kuhrt: We like to jump into any of these task forces and see if there's anything that we can talk about already, or
Tracy Kuhrt: are we at a point where we think we're good.
Tracy Kuhrt: Bobby.
Bobbi Muscara: Oh, well, I know for the 2 that i'm leading. I need time to organize, so
Bobbi Muscara: I guess where the documentation would would be first, and that's in 2 weeks, so i'll have a report into it.
Tracy Kuhrt: Okay, sounds great.
Tracy Kuhrt: I'm. Bobby
Tracy Kuhrt: definitely reach out to
Tracy Kuhrt: Once I set the Channel chat channels up, reach out there, ask questions of the participants to.
Tracy Kuhrt: I've signed up for this, and
Tracy Kuhrt: again, as was mentioned, If there's anybody on this call, because I do see that we have some non poc numbers on the call which very much appreciate You guys joining us.
Tracy Kuhrt: If you would like to participate in these task courses, please join us and add your thoughts and ideas
Tracy Kuhrt: part.
Hart Montgomery: Thanks, Tracy. So talking about the security stuff really, briefly.
Hart Montgomery: you know, particularly for the vulnerability disclosure task force. I just wanted to mention that the open Ssf.
Hart Montgomery: Has a bi-weekly working group focused on vulnerability. Disclosure reporting
Hart Montgomery: and once we have the chat channels up and everything i'll post the information there.
Hart Montgomery: and if you're interested in security stuff, I would highly recommend that you attend their meeting, which is at 8 am. Pacific on Wednesdays. So an hour after this time, but on Wednesdays.
Hart Montgomery: you know, I think they're doing a lot of interesting stuff.
Hart Montgomery: but it's not exactly what we need in terms of
Hart Montgomery: coming up with a template for a policy that lets projects sort of easily determine.
Hart Montgomery: You know, a good vulnerability disclosure policy that fits for them.
Hart Montgomery: So I think this is also an opportunity where we can push back
Hart Montgomery: so
Hart Montgomery: output to the open Ssf: as well, we can say, hey, you know we did this.
Hart Montgomery: This is what we determine sort of actually works in the wild. And and you should, you know, use this for your project as well.
Hart Montgomery: So i'm sort of excited by the you know Cross
Hart Montgomery: Linux Foundation synergy
Hart Montgomery: here.
Hart Montgomery: and if you have a chance and you're interested, I would definitely recommend attending that meeting. So thanks.
Tracy Kuhrt: Yeah, thanks, Heart. And I I remember maybe it was you, Marcus, in our first meeting that we had this year, where you were talking about those cross projects.
Tracy Kuhrt: kind of synergies, and working with other projects to see best practices and those sorts of things.
Tracy Kuhrt: So I think it's definitely a really
Tracy Kuhrt: interesting
Tracy Kuhrt: topic area for us to to start to explore what that looks like as
Tracy Kuhrt: as the Toc and as Hyper Ledger, and these other projects want to to communicate and work together
Tracy Kuhrt: alright any other comments, questions
Tracy Kuhrt: and heart. Did they? Did they just have the security working group
Tracy Kuhrt: for the vulnerability disclosure this Wednesday? Or was it? Is it going to be next Wednesday, this last Wednesday and next Wednesday? So not this week?
Tracy Kuhrt: Okay, so
Tracy Kuhrt: is
Tracy Kuhrt: Do you still think it's okay for us to start with that one next week as far as
Tracy Kuhrt: as far as bringing it to the Poc. And having a discussion.
Hart Montgomery: Sure I may have trouble making the meeting next week, but as long as other people are comfortable talking about it.
Hart Montgomery: I think it's fine.
Tracy Kuhrt: Okay.
Tracy Kuhrt: gonna run. Obviously as the leader, I think that question also
Tracy Kuhrt: ends up going towards you as well.
Arun S M: Yes, thanks. I I'll join the next week's Wednesday's Call as well.
Hart Montgomery: Great.
cool.
Tracy Kuhrt: all right. Any other
Tracy Kuhrt: comments questions before we close out.
Okay.
Tracy Kuhrt: So thank you all for your participation, and we will be meeting again next week.
Tracy Kuhrt: So have a great week.
Tracy Kuhrt: and we will talk to you then.
David Enyeart: Thanks a lot.