10:00

happens there is the

10:02

community has looked at various parts of

10:04

the UI and improved the UI given

10:06

better error messages on login screens and

10:09

things like that just because they're using

10:11

the software. Hey I'm using I'm a

10:13

member of this this software I'm using

10:15

it if I don't like how this

10:18

is outputting this error message I

10:20

can just go in there and make it a

10:22

little bit better at a little if statement there

10:24

a pop in a nice little error message and

10:27

granted that's a very optimistic view of how community

10:29

driven open source works but at a small scale

10:31

you know a handful of people using this stuff

10:33

it can be really just a nice experience now

10:35

granted when you get into code

10:38

bases like VIT or something it could be

10:40

a nightmare of contributions and people wanting to

10:42

mess up things or change things or have

10:45

their opinions or be angry or mad but

10:47

I do like that the community aspect of

10:49

it definitely and I

10:51

think for people that are wanting

10:53

to get into open source for whatever reason like

10:55

wanting to become an open source contributor that's typically

10:57

where it starts is you're using some piece of

10:59

software and then you come across a

11:02

bug or a feature that you would like and

11:04

you just work on it so I did this when I

11:06

was using and learning about coolify so

11:08

there were some like bugs in the UI that I

11:10

came across and I was like might as well I

11:12

mean I'm using it might as well try and fix

11:15

it so that got me to pull the repo down

11:17

make a PR and I think I'd like four different

11:19

PRs that got merged into coolify just because I was

11:21

using it and I found some some ways to improve

11:23

it yeah that was that was pretty neat of

11:25

you by the way so

11:29

let's talk about the different types of licenses

11:31

you'll might notice that anytime you create a

11:33

new project on github if

11:36

you're in the UI at least if you

11:38

if you click new a new repository you

11:40

know you enter your repository perhaps there's a

11:42

little checkbox that says add a gitignore or

11:44

add a readme when you might notice that

11:46

there's also choose a license and

11:48

from here this is the easiest possible

11:50

way to choose a license that

11:53

might suit your project because it's just going

11:55

to initialize your project with that license and

11:57

if you know what you want or what

11:59

type of license license you might want. If

12:01

you just want to throw MIT on there,

12:03

it's super easy to one click MIT and

12:06

then your repo will then have

12:08

that license. So let's start off talking

12:11

about the different types of licenses.

12:13

And the first ones we're going to

12:15

be getting into are the permissive

12:17

types of licenses and permissive in this

12:19

context means you can do

12:21

more with this code. They're

12:24

less locked down. Yeah. And

12:26

the first one and probably most popular is

12:28

the MIT license. And it's very simple and

12:30

readable. And honestly, I'm just going to read

12:33

the first clause in it because you've probably

12:35

seen this before. So it says, permission is

12:37

hereby granted free of charge to any person

12:39

obtaining a copy of the software and associated

12:42

documentation files to deal in the software without

12:44

restriction, including without limitation, the rights to use

12:46

copy, modify, merge, publish, distribute, sub-license, and or

12:49

sell copies of the software and

12:51

to permit persons to whom the software is furnished

12:53

to do so subject to the following conditions. But

12:56

basically, when you put this license on

12:58

your software, you are saying anyone

13:00

is allowed to take my source code and do

13:03

anything they want with it. They could take that

13:05

source code and then close source it. They could

13:07

make it so that any changes they make, no

13:09

one gets to see. They could take that open

13:11

source repo and literally just start a business off

13:14

of it. Like they could create commercial software. They

13:16

don't even have to modify the source code. They

13:18

could literally take that repo, decide to host it

13:20

somewhere and start making money off of it. With

13:23

that also is the like the last clause here,

13:25

that basically prevents the creator of the software from

13:27

being liable for anything. So let's say you had

13:29

some software that you didn't put the MIT license

13:32

on, but maybe you did allow

13:34

people to use your source code. If they started

13:36

a business with that software and then something went

13:38

wrong, maybe somebody got hurt, or maybe

13:40

it lost them money or something like that. If

13:42

you didn't have this little clause here on the

13:44

MIT license that says like, I have no liability

13:46

for what you do with my software, then you

13:48

potentially would be liable. You could get into some

13:50

legal trouble there. So that's another reason you would

13:52

apply this license to your software is because if

13:54

somebody decides to go use it and maybe a

13:56

way you didn't intend or something goes wrong, this

13:59

is a good idea. the

26:00

way, I don't know if I really

26:02

got the anger towards

26:04

Redis, because before Redis

26:07

went under a new business license,

26:09

I had almost never considered

26:11

if I was going to pay for

26:14

I usually host my own Redis.

26:16

But if I was going to pay for

26:18

a Redis, which we actually kind of do

26:20

with up stash here at syntax, I

26:22

would have not gone to Redis's website, because

26:24

I just did not know that they had

26:27

a paid service, I'm going to be entirely

26:29

honest, I've been using Redis for so long.

26:31

And I had no clue. They had their

26:33

own paid service. So for me, it's like,

26:35

Oh, yeah, they they wrote their software. It's

26:38

not like it's an outrageous amount of money.

26:40

I'm gonna typically host mine myself anyways. But

26:43

yeah, I mean, I get I get how people could be

26:45

upset by it, maybe built a business off of it. But

26:47

end users, man, it's really not that hard to host your

26:49

own. If you got your own server

26:51

setup somewhere, it's pretty trivial to spin

26:53

up a Redis instance. Definitely. And

26:56

so yeah, those are the types of licenses. I think

26:58

one of the last things we'll talk about here is

27:01

choosing license and then also like, acknowledge

27:03

acknowledging licenses. So if you

27:05

use software that is under the MIT license,

27:07

technically, the MIT license states that you have

27:10

to include this license in your own software

27:12

whenever you rerelease it. Yeah,

27:14

so it says the above copyright notice and

27:16

this permission notice shall be included in all

27:18

copies or substantial portions of the software. And

27:20

so you may be wondering, all right, I'm

27:22

using a library that's MIT, what does that

27:24

mean? A really good example of this is

27:27

discord. So if you go to discord.com/licenses, they

27:29

have every single dependency listed here that

27:31

they use like in the discord mobile

27:33

app or the discord desktop app, and

27:36

the associated licenses. So things like

27:38

babble are listed here. Yeah, there's

27:40

just a whole bunch of like

27:42

babble dependencies. And they literally have

27:44

the MIT license from Sebastian McKinsey

27:46

listed on this page here. And

27:49

then yeah, there's some other

27:51

babble licenses. And then we

27:53

get into like AWS libraries and stuff like that. These

27:55

are under the Apache license. And so you see that

27:57

listed here. And so this is like a really good

27:59

example