[Python-modules-team] Bug#709138: Bug report contains non-free content and cannot be processed
Scott Kitterman
debian at kitterman.com
Wed May 22 05:06:59 UTC 2013
On Wednesday, May 22, 2013 12:57:45 AM Daniel Kahn Gillmor wrote:
> On 05/21/2013 10:23 PM, Scott Kitterman wrote:
> > On Tuesday, May 21, 2013 03:30:06 PM Daniel Kahn Gillmor wrote:
> >> For clarity: the original poster of #709138 asked no such thing; the
> >> poster merely asserted a CC BY-NC license in the .sig of their e-mail.
> >
> > No, they said, "My quotes in this email licensed under ..." I read that as
> > anything they typed.
>
> I don't think we're actually in disagreement on these factual matters,
> so i am not sure what your "No," is about.
I guess I misread then. I thought you were saying they only asserted the
license against the .sig.
> > I think this sort of thing is obnoxious and annoying and what I did is
> > point out behavior inconsistent with our values. Marking the report
> > closed does not also require forgetting about the issue raised. Love the
> > bug, not the bug report.
>
> i'm sorry, but i think you are mistaken about the nature of the BTS.
>
> http://www.debian.org/Bugs/Developer#closing clearly says:
>
> Debian bug reports should be closed when the problem is fixed. Problems
> in packages can only be considered fixed once a package that includes
> the bug fix enters the Debian archive.
>
> This criterion was not met. The bug report should not have been closed.
I can agree with this.
> > Yes, but ... I think obnoxiousness in bug reports should not be ignored
> > either.
>
> Sure, and if you had politely pointed the bug reporter to one of the
> many places where reasonable people have taken apart the CC NC clause,
> and explained why it might not be effective at promoting the freedoms we
> all want to see expanded, that would have been a perfectly reasonable
> response.
I don't know how to explain my feelings about this in a way that wouldn't be
escalatory, which I don't think is needed. I agree closing the bug wasn't the
best way to deal with it.
Scott K
More information about the Python-modules-team
mailing list