Revert "Revert unlicensed contribution" #24
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/flake-compat#24
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-16-mit-license"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The last contributor has agreed after all. Maybe I acted one day
too soon? In that case, apologies for the drama.
This reverts commit
14dbada01f
.Thank you @zanculmarktum for clearing this up.
Pardon for being the cause of the (little) drama.
I rarely check this repository and rarely check my email as the only reason I became a contributor of this repository was so I could push my code upstream and for that reason alone.
I wasn't intending to become long-term contributor or anything.
I guess I need to be more responsible, sorry guys :^)
@zanculmarktum Don't worry about it! This is a known problem with open source. You're neither the first nor last who's been in this situation.
This is generally a completely fine way to contribute. It's up to the maintainer to decide whether a contribution is sustainable. Implicitly requiring a commitment from contributors would be a far bigger problem. The thing is, in most cases, problems with a contribution can be solved by anyone who puts in the effort. That's just not the case with licensing, at least in general.
However, in this case the "de minimis" exception was applicable but I amplified the drama for no good reason. I was overly careful.