| Okay, so here is the type of license that generally work for me for open source projects. I usually open source software because I've created something useful. I think other people might either find it helpful or develop upon the idea to do it to take my idea and ability further. Attribution is always appreciated but I'd only want to make it mandatory if that wouldn't really sort of create friction with other people who'd like to use a project. <br><br>But attribution really helps me because it opens up the relationship and connectedness of open sourcing because if someone were to use it downstream, they have a way to sort of get in touch with me. People commercializing open source software doesn't sit very well with me, but again, it's only if it's, I'd be very reluctant to add that as a limitation. <br><br>Other than that, nothing else really stands out to me as something that I'd require. Like if people took it in any other direction, it's fine. The only one I think about sometimes is obviously no one wants something that creates to be sort of misused or used for harm. And one also doesn't want to end up with lawsuits if something they create is misused, so I don't know if there's any legal language that can create a little bit of protection around those potentials. |