Brigade Community, 26 Apr 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Brigade Community Meeting -- 2022-04-26

Description

A recording of the Brigade Community Meeting on 2022-04-26

A

Okay, hello and welcome to the what's today's date april, 26 2022 occurrence of the brigade community meeting. um Let me bump up the size of my browser text here. Is this readable, okay cool?

A

um Actually now I don't even know why I shared it because there isn't a significant agenda today, we're just going to do a really quick update on what the last two weeks have looked like and talk about um what the next two weeks look like um and that's pretty much it um so the last two weeks have not looked like what I thought they were going to look like so the last time we met.

A

I talked about uh trying to get a few of the um outstanding gateways across the line, um particularly, I was going to put some effort into the bit bucket gateway and, I think also the noisy neighbor. Let's see if we yep that's what we talked about last time.

A

um I also talked about um starting to um groom the backlog and prepare for basically map out what was going to be in the next release of brigade itself and that actually ended up taking up most of the time and uh the other thing that that has been happening lately, which is actually a really good thing.

A

Is it's it's getting harder to plan things, because the community is actually steering us in different directions, which, at this stage, is a good problem to have right like we're, not kubernetes, um you know we're not at a point where you know we need to be saying.

A

You know, here's this big massive release, we're planning and we're planning on this schedule, and it's going to have this feature in this future and this feature I think, we're at a point where we have a burgeoning community and it's really more beneficial to us to um be paying attention to that community and and allowing them to tell us what they need um and letting them steer us.

A

So um there was uh one particular uh feature, enhancement that came in in the last couple of weeks that kind of got prioritized because it came from somebody who I know is actually using brigade2 quite a bit, um and so you know I wanted to do what I can to keep that individual uh happy with the project and then he actually helped me uncover the fact that a pretty serious I don't know if I want to call it a bug, but oversight exists, um one that I never would have imagined and that kind of took precedence um in the in the last two weeks um and it was a difficult issue to solve.

A

So what it is is that um we are not compatible with uh get um get repositories that are stored in azure devops um and that's kind of you know to me and probably to karen as well kind of a big deal, because you know not that not the brigade is a microsoft project, but we do work at microsoft, and so it's kind of you know kind of reflects poorly on us.

A

If, if you know this project that that we're helping to um to steer, um isn't compatible with um you know microsoft, software that you would expect it to be um compatible with so I did. I did a bit of research and I found that um azure devops is kind of unique among uh github, sorry among git providers, um so you know compare them to like github or bitbucket or jfrog.

A

There's a few others, and the thing that's really unique about azure devops is they require clients to support newer protocols that all the other providers don't require their clients to um to support, so they've set the bar a little higher um than the others in terms of what's required for compatibility um with their repositories, um and so I I started digging more and found that the library that we use for interacting with git repositories.

A

um So this is when a a worker or a job in brigade actually needs to pull stuff down from a repository. We use a particular library for doing it and we found that that library does not implement those newer protocols that azure devops requires and implementing those new protocols is such a gigantic undertaking that that the people behind that library have basically said yeah.

A

This is not anything we're planning to do anytime soon, um so we basically had to go and hunt down uh an alternative library that that we could use um that in itself was pretty difficult. um We we found a good candidate um that is official, um so there there is um something called uh git lib2 and uh it's an official project. So it's it's part of the get project um and it it's it's basically a c library um and they do publish bindings to other languages like rust and go and so forth and so on.

A

So obviously the it's the go bindings that are most relevant to us um and that's where things got really tricky, because when you are compiling go code um that calls c libraries, you need to use something called seago, and that is a relatively easy proposition um on linux and we didn't have any trouble getting um this working on linux.

A

So the whole problem of of not being able to talk to azure devops repositories is solvable pretty easily as long as we're only talking about linux, um but this particular component that can yank source down from you know from whatever your github provider is.

A

It also needs to be able to run um on windows nodes because of the fact that brigade jobs can be windows based if you choose and compiling go code that invokes c libraries for windows was extremely extremely extremely difficult and I spent I'm gonna say at least 30 hours chasing that down.

A

So this is all around about to explain where all the development effort went in recent weeks and uh why the things that we had planned didn't actually get done, um but this is good. I think that this is a a an important issue um to solve and to solve sooner rather than later. So um it's not as if uh we didn't make good progress in the last two weeks.

A

It's just not where we had planned for that progress to be, um and again, I'm feeling pretty okay about this, because I want the community to be steering us right now and telling us where we need to go so um this is, as far as I'm concerned a good problem to have um so as far as what I plan to accomplish over the next two weeks, I'm just going to rewind to um to what to you know two weeks ago and say that that will make these the priority again getting these two components.

A

um Ga! um So that's really all that I have for today. So I'll stop my screen share and um we can open up the floor if karen has anything or haven't.

B

um I wanted to ask like where the um the gsoc, like the the like summer intern situation. Yes,.

C

A

Yeah, actually, that's a good question as well. Actually a considerable amount of time went into that as well, um because they're you use.

B

Some context, that's like what it is.

A

Yeah, so um so gsoc is the google summer of code um and it's a program that google runs every summer where I don't know if it's just for students, it might also be for early and career developers, I'm not sure, but but basically uh people who are kind of just getting their feet wet with you know, contributing to open source and that sort of thing um can look around and find open source projects that have um you know, kind of volunteered to uh sponsor um different projects that they need to get done and the uh the students put together proposals saying: oh, you said this was a thing that you had to get done, and here's how I would here's who I am and here's how I would approach this and I'd love to work with you and so forth.

A

