Next Generation Shell Weekly Meetings, 26 Dec 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: NGS weekly meeting #11 - 2021-12-26

Description

Project website - https://ngs-lang.org/

Pull requests - https://github.com/ngs-lang/ngs/pulls

Red Hat packaging issue - https://github.com/ngs-lang/ngs/issues/513

A

Hello welcome to ngs weekly meetings. Ngs stands for next generation channel. It is a modern programming language for devops, I'm ilya the author of the project. We have ricardo. Today, ricardo is a contributor.

A

Let's start so, ricardo want to start.

B

Yes, so I can start so since last time we moved a bit more. The pull request on the website so earlier had some comments that were fixed. In the meantime, the.

A

Cardio sound is not very good.

B

No, no zoom is playing tricks on me again. No, it should be okay,.

A

It was better before.

B

A

I don't know okay, let's, let's do like this. That's.

B

Right, okay, so so yeah we did some improvements on the website on the pull request, so it should be almost there and there is a new, a new branch with some other design for the menu so that you can look into and decide which ones which one he prefers.

B

That's related to the website, then, on a site topic, I have been talking a bit with fuel about the red, hat's red at installation and so on. So he sent me some code that I unfortunately still couldn't look into, but we'll hopefully use these holidays to look into and to make the thing go forward. So it's all about.

A

Actually, nice to have an open issue about that.

B

We do have about the, I think we do have about uh adding the the actions for red hat and fedora, and so on.

A

Okay, so issues: let's go uh you.

B

Can see the ones that are sent to me or yeah just search, fedora search fedora. I think it's not right after I think it's center walls, centos and fedora yeah.

A

Yum based linux, district github actions, yeah yeah. Well, ah yes, that's for testing, that's uh to make sure that our builds work. Yes, okay,.

B

We have that and then I'm not sure you know if you want to have packages being built for that automatically or you know or if it is enough to say that if it works on these distros people can build it.

A

Well, uh honey.

B

I guess we can ask well.

A

I hope that foreign will get uh there at some point in time and then we'll have reddit packages, as he said he he was like yeah. He did either.

B

A

Or almost done with that, so.

B

He sent me a zip file, but I still couldn't look open it or look into it.

A

Maybe you want to create an issue for that and attach the zip file in there, so it will be like.

B

A

So I could maybe look into this. If I have some time or some somebody else, yeah.

B

So he said that he exactly yeah. I think it's about packages that he sent us. Let's see what we have there and even look inside now.

A

Yeah, you know, let's, let's not do it online. Let's just try to like understand what we are like supposed to be doing: okay, so uh yeah. So it would be nice to have an issue for that.

B

Can you open one or, but you have.

A

B

That you need to attach.

A

Okay, so how would you title the issue I I can't open it.

B

That's why I didn't open, because I don't know how to title it: packaging. Okay, let's see.

A

Packaging, let's, uh let's search for a moment, what do we have about packaging packaging, our clinics packaging? Actually, uh let's we.

B

Don't support, we don't support file formats, that's what github says. We cannot add there the what we see.

A

B

Can attach busy too, because they don't like we'll.

A

Get there so hold the moment so custom run time, debian package, reddit package, I'll open the new issue. I'm opening no worries.

B

You're open, okay,.

A

Yeah I wanted to do to make it later. No.

B

A

Not not to have this uh this meeting too long.

B

It's fine, it's fine! I'm doing it in parallel continue. Please.

A

B

That's it from my side, yeah.

A

Okay, so um here's the overview of open pull requests. So, as ricardo mentioned, we have this website refactoring, at which I requested changes so ricardo. If there is anything new to review for me, please uh re-request.

B

A

B

A

Changes requested that the status.

B

Okay, I think I did in one user, not in both maybe.

A

I don't know okay anyhow, so please do and another uh outstanding issue is uh macos man pages uh ricardo fix that and our only discussion which is left is how we test that. So ricardo was on that and I need to like. I had some comments and ricardo again if it's ready, please re-request the review um and uh hold.

A

Let me finish before I forget what I wanted also regarding our milestones uh since last weekly meeting, which occurred two weeks ago, because we skipped one since then there was no actually progress on the milestone, which is run aws in lambda, but I hope to resume this really soon.

A

That is the zero to 14 milestone that we are working on. Yes, ricardo. You wanted to say something.

B

um Yeah yeah, I will open on that one.

A

I see there's one more issue: the packaging yeah.

B

Yeah about that one with the ah that you just talked while.

A

Yeah files, you added files, folder how? What is this files? Where is it stored.

B

I don't know it just uh dropped, drag and drop there, and they they put it somewhere. For you.

A

Okay, okay, so I started the repository okay.

B

No, I just I just put it there and they upload it somehow interesting yeah.

A

B

Yeah about the man, the man part, we I removed it from the actions uh because well we could add it to the actions, but I need to do some more things. There.

A

Sorry I missed that.

B

The testing, so you, the testing of the man, is set to create a new, a new make file. For that I did you.

A

Know who did it.

B

New make file entry target yeah! That's how yes.

A

B

So I added that so the only thing that is missing is basically to run it now in the test, so in the build. Basically, we do the the actions we need to run. That is still not there, because there is some extra things we need to do under the docker files in order to allow the man to work.

A

Well, I uh I don't know if you actually want this month to be in doka, because you know you mentioned that it doesn't come with man and maybe maybe we shouldn't do it either. Maybe docker is supposed to be that slim and not have one.

A

So what I think we can do about this in each installation where it is actually okay and which has one uh we should do the test in.

B

A

Installations, we don't need to do this test.

B

Yeah, so I don't know so we can we can check. I think there is also a way to activate the man on the docker files, so we can just activate it for the test and see how it goes.

A

Yeah, we need to decide whether we want to package man at all.

A

I need uh I.

B

Think about that.

A

What we need to to see uh if, in this docker other packages, other languages actually package men and if it's only the binary of man command, is missing and we.

B

A

Need to package my pages: if everybody else is not packaging them on pages, then we also don't do that.

B

Yeah, that's fine for the docker version right, but I was thinking for testing right. If the money installation works, we could add to the actions that test right. The that's test, installation. You know when we.

A

B

Right build and whatever uh that test installation there we could also, you know, activate the demand just to test. You know if it does install man on all the systems correctly.

B

So it's not for packing right for packaging for release right on the docker file. It's just for testing right.

A

I don't know we need to think about this. Okay. uh Actually, it would be nice to summarize all open issues with this. What.

B

A

B

A

Okay, good, okay,.

B

A

I guess you're like.

B

Done yeah yeah.

A

Done for today,.

B

A

uh Cool okay, uh thanks for watching, I think.

B

A

Sharing and stop recording ah what we forget as youtubers dude. What we forgot yeah subscribe like.

B

A

B

And subscribe, yes, okay, see.