Im working on a project for some software I want in the world. But I'm such a hobbyist that I've never thought of publishing any of my projects, but after doing so much work in it I kind of want other to have access to it after I feel its ready.

Whats the process of distribution? I guess I typically use github when interacting with FOSS community, but its still confusing for me to navigate as an end user sometimes, let alone being an uploader.

FWIW its simply a few python modules and other supporting txt and jsons. Targeting mostly Windows because that's what I use.

Thanks! (If this isn't the right place to ask please let me know!)

Edit: there are a bunch of great comments here! To clarify, I want to get it functional and somewhat bug free then fully upload everything so someone can see my idea and do it better. So I think I'm going to go with unlicense, because I don't really care about getting credit or getting contributions necessarily. Thanks all!

you are viewing a single comment's thread
view the rest of the comments

[–] Lodra@programming.dev -4 points 6 months ago (4 children)

Open source software literally means that the source code is available to anyone. In GitHub, that just means that your repo is public rather than private. But your method technically doesn’t matter. You could publish to a forum if you wish. That’s still open source!

Free OSS just means that anyone is free to use and modify the source code for any purpose. The details are usually defined in a LICENSE file.

I feel like you’re really asking about the common practices and methods used in FOSS. Right? If so, that’s entirely up to you as the maintainer. As the project matures, you may attract other contributors which will in turn will motivate change to your tools and methods.

Start with what works for you. Model after similar projects if you wish. Adjust as change is needed.

[–] CosmicTurtle0@lemmy.dbzer0.com 14 points 6 months ago* (last edited 6 months ago)

Open source software literally means that the source code is available to anyone. In GitHub, that just means that your repo is public rather than private.

You can make publicly available any code that is fully under copyright. The reader cannot compile, modify, or redistribute it. It's called "source available".

Open Source has a specific definition that has been tested in court, which means that you are able to make modifications, transform, etc. within the confines of the license that is provided with the code.

There are two types of "free": free as in gratis (free beer) vs free as in libre (free speech). The OSS licenses very clearly dictate by which means that you are free.

Edit: added a source

[–] brisk@aussie.zone 8 points 6 months ago

While that is a definition that's used by some, I would argue The OSI's Open Source Definition is more widely used within the field

[–] chebra@mstdn.io 1 points 6 months ago

If you find a piece of code in a forum without any license text, and you use it in your software, you could be in a lot of trouble, and not just because the code might be bad. Code without a license is NOT open source, nor public domain, nor free to use, https://opensource.stackexchange.com/a/1721. It needs to have a license that explicitly allows use, modification, redistribution, only then it is open source. You may have seen some "openwashing", someone trying to redefine the term to make them look good