Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Choosing a license depends on what you want to do and what you want to control. You haven't said anything about that.

    My goal for my publicly available code is that people can use it. Putting "under the same terms as Perl itself" seems to accomplish that goal, and I don't think about it any further.

    Some people like to go on and on about licenses, but I tend to think it's mostly just shifting the bits around with providing any more real benefit to the world. I just want people to be able to use my code. I'm not much for GNU religion, etc.

    If you have some other goals, then a particular license may work for you. First, though, figure out what you want to do.
    • Right.

      My primary goal is to make a contribution. That means that I want people to be able to use, learn from, contribute to, and improve on my code.

      That said, I'm not particularly happy on giving somebody the right to license my code under terms I haven't even read because they don't exist yet.
    • And this isn't a question about which license I should use. I wouldn't be asking that on use.perl. I simply want to know how a particular choice of license would affect others.
      • Some concerns:

        If you plan on having your code go into core, then providing it under a licence different from that of Perl is going to be a serious issue.

        If you want to avoid burdening commercial users of your code, you should stay close to the pack, because some of them will have to have everything vetted by the legal dept. before they can use it. The less new text you introduce, the more likely that will succeed.

        • If I were to write anything that was considered for inclusion into the core, I would be happy to relicense it under "the same terms as Perl itself". Most modules IIRC don't go into core without other revamping as well, so it would be the perfect opportunity for a relicense.

          The "avoid burdening users" thing is exactly what I'm trying to figure out. Commercial users have to get everything vetted by their legal department, but a ton of people don't even have a legal department to check things with. I'm trying