node-portscanner
node-portscanner copied to clipboard
Looking for Maintainer
I don't have the time and drive to maintain this project. It doesn't require a lot of work, but I would appreciate it if someone else could take control. Reply here if you are interested!
I asked @EndangeredMassa to take over as maintainer several months ago for portscanner and he has done an amazing job responding to issues and pull requests. If anyone is relying on portscanner and doesn't mind spending the time to review issues and pull requests and manage releases (there's not many issues or pull requests), the help would be greatly appreciated!
And thanks @EndangeredMassa for your help on portscanner thus far!
I'll take it if you're still interested. I need it to include it in Bluebox-ng or in a new project in which we're starting to work: https://gist.github.com/jesusprubio/8f092af4ca252e252eab
@jesusprubio sounds good to me. @baalexander any objections?
Thanks @jesusprubio for the offer!
My only request is that since portscanner is depended on by a decent number of packages, it remain dependable and breaking changes follow the semver guidelines.
I can take it on, too. I've maintained a lot of projects whose owners are too busy to maintain them.
For example:
- https://github.com/adametry/gulp-eslint/issues/24
- https://github.com/lmtm/gulp-front-matter/pull/5#issuecomment-65747363
- https://github.com/kombucha/gulp-assets/issues/8
Then all yours :). I take the opportunity to invite to our new community/project related with Node and security: https://github.com/assaultjs/assaultjs
I'm not that big of a maintainer, but wouldn't mind to keep an eye on this small project.
I would like to welcome @shinnn as a maintainer for portscanner! Thank you @jesusprubio and @stroncium for the offers to help. And thank you @EndangeredMassa for keeping the project going until now.
@shinnn Do you have a time to maintain this?
@TrySound I was wondering the same thing... seems like everything has been outdated.
I'd be willing to take over maintenance if @shinnn is too busy and none of the other people who volunteered are still interested.
I am much more busy now, but I still can maintain it if needed. However I won't object if @baderbuddy will take on the task.
On Fri, 23 Sep 2016, 23:02 baderbuddy, [email protected] wrote:
I'd be willing to take over maintenance if @shinnn https://github.com/shinnn is too busy and none of the other people who volunteered are still interested.
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/baalexander/node-portscanner/issues/25#issuecomment-249288848, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKwVmSSpQ_kMR9x9EyaTnGFfG0Do0fBks5qtDBagaJpZM4C2FrM .
I'd gladly take it on
PRs are stacking up and master branch is messed up. Please assign a maintainer. I can also maintain and clear up existing backlog, at least for now.
Big shout out to all the previous maintainers for helping with node-portscanner. I have been out of the Node.js community for a few years and I greatly appreciate everyone who has stepped up and offered to step up on keeping packages like portscanner going.
After a brief discussion, I have added @laggingreflex as a maintainer for the repo. @laggingreflex has been active with PRs and issues and I am excited to see this little project get some extra attention. Thank you @laggingreflex!
Released a new minor version 1.1.0 with bugfixes and some new features. Please check it out and let me know. Glad I could help out!
@baalexander @laggingreflex i can maintain, also found bug browser-sync
use
portScanner.findAPortNotInUse(port, max, {
host: "localhost",
timeout: 10000000000
}, cb);
but findAPortWithStatus
function don't accept arguments from object
:disappointed: I can do PR and fix this, just ping me, thank you!
@evilebottnawi Please go ahead with the PR, I will check it out and merge. Could you also link to the browser-sync bug?
@laggingreflex no bug in browsersync issues :disappointed: i find this bug accidentally, but i can link link to lines with issue
@laggingreflex link to problem lines https://github.com/BrowserSync/browser-sync/blob/3aced708d47f032905721d01dd435d809d8feb33/lib/utils.js#L126
Yellow, I would like to volunteer if the port scanner community still needs help :D I'll try to be active on issues and PR's.
Hi @EndangeredMassa, I can contribute to this project as a maintainer. Let's be in touch.