If I intend for something to have a mostly educational tilt, I lean on the Mozilla Public Licence 2.0. The boundaries are at the file, so if someone else wants to incorporate the MPL-licensed stuff into their stuff, the whole does not need a relicensing; only the MPL-licensed parts have to remain that way and distributed under those terms.
Otherwise, I prefer the three-clause BSD licence. I warmed up to this after I started getting involved with the BSD communities, where there is very much a don't-reinvent-the-wheel attitude; the BSD licences allow for that sort of thinking on a wider scale. Unlike the operating system projects, however, I actually have the energy to respond and want to know who wants to use my or the project's name in derivative works. Again, the boundaries are at the file.
For ham radio stuff, GPLv2 for any user-facing (ie not a library) stuff. We continue to have problems (although fading, thankfully) of code and implementations released under proprietary terms in a community and service where openness is required by regulation. Libraries, see above.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Depends on the project.
If I intend for something to have a mostly educational tilt, I lean on the Mozilla Public Licence 2.0. The boundaries are at the file, so if someone else wants to incorporate the MPL-licensed stuff into their stuff, the whole does not need a relicensing; only the MPL-licensed parts have to remain that way and distributed under those terms.
Otherwise, I prefer the three-clause BSD licence. I warmed up to this after I started getting involved with the BSD communities, where there is very much a don't-reinvent-the-wheel attitude; the BSD licences allow for that sort of thinking on a wider scale. Unlike the operating system projects, however, I actually have the energy to respond and want to know who wants to use my or the project's name in derivative works. Again, the boundaries are at the file.
For ham radio stuff, GPLv2 for any user-facing (ie not a library) stuff. We continue to have problems (although fading, thankfully) of code and implementations released under proprietary terms in a community and service where openness is required by regulation. Libraries, see above.