GitLab Developer Evangelism Team, 11 Apr 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: How to Open Source YOUR project

Description

We are going to Open Source a project and discuss how you can do it too! With amazing guests...

Laurel Younis https://twitter.com/LaurelYounisDev
Michael Friedrich https://twitter.com/dnsmichi
Matthew Codes https://twitter.com/matthew_codes

Repo + Org https://github.com/XollabOS

Discussion on GitHub https://github.com/EddieHubCommunity/support/discussions/3800

I now have a 2nd YouTube channel for short video clips of 60s or less, subscribe...
https://youtube.com/eddiejaoudetv

JOIN our inclusive open source community now for FREE... https://www.eddiehub.org, also checkout my website and sign up to our community NEWSLETTER... https://www.eddiejaoude.io for my live stream + video schedule and community calls

Reviewing your Open Source projects #OpenSource #GitHub #DevRel

SERVICES I USE AND RECOMMEND

Some of these might be affiliate links, no extra cost to you, but I get a little $ if you sign up, plus you might get a discount too.

- Live streaming with Streamyard http://links.eddiejaoude.io/t/pYlzGjcta1a4
- Cloud hosting with Digital Ocean, you will get $100 FREE credit http://links.eddiejaoude.io/t/EAaCRWhsnZlF
- Membership, Newsletters, CRM all in one with Kartra http://links.eddiejaoude.io/t/pQ5W3FRLk8Cp
- Awesome backup platform, BackBlaze http://links.eddiejaoude.io/t/4rqTZjLbwmCp

COMMUNITY SPONSORS

A BIG thank you to my GitHub Sponsors:
***
Stephen Mount http://github.com/stemount
DailyDotDev https://github.com/dailydotdev
***

- Nicholas Carrigan https://github.com/nhcarrigan
- Santosh Yadav https://github.com/santoshyadavdev
- Andrew Cunliffe https://github.com/andrew-cunliffe
- Alexander Stoichkov https://github.com/SashoStoichkov
- Allan Regush https://github.com/AllanRegush
- CORE Multi-Chain Framework https://github.com/CORE-Blockchain

FIND ME ON OTHER SOCIAL PLATFORMS

Don’t forget to support my channel by subscribing below, it’s free, and also share with your friends. Subscribe now!
https://www.youtube.com/eddiejaoude?sub_confirmation=1

Follow on other socials for behind the scenes footage and join the Discord server to continue the conversation.

https://www.eddiejaoude.io/
https://github.com/eddiejaoude
https://youtube.com/eddiejaoude
https://twitter.com/eddiejaoude
https://instagram.com/eddiejaoude
https://linkedin.com/in/eddiejaoude
http://discord.eddiehub.org/
https://github.com/EddieHubCommunity

How to Open Source YOUR project

A

A

B

Hey everyone welcome happy monday, I hope you're having a great week. It's just started depending where you are in the world. I hope you all had a great weekend. We have an exciting live stream for you today super fun. I am super excited. It involves I'll give you a clue, involves open source, green squares and awesome people, and let me give you a bit of a backstory, no I'll. Let other people give the backstory, because I can't remember very much about it, but let's do some introductions.

B

um So let me start. I have got a list. I've made note, so we have laurel with us um who's an inclusive tech leader and a software engineer and laurel has started an amazing app and I'm gonna. Let her explain a bit more about it and why it's an amazing story. I can't wait to get all of you involved in this open source project and then we'll move on to uh michael michael is um a devops. So in dev forget that right engineer from gitlab.

B

You know I all talk about github, so it's great to have a different perspective and point of view and I've been really enjoying geeking out with michael and we also have matthew as well who's all software engineers me working on this project too. So, let's uh enough for me, let's head over to laura first laurel, please give yourself an intro. Tell us a bit about uh your project.

C

I'm laurel eunice- and I am a software engineer going through the 100 devs cohort right now, um so the project came about because when my I have a kiddo on the spectrum and when she was younger, she needed to use a digital communication board to communicate with our family. um She was non-verbal, and so we needed to purchase a software and at the time it was extremely expensive.

C

For myself I was a single mom of three and um it came down to either purchasing this expensive software and I've had to win it off of or paying the power bill.

C

That month and I obviously chose the communication with my daughter and yeah- that was just a really big economic barrier, and so when we were in a class learning javascript, I saw the speech api and realized that I could build out this digital communication board software and put it out there for free so that nobody will ever have that economic barrier to access uh digital technology communication boards again- and so that's where the idea came from, um we built the mvp now and we're moving forward on working on iterations to build out the product, bigger and better and more functionalities included in it and um yeah.

C

It's just basically to eradicate economic barriers. There's barriers and other spheres too, like licensing for education, um has to pay licensing fees and different professionals have to pay licensing fees and we want to make communication accessible for all and we want to get rid of those fees. So this product will do that and that's our goal and that's our hope and yeah. We want to open source it so that other engineers can get involved with this project and help us move towards that gold and provide a product that will help others communicate.

B

I absolutely love that I'm just gonna jump in there and I'm gonna, I'm gonna share my screen. We are gonna, get back to interest, but just to add a little bit to uh what laurel was saying. So um let me just bring up this tweet that you did um laurel for people just to give an example of what it what it is. So um is this your product that I'm bringing up on my screen a little video clip.

B

This is your one, so people can get an idea of what it kind of looks like and we're going to be, adding this to the readmes and getting everyone's community's help with this, and so on so perfect, just to give people a bit of a visual idea of what we're talking about it took me a moment when you explained it on a twitter space which michael will talk about in a moment. I couldn't visualize what it was so yeah, perfect.

B

Okay, let me stop showing my screen. We are going to get back to my screen in github in a moment, um michael over to you.

D

Yeah thanks, um so I'm a senior developer when she listed gitlab and I'm super inspired by open source everything around it and like sometimes I'm replying to eddie's tweets with my own ideas and my own helpful resources, and I I don't care whether it's like github, gitlab or whatever platform we use. um We should be using with them what we are the most confident in and like working together for a greater common good.

D

I would say- and this kind of inspired us to host the twitter space like getting started in open source um and I thought of like it would be one hour something and I think the recording is two and two and a half hours actually, so there were really great and inspiring questions and um stories and when eddie uh pinned the tweet from laurel in the space- and I was like- oh let's look that looks amazing and I totally want to learn more about it.

D

I'm not a front-end developer, so it will be hard for me to contribute in that area. But I really want to see this open sourced and I also want to hear laura speak about it. Tell her story. Maybe give a talk at a future event or something like that, but those inspire the community to like make it open soon, so that everyone can contribute and um yeah like making new friends all over the world, which is which is I'm now repeating from the space.

D

um This is open source for me, um making friends all over the world like the uh the four of us now, and hopefully everyone who listens in um yeah and this this is actually the story behind it and I'm super happy to be here today, even though my github is a little rusty sometimes, um but I'm also here to learn myself. So let's do this together and handing over to matthew.

B

Thank you. I want to interrupt again. I want to say you're, absolutely right, we're all here to learn. You know, I'm happy to start the conversation and bring you all together and we're all here to learn, including myself. So I can't I can't wait to geek out with you and we are going to be doing lots of githubby stuff. I'm going to interested to see um uh the difference in how you know. Maybe things would happen in gitlab as well. We could kind of slip those in a little bit just so again.

B

We can learn more about some alternatives too. So uh super excited sorry.

D

I just saw- I just saw that andrea was in the chat um we. I just want to give a shout out, because we had a conversation, hacker news and I helped him uh bring up the uh lee app, which is another open source project. I also did a review and um yeah this. This is just another example of why open source is awesome.

B

That sounds great. I love hearing these stories matthew over to you.

E

Hey everyone, I'm matthew, mitchell. um I am a software engineer and I'm also going through the 100 devs cohort right now. I've been working with laurel pretty early on, we've been just exchanging ideas, helping each other out getting through.

E

You know our small trials and tribulations and all that stuff and the, and uh when I saw the project I was super inspired, um because I've worked with uh behavior as a behavior late in the past, and I've seen this technology used, but, um as laurel stated before, there's always pay walls to it and I've actually worked with uh one of the children I worked with. They couldn't afford once they literally just had a laminated piece of paper with words on it. He would just point to the words on it.

E

You know so getting something like this, where you can take any device and make it into a communication board was super inspiring to me, and so I was asked to help. You know work on some of the code, uh try to make it a little more dry. So that's where I came in and I've just been loving the journey and having a great time helping out with this project.

B

That sounds awesome and I can't wait to show everyone that there isn't much so far in terms of the github-ness.

B

There is the project there we're going to hopefully hear a bit more about it, but if I, if I show everyone why there's so many green squares is because um this organization was just created um only a few days ago um by laurel and matthew- and I did say to them- don't do too much on it. We want to do it on the live stream.

B

We want to get the community involved, so I saw I was looking at this about 30 minutes before the live stream, and then this pinned item came up and I messaged lauren laurel. I think you just pinned something it just popped up on my screen. As I was looking at it, she was no, it's probably matthew on the live stream. um It was great to see that kind of you know asynchronous collaboration and we're keen to when we go into the project.

B

We've got only two contributors at the moment. I'm really keen to get all of you in the audience in giving us your ideas, suggestions and getting you on this contributors list as well as you can see, as I mentioned before, the readme could do with like a screenshot or a video, or something like that, and you can get involved by raising issues on these um call requests we're going to go through all that. So don't worry, you're going to learn, lots and.

B

So um did I miss anything or shall we get started? I'm.

D

B

Everyone ready in the chat well before, if everyone's ready here and in the chat, if you want to follow any of the my amazing guests, their link to their twitter is in description below you can check it out now or later, but do go check out what they're tweeting about and follow their awesome journey. um Open source, 100, devs gitlab like so many things, go check them out and you can learn more about it. um So we we have a. We have a question, so um we should give some shout outs.

B

Actually let me give some shout outs and then, and then after we have some questions and you'll understand. Why that's an important question so hyperduma you're, the first one. I see you already raising issues. I think michael someone mentioned, um which I think is epic, predominantly always so supportive emma great to have you here emma, I hope, you're feeling better by the way I hope you're resting as well.

B

I know you've got a lot on at the moment, but thanks for being here, uh I'd be shay because we're awesome to have you here, michael um daily tech, sabrina awesome to have you here as well. I can't wait to geek out with you uh andre as well yassen, so many people um shasmita awesome to have you all here, can't wait to kick out. So, let's get started so abby sheikh asks. Can we get a brief about this project?

B

I know laurel has just done that, but I think that really highlights that we probably need something like here that gives an intro about what it is. I just realized it's covering michael's face when I put that on the screen like that is someone is streaming open source. We need to raise a bug. I think I don't like that. I'm sorry, michael! I can't I don't think I can do anything about that. um If I can it's funny.

D

B

D

Just follow me on twitter: instead, that's it.

B

If I could move myself to the bottom, then I will, I don't know, unfortunately not um okay awesome, so people are keen to get some green squares, okay and get con contributing. Okay, great, to hear uh jordan um great, to hear emma too as well and mikhail has just joined okay great, so I think you know we're looking at the organization I mean, let us know in the chat what your first impressions are. My first impressions um are would probably need like to customize it. What do you?

B

What do you all think laurel matthew and michael.

C

Definitely so um also, maybe to answer the question about: why is an organization, and not just a project, might make sense too right.

B

Sure was there a question about that? Did I miss it? Sorry, I probably did.

C

No, but I think that it might give more of an overview of how to I guess, make the face if we're doing like different things on the organization profile, it would make more sense to kind of know why it's an organization versus just the project itself, but maybe.

B

Not no, please go ahead. That's great.

C

So um in doing this project we were talking about if we wanted to collaborate on further accessibility, technology projects um or other projects in the future and uh matthew, and I both realized like this- is a really important sector and there's a lot of paywalls in this sector and it costs a lot of need for accessibility technologies and there are other projects that we want to do so we cl we created this organization to put the projects that we will continue to build out in other spheres and other things that we're doing under the organization.

C

So if you don't want to or don't um aren't able to contribute to the talk to me technology project, there will be other ways that you can contribute as well in the future. Exactly.

B

That's great, I mean, I think, organizations for these sorts of things make make sense. You get better kind of more uh customizable, um adding members to different projects with different roles and responsibilities, and so on. um So let's let's get started. um Okay, so I'm going to create a new repo, and this is going to be so we can customize in this special repo. So we can customize this this home page. um Hopefully it sounds good to all of you.

E

Yeah I was going to do this the other day and I'm glad I didn't.

B

Yeah, I'm glad you didn't as well. Let's do it on the live so.

E

Yeah, that's what I heard. I was like. Oh yeah, that makes sense.

B

So uh everyone look and you'll see: uh we've got a pinned repo and we've got the same repo down here and if we look over to eddie harb, which you're all probably a member of you can see, we've customized this already at the top here, and this is done with a special repo that is called dot github.

B

So we'll do the same for laurel's um organization a lot I should say laurel and matthew's organization to create a new um repo and I'm going to say it's called a dot github there we go, and it even said this is a special repo.

B

