Hi, > On Nov 26, 2024, at 7:00 PM, Jim Hall via Freedos-devel > <freedos-devel@lists.sourceforge.net> wrote: > > (added paragraph breaks to your email to make it easier to read) > > >> On Tue, Nov 26, 2024 at 3:59 PM Davide Erbetta via Freedos-devel >> <freedos-devel@lists.sourceforge.net> wrote: >> >> >> Dear all, >> I'm new to this mailing list and maybe I'm asking a silly question, if >> so I apologize in advance. >> >> I'm enthusiastically using FreeDos, FED editor and OpenWatcom to develop >> a small program to mimic the RPN Voyager HP10 calculator with a text >> user interface with the C conio library (thanks to Jim Hall for their >> nice tutorials!). I'm doing it just for fun and I'm not interested to >> replicate all the calculator functionality but just some basic >> functionalities. So of course it's nothing comparable to all the great >> RPN calculator simulators available on the web. > > > I'm glad you like the videos and that they're helpful. That's why I > make them! :-) > > >> At a certain point I would like anyway to share this small code just in >> case someone want to try it. Since I'm an hobbyist programmer I've never >> done it before, so what would be the best way to share it ? should I >> share with under GPL or something similar ? >> >> Since everything is done in FreeDos I though this was the best place to ask. >> Thanks to anyone that would like to give me a hint. > > > If you want to share your code, there are several options: > > Sourceforge.net will let you set up a "project" where you can post > your project. But Sourceforge.net has a lot of "overhead" (like a News > feature, and Bug tracker .. things you don't need) so this is probably > not a good option for a beginner. > > GitHub.com or GitLab.com both let you share source code. You can > create a repository for everything you want to work on -- you don't > have to share a repository, you can also make a repository private so > only you have access to it. Both have features that you may not be > interested in .. but they are easy to ignore, so this is probably a > good option for you. > > All of these sites let you set up a free account. > > You also asked about licenses. You can pick any license that you like. > Everyone will have their own preference, and I'm sure others will > chime in too. Ultimately, pick a license you like, and use it. Popular > licenses include GNU GPL version 2, GNU GPL version 3, MIT, BSD > 3-clause, BSD 2-clause, and Apache 2.0. The Open Source Initiative has > an archive of all the "approved open source" licenses on their > website: > https://opensource.org/licenses > > For myself, if I'm working on a larger, more complex project, I might > use the GNU GPL version 2 (I don't like some of the terms in the GNU > GPL version 3 .. but those terms don't really apply to DOS stuff, so > there's no point for me to use version 3 anyway). But these days, a > lot of my source code is just "demo" code, so it's pretty trivial. > Anyone could write something similar on their own. For those projects, > I might use the MIT license (I could also use BSD -- I just happen to > use MIT). I would give this "demo" code away as "public domain" but > not every country agrees what "public domain" means, so that's why I > use a permissive license like the MIT license. >
As for “Public Domain” there is always the “Unlicense”. https://unlicense.org/ :-) Jerome > > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel
_______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
