-
Notifications
You must be signed in to change notification settings - Fork 3
Scrapify #25
Comments
@dfcreative That's a good idea actually. I hadn't heard of scrapjs so thanks to bringing it to my attention. I'm going to do that now :) |
@dfcreative One question though, what is intended by the following statement as part of a potential future feature?
I definitely like the idea of what you are doing, but I also know that npm has documentation outlining the proposed approach for claiming a package name (I've released quite a few in instances where appropriate). Apologies for the additional questions, just trying to get a bit more of a picture of the intent behind scrapjs. |
@DamonOehlman well, it happened to me too claiming an npm name not once, and should say that is a pain - waiting a month. Usually the name is required within following couple of days most. Unfortunately npm "free market" has no policies regarding quality of packages and owner contacts, so that practically anonymous users may squat really good names, without readme or anything and not get in contact, and other real devs are forced to wait or look up for different name, sometimes that blocks workflow and harms community, as happened with audio-play. That is why I ask not to transfer stuff over download threshold (>300) and transfer full rights to scrapjs to let us make sure we respond to requests less than a month. By TTL I meant regular practice of getting rid of doubtful modules. It is optional, but I would suggest, eg. if a package hasn't been claimed for 2 years we just dispose everything related with it and delete it permanently, kind of garbage collector. As for interleave, I was searching a free name for deinterleave module, that is why I reached you out. If you feel like keeping it - please do. Or if you want to take part in scrapjs - feel free to join :) |
Hi @nathanoehlman @DamonOehlman!
Since the project is abandoned and there are not so many downloads, I suggest transferring it to scrapjs, if you feel comfortable with that.
Cheers
The text was updated successfully, but these errors were encountered: