So then why not fork the project? The great thing about open source software in Git is you don't need permission.
As for the npm registry, I don't know how else you'd do that, people have to own their little corner of the namespace. The problem with npm (one of many) is that it uses a single, global, Node.js-specific namespace. That's probably a discussion for the npm mailing list. On Wednesday, November 21, 2012 12:15:51 AM UTC-7, Martin Heidegger wrote: > > I just stumbled over the problem of choosing a zip library to use. Many of > the zip projects are not actively maintained by their owners at github. One > problem I found was that it took too long to answer a maintenance request > and yet another project spammed the npm directory. > https://github.com/wellawaretech/node-zipstream/issues/18 > > Now I was thinking that it might be good to have a "npm-archive" github > organisation that offers people to "hand over" their projects if there is > no maintainer left. This organisation would itself not start any further > development but eventually pass-on projects if new maintainers would be > found. > > What do you think of that? > > yours > Martin Heidegger > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