Let's, uh let's do this again the description, so I think it's always important to have. I will leave this and I can let others uh fill it in as well and we should add a readme, I'm not going to add a git, ignore, I'm probably going to add a license for the for the moment as well.

A

B

There's going to be any code in this project, it's just going to probably be a readme file, so let me hit create.

B

And now we've got that. Okay, that doesn't look like a great title, because you know if we, if we go back to the organization in theory, it should appear, it might take a moment to appear for the first time, though, if I remember correctly, anyone let me know into the chat uh if it does take a few moments to appear, but while it's appearing, we should go in and change this.

B

Someone else can change it in the audience as well. What should we include on this readme? So now this repro is created. I want to I'm going to share it in the chat as well. um So now this repo is created raise some issues. uh What we should like description- um it's not so much about uh it, should be the organizational level. I think what do you think um laurel, matthew and michael? I I think, because this is the customization kind of of the organization.

B

We shouldn't put anything project specific in this, because they're going to be multiple projects in the future.

D

I think, like a description which says um this is the home of all accessibility projects in the future. Something like that, like one sentence telling me that why this organization exists, um I think you can customize it further with a project url in the settings, but I'm not deeply familiar with it. um Just just so, you know what it is about and if there is like you can you can add your social handles to say: hey, follow me on twitter.

D

Follow me on linkedin or something like that, which is a good great way to to make people aware of it um yeah and then, maybe, if you want to promote the specific project, so thinking in the future, you might be having 20 of them, and you really want users getting started more easily pinpoint the getting started in in the organization description so like starting this project. If you want to learn more about specific technologies, go over there and so on.

D

um This could also be done with uh with pages set up on your own domain, of course, um but potentially uh people will also find your organization on github and and can see it there as well.

B

Sounds good: we've got a lot to do. Let's get started and purduma is always as always giving great feedback and has noticed that I've made a mistake. Already. That's fine we're going to fix that. So thank you. So much and I see emma has just raised an issue as well. So if I refresh this, we can see the issues climbing and also tom has also mentioned. We should start hiding things that we're not using as well so many great feedback. I love this, so I'm gonna conscious of times.

B

I want to go quick through some of it. If I miss anything or want to go a bit slower people ask questions in the chat. um The other people on here can also give their thoughts and feedback to your comments into what I'm doing. um I will try and drive at a hopefully a sensible speed, so I want to do what tom suggests first and let's, let's hide the stuff. We don't need so this project, probably won't have releases, won't have packages. So, let's, let's hide the stuff that we're not um not going to use.

B

If we ever need it in the future. We can obviously add it back, so I'm just going to hide those and hit save so they've now disappeared from the right hand, side we've got wiki up here, project board, I'm probably going to hide those as well again we're not going to use this for the customization of the organization.

B

So we're going to hide the wiki documentation is really important and we're going to get to that shortly. Issues will keep because we want people to to raise issues uh laurel. Have you set up sponsorship, yet I thought I think you had. If I remember correctly, I.

C

Started it and then I have to link the stripe account with it. So but we'll.

B

C

Ein from the irs.

B

Okay, so I'll leave it off for now, but in the future you can enable that on so a button appears as well project board. I think we'll we'll turn that off for now again, we can always enable it in terms of discussions. I think it makes sense to to leave it off. um So if we go back to this project again, you see the tabs now have reduced in in numbers. um So we don't.

B

We want to show the the features that we're going to use, but the ones where we're not, let's, let's hide them as well. um Okay, anything else I missed on that any suggestions from all of you are we looking good so far.

C

E

Looks good to me, but I'm also new to the org stuff. So I'm learning with everybody.

B

We're all learning, so it's perfect, let's uh um tom, loves the twitter handle by our names. Perfect. I'm keep I'm not bringing up the comments for too long because they go over michael's face and I feel so bad about it. I don't know how I can move myself to the bottom. Let me go, but my face is fine. Yeah.

D

Just let's focus on getting things done and then let's worry about my face.

B

I love that um okay. So, as praduma pointed out, I need to put the readme in the profile folder, like I thought, on the eddie hub, not in the root, so the root is for the um read me of the project. So absolutely good point. um I completely forgot about that. I've done it once and never again. So what we can do is uh add this file. I'll, add it as I'm showing my screen. I suppose, um and then we're gonna have different content in this readme and then different content in um the profile folder.

B

So I think it was profile that correct you see profile and then readme dot, n.

D

I think that's a great point, um especially when you're getting started. You can look at other open source projects as an example, because I always forget the different paths and it doesn't matter whether it's github, gitlab and or something else. You can just like look at the popular open source project and see how it is done there.

D

You are not you shouldn't, be copying everything, but for this specific thing, just look it up. Maybe the documentation is not that clear and just copy that, and once you have created the first project, you can always like copy paste in a specific sentence to to future projects or just use a project template or something something similar.

B

Exactly I think, it's great for templates um for how people have set things up with maybe ci be you have actions or git lab ci. I don't know what you call that by the way is it just git lab ci, then.

D

Yeah um the thing is, like you said, specific things where you need to reinvent the wheel: um try to keep a project template or a central um project where you store all the things, and then you can source from that. We will come to similar things like greet me and contributing in other documents.

D

um In previous times it would have been copy pasted on the cli. Nowadays we can like just clone something or copy it over, and uh everything can be done in the browser, mostly, which is a great thing.

B

Yeah so much we're doing the browser, I think that's epic, um okay, so we've got admission statement created by emma. So I can't write this so I'm going to leave these issues here and it's probably going to be um for laurel and matthew to um to write something. Maybe they can write something now like a one-liner to start it, and then it can be the first iteration and improve on it. um So maybe that's a possibility too.

B

I go back to. Let me create this far once you got this far, we can collaborate it on it a bit a bit more. um Can you give us a one line, maybe laurel? I can write like about the organization.

C

Yeah, I think that um our goal, our mission is to eradicate economic barriers to accessible technologies for their users.

B

I'm smiling there's a lot of big words that I can't remember.

C

I always go like yeah in.

A

C

Maybe matthew has an idea of how to speak.

E

Yeah, it's basically we're trying to remove pay walls, yeah.

B

I can still pay walls, two words to one I don't know pay walls. Oh.

E

It looks like it's one, we'll let the computer, let us know either way.

B

Okay mission to remove pay.

E

Accessibility, technology from.

B

D

Yeah, that's great because you can always iterate later on on a better phrases exactly.

B

A

They are big words: okay,.

B

Okay again, this can be absolutely iterated on so I've created that and let's go back to this page, give it a refresh okay. So it's appeared so we've got something appearing, and so now people can iterate on this and raise issues and so forth.

B

Okay, lots of great stuff um completely agree and a pull request has come in, but we'll uh we'll send to the org name. Well, people are fast notifications for all of you to go through um it's a new.

D

Issue race, one thing: um so I'm missing uh permissions right now on the project. If.

E

You can fix.

D

That I can merge, pull requests and send in myself.

B

Let's do it so what we're gonna do is we're going to head over to teams, and I see laura's already lori laurel or matthew, you've already created maintainers and there's four members. So um it's the four of us, which is great, um but we need to add a repository to that team. So they've got access. So what I'm going to do is I'm going to add the repository which was called I'll, find it talk.

A

B

Autocomplete and there we go, I want to add it to the teams. The team has access, but they've only got read access at the moment, so I want to put right access. There are other things that people can do if you want admin, maintainer and so forth, but right should be enough. I think um I suppose you want to manage maybe issues and pull requests. You can still merge pull requests with write, but let's just put maintain for now, just especially for this live stream, and so now you should all be good. um Michael.

B

Is that correct.

D

I think so and for I think we need to do the same for the github repository as well. That's.

A

D

The thing is, if you want to get started with a group of friends or something, this is a great way to really handle it, create a team um in in the organization and then assign the the permissions for the specific teams um could also be like something. One project is front and one is back end and you want to like split split up the maintainership and the permissions and do something um but yeah thanks for fixing my permissions. Now I can do something.

B

No, that sounds good and then matthew is going to hate me. I want to remove the pinned repository um just so we can get more of that. Oh it comes up with popular. I wish you better hide that I think I don't know.

B

I think that when you get like 10 repos, you might want to pin like two, but when there's like only like two, maybe we're going to pin it, but I was trying to make more use of space, but I did a terrible job, because now it's showing popular repositories in settings, we can hide that. I'm not sure we can look at that later on. That's not important. For now someone can raise an issue on the dot, github, repo and maybe say hi popular repositories. There must be a way to do it.

B

Okay, what is uh what is next?

B

We've got some comments coming in tom ray's that raise an issue on the on the repo great suggestion. Another thing we can do so we've got this. This read me people to customize lots more stuff coming in there. I think it's going to be great socials as well, so maybe for now you might want to put laurel socials. So therefore she's posting about the project.

B

um Another thing you can do when we go into the actual repo, which is where we're going to spend a bit of time on um is you can go to the insights tab and then we can go to the community standards and we can have a look at what's missing. So if people want green squares to raise issues and raise pull requests, we need to code a conduct, we need a contributing file again. This can be like one line contributing file.

B

It could be any questions, start a discussion or any questions asking discord. So you might want to ask that question an issue and see what the maintainers come back with and then you know you can raise that file with one or two lines, and then people can iterate on that file license and issue templates.

B

um But before we get into that nine stars already looking good, we get into I'm just gonna hide some of these things again. To make it easier for people we will. Hopefully, get to releases, um I'm really a big fan of releases. um Michael did you say you weren't? I can't remember. Maybe I've just made that up in my head, or did you come up with an alternative way of doing it? For some reason, I remember I was having a discussion on releases, I think, or maybe it was the automated ultimate automation.

D

Yeah, it was ci cd and automation um things, but we can just enable it at a later point.

B

Okay, so now we're on this repo are you? Are you all happy with the um the status of the org for the moment and we get onto the reaper? What do you think.

D

Yeah, I will create a pull request right now for adding the twitter handles to the org description, um but we can move on to the project.

B

Do that and we can review that on the live stream, show people um how to do that and then I'll raise another pull request again to show people how to how to contribute as well. So I think that'd be good. I didn't I created this change directly to the file, which is really bad people you shouldn't do that, but uh for the sake of time, I'll show you something more more interesting. For the sake of time, such famous last words.

B

Do what I say not what I do. I think it's, the other other expression. um Let's go back to this, this repo I've hidden, some things on the side and we'll give a refresh if any more issues have already have come up, no more issues and let's try and get some more issues. So we need a screenshot uh to the um to the readme and other issues. Someone can raise.

B

Someone can raise creating a release.

B

Well, someone gonna say something by the way, so I was on a different screen, so I couldn't see if someone was gonna speak if you, if people are gonna, speak just interrupt me because or if you see something in the chat, let us uh let us know um as well um loving all this all the collaboration, the chat already yeah.

B

Okay, so what shall I do? Next? um Oh yeah. We've got a nice description here already as well, which is awesome like that. um So someone can add, maybe create a release. I can do it manually because the last change that happened was three days ago and I'm guessing the the state of the of the project um you're both happy with, like the current state of the project, you yeah, that's, maybe correct release and does everything.

E

Big stuff changing anytime soon we gotta we did like a big refactoring of the code and I feel like it's at a good. At least, like you know, minimum viable.

C

E

Right now, yeah.

C

Good mvp for now- and we really want to do a lot of user-based research to develop the product around the research and the data that we get back versus like. Oh, we think this might be a great idea. Let's do.

E

C

And then we're going in the wrong direction so yeah, that's another thing that we're going to definitely be focusing on is getting feedback.

B

Sounds good and as um abhishek mentioned, there's no deployment. I I think there is a deployed version somewhere. Is that correct, add a link to the the repo, so people can find it so uh laurel. If you could send me in the chat or stream you're the link, I can share it in the in the chat on youtube, because youtube will remove the link. If you share it um and then I can add it to the repo as well. Aha, um perfect and then labels people asking about labels.

B

So I want to do first before I forget. If someone could raise an issue um for a release, we haven't got one yet, but I'm gonna do that and people can raise it um kind of um in the past. So what we will do is um go to the tags and go to releases and we will create a release, and I want to automate this later on with github actions, we'll see how time goes, but for now I'm going to do it manually.

B

um So let's create a release and we'll take it from the main branch and then we're going to give it a release. Name. What? uh What are you all your thoughts on release names, I'm kind of a fan of like that? I don't know what you will think yeah.

C

I, like the number system that you were telling us about before that, made a lot of sense.

D

Semantic versioning makes sense.

A

B

I'll do it manually for now, but we will hopefully get time to automate this. If now, if not, we'll do a part two and or do it asynchronously as well, so I'm gonna do it manually. For now and in the description, what can I write in the description? uh You just said you did a refactor matthew. So can you tell me a little bit about that.

E

Yeah, so when we, when the project was initially started, um we didn't have much javascript knowledge, so it was a lot of copy paste, not very dry. So I took what was, I don't know over over a thousand lines of code of javascript and refactored it into a constructor so that it went down to like a couple hundred lines of.

A

E

So that it, you know just instead of having to redo it, we just made a script that did it for us, um because you know we're still learning as all this stuff is all learning process we're having a great journey with it. But you know with that comes a lot of. Oh, we probably could do this. We probably could do this instead of you know, make it dryer uh easier on the browser that kind of stuff.

E

So that's the kind of stuff we were working on with this refactor is just make it smaller, make the um html size smaller. All that stuff.

B

Okay sounds good, I'll, try and write some notes in and again this is usually automated from uh the git commits um as as tom mentioned, but for now I'll do something just as a starting point. I change it to number two, because you had that kind of it sounds like you had a point one before so this is. I feel this is a point right.

A

B

Was a major but I'm not gonna get into anything. You know two we'll just start from two yeah.

E

That works for us.

D

Can you do a past release from the ui from uh from a different.

B

Community, you can yes, um let me come back to this one. Then it's a really good point: you can you can do it from a commit, but I don't know if it was all done in one commit or it.

E

Was multiple yeah we had to? We were messing with little pieces and realizing.

D

E

Oh, we should have done this and you know it was.

D

uh Yeah you, you can do it async, um maybe on the cli, uh just like figure out the uh the old commit which marks the version. Do a git tag, push it and from the git tag you can create a github release um as well.

B

So I haven't done that before. Okay, that's interesting, I've always done it from from branches rather than from from commit. So it's interesting that yeah that's possible. Yeah.

D

From like from my experience, sometimes when you're releasing something um you might have forgotten to tag something and and from there it's um it's an easy way to fall back to the raw git, cli command line and check out the branch check out the commit and tag specifically. It is this commit when you push it github and also gitlab marks that as a git tag and from the tag you can create a release. So um just for an additional context. A git tag is within the git repositories.

D

Whenever you clone it and you clone it somewhere else, you have the tags available. A release is proprietary in that sense, so it exists on github. It exists on gitlab and it's an add-on to uh to kit itself.

D

So it's like linked together and knowing that detail, helps you when you have to migrate between different systems and just want to rock it get repository information, but for.

B

D

It's not really necessary.

B

No, that's a really good point and thank you so much for clarifying that. So on that note, you've given me an idea, so what I'm gonna do is if someone could take a screenshot of this and we'll pose tag us on twitter and include that tip. That michael just said, because that was epic absolutely right on github. When I create a release, it automatically creates a tag and git.

B

So when I clone it, I get kind of the release but more the the raw git, not the extra fidelity or extra features that comes from github, and so I treat them to be the same. But you know michael's absolutely right. They all are different. I think that's really important or something I don't talk about enough on twitter. So um great point michael and although I knew that I feel that I forgot that so that refreshed my memory. So thank you so much um someone can do that.

B

um Whoever's is the best I will retweet to almost 50 000 followers as well, so tag us and we'll we'll do that, so everyone pose he will take a screenshot and uh and then put that at that value. Remember everyone listening! If you take the screenshot and put on twitter tag us and add that value, um so I can reshare it a live stream. Okay, perfect!

B

D

All pausing is the thing we can do best. I think.

B

Okay, I'm going to publish this release. uh Oh did I not oh, um create a new tag on publish there. We go that's.

D

B

That never used to be there interesting.

D

I think previously it was done automatically but yeah um in in a sense uh you can verify the linking if you like, clone the repository and run a git log on the cli.

E

D

See the tag or you can also do um git show and get show and attack version so like.

B

D

And then you get to see the details which is actually being um stored in in the kit repository itself. um I can dive into that because I was a kitten gitlab trainer in the past, but it's it's a it's a detail to know when you're cloning something and wondering hey. Where are my releases yeah? They are in github itself.

B

D

Know that there is a cli for github on, I see, live for github as well or specific other local clients and ides include that and hide it away from you and you shouldn't be caring about it unless there is something which is not working, and it's often good to really like know the git basics um to to debug or ask a friend to debug, which is more fun.

D

B

I've just noticed so many new features here. It's got auto generate release, notes which is really interesting, something I have to look into later on, um and this is create new tag. I might have found the bug, I'm not sure, create new tag on publish and click. Add it's not doing anything, so I'm guessing that must be tied into this auto generate part of like similar to a github action with some buttons.

B

But my concern is: will it let me do it manually, which I'm pretty sure it should, and I haven't seen this something I have to have to look into afterwards- make sure you have a valid tag, but um unless it does it the other way around. um So maybe.

D

You need to create a tag and then a release which.

B

I've never done in the past. So that's uh quite interesting, um yeah. So either it's it's a bug or it's a feature. Maybe it's a feature- and I haven't done this manually in years so yeah interesting. If someone.

A

Could raise an.

B

Issue that'd be quite interesting. Let me see.

D

The repository and manually push attack.

B

uh If someone could uh someone who wants a green square on their profile, raise an issue on this repo saying create release but also include creating the release manually, had an error um so do that and we can. We can look into that. Maybe afterwards you don't like all get bored while we're struggling with that so uh mikhail matthews twitter should be um in the in the description um below otherwise. Actually I can drop them in the chat as well uh our producer's helping me again. I think, let me see.

B

Maybe we um did I do something. Did I not add a name? Was I being really like silly, which is probably the case, um the pressure? Let me try again so if I create a new release, oh you actually add a name right got you I was. This is the release name. This is the tag name yes, you're right. I always have them the same as part of the github action. So thank you. So much for duma saving the day again so release I could put v 0.0.2, but the actual tag shouldn't have the v.

B

If I remember correctly, it should be 0.0.2 yeah, okay,.

B

That's the one, thank you so much for doing it. You've, you, you saved my life because I.

A

B

Feeling a bit like what am I doing in my defense, it's almost tuesday for me, so I'm kind of like you know.

D

It's it's just. I didn't know that either so interesting ux should be improved.

A

D

So I won't push the tech then, so I had it prepared on the cli already.

B

uh Okay, thank you so much for doing that, though, but you're right, you raise a good point. You can create a tag locally and push it up and then what will happen when you do that? um I.

D

Can I can show you with a different tag.

B

Here, rather than under releases, so with releases just going back to what michael was saying, I created the release. So github has created a tag for me and you can see it matches with the name that I mentioned.

B

But if you create a tag on the command line, you'll get a tag but not a release. So just something.

D

When you press refresh, you should see.

D

To version 3.

B

So I want to refresh the releases and it shouldn't appear and then if I go.

D

B

It should appear there, you go.

D

B

D

Used the version thing, that's.

B

Fine and then you can create release from here. Okay, so you can then do it from there. So if you're ever on a plane, you haven't got internet, you want to create release locally, you can do it, you can push it up when you get internet and it looks like you can create a release from here to have the extra kind of.

D

You can also delete it from the web interface, so there's a way on the clr as well, which is a little complicated push.

A

D

Into an existing ref.

B

D

Which is super hard to explain on on the stream, um but the other thing is since, since you can manage many things on the server side already, it makes more sense to really navigate in there and press on the delete or purge button uh rather than.

B

Sorry, michael thanks.

D

On this year, right skit tag, dash d and then the tech name, and then it's gone as well so yeah. Sometimes you might be making a mistake, which I did often in my past, open source journeys and then it's. Then it's really up to really um delete the tag in a speedy way, because some folks have watchdogs on the repositories and then they automatically publish something. And then it's basically you. You cannot delete it.

D

When you delete it, you're breaking build process which is not nice so like, instead of deleting a tag in the future, just take a new release and just increment the number by one or make it a new revision or at maybe the the current date or something which makes it a unique identifier.

B

Exactly and one thing like we do with you know my client projects or any car projects is we don't really roll back, um because it's so quick and easy to make a fix and it just deploys out within minutes. We always roll forward. So we'll get a new release, we'll get a new container build and then we'll deploy to our kubernetes cluster, it's easier than trying to unpick stuff and wind backwards, we'll just roll it forwards. um So yeah we'll automate as much as possible.

D

The mini mini workaround trick is more or less you add an empty line to your readme or to just some file commit that and then you have basically a new version. You can tag if you want that or you have sort of um changelog generation or something else uh which, which also makes the release happen but yeah in the past. We deleted text nowadays we'll just roll. The next release.

B

Exactly and yassin, thank you so much for talking about the release number as well. um For that help, I'd love to hear that tom has run lighthouse um and apparently amazing scores. So that's great. There is a lighthouse action for github action. So if someone can create an issue for that and create a pull request for that, and if you want to know how to do that, I think we have it on. Is it a link free project on any hub? I will show everyone um that you can go to linkfree.github workflows.

B

uh I thought we had it on here on lighthouse. We maybe we don't, um but there is somewhere. I know someone in the community will answer in the chat. One of our repos has it and it's just going to be copy and paste um so do go. Do that add that to the pull request and we'll get that merged in and watch that start running as well, I miss anything in the chat. uh Let me see.

D

Yeah, you were talking about issue labels, I think in the beginning. This is something where we can continue.

B

That is true, so this is a discussion for all of you. Then there's different ways. This can be done. um We can create the manual, let me bring them up on the screen which we've got so we've got all these issues, loads of stuff, loving that um and there's the default labels that github creates for us.

B

um You know they're, pretty pretty useful and you know pretty good. However, you can get you can create your own ones um and there is an open source standard for labels that we use again in eddie hub and we use a github action to create them because it might be like 30 of them. um So what about? What are all of your thoughts on labels?

B

Labels are a great way for not only for people to understand, like your issues but to discover your project so when people search at the top for github and they go to issues and they do a search, um I default shows you mine, but if I search for label um good first issue, maybe with python- maybe you know javascript or whatever it is um oh, is it not got a space or something I can't remember highlighted? I can't even remember now very bad of me. I should have prepared this beforehand.

B

um Okay, there we go okay, so there's no space after the code on my map, so these are all projects on github they're searching across the whole of github. So you can then add multiple labels. If you wanted, you know enhancement or you want to fix a bug, combine it with a language and so forth.

B

So there's lots of lots of issues on github, and this is how people discover your repos.

C

Yeah, I think using labels is brilliant. I think that's great. It would be a great idea to use labels.

B

uh Okay, let's do that and then another green square. Sorry michael, covering your face uh emma rightfully points out that we haven't got uh lighthouse action on link3, yet so another green square for someone as well. Oh, it's still a pr okay, so there's an example for someone to to copy it as well um carl. Thank you so much for for joining uh okay. So what label should we do? Do you want to create your own one? Do you have any in mind, or do you want to use maybe some some standard ones.

E

B

C

B

E

C

Yeah I'm looking through these labels and it looks like they're pretty decent for things that we'll start using them for initially, I think as we go along and progress and needs things specific to the project. We could create, like our own labels, for that, um but other.

E

B

C

Think the standard ones initially.

B

Let's, uh let's do that and also carl has uh pointed out that carl's got so many awesome projects in any hub. We have a project which is good first issue project. So if we add the label um eddie hub good first issue, any issue that you um add that label to it appears in in the project on edith as well. So you get more visibility for your context, so.

A

We'll give that.

B

A test in the moment as well can't believe carl is going because I'll probably break it. I need carl to help me out that should.

A

Be straightforward: I'm joking.

B

On your reaper, I'm just gonna go hide the wiki um again before I forget. I forgot.

D

Another thought on on issue levels is when you're like expanding and making it in making it bigger, and you might have a mono ripple, for example, where you have back end and front end, and you want to want to create something like a scoped labor, and this is something which gitlab has in github. You can do, for example, with the colon or with the slash in in saying hey. This is type or this is area, slash back end or front end, um or this like touches the documentation.

D

So you kind of make it sortable in a sense of this is the type and then um have specific other things, but for like when you're getting started and in a small project, it totally makes sense to use the default labels. But who knows how many contributors you will get in the future? Hopefully there might be the need for discussion in an issue to expand on the existing labels.

D

You can use the api or specific other tools really to automate renaming of labels and all sorts of magic. In the background, we did it in the past with an open source project which we migrated to github. um So there are ways to automate the borrowing stuff when it gets too, when you need too much time in essence, um but yeah just for now, um it only makes sense to use to default.

B

They're trying to automate as much as possible and then customize later, it's good to have a um have something to get started. So this is the the um I use a github action. um So this is it so everyone uh looking this is if you want to get a green square I'll, make a pull request. Contribution get your name um on. Where is it go to here?

B

Get your profile picture appearing on the contributors on this repo. Then you can literally copy and paste this file and put it in the same directory on the talk to me technology project and you have actions or a lot of see. Modern state ci nows are literally copy and paste config and make tweaks. um These look are variables, but the github token is created when the github action runs. This is just kind of like a standard variable and the repository owner and repository name again are environment variables in the github action.

B

So uh yeah, that's something to do it's a pr created already love that that's awesome. Thank you. Shasmita um super super awesome already done. Thank you. um Will the live chat be up? Well, the live. Yes, the live will be up afterwards, so you can um catch up on it after as well um cool, okay, and hopefully this issue is available on the action as well would have to add it manually. I can't remember, if not, there's, definitely some more green squares for people. So let's have a look.

B

um So apparently we have a pull request, create labels, um and this is how we, how we review it as well, so uh create labels, and then we've got a files change. Let's have a look. It's in github workflows, labels that looks good and that looks pretty good to me so just to be um what's the word follow best practices? We should have an issue first, so we can discuss it before the changes.

B

Oh new release, let me close that new release created manually and then really what I should do is actually just link that so I'm just going to kind of reduce the numbers as they go along, as I see things um so I'll, just copy that and drop that in there that's off, and I can assign that to me to say that it was something that I did. Okay back to back to issues, so let's create another issue which is going to be.

B

um Let me close that one uh something like this create a github action for issue labels. You have action to create issue labels and really you want to um add a description and give a bit of information and people can discuss it. But for the sake of time, I'm just going to hit submit new issue um and we've got a number now so 16.

B

And then, if I go back to the pull request, which I think I closed.

B

And we can see uh another pull request coming in um in here. What we do is the person would then when they raise the pull requests, and this is where templates really help is the top of the pull request say close it and then the number and the number was 16. already on 16 awesome, um so create issue and I'm going to hit update.

B

So I left it the same description as I did, but I just added this in and if you hover this you'll see github says it will close this issue, so it creates less admin for the maintainer to have to then go find the issue and so forth and also should link it together. As you can see now someone stumbles across the issue.

B

Even when it's closed, they can get the pull request from it as well, so you're trying to link issues to pull requests and pull requests to issues, and you can see smelter has already reviewed it, and this is a great example. I love this. If you're not a maintainer on a project, you still can get involved in the project, you can still review it. You can still give your thoughts and feedback. That's awesome.

B

The only thing you can't do is hit merge, but what I love is when we come to some of my projects um like on eddie hub, for example, we've got maintainers. They they review it as well as the community and they merge. It say on my personal projects on my repo, I'm the only maintainer it's very few of those, but I have some I usually get to. It's got three or four reviews and everything's taken care of.

B

I can let you just hit merge and it's such a great way to bring on more maintainers, because you can see people um already collaborating on it already familiar with the project. But please everyone. I beg you, don't just hear, approve, pull request about reviewing it just to get the the stats, it will hurt your account and it will really upset maintainers. It's a good way to get blocked on repost organizations because, unfortunately, you're not adding value you're, creating noise.

B

So if you think it's a good uh review, do approve it, but if you don't and you're not sure ask questions by all means, I'm gonna show you how to do that now, but don't just hit approve, um as we have had. Unfortunately, one or two people in the past just go through and approve every every progress without checking it because it it confuses the whole situation and to add a question. I'm going to say something like this.

B

um Is this the latest version you can ask questions in line by clicking plus on the side and then hitting add single comment again just meter just ignore that that was just an example. So um the author of the pull request will get the notification as a question there and they can reply and we can have a discussion but no need for this one. Let's get it merged and I see shimelto as you can see, tom has reviewed it, but tom has also used a tool. We're trialing called sema technologies.

B

It allows you to use templated responses, and so therefore you can improve the responses that are quite common. Like looks good to me, um but you can also add a bit more information. It makes it easier again it's something I'm going to do a live stream and a video on in the future. So I'm not going to kind of add more to the conversation now and you can see. Predomo is using it as well, so that if you don't use the plugin you get this below.

B

um But if you use the plugin, you get a lot more functionality uh to it as well. So that's why you see this. I think it's great and you can filter by tags and all the rest so and then you can see. My question appeared here. Okay, so let's get this merged um merge and I'm just gonna. Do a standard default merge for now.

B

There are way I can see michael smiling, but it's important when we use the automated uh give up action to create the releases that you do squash, but again we'll we'll dip we'll take a step at a time. I'm just gonna uh confirm the merge and it's gonna get merged in for now. So if I go back to the repo um you'll see that it was merged in and in the history, um you will see eight minutes ago it the commit.

B

Is there and my commit merging in one thing, I do want to point out, and one thing I didn't check and it doesn't affect this project. It affects the contributor. So if you look at this, this is great. So if you look, umita has done it not in the default branch, so it's not in main and and they could have done it in main and it wouldn't have caused any problems on this time round.

B

However, if we squash the pull request, then the second contribution will have issues, because the history won't align and as they try to update their forked version, it will say something's wrong. You've got conflict and you'll conflict with yourself, which is really confusing. So it's really important to never con. Never make changes to the default branch in your fork.

B

Do it in any other branch name um and then before you create a new, a new contribution in the future, make sure you go back to the default branch in your fork, update it then make a new branch, so you don't want to make patch two from your patch one, because you'll have the the the same problem. So this is a. This is a great example.

D

And I think you can update the focal origin on the on the uh ui.

D

um If you want to do it on on the cli, you can work with two origin, two remotes so like you have the default, which is called origin in git, and this is like the forked repository you're using and then you say, git remote, add upstream, for example, for the upstream repository, and so you can keep things in sync. So in your local branch it would be git pull upstream main pulling the upstream into your fork, and then you have it available.

D

I I'm sometimes faster working on the cli myself, so I know all the all the magic commands, but the thing is like git checkout dash b and the branch name from the current branch brings you into a new one. You can work, you can push and so on, and you never should be touching main. um This is the thing so like really focus focusing on a branching model for features for bug, fixes for anything even releases, and this like maps directly into pull requests on github into a merch request on gitlab and other systems.

D

The reason- and there are many discussions out there about development workflows. The reason why I think, pull and merge requests are great, because you can see the history of the code revenues. You can see the discussion. You can even learn the decisions being made in the process of adding something and not just like two weeks in the in the past, but instead like in two years and the teams might have changed over time and maintainers have gone. um You can still see what what has been changed, which is, for example, not the case.

D

If you push to main all the time which is called track based development, um for example, so like when you're working on bigger teams and changes always happen, use branches, use, uh pull and match requests because yeah it's documentation already, and it also helps you to add documentation then like from the decisions. What is the current state um yeah and depend, depending on the development workflow, either?

D

Have the documentation update in the pull request or at it as an extra step, which kind of brings us to task lists and embarked on formatting and templates, which we didn't add. Yet.

B

Yeah we need to do those as well.

D

B

D

Bridge builder now eddie, it's.

B

D

B

Okay, um just to answer this question, abby shake um you're right when I say things like this is really confusing. um I have some videos on this from maybe two years ago, but you've given me a great idea um to actually do an updated video and I can use this project an example. Therefore it have worked two-fold one. We get some more uh understanding on those commands that I mentioned, and how to make our lives easier and avoid conflict.

B

It'll be a short five minute video and I can also show how to do the similar thing on the ui, as well as on the command line, um but also get more publicity to this project. So it's like you, know two birds, one stone love it so abby sheik. Could you maybe, um as soon as they raise an issue, but I've got so many notifications, I've since you've been on this live stream. I have got. Let me check.

B

Oh my god. I've got like 140 m notifications since we've been on this live stream already, so um I'll probably miss it. If you don't mind, dming me on twitter or on discord and just say, create video on um branching and conflicts or something I'll remember what it is when you do that, and I will create that probably tomorrow so that'll be awesome. Thank you.

B

Okay, we'll get to templates in a moment. So if someone can raise an issue actually do we have one on templates. um I think.

D

We already have some.

B

A

D

The amazing contributor, whose name I forgot now, purdue.

B

D

It thanks raced it on saturday. I think.

B

Oh yes, and before okay, perfect, okay, let's have a look, so we do have this github workflows and we have labels. So it's been created this uh we'll check this work before we move on to the next thing. Let's see did it run it's running at the moment and I think the reason why it's running is we have to approve it. I think usually the first time you get a contributor um you have to, uh would you call it approve it, but it might have already run. Yours is fine waiting for check to run.

B

Okay, that's for your lighthouse, okay, okay, just taking a moment to start and the other one didn't run, I don't think import open source standard, um it's manual, running, okay, brilliant! So, let's run this now run we'll run that workflow and we should get our labels, because if we look in the labels we have nine, which the original line that number should increase to. I don't know what it is like 25 or something and.

A

B

Will see that and it follows the open source, conventional kind of standard, which I think is shows consistencies when people are searching, they know what to search for on github and I've added a few more things to it like points um like uh like um I've only got too much into it, but it's great to have good first issue. I actually created a video on this last week, but there are different levels um and then I think mikael is in the chat.

B

The different levels are good first issue, and so what I wanted to demonstrate is with story point or points of a ticket is um a good first issue for someone else or person. A might not be the same type of good first issue: person b right, what one's a back end, person, they're, going to be more familiar with a back end task and if they're front end person they're more familiar with finance.

B

But what I want to try and demonstrate with story points is if one good first issue is one point and a second good. First issue has three points, then uh the terms of risk and unknown and so forth, increases rather than the time or effort and so forth. So really that should be done by a group of people rather than one person, because no one knows what that one point is, but at least they know that whoever pointed it that it's on a scale that three points is more than once.

B

If they want something easy they go for one or something easier, I should say not easy easier.

B

Okay, lighthouse failed, we'll come back to that in a second. The standards has uh issues have passed. So let's look.

D

We've got 28.. I need to to fix the lighthouse thing, because I'm too dumb today, um no just kidding.

A

I was copying the.

D

Documentation and later on, I figured I should be editing the urls actually from example.com to something else and and the runner was not picking up. So I was staring at the screen for 10 minutes now, like yeah, okay, maybe I I might be installing my own local runner for that which.

B

D

Do but it's an option.

B

So we can have a look, let's see if someone commented. So this is uh the changes that were made and we can see. Urls to check is example.com and example.com, which is not part.

A

B

So um that's quite interesting. um So apparently we've got a budget path as well. So don't forget the budget.

D

Yeah, this is what I cop it, um but the thing is.

B

Again, I can be.

D

As experienced as uh as possible, but in this case I'm I'm a newbie and I'm reading the docs and just copying and expecting it to work um so I didn't read properly and now I need to fix it. It's I.

B

Do that all the time, and so that's why there's good docs right the good docs are, is when you've got something really simple and you can, if you copy and paste it get it started, the person gets excited and looks further into customizing, it and so forth. So um if they had done something like google.com, that probably maybe would have worked, I don't know but um but it would have been a false. I suppose. Oh it's gone green great and maybe a month later, people realize it's not checking the right app yeah.

B

That kind of thing something else. I.

D

Would say for like when you're creating a workshop or something small as a snippet, to learn um it's it's great, to have the five-minute success and really have something which works all the time um like google or something else. If you, if you do it in an official official documentation, you should be using something like example.com or whatever, um so that it fails, and people can really customize for the environment.

B

Absolutely I've seen this happen with automated testing and other things. I remember going into one client really quick story. I promise automated testing is so important, but to see it read is so important. I went to one client, big client in the uk and um they were like I'll automate a test pass and then um I deleted the entire code base and ran the test they still passed. I said: there's no value in that. You've got false, like hope, and what it was was.

B

The test was testing like if one equaled one forever, but it was under the seams like hidden away and so everyone's writing all these complicated tests, but the actual assertion wasn't really doing the session, so the red is important, so michael was just proving that it it went red and before we get it green. So that's uh test driven developments that we love and for doom is saying we need michael on another, live stream. I love that okay and predomina saving the day run it manually. Thank you so much.

B

I forgot okay awesome, so uh we could put a comment in so no one picked up on that. You know. Minus five points to everyone watching this live stream. um You didn't notice, it was example.com, that's fine! um We all missed it. uh Okay, so we've got the issues so now what we can do as maintainers on the repo. As I mentioned, people can merge, pull requests, but they can also add um issues so add labels to issues so, for example, we've got this um issue already, and this is actually a really great example.

B

So uh shmeeta has raised this issue and apparently it's a duplicate which is fine. It happens, no problem um contributing file code of conduct, as you can see, I'm trying to find it. uh There is one down here here we go so what I would recommend.

B

This is great that um abby shake put in a comment and help the maintainers to say it's a duplicate, but what would be really helpful is make it easier for everyone, and you can do that by adding a link to the original original one, and that way again just makes it easier for someone to to spot and notice that so it's really important.

B

So what I'm going to do, I'm going to give a task to uh laurel or matthew, and the task is going to be, if you could edit abby shakes, comment and or even put a new comment in and just say, yeah. This is a duplicate, a link to the other issue, and then please close this. Then we can get the issues down from 12 to 11 as well, um but thank you shashmita for raising. um I appreciate it. I think the other one by the way is I lost it.

B

I did see it before, um but double check. That is a duplicate contributing file that could have condo. I thought I did see it. I must be going crazy, double check it. If it's a duplicate, then we close it if not and we keep it um okay so back to the issues. So what we can do now is the labels. We've got all these labels now and so code of conduct we should have um you can see, got the points in there. We've got how important it is. So I want to put that as critical.

B

I think it's super important to have that. um It's not a question: it's not a blocker anything like that. I think because it uses a template again. You should point as a team on on these, but just for the sake of time I want to pick a one pointer um and it's an improvement and it's text. It's not um it's not code or anything like that, and so now the issues appear.

B

So anyone searching for those on github this issue would appear or if someone wants to filter by one pointers or critical, they can click on it directly and automatically filters it at the top up here. Just to let everyone know, if you want to search for things as the issue number, I know that we're all going to wake up tomorrow, it's probably going to have like 100 issues um already, so this is a great way to kind of filter stuff. If people wanna wanna see it, and so okay uh showed labels.

B

