• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2023

help-circle











  • Either you misunderstand or the person you are responding to is. If you retroactively add a license to the current state of the code (for example by committing a new LICENSE file and adding the new license to the top of each file), or course that applies to the entire state of that code as of that commit. What is more difficult is that earlier commits won’t have that license explicitly unless you rewrite git history to make that happen (which is possible but tedious).

    You can always relicense code you own the rights to. You can even dual license it, or continue to use it commercially in terms contradicting the license you open sourced it as, as long as you have the permission of every contributor.

    The idea that a license added would only apply to code added after the license change is very funny.


  • If you put a quarter of the effort you put in this post into apologizing for the misunderstanding arising from trying to submit something you hadn’t tested thoroughly and then another into finishing the patch up none of this essay would be necessary.

    You feel “extremely disrespected” which is an overreaction to what was said to you. It allows you to be self righteous instead of reflecting honestly.

    All the things you’ve listed that you think you did wrong are kinda right, but you’re only listing them so we think you’re being reasonable and we won’t attack you on them. You’re listing them here instead of acknowledging them in the github thread and realizing that what you think you said and how you are perceived can be different, because you don’t like the idea that someone else might think you were wrong. The only person who is allowed to insinuate that you were wrong is yourself.

    There’s not a lot of glory in OSS and there is a lot of ego and butting heads. If you love doing this stuff, you gotta get a bit more calm and resilient.