On തിങ്കള് 12 ഡിസംബര് 2016 08:29 വൈകു, Ian Jackson wrote: > This is quite a checklist. Frankly, in Paul's position, I probably > wouldn't have thought of such a list and if I had I would have > concluded that the problem was too hard, and go and spend my effort > somewhere else. > > What would you prefer from people who don't have the time or ability > to do all of the things you suggest ? Leave packages in "fragile > languages" alone ? Or try to do what they can in the knowledge that > there will occasionally be fallout ? > > If you don't want help from people who are ignorant, busy, or perhaps > sometimes a bit clumsy, then your response is appropriate. > > If you do welcome such help (such as it is), I'm afraid that it will > inevitably sometimes seem a hindrance. You may want to consider how > to be more encouraging, regardless. Updating a library is a difficult task compared to packaging new libraries or applications. I suggest someone new to a language community start with tasks that does not need the level of care a library update requires. Best way would be to join that particular language and send an email showing your interest to contribute. Someone is likely to suggest a task that is suitable for someone new to that language. 1. They can start with fixing bugs of existing packages 2. They can update leaf packages without reverse dependencies 3. They can help with RFPs For javascript/nodejs, there are many new packages we need. Any one interested to help can pick one from the list and start packaging it. 1. Babel https://wiki.debian.org/Javascript/Nodejs/Tasks/babel-cli anything not starting with babel you can take (all babel modules are maintained in a single repo and we plan to create multiple binaries from same repo). Required to build handlebars and move diaspora to main. 2. Ava https://wiki.debian.org/Javascript/Nodejs/Tasks/ava Many node packages use ava as their test framework and packaging it will help maintain node packages well. 3. Webpack https://wiki.debian.org/Javascript/Nodejs/Tasks/webpack many node modules require this to build their browserified versions. 4. Browserify https://wiki.debian.org/Javascript/Nodejs/Tasks/Browserify node-browserify-lite does not have nodejs shims and many node modules need this to browserify.
Attachment:
signature.asc
Description: OpenPGP digital signature