um What else did you wanna? Show actions? We've gone, green, okay, it's still going red. Let michael work on that um for the moment and everyone. If you do want to look at why it's failing you can go to actions. You can click on the action. The latest one is at the top and then you get to see kind of the um the flow workflow where you have.

B

You can have multiple ones of these um and then you can click on it and you can go to that step and then you can kind of actually see what happened. The error looks a lot shorter, so we're getting closer, um but uh it's the.

D

Typical story, when you start with ci um it's red, then it's red again different.

A

D

And at a certain point, it's green again, which we're still like hoping for an easier way, um but that's about it.

B

D

Don't feel ashamed when ci is not working in the beginning, um when I, when I start a fresh project and it doesn't matter whether it's gitlab git top whatever um ci is red and then you fix it.

B

Yeah, red ci is, if you don't see red ci that often you get a bit worried that maybe it's just always green, so yeah, so red ci, occasionally is is a good thing. Yeah.

D

When it's always green, you check for exit zero, which is basically um success.

A

D

Is fake, so you should fix that.

B

Yeah and predomina is sharing some more green square love, so anyone who needs some more green squares uh um add an issue for adding workflow uh the badge to the readme as well, um and emma is saying uh we need to allow lighthouse ci to the repo okay, so you might have to check the box for that.

B

D

I need uh not maintain our permissions, but admin permissions.

B

Potentially, I don't know if anything came up on that uh emma. If you shed some more light on that and purdue was saying, maybe private token, I need to check that you might be right, it's not in a fork, so it should be okay, um but let's see uh other thing I was gonna say that I've now forgotten. I can't remember I'll come back to it um check the token okay, uh oh emery said you need to add more than just the action for lighthouse need a config file to authorize lighthouse.

B

I don't remember doing any of this. My memory is terrible. Okay, um there's something we can look into again.

B

I don't want to get too focused on one particular thing: we're trying to do a light touch on lots of things, and then we can kind of come back to it later on as well, and we can always have some uh discord calls where we can bring people up as well, because I know emma will show us like in one second, rather than us kind of struggling around there's only so much you can type in the youtube chat as well.

B

So um maybe it's something we can do on a discord call, and um you know people can actually help us and share their screen and so forth. um Oh okay, I've just seen this. Oh no! Really I've missed this for a while. Now I know so. I mentioned it a long long time ago and I completely forgot.

A

B

Get me on a call tomorrow.

D

B

We will resolve.

D

This getting called out in your live stream.

B

No, I love that. This is why I love the idea. They know to call me out um and emma is an amazing, maintainer and mod. So that's really awesome.

D

You know just kidding, um I think I have no idea, so I was just following the documentation and adding it and didn't work. So now we learned we need authorization and and much more things. I think I probably should have read the documentation first, but sometimes I'm really like. Let's try it out and see how far we can get.

B

It's the way right, just try out and try out and mikhail's saying collaboration, collaboration collaboration exactly um so. I've noticed I've done something very, very bad and that I did say I was going to put the url in the repo, so people could find the deployed version and I shared it in the chat and forgot to add it to the repo. So the downside of not doing that is. Where is it I did see it carl has also asked: where is the deployed version?

B

So if I had done that first, this is why documentation and organizing everything is really important. So therefore, we can still have that collaboration, but we can collaborate on the more important things rather than the same thing over and over again. So thank you so much for reminding me carl. I want to do that right now and that's the website, the floyd, so it's in the repo, but.

D

B

Share it in the chat again.

D

Yeah, you can also look into my now fixed, no I'm not fixed pr, but I edited the url from netlify in there.

B

Okay, so it won't pass still because you need the approval, um you don't need the budget.json, though so I'm going to leave a comment and say: is this still needed question mark and it's really important on how to give reviews- and I think it's a skill that I'm still learning and it's something that takes time to learn, um because sometimes we write a short reply and um it uh can be taken in the wrong way. So I think it's um like is this still needed?

B

I think this could be taken a bit of a mean way, so um you know maybe I should have written more, but on the live stream and and michael knows, I'm a friendly guy and always smiling so hopefully he won't be offended by it, but that's something we should probably discuss about in the future. I know with mikael we've talked about and actually matt who isn't here about maybe having a live stream or a twitter space on how to give good reviews. I think it's really really important.

B

um Okay, let's have a look right. What next? What have we got?.

D

Such a stream would be awesome, so I can source from my my past with um confident in c blasphemous and python the most. um But I would love to join and just share on ideas and code revenue and also like using it in a way of being a little doing, a little mentorship and also encouraging others to learn and not just fix the code.

B

Yeah it's about knowledge transfer, as well as making improvements to original changes. So I have a question for laurel and matthew. How are we doing on the on this project on the live stream? Are we looking good so far.

C

Yeah, definitely, I think it's looking really good.

E

It looks like there's a lot to learn and do which I'm excited for you know so trial.

A

E

Kind of a thing for me, um but that's the best way to learn, sometimes is to just say: hey. I don't know how to do this, so I'm going to research how to do it and then, if I can't figure it out there, I'm going to reach out to y'all and see what we can figure.

A

B

Sounds good I've learned so much today already as well. We've already.

A

B

Over an hour, time flies when you're when you're having fun. That's.

E

B

We've got 13 stars, we've got, you know some contributors here as well, so we're gonna get a few more in two as well. So the read me the readme doesn't have a screenshot. So if someone wants to take a screenshot, all you have to do is click on the deployed version.

B

Take a screenshot of it and add it to the readme and again an animated, gif or a video will be really nice, but that's more work, let's just add value as soon as possible, and then we can iterate on it and make it fancier better and all the rest.

B

Okay um right, I see carl coming up with some all really good suggestions as well um carl raise it as an issue, because I will forget, and then you did say something out: oh yes about that label, getting it to appear in the eddy hub project as well. You might have to do that afterwards.

B

So what else have we got? So lots of issues being raised? Lots of green squares for people, um don't forget, do some pull requests and let's have a look. This is assigned already, okay, brilliant.

B

um What else should we do? Next, don't forget: do check out the insights tab, everyone watching you can get some ideas for issues to raise, but also for uh actual raising pull requests so laurel. Do you have an idea or matthew um on licensing that you'd like to do for this? Maybe this might be one for later, but but oh you might have thought about it already. I don't know.

C

Yeah, I think uh michael, was kind of talking about licensing the other day and the different options, and I think michael, were you recommending doing that mit license was the most like the one.

A

C

D

Think mit or maybe apache version two is widely adopted, and this like um it doesn't restrict anyone from contributing, and I don't think you need something like gpl which which restricts you in a way that you, um for example, when you use the software in an enterprise, closed tools, environment that you need to publicize changes. This is something you probably don't need, so you have everywhere like open source license and it's really open um from there. I think mit. Your apache is just fine yeah.

C

So I think mit would be the way to go just initially and if we ever need a different one, I don't know.

D

C

See us needing, you know.

D

I was I was using gpa or was I was bound to gpl in past projects, because it was a fork of of a previous other project um but yeah we at gitlab we use mit for open source software and um within the cloud native commuting foundation.

D

I think it's a mix of apache and mit, so they are they're widely adopted and it's also a great way. You can reuse certain code snippets from mit into apache and vice versa. I think I'm not a lawyer. Please read it.

D

The thing you can you cannot do is, for example, you cannot use apache code in gpl code and then compile it and ship it that's not allowed, and this is like a rabbit hole with open source licenses. So for beginners I would just recommend mit and apache and if you're looking to maybe monetize the project later on or at an enterprise version on top with open core, um it's still possible to to change that. At a later point,.

C

B

But yeah, oh sorry, go on laurel. Oh.

C

I was just gonna say yeah, I think, probably mit. It sounds like the way to go. What do you think eddie.

B

Yeah, I think mit is a really really good one as well. I've just brought up this website um by by github and um they give you some examples. So, for example, mit is used by babble.net and rails as examples um I have got a youtube video comparing all of these and I did get some advice to do it and I did script to get checked because I don't, I think I understand it and I start reading it and I get confused.

B

So um again, I'm not a lawyer, but I did validate what I put in that in that video. um If you want to know more information about each one, you can click on um find out more and then you can see the comparison. So if you go down to like mit, you can permissions that people can have um conditions and then, if you hover over it, you get more information about that. So let's do mit. For now.

B

So, let's do licensing, I want to hit, add and then we can choose and go down to mit. You can see these are the popular ones um and, let's review and submit again it's giving you a bit more information over there. You have really helps with this.

B

I'm trying to create it. Usually you do it to a branch, but I haven't changed anything. This is a template effectively, so I'll be very bad and create it to.

A

B

uh Okay, so now on the on this on the uh insights, we should see a green tick. Yeah green tick done it's, not a full house, a full house yet, but we're working towards that. So if licenses is here license, I can now close that and I can say done.

B

B

That close I'll just assign that to me, okay, another pull request has come in so we're going to leave the this pull request for lighthouse for the moment, because it's failing, we don't want to merge things that are failed and things you can do to stop. This is, if you go to the branches inside settings, then branches, you can you set your default branch and then you can also add rules so therefore require a pull request before merging you can make sure the status checks are passed.

B

So therefore, it's green before merging, so you never emerge in anything, that's broken. um You can actually require that your your signatures are so your commits are signed, but that will prevent a lot of people from contributing. So that's something I love it. um It's something we don't really do in open source projects, but the importance of it is. Is it checks that the commit came from the person who committed it rather than someone else pretending to be them, which is possible to do um other thing. uh I'd like to include is included administrators.

B

So, for example, if that was ticked, I couldn't have committed to the the main branch would have actually had to come for a pull request. I think that's quite important and I leave these uh leave.

B

This off do not allow force pushers, I'm really not a fan of force pushers um on the main branch, if someone's doing in a pull request on their own branch until they get smashed, they can do whatever they want as long as they're the only people working on it, because, as soon as you start rewriting history and someone else is working on it, you'll start getting really weird conflicts. So I think it's important.

A

B

The only one working on a feature, branch or a bug, fix branch and you decide you want to change the history by all means: do whatever you want, but as soon as it's merged or someone else wants to work on that branch with you. If it's a bigger feature and there's two of you working on it, don't rewrite history um until you're both done, you might retire as part of the merge or something like that.

B

Just be respectful of people's history and don't create more work for yourself, but I won't protect it now, there's something um that can be added.

D

Later to to add to the thing.

B

D

You're working in a feature branch together or so this can happen when you have sort of like bigger changes coming in. um There is a way to reset um your current branch to the one which has been pushed, so you need to get fetch in instead of pull, and then I think it's get get reset heart origin and the branch name. um But beware: if you have local changes, you need to stash them.

D

Stashing means putting them aside temporarily. Then you can like update what the other side or your team member has been like force pushing, and then you can continue your work and hopefully commit push and um be on the same side again. But I.

B

Think this is better done as a video, though there's your next video michael.

D

Yeah, the thing is like get this sometimes a little black magic and when it goes into advanced conflict, resolving um it's, it needs some visuals and some drawings yeah. So for jumping in. um I also created a pull request for updating the screenshot in the readme. um If you want to review that.

B

Let's uh have a look, I think someone beat you to it.

D

Oh yeah, then someone beat me to it and I'll close. My last public head.

B

uh Yeah, you can close it as duplicate, um I think you got beaten to it. So I've gone to the pull request. I've gone the files changed and this we can't see it. So what I recommend people raising pull requests is add a screenshot to. I know it's kind of like construction, adding a screenshot pull request and we add a screenshot to it, but screenshots are really really helpful um and so what we can do, though, to view it before we merge it. We can see the changes we can see.

B

It's got a heading one which is probably not the right thing for heading one, and so I want to show a trick on how we can make some changes to that, and then it's got an image, but I don't know what that image is so, yes, I could grab the url paste it in another thing you can do. Is click on these three dots and open a new tab view file and we can see what the the rendered version looks like.

B

This is what it looks like the reason why there should only be one hash title. So one sorry one single hash title so h1 on the page. This is probably like a h2, for example, but thank you so much for the pull request. uh Schmidta.

B

I want to leave a comment and say um uh I think uh this should be uh h2 or double hash. um Another thing we can do is this button up here. I don't have anyone noticed it's suggestions and the reason for this is if I make this comment, someone might obviously this is quite a straightforward one but say I'm trying to explain something doesn't quite make sense. um It's not very clear. Rather than having back and forth conversation, I can make almost like a micro pr to this pr.

B

It won't be a pull request, but I can make a suggestion. I really like this, so this one will be what they've got and then I can. I can make some changes so um actually that didn't come through right.

B

I don't think it should have been a minus and then the plus that's a bit strange, but I would say something like that. So if I copy and paste this, I mean I can preview it and check. um Why does that? Come with two and then what it would be can.

D

You can you show me the suggestion again, yeah.

B

D

Think you just need. No, no, no is.

B

It just the one.

D

B

You want to change. Okay got you, how does it know what line it is, though? Oh it's the line above it okay, interesting, perfect. So um and then I can um submit this as a comment and then uh shashmita or someone else can. Actually you know they will have a button that says accept, so it will add the commit and change to their pull request without them, making the changes locally or whatever. It is, if it's just something kind of small.

B

