Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • chromatic: I did not realize until an hour ago, thanks to Limbic_Region's reminder, that it is possible that the "the src/ tree" in my journal entries was likely to be parsed as "the entire source tree".

    I think I owe Pugs contributors in general, and you in particular, for having conveyed this intent-of-change very badly.

    Also, by reading your journal entry, it did not occur to me until later that it is the public domain implementation that you are opposed to, instead of my maximum unrestricted reuse intent. So, apologies for proceeding the rewrite too soon before discussing this matter in more detail with you.

    Can you check my clarification [blogs.com] entry and let me know if there's anything you'd like to see clarified further?

    If you are willing to contribute, under the MIT license, to src/ tree again -- especially next week when we completed the switch to use Perl 6 Rules instead of Parsec for the parsing and Perl 6 itself for first-stage semantic analysis -- please say so, and I will change the SQLite terms to MIT-license terms to comply with your wish.

    You are too valuable a contributor to lose, especially now we are inching closing to self-hosting. :-)

    Thanks in advance, and apologies again for my inability of communication...

    • Audrey, You are a free-spirited, brilliant, good-natured guy. I feel sorry that the GPL ideology makes things so complicated that you have to apologize for something. After Parrot, I chose not to participate in anything that smells like GPL ever again. I like the BSD or plain Public Domain style licenses just fine for stuff I want to give to the world, otherwise, if I care so much about how someone might use a piece of my code, I keep it private in the first place.
      • Thanks for your kind support -- it's true that I'm a free-spirited girl, which sometimes can upset people through lack of detailed explanation.

        I'm glad that this particular issue is resolved now... Though I'm of the copycenter [faqs.org] inclination for my fun projects, I did use copyleft in the past when I have a industrial interest in the code -- i.e. when I worry about proprietary competitors, and I think TPF is wise (and right) to worry about that. :-)

      • feel sorry that the GPL ideology makes things so complicated that you have to apologize for something.

        I don't know where you picked up that impression, but if it's from what I've written, I have done a very poor job of explaining my reservations.

        • I don't know where you picked up that impression, but if it's from what I've written, I have done a very poor job of explaining my reservations.

          Your original post came across to me as a passive disagreement with Audrey's choice to go public domain, and an ideological stance purely for the sake of supporting your choice of license. I completely respect and admire that, if it was your intent, but I wonder sometimes if it gets in the way of folks just doing the polite, reasonable thing, which is to go along

          • So, in closing, regarding your "stand" on your code contributions, you have the benefit of being a well-known personality in the Perl community, so you can pull it off (assuming that was your intent).

            I see. I disagree, but I can see the logic in that.

            ... I wonder sometimes if it gets in the way of folks just doing the polite, reasonable thing, which is to go along with the leader of a distribution in their choice of copyright.

            Conversely, the polite and reasonable thing for the leader of a distrib

            • Conversely, the polite and reasonable thing for the leader of a distribution is to ask contributors if changing the rules after receiving contributions is acceptable. Respect and politeness goes both ways. That's all.

              Yeah. My wording did give an impression that the move was unilateral, and I'm sorry that things escalated as a result -- which is why I think a public apology was called for. Still, I owe you a drink-of-your-choice at YAPC::NA. :-)