Involving git as in the theme or git as in it’s used to sync data between the game and some sort of git repo? I think that would be pretty interesting either way. For the latter, a git repo might be used to add more adventures to explore or treasures to find over time!
If you mean somewhere to host a git repo, if your project is going to be FOSS, Codeberg is a great option. If you want to self-host, Forgejo is awesome, since you can have full control over the data (you will need to set up stuff to make it accessible over the internet though). Aside from Codeberg and Forgejo, you also have GitLab and others, which could be what you want if your project is commercial and you don’t want to self-host
I doubt you really need to speak to them for anything. It would be better if you could properly describe what you have in mind because I don’t think you really understand what git is.
No I do not. Why would you need to speak to them? You just create an account on their website, and you can add any kind of code on Codeberg as long as it has a open-source license and it isn’t illegal.
Let’s dissect thus term by term. First, what is a license?
In a nutshell, a license lists what you can and cannot do with something. They can apply to both software and code as well as things like art and music. You might have heard of Creative Common licenses and things that are “free for noncommercial use” or “only for personal use”.
Open source means that others view, modify, and redistribute the source. They can apply to software as well as hardware, art, music, etc. If you want to look at the specific terms, search up the Open Source Initiative. The Free Software Foundation also has their own definition you could look at.
So, an open-source license is a list of things you can do with something, usually but not always software, that aims to allow others to view, modify, and redistribute the source.
There are multiple open-source licenses, and they each have their pros and cons, but there is a general split between permissive and copyleft licenses. Permissive licenses (like Apache, MIT, etc.) try to provide the user more freedom by having no restriction on how the source can be used, while copyleft licenses (like GPL) aim to ensure that freedom will last by restricting how closed-source projects can use open-source licensed bits.
There is a large debate between the two that I won’t get into, there are plenty of articles available discussing points for each side.
Involving git as in the theme or git as in it’s used to sync data between the game and some sort of git repo? I think that would be pretty interesting either way. For the latter, a git repo might be used to add more adventures to explore or treasures to find over time!
Can you suggest some easy repo to start with ?
If you mean somewhere to host a git repo, if your project is going to be FOSS, Codeberg is a great option. If you want to self-host, Forgejo is awesome, since you can have full control over the data (you will need to set up stuff to make it accessible over the internet though). Aside from Codeberg and Forgejo, you also have GitLab and others, which could be what you want if your project is commercial and you don’t want to self-host
I wish to do it public as I don’t have the means to self-host. Which would be a nice open source community platform ?
Codeberg is probably the way to go if you are making the game open-source. GitLab or similar if it’s commercial software (i.e. closed-source)
Do you know the folks behind codeberg ? I need to speak to them regarding this.
I doubt you really need to speak to them for anything. It would be better if you could properly describe what you have in mind because I don’t think you really understand what git is.
Absolutely 💯
No I do not. Why would you need to speak to them? You just create an account on their website, and you can add any kind of code on Codeberg as long as it has a open-source license and it isn’t illegal.
I need to understand what’s an open source license.
Let’s dissect thus term by term. First, what is a license?
In a nutshell, a license lists what you can and cannot do with something. They can apply to both software and code as well as things like art and music. You might have heard of Creative Common licenses and things that are “free for noncommercial use” or “only for personal use”.
Open source means that others view, modify, and redistribute the source. They can apply to software as well as hardware, art, music, etc. If you want to look at the specific terms, search up the Open Source Initiative. The Free Software Foundation also has their own definition you could look at.
So, an open-source license is a list of things you can do with something, usually but not always software, that aims to allow others to view, modify, and redistribute the source.
There are multiple open-source licenses, and they each have their pros and cons, but there is a general split between permissive and copyleft licenses. Permissive licenses (like Apache, MIT, etc.) try to provide the user more freedom by having no restriction on how the source can be used, while copyleft licenses (like GPL) aim to ensure that freedom will last by restricting how closed-source projects can use open-source licensed bits.
There is a large debate between the two that I won’t get into, there are plenty of articles available discussing points for each side.