Obviously, if it's multiple lines and a bit more complicated, they probably um want to do it. But another thing you can do is: if you want to discuss something and it's more going over multiple lines, so maybe um simple example: you could do diff and so uh there's multiple lines changes.

B

um I think we should, you know, explain a bit more, but we could say right. So this is the lines this could be line. One and I could say, remove line two and then add line three and then this is not. They can't accept this.

B

They would have to make these changes manually, but the interesting thing is they can actually see what you mean if it is a kind of a complicated uh discussion, again that's available everywhere on github, where markdown's possible, and so I just again a bit of a tip there and I can see now the refresh button has appeared at the top, so I'm guessing another commit has come in. I hit refresh.

B

uh Yep it's been accepted and then also michael, has also again, oh made some changes too again, so another suggestions come in, which is which is great. um So now it's not mine. I can also accept it as well. If I want.

D

Just to give more context, I didn't comment it. Yet um when you're adding a markdown picture, you can add an alt text to it and I prefer to have it descriptive and okay overview is not really inspiring, but it's better than the default which says image um so.

B

Yeah that makes sense, gets.

D

Rendered when you're doing a mouse over on the picture, but I'm not sure um I.

B

Think it does as well.

D

It's important for accessibility as well.

B

Absolutely I've been really bad at the chats. I've missed that, so I can see um emma dawson, who got multiple. Ms, I say emma dawson has said um added a suggestion and I missed that, as as michael said um predominance also said it so sorry, everyone. This is where having two screens is really helpful, because when I go to the the github page, I lose all the chat and everything else. So um thank you all for shouting at the screen saying eddie. This is simple.

B

It's simple when you know how.

D

I think just covering the button is not simple, because I know that gitlab has the same functionality and when you, when you figure out the button- and you want to make a suggestion and you're not sure about it, just do it do it in your own repository and and play around with it.

D

The more confident you get with suggestions, the more powerful they are because, rather than opening your local client and do fetch pull push whatever you can just make a suggestion in your browser, which, which is helpful, for example, writing documentation or fixing a title or things you can do on the ipad or on the tablet, which, which is amazing similar to you, can even run git port on the ipad, actually um different, different thing, which we should touch base on, um but the more easy and approachable it is and the more accessible it is.

D

um The better. The contributions also get.

B

Exactly and you mentioned git pod, which is something we'll just briefly touch on now so carl, are you still here? Carl is from the edith community and um at gitpod as well. So I know carl will get modify this project like in a few seconds and it'll make it easier for people to contribute. They can contribute, like you said from the ipad and as you add or you know whatever it is, they don't need to install and set up all these things.

B

Then click a button and start contributing in a whole dev environment for free, which is amazing, um so hopefully carla's still here and can uh help us with that. I see francesco has joined us, everyone say hi to francesco and francesco's um recovering from covid another awesome youtuber um on twitter. You probably all know francesca already doing so many things in the kind of docker space and web 3..

B

I don't want to shout about that. So, um oh.

D

Yeah, that's interesting. Tell me more.

B

No, no, that's enough! I'm still studying web too. You know I'm still learning it.

D

Okay, I would love to.

A

D

But I don't have time so.

A

B

uh The project isn't having an install or start command. You know what let me merge this pr and then let's chat about the actual code and the project. For a moment we haven't covered that. So I think it's a really good idea and you can hear less from me and more from others, so yeah this looks really good. So thank you so much um we're gonna say approve.

B

It looks great.

D

B

D

Got another pull request already with a gif um which might have a conflict now, please do replace.

B

Okay, so I don't want to make this too complicated, but your yeah they'll have to potentially rebase, but what I'm going to do is I'm going to squash this so just to talk about a briefly touch on the different merging principles. There are three and michael can jump, can jump in and probably explain it a lot better than me. There are three um ways to emerge. There might actually be more, but like kind of the main ones the create merge commit, which you saw me do before so you in the history.

B

You have the commit of the person who made the changes and then you have a merge, commit of the merge and the commits coming in. But the reason why, on this one I don't want to do this is because, if I do that you'll end up in the history that has update, read me, update, read me, add screenshot and then the merge commit by eddie.

B

So it kind of makes the history a bit dirty and then, when you're automating the releases again and the change log that won't make sense, because you'll just have this list of the change blog. It won't make sense, so what we can do is in this case I would recommend, squashing and merging, and what that will do is it will squash it all into one commit and then I can actually rewrite now. What that commit is. um Do you agree? Michael, do you want to explain? Maybe a bit more about it?

B

D

It so it depends on on the workflow um if you're for, following, like the good, commit, storyline and you're developing a feature over like two weeks or more time, and you really want to see the design and development history, I would recommend keeping the history of git comics, which is like 20 or 30 or whatever, um because when you're coming back, it's super hard to identify a bug or regression in a huge depth. This is like um this is where I say well get. Blame is interesting because I know whom to ping and say hey.

D

Please don't do that again, um because it's in I experienced that myself like staring at the diff and figuring out sex faulting. It's interesting ah yeah thanks thanks for nothing. uh Now I need to like revert everything by hand and so for um smaller changes or when you have like um a history which is polluted, I would say, with update readme the default um try to squash it and alternative to that is to rebase the history, which means you pick um a specific commit in the past and then change all the commit messages.

D

Based on that, so you can amend the commit history. Even change the commit inside and which changes the history, so you need to force push later on, um but it helps to to keep the history clean and I think foreign for open source projects getting started. It makes sense to really like say his caution merge. So you keep the merge comet as an identifier, but maybe your workflows require a different way and you also generate the changelog in a different way.

D

So it makes sense to keep the git history itself, um but again, um ten different opinions, um but.

B

Do you raise some really good points you need to.

D

Discuss this on the team you're working with, should we like pick the default uh explosion, merge for example, or do we need something more special and then that's the way to go.

B

Yeah, I think that the point I want to highlight so many great points in there but you're right. If it's small like this, then then we squash it. We don't need all those different commits that don't add value. But if it's someone who's working on a feature like uh matthew was saying they did a whole refactor. There might have been 10 or 20 commits as they went through those stages um and their like descriptive commits you probably don't want to lose that history. There was a reason for that.

B

If it ever broke at one point, then you might want to lose that, but if each one was a it still worked, but you were kind of doing each kind of page or section or component at a time, then you probably want to keep that history. So absolutely right really good point there, michael thank you for um and.

D

The other suggestion I just have at the top of my head um when you're committing like you're ending your day, and you don't know if you're continuing the next day or the next week. You can also add a work in progress, commit like wip or whatever and com commit that push that so that your team members can see it and at a later point you reset the commit to re, remove it but keep the changes which is git, reset dash, dash soft head and then the tilde 1 thing or the second flex.

D

um So you can like continue at a later point. um I'm.

B

Just smiling because you need to do some videos on this michael.

D

Yeah totally I should I should use my hands and draw more. The thing is: there are ways to make it work in an all remote environment. It's super important to really also push the changes, even if they are not finished, so that everyone can have a look, and you can always rewrite it later. On yeah.

B

There's nothing worse than someone um worth spending like a. Hopefully it doesn't happen, but spending a while like a week on a feature and then they're off sick or something happen, they're going to deal with it and everyone else was like right. We just need to spend an hour to finish off that piece of work, but we haven't got access to it on their computer, so I agree definitely push it up to a branch, um crazy, create a draft pull request as well. So it's not ready for review, but it's there.

B

If anyone wants to have a look or maybe the author wants to get feedback, so draft progress is really really important as well. It shows that don't invest too much time in it, but you have a peak. um I think that's a really really important, just be careful with the reset command everyone. You can rewrite history and undo other people's work, so just be really careful with it. um I think it's important. I remember someone saying I want to undo my commit and they've done.

B

A pull they've brought down two more commits, so it's kind of their commit and two more on top and they undid it. Their work was still there. They could see it in vs codes. They did it again. These command's not working. Let me run it again and eventually their work disappeared, but then so did two other people's to get it. So um I am not a huge fan. The reset is used for so many different things. So just be wary with it, but I'm a huge fan of not um undoing any commits.

B

There's another commit you can do on a command. You can do, and I forget what it is revert which effectively say, for example, I did something now and it was in a commit. I was like you know what I want to pull all that out, but it's got one line over here in this file, one line over here in this file. I don't want to do that manually. If you do them. Let me go back to this. uh I can actually show it. I won't do it I'll show you.

B

So what you would do is just say. For example, these commits are quite small. um Let me see if I got a big bigger commit.

B

Let me go to um maybe matthew's refactors have a look, not that one okay say, for example like each one of these was in a different file and I would have to go through the files undo it if I wanted to undo this for every reason I could take that hash and do git revert that hash and all it will do is make a new commit doing the complete opposite of everything that got put in that commit that I shared and there's the beauty of. That is that I still keep the history.

B

So if ever I reverted it temporarily or as a mistake or whatever I've still got the original changes. I could just revert my revert if I wanted to- or I can see it and do it manually, take part of it there's just so many benefits to that. I'm always keen to again roll forwards with your deployments versions and also commits, I think, that's really really important. Yes, um keeping the the the history beautiful. You know within reason, though I think um I think too. um Okay, let me merge this pull request.

B

Where was, I add, screenshots? I think this is looking good now, yeah, don't.

D

B

No, no, no! No! It's good. I think it's a great discussion to have really really important and you've got web dev uh junkie. Agreeing with you keeping commits, has proven to be uh really useful yeah as long as they're, descriptive, commits and not work in progress. Work in progress. Update, update, create in your branch is fine, but it's something that you don't really want to keep.

B

So I want to uh squash and merge so we won't get uh github automatically puts this in uh in the description of the commit um and I'm gonna start using conventional change log, which is again an open source standard for doing commits, and this will be used later for to create the change, log and trigger uh deployments and stuff. So I want to do that just to set an example. um So what we would do here, it would be docs, so it could be a feature.

B

It can be a fix in this case docs and the screen should add to, um or you know, screenshot added added and readme aren't great because added. We know it's added from the pull request and readme. We know it was in the ruby file from the pull request. You want to add stuff that um creator of app. I don't know, um then the reason why it has the.

B

uh If I go back to here and we go to the um commits you can see now, there's no all those um updated and all the rest and not here in the history. They've all been squashed into one, and it said that there are multiple contributors to this as well, which is great, it's partially verified because mine are verified, but someone else in here wasn't, um and that goes to the whole um verification of person who who they are and so forth.

B

But what I wanted to show is there's a number here and it's important to leave this in, because when you get the change log, if you ever want to go look at the changes you can just literally click on it. It'll take you straight to the pull request with those changes. So um when that gets added, I'd recommend leaving it leaving in it just makes that whole thing really really easy or easier, not easy.

B

Okay, we've got a template as well. Nice.

D

I'm not sure if it works, because I'm using the markdown style for templates.

B

Jumped to a different one for a second sorry I jumped to this so there's an animated gif on this, which looks pretty cool, but I wanna we're gonna leave some comments on this. um So uh thank you so much abishake for the contribution. But if you look this isn't being rendered properly, so I always recommend um checking you can see the title because it hasn't got space after the hashes. It's um it's markdown's, not picking up. So in this case I'm just going to suggest oops. Let's play. Oh can't even write.

A

B

It's definitely.

D

Like it's late for you, so yeah.

B

um And then, following um following michael's suggestion, also, maybe you want to change this to be uh you call it screenshot. I can't remember now.

D

Maybe let's call it animated overview.

B

Demo, I don't know that my work.

E

D

You should be describing what's happening in the picture.

B

Demo of app that terry thinks it works.

D

How would you describe the picture to someone who cannot see it.

B

Yeah animated overview, great okay sounds good, so I've made those suggestions in so we can come back to that in a minute um right, I'm conscious of time we've been going for an hour and 45 minutes. What else should we cover?

B

um I I know carl was asking about speeding up a dev environment um which would be great on git pods. At the moment. I think it's just front-end uh code at the moment so probably keep it really really straightforward. If you have a quick look at the code, does that work for everybody, yeah and and the project you talk us through it yeah so where? Where shall I go? What should we do so? um Carl also asked about uh replicas.

B

E

That was that was us just trying to collaborate on something we probably should have taken that out, but we were.

A

E

Replit to uh collab for a bit just to test some stuff out, we're just see which ones work we ended up. I think using glitch for a little bit and then that way.

A

E

Collaborate live and they can. You know we can both see changes as we go.

B

I don't know any of these things. I use um vs code liveshare.

E

It's probably the same thing, probably okay,.

A

E

Well, now that's what I'm going to go! Look up afterwards.

C

We're learning tools and ways of doing things.

B

Exactly and I think gitpod has it built in as well. So um not only do you get everything all the dependencies everything you need, you know even mpo in store. Everything is done. I think you can collaborate on it. I'm pretty sure that's what we did carla needed on the live stream. Carl, let me know my memory is terrible.

B

um Okay, so where should we? Where should I go? First, do you want to drive someone if you could raise an issue and remember to say, remove the replica uh file and also if someone can raise a pull request as well, for that so matthew, which I go through the index file first yeah.

E

Let's go index start with the basics. There.

E

Yeah, so we it's just a basic most of the html gets spit out into the dom by the javascript that we made, and then we have.

