[Pkg-javascript-devel] Bug#854675: npm2deb: template for ITP should strongly encourage writing a proper package description

On 09-Feb-2017, Praveen Arimbrathodiyil wrote: > Add one more paragraph and sent a pull request upstream. Once > they review and merge, I will upload a new version. On 09-Feb-2017, Praveen Arimbrathodiyil wrote: > Can you try to update control file template too as suggested by > Shanavas? Okay,

[Pkg-javascript-devel] Bug#854675: npm2deb: template for ITP should strongly encourage writing a proper package description

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Praveen Arimbrathodiyil wrote: > https://github.com/LeoIannacone/npm2deb/pull/51 Can you try to update control file template too as suggested by Shanavas? -BEGIN PGP SIGNATURE-

[Pkg-javascript-devel] Bug#854675: npm2deb: template for ITP should strongly encourage writing a proper package description

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: forwarded -1 https://github.com/LeoIannacone/npm2deb/pull/51 Ben Finney wrote: > Attached is my suggested patch for this. Add one more paragraph and sent a pull request upstream. Once they review and merge, I will

[Pkg-javascript-devel] Bug#854675: npm2deb: template for ITP should strongly encourage writing a proper package description

Package: npm2deb Version: 0.2.6-1 Severity: normal Tags: patch The ‘npm2deb’ tool can automatically generate an ITP report. One field that it automatically generates is the package description. This unfortunately makes it very easy to submit *bad* ITP reports, with package descriptions that are