So um I did spend a lot of time over the past two weeks um reviewing proposals prior to the deadline because they do permit that so sponsors are are permitted to review proposals and give feedback. So um I spent a lot of time on that and then I spent time also reviewing the the finalized proposals that that everybody submitted. I think we had about six or seven um that that were submitted. um We, we actually had proposed three different projects and we had about six or seven proposals that that came in.

A

So some people put in multiple proposals for multiple projects, um and I did provide my feedback on all of those proposals, but that in no way guarantees that the ones that I was willing to accept doesn't guarantee that they will get accepted because um cncf as a whole um received, I think, 71 applications.

A

um The fact that out of 71, six or seven of them were for brigade is like really not bad, um so I'll. Take that that's pretty good, um but you know, hopefully you know so it basically remains up in the air right now. How many um slots will google give to cncf and how many, uh if any of those slots will cncf allocate to brigade being that we're just a sandbox project and not incubating?

A

Yet it's probably we're probably not high on the priority list, but um but we will see what happens but but yeah, a considerable amount of time went into that whole process. Over the last two weeks.

B

Wait so do we just wait now.

A

Yeah, so cncf uh has to um basically uh prioritize what what they want done by uh may 12th, so I've I've done my part in terms of reviewing and making my recommendations. But now it's now it's up to people at cncf to prioritize and request slots from google.

B

And then from there the the students like pick what they want right and then I think we're supposed to then choose.

A

um No so so there was a lot of confusion about this. It's so the way it all works. It's a um everything is considered as a unit right, so we so we proposed three different project ideas and then the proposals that we got from, I think four or five different individuals. We got seven proposals total from four or five different individuals.

A

They talk about a specific project idea and how they would approach it, and so it's it is us and the idea and the student who are all considered as one unit and it's like. Will we give this the green light, or will we give this the green light? It's it's not like brigade is good to go. This guy is good to go figure out what you're going to work on together. It's it's not like that. It's all considered as a unit.

A

Okay got it, which and- and that was uh I would say, not obvious up front. um There is a lot of you know. I don't mean to put anybody down at all, but there's a lot of room for improvement in how um google and cncf and everybody involved in this just coordinates, because I I've mainly been coordinating with people from cncf and they're like a middleman.

A

um And so sometimes I ask them questions and they don't know the answers and they have to go chase them down so to be prepared.

B

I think normally this program is run by ihor and ehor is currently in ukraine, so I think that's kind of where yeah context. Okay,.

A

Yeah, okay yeah cause, because I I know it it's nate waddington, who's running it um right now and he's he's been nothing but awesome throughout. All of this he's been very responsive and and everything, but often the the answer to the question is well, I don't know the answer, but I will find out for you- and you know I appreciate all of his efforts, but it's it's been a difficult process to understand, but I didn't I didn't have that context that that it was usually run by somebody who is in ukraine right now.

A

Yeah, that's unfortunate.

C

A

Sure we're having a little bit of trouble hearing you you might can, can you turn up the mic or or speak a little louder, possibly.

D

Yes, also another people know, but.

A

Yeah much better.

D

Yeah so basically I am a beginner and my expertise lies only in the front end development.

D

So how can I like? How can I contribute to the community.

A

Sure so we we have only one component that um has any significant front end to it, um and that is the brigade dashboard, um and so that might be what you focus on. If, if you are interested in contributing it's all written in react and typescript, um are those uh technologies you're familiar with.

D

uh Yes, I'm familiar with like I've applied for the g-store, also, okay,.

A

A

Wait, you did you say you applied for gsoc.

A

uh Yes, uh I don't. You know what I'm gonna double check. I don't remember seeing your application, but I'm going to double check um just like I applied in the very last hour. um Okay, all right! Thank you. Thank you for letting me know. So I'm going to go back yeah, I'm going to go back and have a look um because you're you're, okay, I don't think I've reviewed yours, so I will go back and take a look.

A

Thank you for pointing that out.

D

Yes, sir, we have also discussed about this two in the github, I'm sorry. What was that uh like? We have also discussed about the issues in the database, the take prototype to gas2.

A

Yes, yep, let me see hold on. Let me see if I can pull this up right now. Where did it go.

A

So so you put in two applications.

C

uh Did you put in two applications to gsoc.

D

Yes, for, like two organizations.

A

A

Oh okay, I I see it now. uh Oh april 19th you put it in.

D

Yes, I put it in the last hours.

A

Okay, all right so so I may have missed those. So thank you for pointing that out to me, I'm glad you were here to point that out.

A

Okay, so it's not too late for me um to review because, like I said the the deadline for cncf to request whatever slots they want is may 12th. um So it's not too late um for me to give my feedback. So thank you for for pointing that out to me. um If, if those came in at the last minute, I had not seen them already so thank you.

D

Yeah, I also had one question sure: uh what, if that brigade dashboard component, don't get a g-stock start. So how will the development of that component go ahead?.

A

uh I'm sorry, I think I missed part of the question.

D

uh I asked I was: I was asking like what, if the duplicate dashboard thing does not get the slot for the gsoc, so how will the things work after that.

A

uh I I don't think, I'm completely understanding you know. What do you think it's possible? We can um take that question offline.

C

Yes, sir, okay, awesome.

B

Are you in the brigade slack? Do you know where to find us? Yes, okay,.

C

Yes, yes, okay,.

A

Yep, so so, pink so opinion yep, so ping me over there. Please, yes, yep awesome.

A

All right, if there's nothing else, I think we'll uh wrap this up.

A

Okay, thank you guys, and I will post this to youtube tomorrow, um so that the rest of the community can watch it at their.

C

All convenience all.

A

Right have a great day, bye.