Bug#857986: [Pkg-javascript-devel] Bug#857986: npm: This pakcage is 3 years old? (consider removal)

[Jonas Smedegaard]

Quoting Pirate Praveen (2017-05-22 16:10:32)
> On തിങ്കള്‍ 22 മെയ് 2017 06:41 വൈകു, Jonas Smedegaard wrote:
>> ...for the _initial_ packaging work.
>> 
>> We are package *maintainers*.
>
> If you have not realized, we are discussing about maintaining an 
> existing package. I think you have also not realized the meaning of 
> team maintained packages. The person who did the initial package need 
> not be the maintainer of the packager for ever. When there is enough 
> interest in the package, it will remain maintained else it gets 
> removed.

Exactly: Packages poorly _maintained_ should be removed.  E.g. npm!

My point in previous post was that focusing only on the workload for 
_initial_ packaging masks the actual real workload, which is being 
discussed here!


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#857986: [Pkg-javascript-devel] Bug#857986: npm: This pakcage is 3 years old? (consider removal)

[Jonathan Wiltshire]

On 2017-05-22 15:19, Jérémy Lal wrote:

2017-05-22 16:10 GMT+02:00 Pirate Praveen :


On തിങ്കള്‍ 22 മെയ് 2017 06:41 വൈകു,
Jonas Smedegaard wrote:

...for the _initial_ packaging work.

We are package *maintainers*.


If you have not realized, we are discussing about maintaining an
existing package. I think you have also not realized the meaning of
team
maintained packages. The person who did the initial package need not
be
the maintainer of the packager for ever. When there is enough
interest
in the package, it will remain maintained else it gets removed.


I did the initial npm packaging. At that moment i was optimistic
upstream wouldn't add or change dependencies too much. I was wrong,
npm is constantly adding/removing modules through the months and
years, requiring a lot of maintainer work to keep up.
I think Jonas was pointing out that updating npm today won't actually
solve any issue regarding npm maintenance. Some company should fund
that work.

Jérémy


Can this discussion please not be on debian-release? Thanks.



--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

 i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits

Bug#857986: [Pkg-javascript-devel] Bug#857986: npm: This pakcage is 3 years old? (consider removal)

[Jérémy Lal]

2017-05-22 16:10 GMT+02:00 Pirate Praveen :

> On തിങ്കള്‍ 22 മെയ് 2017 06:41 വൈകു, Jonas Smedegaard wrote:
> > ...for the _initial_ packaging work.
> >
> > We are package *maintainers*.
>
> If you have not realized, we are discussing about maintaining an
> existing package. I think you have also not realized the meaning of team
> maintained packages. The person who did the initial package need not be
> the maintainer of the packager for ever. When there is enough interest
> in the package, it will remain maintained else it gets removed.
>

I did the initial npm packaging. At that moment i was optimistic upstream
wouldn't add or change dependencies too much. I was wrong, npm is
constantly adding/removing modules through the months and years, requiring
a lot of maintainer work to keep up.
I think Jonas was pointing out that updating npm today won't actually solve
any issue regarding npm maintenance. Some company should fund that work.

Jérémy

Bug#857986: [Pkg-javascript-devel] Bug#857986: npm: This pakcage is 3 years old? (consider removal)

[Pirate Praveen]

On തിങ്കള്‍ 22 മെയ് 2017 06:41 വൈകു, Jonas Smedegaard wrote:
> ...for the _initial_ packaging work.
> 
> We are package *maintainers*.

If you have not realized, we are discussing about maintaining an
existing package. I think you have also not realized the meaning of team
maintained packages. The person who did the initial package need not be
the maintainer of the packager for ever. When there is enough interest
in the package, it will remain maintained else it gets removed.



signature.asc
Description: OpenPGP digital signature

Bug#857986: [Pkg-javascript-devel] Bug#857986: npm: This pakcage is 3 years old? (consider removal)

[Jonas Smedegaard]

Quoting Pirate Praveen (2017-05-22 13:27:35)
> On വെള്ളി 19 മെയ് 2017 03:45 വൈകു, Jérémy Lal wrote:
>> There are complications to distributing npm: it depends on a LOT of 
>> modules, which means it requires a lot of debian-maintainer time to 
>> package, and update.
>
> https://wiki.debian.org/Javascript/Nodejs/Tasks/npm ie, roughly about 
> 78 new modules to package. If one person were to work full time, I 
> think about 10-15 days time.

...for the _initial_ packaging work.

We are package *maintainers*.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#857986: [Pkg-javascript-devel] Bug#857986: npm: This pakcage is 3 years old? (consider removal)

[Pirate Praveen]

On വെള്ളി 19 മെയ് 2017 03:45 വൈകു, Jérémy Lal wrote:
> There are complications to distributing npm: it depends on a LOT of
> modules, which
> means it requires a lot of debian-maintainer time to package, and update.

https://wiki.debian.org/Javascript/Nodejs/Tasks/npm ie, roughly about 78
new modules to package. If one person were to work full time, I think
about 10-15 days time.




signature.asc
Description: OpenPGP digital signature