npm "supergenpass"
denis-sokolov opened this issue · comments
I have taken the supergenpass name on npm, it makes sense that you should own it, especially if you already have supergenpass-lib.
What do we do with it?
Does it make sense to publish the current repository there?
Should it be a Node command line tool that depends on supergenpass-lib?
It can even be a Node command line tool that depends on supergenpass-lib and also exports supergenpass-lib, so that users can transparently use supergenpass in their scripts.
Do you have any thoughts, @chriszarate?
Poooke, @chriszarate. We can't squat on a name in npm and not use it, npm doesn't like that.
Do we have a deadline to put something there before it's deleted? I like the idea of a Node command-line tool that exports SGP.
There's no strict deadline, just a general guideline.
But also I'm willing to spend some time to make this perfect.
If you like that idea, that's great. There's already kkaefer/sgp, that does almost exactly this.
It has some of my pull requests that haven't been merged in.
I could fork it and we can make our official version. Do you agree?
Not much to fork ... most of it will be replaced with a require('supergenpass-lib'). I like the idea, though, so go right ahead (and thanks!).