Bug#839570: Browserified javascript and DFSG 2 (reopening)

[Pirate Praveen <praveen@debian.org>]

On 2016, ഒക്‌ടോബർ 4 4:16:48 AM IST, Philip Hands <phil@hands.com> wrote:
>I think you need to try a little harder than that -- it is still
>unclear
>to me what you are even attempting to ask for.  Unless that changes I
>would think that the right response to this is to simply close the bug.

First, the issue is already discussed and understood in an earlier bug (referenced it in my first message). When that bug was closed, TC members suggested any member could reopen the bug if a formal vote was desired.

Second, this issue is already demoralising, and responses like this are not helpful. Isn't it reasonable to expect someone commenting on a bug to read the comments posted already?

>
>As a bare minimum, try specifying what outcome you are hoping for, with
>respect to which package.
>

libjs-handlebars, libjs-fuzzaldrin-plus and other browserified javascript should be allowed in main (the browserified javascript can be modified by anyone who understand javascript without difficulty and can satisfy dfsg requirement for source). This would result in diaspora, gitlab, pagure, prometheus (and likely other afftected packages) to be shipped in main instead of contrib.

But it would be better to ship the source code used by upstream (consider it as severity important and not serious), so we should try to package grunt for stretch+1 and browserify during build.