## Javascript Team Maintenance

The node ecosystem; team (un)maintained packages; (very) out-dated javascript packages; jquery-goodies.

Lots of stuff that isn’t going very smoothly in this very loose team. Let’s come together to meet and greet and see if we can improve our cooperation. E.g by learning approaches and incentives.

Possible topics:
- how to improve the situation (2017-08-10 16:00)
  - 112 Alioth members
**  https://udd.debian.org/dmd/?email1=pkg-javascript-devel@lists.alioth.debian.org
  - 1076 (+ 2 contrib) packages
  - RC bugs: 34
  - newer upstream release versions 453 packages
  - uscan errors 55 packages

- node packages often have autopkgtests:
  - what does it test?
  - does this test enough
  - is this automated (from upstream)?

- security support, not by security team, but we can still do it

- how to handle updating with large amount of reverse dependencies?
  * My practise, just upload, but I don't like it

- JavaScript ecosystem & micro packages vs Debian packages

- Need a new policy

Teammetrics stats:
  -> http://blends.debian.net/liststats/maintainer_per_package_pkg-javascript.png
       (proving its not really team
  -> Commiters
     http://blends.debian.net/liststats/commitstat_pkg-javascript.png
  -> Writers on the list
     http://blends.debian.net/liststats/authorstat_pkg-javascript-devel.png
  -> Uploaders
     http://blends.debian.net/liststats/uploaders_pkg-javascript.png
  -> Bugs
     http://blends.debian.net/liststats/bugs_pkg-javascript.png

- Sprints?