A

E

Data file that has all of the it has an array of all the information that we use to spit it out. um Let's.

B

E

Why not probably not the best but we're gonna we're gonna refactor this and change some of the names and stuff we don't need the. I don't think we need the id as much um as much as we can just use title as the id since they're all uh you know special anyway, so um I I switched them all around manually, so they would be color coded so that they were grouped up together. That's why they're out of order id number wise. I.

B

E

Like I said, the id was something that we started with and then we realized, we didn't need it and then we just haven't removed it yet, and you know we wanted to get everything at least workable for today.

B

No, that's awesome. um One suggestion I have potentially, if you do have the one grouping together, you could potentially um in your json, do it so that you have um like uh sky blue is the um property and then, under that you have a collection of all the ones that belong to sky roof. Blue, for example, beautiful.

E

B

Love it depending on what you want to do on the front end as well. So it's just like a little bit of information. I have it's just a suggestion, but it might not fit in with what you're you're trying to do as well.

E

Well, we can always test it out. That's what the beauty about this project is is we're learning all sorts of best practices and mostly learning worse practices, but those eventually get better right as you as you practice, and keep going.

B

Exactly and so this is the uh the javascript.

E

Yeah, it's not the prettiest thing we, uh you know have some stuff commented out, um but it's just a basic constructor that we that I made well. We made definitely uh and then we just tested things piece by piece until it kind of worked um perfect. We don't yeah. So you know all of this stuff, like I said we're just using what we know, which isn't a ton. Yet um every day is learning new stuff and uh yeah. We just we that was this file was like about 1700 lines. So then I.

A

E

It down to this so instead copy and paste everything we're just like. Why don't we just make it copy and paste for us, and then we want to.

A

E

Something we go and we on line 15 the box spitter that I made. I want to change the way it looks the way that things are set up. I can just go in there change one thing: instead of 1700 lines of stuff.

B

E

Yeah, so that's I mean I'm sure. A lot of this is pretty standard like you know, trying to make stuff into scripts, but you know we're we're pretty new into the javascript world, so I think we're doing pretty good for what we're.

B

Doing more than pretty good you're new to the javascript world, you're on a live stream, you're doing open source! Oh my god! It took me like a decade to even start on some of those. So.

A

You're way ahead.

B

Of me, so that's epic! um I.

C

Think we've been learning javascript for like a month now. Maybe I don't even.

E

Know that oh yeah yeah, we we started our first javascript class was in at the end of march.

C

Yeah um this project was written. On the second day. I've ever been exposed to javascript in my life like, which was why it was so many lines of code, and then the refactoring was done last week, right, matthew, yeah,.

E

We I think we had known constructors for a couple of days, and I was like.

C

We can use that.

E

To redo all this, so it was uh yeah as we learn. We, we refactor and put.

A

E

You know we do what we can. um Thank you enema. That's very nice.

B

Yeah and a really great question from emma as well, and what do the colors mean? I think that's yeah really good. So if maybe um one of you could raise an issue um on what the colors mean and then someone, maybe in the community, can raise a pull request, adding that to the to the readme or one of you could do that as well. um If you wanted to, but that's I think it's really important, um and I see carl saying my pr is really bad practice. When carl says his pr is bad practice.

B

It's like my best. My best pr's are like carl's bad one, so yeah his work is awesome.

B

He's done some great stuff, uh we'll have a uh always open a pr car worst cases. It gets closed. If it's not too much effort for you open it, it's easier to have a look um at what the changes are or maybe raise an issue with some like thoughts and points um and see. um I really think this project could, I know, you're going to add. So when we briefly talk about the future of the project. Is there anything else to.

E

Look at the css ideas of what we want new.

C

Ideas, so uh in part of that commented out code on the js matthew actually made a constructor.

B

Did you say everything.

E

Yeah I mean it's coming the thing.

B

E

It's so you can add your own. uh You.

A

E

Want to be able to add your own, your own tiles, save them edit. It delete the ones that we have in there. You don't like and then have a eventually have an account, so it just across all your devices. Oh, I forgot the thing. The ipad we usually use here, I'm going to use my phone. So at least you know the person who's using this service still has access to on any device right.

E

We want it to be everywhere as accessible as possible and that you know um when I was working with as a behavioral aide a lot of the day-to-day is. um It has to be like on a schedule right. So if, if things aren't the same, like you pull it up and everything's different that could throw you know the whole day off, but you throw it up.

C

E

Phone and you have your account so then boom everything is the same. You know you have that repetition that which um is really good, and that way you can. You know everything is still the same, might be smaller, but you know exactly where everything is. You know what you're.

B

Getting to see yeah and.

E

It's tailored to you right, so it's like you know, maybe the default green. You want it to be red, so you change them all to red and then, and that way, when you bring it back up on a computer you're at your you know a family member's house, and you forgot your thing like hey: can I borrow your ipad, throw it up on there everything's the same, and that way you know that, like I said that, that consistency is still there for the user.

E

um That's really! This is about it's about the person who needs it and not about really us. We just want to get it. There sure.

C

Basically, each user will be able to create their own custom con combo.

C

So it's not going to look like this or they can use the default one which will be the product that you land on the site, but then you'll be able to eventually create your own user account you'll create your own custom communication boards with tiles that are provided or you can create your own custom custom tiles to add to your own combo and also the color configuration and different functionalities as well, which we actually just recently learned that you can integrate this with um being able to make phone calls with your calm board. So.

E

C

A step that we want to take put that. I can't even talk. That's something that we want to add to this as well, because um people that have to use that there's like another piece of technology that you have to use in order to make phone calls when you need a communication system, if you're a non-verbal or non-speaking person or someone that has verbal disabilities, um and so this would eliminate that need for them as well.

C

um So it's just one more step in the direction of getting them the technology easier and accessible, and for free, um so we'd love to integrate functionality like that to this as well and there's some other things that we've talked about, um which I'm.

B

Well, that sounds that sounds awesome and we should quickly touch on project boards, so you've got a milestone. So we quickly like put those high level ideas in and you can assign those issues. So we could touch on that. But before we do, I did um matthew sent me a message about probably like an hour ago completely, because I've had so many notifications. Looking at my discord and my everything I've had so many notifications come in, so apologies. I forgot um it's um and apparently uh michael's saying carl's on fire with gitpod.

B

Okay, we're gonna get.

E

B

And my memory is terrible, but don't forget everyone to also follow my amazing guests on twitter, their links, description below, but follow and start follow the organization on github and star the project, 2 support and then we're going to circle back in a moment to the pull requests.

B

But carl asked a good question which I was going to ask sounds like it's going to be full stack, yeah, that's that's the goal. Okay, and um I know carl is going to suggest swap kits. I will recommend next gs and what is quite funny is a little backstory here. Reason why I find it so funny is um carl recommended next gs to me and prime react and then I get into him. This is brilliant and he switches to spell kit and I think tail wins. I'm like you got me into this.

E

You know your bait switch on you yeah.

B

um Awesome, uh but uh yes, um so quite fine but yeah see what technology you want to want to use. um I think just seeing at the looking at the code, I think yeah, it would be absolutely great to um uh kind of you could do oauth authentication. So therefore, someone can log in with google or github. You have to worry about managing passwords and all the rest and resetting passwords those sorts of things um uh self promo.

B

I did a video on that like two weeks ago how you can get up and running in like 10 minutes, so that's just just done um and then that'll be with the back end and uh the manga video I haven't done yet. So it assumes you've got a more connection, but it yeah but the, but the library that I use creates all the tables and does the authentication literally it's just ten minutes, you'll be up and running and then um for the upload of the files.

B

uh I did a video on that the week before so three weeks ago, how to upload uh the user can upload the files to digitalocean again within 10 minutes like it's. How we used to do it before was so painful. When I was thinking I tried it, I got up running so quickly. I used to do a video on this. This is super important um digital ocean gives you like 250 gigs for like five dollars a month. So it's like nothing. um I know michael's going to be like let's get kubernetes involved.

B

I agree. I think we should, but that's a conversation for another time, especially if.

A

D

B

Project, no, no, no, no. I mean for the full stack version when you've got. You know everything else.

C

User accounts user.

E

D

E

D

I think it's like a great learning curve when you have micro services and front and back and later on, um because it's easier for you to test things. um But for now don't worry about kubernetes yeah.

B

Don't worry about it for now.

E

We haven't even touched the back end, yet that's supposed to be starting soon, but I'm sure two days after our first back end thing will build something: that's what we do. We learn one little thing and then just run with it until we build something on it.

D

And I think when you're, when you're coming to the front and then back inside and you have sort of like a little distribution there and when you want to like debug performance issues or something I can also jump in and share some ideas and code implementation around observability and app instrumentation things. I'm learning myself at the moment, um but I'm also keen to like I have little javascript knowledge um just to see, maybe how to instrument node.js and figure out what is slow.

D

What is what is going on in the code um just to make sure that everything runs smooth, because we want to scale this app to like a million or billion users or something like that? Maybe have a shop or where using or some donation system- or I don't know so, the the possibilities are kind of kind of endless. I would say.

E

D

E

It if it uh blows up like we hope it does, you know we'll we want to. One of the things we want is like the whole paywall thing we talked about is like really important to like figure out how to make it run for free for users, um and I think, a lot of we're gonna do you know, I don't know if we'll do, grant, writing or whatever, but we're gonna ask for. You know: donations to help with that kind of stuff, and uh just.

A

Go from there, I think.

E

That you know with this kind of service this kind of project people will definitely resonate with it and will want to help. You know make it go as far as it can and if, if we have some financial restrictions, hopefully the community can help us out. We can continue on and if not we'll figure it out regardless, because it's you know it's that passion that I'm not going to. Let some money get in the way of me getting this out to people who need it. You know.

E

So if we get, if we get some sponsorships, that'd be great, if not we'll figure it out when that time comes, but uh yeah, that's definitely what we're looking into is some donation or sponsorship based thing to you know, make sure that this can be the best possible app for people who need it.

B

Sounds good, I mean there's just yeah, so many ways to get, um I think like free hosting so, for example, in their youtube description below I've, got my affiliate link for the solution. um So if you pay anything in the future, I might get like. I don't know what it is 10 of it or something, but by signing up you get immediately 150 credit and 150 dollars goes really far, because my my um spaces for 250 gigs cost me 5 a month and my kubernetes cluster cost me like 15 a month, so you can see.

B

150 goes like quite quite far so um yeah. There's this and you know aws does something similar and gtp. I'm sure they all have their own kind of promo thing. So I think you can get the hosting coverage for quite a while. While it's front end, you can get free hosting on github pages as well. um Netlife does lots of stuff. I've never used it, but I know it does lots of things on there as well great collaboration going on on your uh pull request. Already.

B

I see loving this okay, so we'll come back to this in a minute. The collaboration is still going on, but carl has jumped in he got the closes in there yes um and then pre-builds. I love that a bit of a disclaimer and what pre-builds mean excuse me.

B

So um if I click on that, if I, if I run this app on git pod, it might take, I think, like maybe 30 seconds a minute, but if you allow pre-builds on the organization on the reaper, I can't remember what level it's at. What did they write um yeah on the org, then? What it will do is it will cache all of the npm modules and other bits and pieces and so forth. Therefore, it just runs a lot faster next time around um michael's smiling I'm worrying. It usually means I've done something wrong.

B

What am I done wrong? Michael tell me.

D

No, no, no, nothing wrong. I! I was sharing um the git podify blog on the issue and predomina. I said: that's a great blog, didn't even know I didn't know about it. Thank you for sharing and I was like hey. I wrote a blog post a while ago about gitpod and gitlab, actually, which also has some insights into building your own workspace and extending things around kidbot, which is not needed for this project, but it makes me smile because it's a blog post, I wrote.

B

Nice, yeah blog posts and youtube videos are very evergreen. I mean I have videos from two years ago. I'm super embarrassed about, but still get people coming to say, hi and you know views and all the rest. So we're expecting um videos and blog posts on your project laurel and matthew as well. So.

B

Two hours yes, we're gonna have to you know we'll go on until you know. I think till tomorrow, it's tomorrow for me, but we're going for a while, so we'll have to draw a line somewhere and everyone's getting busy with their day and stuff.

E

I saw in chat someone asked if we were if we were new to js and new to developing uh or we're not new to developing, but we are actually we're pretty uh we're all me and laurel at least, are both new um and we're just kind of hitting the floor with the ground running or hitting the ground they're running there. I don't know, I can't even say the uh saying is the saying is right now but yeah.

E

So that's how much we've been working on this stuff is our brains are just mush but yeah we're pretty new um and we're just working hard, and you know doing what we can trying to get our names out there and our faces out there and this project out there. You know, and just it's uh it's been fun and yeah. Hopefully this this uh journey, you all, can keep watching.

E

um If you follow us and stuff watch our dev journey and see from where we started to where we're going, um you'll see on our twitters there's some pretty crude, looking stuff that we made early on. uh So you can see the progress from where we started, where we're at um already in just a short amount of time.

C

Yeah and I think too, it works as like an inspiration for people that are new to developing and new to coding, like there's so much that you can do if you just write stuff with bad code, just to get it out there and make it happen, and you can go back and refactor later and you can create amazing products that can actually help people.

