Skip Menu |

This queue is for tickets about the Log-Any-Adapter CPAN distribution.

Maintainer(s)' notes

DO NOT FILE TICKETS HERE

This distribution has been merged with Log-Any. Instead, file tickets on Github here → Log Any Issues.

Report information
The Basics
Id: 98961
Status: resolved
Priority: 0/
Queue: Log-Any-Adapter

People
Owner: Nobody in particular
Requestors: ether [...] cpan.org
REHSACK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Avoid Guard or make it at least optional
Since https://metacpan.org/release/Guard has no reasonable license nor any terms of use pointing to a reasonable statement of the author regarding the permissions of using his code, it's an unpredictable risk for any consultant/employee to use such a software in any product. Please work out and document where Guard is needed and make it optional (recommended) if it cannot be avoided at all and add documentation how to avoid it.
Subject: Re: [rt.cpan.org #98961] Avoid Guard or make it at least optional
Date: Thu, 18 Sep 2014 08:12:31 -0400
To: bug-Log-Any-Adapter [...] rt.cpan.org
From: David Golden <xdg [...] xdg.me>
I have a branch without it, but I'm stalled getting documentation done to ship it. Feel free to lean on me to finish it up. :-) David On Sep 18, 2014 7:20 AM, "Jens Rehsack via RT" < bug-Log-Any-Adapter@rt.cpan.org> wrote: Show quoted text
> Thu Sep 18 07:20:20 2014: Request 98961 was acted upon. > Transaction: Ticket created by REHSACK > Queue: Log-Any-Adapter > Subject: Avoid Guard or make it at least optional > Broken in: (no value) > Severity: (no value) > Owner: Nobody > Requestors: REHSACK@cpan.org > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=98961 > > > > Since https://metacpan.org/release/Guard has no reasonable license nor > any terms of use pointing to a reasonable statement of the author regarding > the permissions of using his code, it's an unpredictable risk for any > consultant/employee to use such a software in any product. > > Please work out and document where Guard is needed and make it optional > (recommended) if it cannot be avoided at all and add documentation how to > avoid it. >
On Thu Sep 18 08:12:49 2014, xdg@xdg.me wrote: Show quoted text
> I have a branch without it, but I'm stalled getting documentation done > to > ship it. > > Feel free to lean on me to finish it up. :-)
I'll take a look. Before I stuck - in your Github repo list? Jens
Subject: Re: [rt.cpan.org #98961] Avoid Guard or make it at least optional
Date: Thu, 18 Sep 2014 10:14:59 -0400
To: bug-Log-Any-Adapter [...] rt.cpan.org
From: David Golden <dagolden [...] cpan.org>
On Thu, Sep 18, 2014 at 10:02 AM, Jens Rehsack via RT < bug-Log-Any-Adapter@rt.cpan.org> wrote: Show quoted text
> I'll take a look. Before I stuck - in your Github repo list? >
https://github.com/dagolden/Log-Any -- David Golden <dagolden@cpan.org> Twitter/IRC: @xdg
On 2014-09-18 05:12:49, xdg@xdg.me wrote: Show quoted text
> I have a branch without it, but I'm stalled getting documentation done > to > ship it. > > Feel free to lean on me to finish it up. :-)
*gentle nudge* :)
RT-Send-CC: xdg [...] xdg.me
On 2014-09-18 05:12:49, xdg@xdg.me wrote: Show quoted text
> I have a branch without it, but I'm stalled getting documentation done > to > ship it. > > Feel free to lean on me to finish it up. :-)
As requested, here is another lean :)
On 2014-09-18 07:20:20, REHSACK wrote: Show quoted text
> Since https://metacpan.org/release/Guard has no reasonable license nor > any terms of use pointing to a reasonable statement of the author > regarding the permissions of using his code, it's an unpredictable > risk for any consultant/employee to use such a software in any > product.
What about https://metacpan.org/source/MLEHMANN/Guard-1.023/COPYING ?
I commented that against him: It contains a COPYING file which is neither displayed nor evaluated by any CPAN page, nether cpan-api. To avoid making your life more difficult, I better don't explain more background details why this is important from time to time and especially in the root cause of the issue. In fact, the issue is valid (even when you decide to reject it) without the knowledge of the root cause. Please also check * http://www.gnu.org/licenses/gpl-howto.html * http://stackoverflow.com/questions/5678462/should-i-provide-a-licence-txt-or-copying-txt-file-in-my-project for details about the license conditions (Perl5 license means either GNU GPLv2 or Artistic 1.0 - but JSON-XS doesn't follow the rules of FSF regarding the GPL). Maybe there is some gap, I'm not a lawyer, I try to follow recommendations there.
On 2014-12-11 22:31:01, SREZIC wrote: Show quoted text
> On 2014-09-18 07:20:20, REHSACK wrote:
> > Since https://metacpan.org/release/Guard has no reasonable license nor > > any terms of use pointing to a reasonable statement of the author > > regarding the permissions of using his code, it's an unpredictable > > risk for any consultant/employee to use such a software in any > > product.
> > What about > https://metacpan.org/source/MLEHMANN/Guard-1.023/COPYING > ?
Sigh, if the license is Perl_5, why can't he just put that in META.* like a normal vertebrate?
Latest edition -- now part of the Log-Any distribution, does not use Guard.