Never done that before.

Open source has become a huge part of the software industry today, and it's something that I really like.

The idea.

The idea behind open source is pretty much what it sounds like.

Software with source code that is open for anyone to download, to view and edit.

Essentially, anyone can download the software and fix bugs ad features and just help make the thing better.

This is something that could help improve not only the use of experience but also improve the safety of the software.

More people are looking at the code, and so there's a higher chance of catching mistakes and fixing vulnerabilities.

Okay, So, like I said, I've started an open source project, which I'm really excited about.

And the thing is that when I started it, I sort of you with the basics of open source software.

Kind of meant, which is that a lot of people work on one project together instead of like a single person or a single team.

But beyond that, I didn't really know too much about it, and I had very little experience with it, especially regards to like running one myself, and I still don't really.

So a lot of my time in the past week has been spent just trying to learn more about it, trying to figure out how to structure a project for open source, how to make it clear for anyone who wants to contribute, how they can actually contribute, thinking through the project and trying to create issues and milestones on gift.

Tubb for all the things that need to be done, which is pretty boring and difficult to do and takes a lot of work.

But doing all those things also saves time in the end, because it hopefully makes it easier once coding actually starts.

So I'm not an expert in this at all, rather the opposite.

I'm very new to all of this and how old that works, but I figured that the best way to learn is to just start.

So I created this open source project, and it was originally going to be a one day build until I kind of realized that it was way too big to just do in one day.

Here's the idea.

I want to automate my planning, meaning that planning meetings or even just catch ups with friends is usually a really tiresome back and forth where you suggest the time and then the other party can do that time.

So they suggested time.

But then you can't do that time, and it just keeps going until you find a time that works.

For both parties, the idea is to create a website with some sort of calendar where you can ad in the times when you're available for meetings and then when someone contact you and wants to book a meeting with you, you can just send back a link to that site, and then they can go in on their own and they can see all the times when you're available, and then they can find a time that suits them.

And then they can request a booking for that time.

And when they request that booking, you should get notified and they you can either approve or disapprove that booking, and then once it's approved, it should automatically get added to your calendar of choice.

So that's kind of the idea.

Oh, and also, while we're on the topic, this video, sponsored by atlantic dot net atlantic dot net provides great VBS hosting, and they're offering a free one gig virtual server with SS teas and block storage for free for a year, plus $50 in free credits to use for other service is that they offer.

Try atlantic dot net to develop tests or launch your next projects.

Unlike many other big names, they have great, always available technical support and their support.

People actually work there, which is something that's really important for me, especially when I get stuck late at night coating on some problem and I want to get help straightaway.

They actually provide this, which is great.

Go to atlantic dot net slash cow and use a Cuban code cal with capital letters to get a $50 credit.

So I don't know if you can tell or not.

But this is a pretty big project, and at least for me, it would be very difficult to do on my own.

But it's perfectly suited for an open source project, and so that's my idea.

And this video is basically just to let you know that if you want to help out, I highly encourage you to do so and No, you don't need to be an experienced developer to help out.

You can't break anything, so just go to get tub.

There's a link to the repo in the description Fork the repo and see if there's something that needs to be done that you know how to do and then you're off to the races.

I really want to emphasize that there's literally no pressure for you to be a pro where anything like that to be able to contribute to this project.

I'm not a pro.

Just check out my life coating on my life cutter channel and you'll see that, like half the time, I have no clue what I'm doing.

So if they say it's interesting to you, then don't be afraid to give it a go.

If you go to the repo, we have a project board where you can see three different columns to dio ready in progress and completed.

You can pick any issue from the ready stack, assign it to yourself and move it over to the in progress stack, and they should be information on each issue regarding what needs to be done and how to know when it is done.

And once it's done, you can create a pull request and name it to the corresponding issue and you're done.

And in case all that sounded like gibberish to you, then don't worry, because it did for me to once.

But it really isn't that difficult.

You just need to do with, like, once or twice, and then you get the hang of it.

I'll also add some resource is in the description that I think could help.

The idea is to have this be a website where you simply create an account and then you can start using it.

I did a poll over on my life coder channel, where I asked which framework we should use for building at the site.

And the winning suggestion was to use Jango with Python to create the site.

And then we're going to use Fire base for the back end part of it, which really isn't a major focus.

All we need is for people to be able to sign in and to see that calendars with available times.

So it's a fairly uncomplicated back end that we're gonna need for the project.

That and the fact that I don't think too many people are gonna use.

It means that firebase will do fine for the back end to start out with the least.

A few people have suggested building an app to go along with this sites, and I think that that's a great idea.

But I don't think that it's high priority right now because I think that the main use case will be that someone send you a message wanting to book a meeting, either via text message email or something else.

And then you'll send back a link to the site and then they can go in and book a meeting with you themselves.

And I think that that's gonna be the easiest way of interacting with this compared to if we create a nap, then you'd have to get them to download that app, create an account within the APP and then find your profile and then book a meeting with you, which I think is a bit more of a hassle to d'oh and therefore I think that the main use case will be just sending a link to a site.

But further down the line, I think that it definitely will make sense to create an app to go along with this, a swell who knows?

It might even be a one day build.

And to be honest, that's the really cool thing about open source, the fact that anyone who wants to can contribute and come up with new ideas for what this software should be.

We've already had several contributions and pull requests to the repositories, which is awesome and exactly what I was hoping for.

So thank you to everyone who has contributed to the project so far, so that it's my idea for this open source project and I'm really excited about it, and I think it's a really good idea as well.

I mean, of course, I think it's a really good idea, but I do think that it's something that can be very useful for a lot of people.

So I really want to make this happen and, yeah, that's it for this one.

I hope you enjoyed it.

And also in case you want to come hang out with me as I do some live coding.

You could do that over on my other channel called Live Coder, where I will do some live streams every now and then.

So if that sounds interesting to you, then you can go subscribe to that channel for some pure longform coding sessions.

All right, that's it for this one.

I hope you enjoyed it.

Maybe this can also be something.

I'm thinking that this could be a nice thing just for people to see or for you guys to see how bad or good I am.

A programming in real life like this is how good or bad I am.

And, uh, since it's live, you can see all the errors.

You can see how much time it takes me to do these things because I feel like on the other channel, Sometimes people tend to think that I'm like some extreme expert when it comes to this stuff, which I'm really not.

And I think that this, like live streaming this sort of stuff maybe makes it a little bit Maur seem a little bit more achievable because you can see that even though I could do all of those things on the other channel, you can also see how how much time things take for me and how many errors I run into and how many random difficulties that I d'oh and stupid mistakes I make, and ah, that might make it.

I'm hoping that that will make it easier or make you feel more achievable for people.

Because really s you, you'll probably be able to tell here, Um, I'm not an expert, and I'm not perfect when it comes to coding.

It's not like I just write things once, and then it works.

Um, so, yeah, I'm hoping that this will be something that was interesting to watch and just come hang out as I code different projects out.

But yeah, next time is going to be a log in screen and connecting a flutter app to firebase, basically.

But that's it for this one.

I hope I'll see you in the next stream as well.