C

Even if you are new- and I think that's like a really good thing to know, because a lot of people want to get down best practices and get down beautiful, looking code before they're ready to expose it to the world and get other people to help it help out on it. But you don't have to get to that stage. I don't think to do that, and sometimes it's better, like eddie, said open source it sooner than later, so that you can make a beautiful project quicker and create a product that can help people. So.

B

Yeah, with the help of the awesome community yeah.

D

Yeah it's. It reminded me of what we kind of say at gitlab, low level of shame, which I kind of needed for myself. It's not perfect yet, but I can show it to the world and we can collaborate on it um yeah. I was just like scrolling over the project. I'm certainly not from the engineer- um and I was we were talking about like dropping permissions afterwards, but um like looking at it now and the idea is, I would love to stay as a maintainer. If you want me to.

A

Just keep an eye.

E

D

And help reviewing progress and things like that, um just to make sure that um yeah that I can also follow along and maybe contribute a little bit um and front end um together, because I think I have no idea how to learn it too. Many courses to too little time reviewing things, I think, is a great way.

A

E

A

Love to help and.

E

Any front-end knowledge I can pass on to you. I will.

D

E

D

Non-Love relationship turns into a love relationship. I don't know.

B

Yes, css yeah, I'm with you, I don't know, love hate relationship as well.

E

I'll teach you how to center a div and then you'll be able to oh.

B

Why does that always make me cringe.

A

I always worry.

B

I'm like 15 years later and then when someone says to this, I'm like oh no, I got that.

D

Can you explain the what is it the exclamation mark, important and the set index? I can explain these.

B

Are these are funny funny.

D

Attributes which keep banging my head all the time.

B

I can explain it really quickly, like so quickly. Silver bullet exclamation mark important, never use it if you're using it something's wrong with the project.

E

I I heard the only reason to use it is you have 10 minutes to show somebody something and you need something to work, so you throw a bang important on it and then you figure it out after the presentation's.

C

Done we'll see you later.

B

But if, if you do that, I guarantee you it's going to stay there forever. No problem and we've got emma saying, love, css, okay, so um any questions we know who to ask yes until.

D

We do the code search now, nothing in there you're you're good to go with open source.

B

Okay, very important, I'm just going to create this issue before we look at git pods automatic testing with cyprus and cucumber just to touch on this. The reason why it's like super beneficial to have automated testing I'm suggesting cyprus and cucumber. There are other tools, but as matthew mentioned, they did a refactor.

B

So um if uh you're gonna, you know test everything manually make sure it works. Whereas if you have automated testing, you can make changes and then you can run and there may be 100 tests in 10 15 seconds and it will drive the cyprus or similar tools. It will actually drive the browser and it will take screenshots and videos if it fails. So you can see what's going wrong, but it's driving it like a user and it can run.

B

You know the happy paths, the sad paths, my sad paths, I mean, if you're expecting an error, do you get an error or you're expecting something like not to happen like? I know you put it in disable mode and you shouldn't be able to click a button. Then it can. It can check that and and so forth. So I'm just gonna gonna raise this. I should put a description I'll leave it open. So I can description later.

B

Let's look at um git pod as well, and if I remember correctly, um https get pods, oh no github, getpod.com or slash hash. Is that correct uh carl did write in the chat. Maybe.

D

The thing is there are, I think there are changes.

B

D

For the project, um this is what uh is it carl.

B

D

B

D

Carl um was saying.

D

Okay, this might break the netlife deployment.

B

Then that was something else if that's for the actual pull request, rather than opening it in yeah.

D

I think you should be able to open it with, and this is me looking in the readme md put in the pull request now.

B

Let while you're looking I'm just gonna, say something that carl shared. um This reminds me of something that I heard once I remember who said it. They said if you ship it and there are no bugs you shipped it too late. I thought it was quite.

B

That's funny thanks mikey, oh in the main branch, like did. I mess it up. I think I'm okay.

D

Okay, you've got it already, yeah.

B

Yeah, the thing is.

D

um You you have to ship it at a certain point and just to to give you an idea like uh gitlab is being released um every every month on the 22nd. Sorry, there were some talks in the background um and like the zero release there might be bugs, um but it might be fixed that they are, after with the patch release. So even if you like have a fixed plan on on doing a release, do it um you can always ship a bug fix release later on.

D

If there is like a huge breaking bark, it makes sense to delay the release. But then again you should ask yourself what are the quality assurance or the automated ci cd checks? Why didn't they catch this? So you can automate many things, not not only.

D

We touch based now on testing and things like that, but you can also test for code quality for um static application, security, testing security scanning overall for secrets which might be leaked for dependencies, which is supply, chain attacks um nowadays, um things which might happen- and you didn't even know about it. So like the the unknown unknowns which come around um and the more you can automate away.

D

The better- and this can be also seen in in the pull request, integrated or as a comment there just to be on the safe side, and I think we we talked about this somewhere last week. We all tried to collaborate on the good, open source citizens, but sometimes a board. A malicious actor might open a pull request, and then you have the possibility that you add something insecure to your to your repository and many other users have that installed use it.

D

um So you also need some sort of review of security in your project, which is why it is great that there are so many tools out there, which you can integrate.

D

Long story short, I know security is boring, but we need to care about it.

B

Oh, it's super important, um definitely, especially when you start going database and back end. I think at this stage, when it's front end only it's probably less of a concern but yeah, it's good to start off with good foundations from the beginning.

D

And I think, like deploying tornado fee or whatever hosting service you're, using um if you use, if you're, having real data inside- and this is especially a problem in in the european union with gdpr and data privacy. You need to take care about certain regulations and measurement measurements, that the data is not being leaked and things like that and it's normally, you shouldn't be talking about it.

D

But it can happen that you, as a private person, get uh in front of the law and someone likes use you for not keeping your data safe and you're like yeah. It's just my open source project and it's hosted somewhere. um So being aware of these things is important, but don't like make it your number one priority when contributing to open source, um because it should be fun and shouldn't be much worrying about malicious or bad actors.

D

We should be collaborating together and when someone sees something flag, it best flag it in private to maintain us or um depending on how the future goes. um Register domain, um handle or host the mail server or get a mailbox with security or abuse, or something so that people can reach out in private and tell you about certain things. They might not be um being able to open a private issue or something.

D

I'm not hoping that it catches you it's just just.

B

D

B

It's good to be aware of things, so I've opened this in git pod. I didn't use the badge because it hasn't been merging or anything like that, but in the pr I pre-pended it as um carl said, of https colon for four slash, get pod dot, io four slash hash and then just everything else on github's, exactly the same, so what it did was. It gave me vs code in the browser it's run, um npm install and it's running the the project and you can see the preview on the side here.

B

I don't know if I press it, I can hear it. I don't know if anyone else can hear it, as I click things, um but probably not so it's coming out my headphones.

D

Pretending to to be hearing okay,.

B

Not not alone um and.

D

B

You can then, uh yes see it.

D

Yeah the thing you can do if the if the port is made public, which I think currently it is not. You can theoretically share the url with everyone of the of the git of the port and we can like click around. But I'm not sure. I think the previous setting by default is only you, but this.

E

Is the possibility.

D

If you want to collaborate and showcase the current state of development in a live environment, you can share the git port, the git port port url, something like that.

B

Sense, um yeah we've collaborated another way. I can't remember how I'm at I remember. We installed vs code liveshare or something, but there was well there's something built into github. I can't there is a way to to do it, um so this is the the pr um this pr adds parcel bundler. So yes, this is what carl was saying was a bad pr and the reason why is his 95 files changed, which is obviously a massive massive um pr, but his warning this might break netflie deployment.

B

So I want to leave this, I'm not going to merge it I'll leave it for you both to review um and then and then chat with carl uh as well um about it too. So I'm not gonna merge this. You can have a look through it. This.

E

Is the basically.

B

This is the get pod config and most of it, if not all, of it is kind of from the template. I'm not going to go through every line, but um the important ones are this one and this one and then this is for the pre builds which wouldn't affect now anyway. um If you add it to the organization, then you get the benefits, so it puts badges in the in the in the pull request. So um the pull request appears like at the bottom or the top.

B

I can't remember, and you can just click it, and then you can just review that progress. You have to stash your changes locally to then switch to a branch to test it. You can actually click the button have a play in the browser. If you're happy, then you can, you know you can merge it.

B

So yeah, okay, we've been going for almost two and a half hours. I think it's probably a good place uh to um to to stop and uh any final thoughts or questions from any of you. I'd love to um include it now and everyone's being super supportive schmidt said going for two hours. That was like half an hour ago. Thank.

A

B

um And thanks everyone for watching listening. So what would you all um any of you like to add anything, any closing notes.

E

uh I'll I'll just say that uh please be patient with us, as this is all so new to us. So, like you know, we might not get to the issue or pull requests in like as quick as some other projects, as we were going to be going over going over everything very thoroughly as it's all new to us, because we want to make sure that we are doing this correctly and and pulling the right stuff emerging, the right, stuff and and uh making sure that's good to go.

B

C

B

C

Yeah completely what matthew said and also um if anybody would like to like help, give us advice and guidance on how to run this project or how to run a project and different. I know we have michael on board now so that I love that that makes me really you're.

A

C

Here than you could probably imagine.

C

Yeah anybody that would like to like lend a guiding hand in the project management kind of aspect of the project as well and like best practices and how to go about it and yeah just give advice. We would love any advice or guidance that anybody has to offer and any help on the project that you guys would want to help in any aspect is more than appreciated and yeah the more the more the more the merrier. But, as you said, we're really needed to this, and this is really our first go at it.

C

So I yeah we're going to be a little bit slow, probably slower than other people.

B

Yeah we're all always learning, so it's part of the fun um uh sounds exciting and uh you know looking forward to seeing how it all goes uh mike. What about yourself any closing thoughts.

D

I think it's um for two and a half hours we kind of did touch base a lot of topics. um I think one remaining task is to review what we plan for the stream in the discussion and and to open remaining issues. um This is something I started, but together we are faster and um yeah from there.

D

I would just say: let's focus on defining, what's needed to to kick it off in the sense of like adding a code of conduct populating the readme and copying some some templates over um yeah, and then I have some ideas around registering a domain, doing certain things um doing a pages hosting something where people can like really discover it hosting the demo, and things like that. This is this is really like.

D

Iteration um just um focus focus on things now and I would encourage everyone who's listening now or maybe watching the recording reach out um on for this. For this project there is no community yet, but I would just say, let's use eddie hub and make it um make it a little umbrella if that's okay, otherwise just ping us on on social or twitter and create issues create pull requests.

D

And even if someone is not responding in a pull request, try reaching out, um we might all be just be busy, and I promise you I will. I will be busy up until kubecon in may. So um if, if something merchants come comes up, kindly ping us uh to to really make the reviews happen or ping eddie, and he will make it happen.

B

Yeah, no, don't ping me chat to us publicly and then someone else probably beat me to it. But if yeah, if ta do tag me, if you need my or help but usually because of time zones and because of me getting so many notifications, I'm usually the last to reply, um but I love it. How yeah? Let's just use the eddie hub discord, that we can chat in there it's about open source and collaboration. So it's a great way for you to get more contributors talking in public um mma is a really good point.

B

Don't feel like you need to tackle all the issues yourself. I love this. Thank.

A

E

D

When I say ping, I'm using a this is the wrong term. This is something uh admin thinking um uh take me in public, because I don't respond to dms often, and I really prefer transparency and collaboration in public.

E

D

We're going to have a discord.

E

Eventually set up for this project, but we don't need to get into that yet.

B

Yeah, don't distract yourself straight away, I would yeah do it as and when you need, because you need your new bots, you need to protect yourself from spammers and maintainers and yeah focus on the organization first, and you can move over later um and uh emma's. Also saying do you know she'd like to help out when schedule comes.

C

Down as well, which is awesome, I love that we love that so.

B

E

Be a it'll be a lengthy process. Getting this thing I feel, like it'll, be a work in progress forever, which will be fine, because you know new things. New new features all that stuff as they come out. If something comes up and we might think it's done they're like well wait, there's this cool feature we can add, and then no it's still not done so definitely excited just to see where it goes, and- and thank you, for you know all the help already that you all have put into this project.

E

um I was not expecting so many issues and pull requests so far. um It's great to see um it's great to see that people have interest in this project as well.

B

Yeah, it's uh you know already doing super super. Well. I can't wait to uh wake up tomorrow morning or later on this morning and see all those numbers climb and see all the amazing collaboration. That's been uh been going on, so um I I can't wait. It's gonna be super exciting. Thank you all so much for for joining. I really appreciate it um and always keen to geek out everyone don't forget to give this video a thumbs up and follow my amazing guests below and uh yeah. Everyone have a great week, uh my guest.

B

If you could stay on for a few more minutes, I want to end the stream and I'll just thank you personally um and uh yeah. I see the amazing support by everyone. I'm sorry, michael, is going over your face still.

D

B

Thanks, everyone have a have a um a great week, we'll chat soon.

E

Bye, everybody.

C

A