node-bunyan
node-bunyan copied to clipboard
trentm
Is this project still active?
@trentm
Should this project be considered deprecated? It doesn't appear to be actively maintained. No PRs have been merged in nine months. No issues or PRs have been commented on in that time either. There are many PRs (e.g. trivial bug fixes such as this one) that require no thought to merge.
For organizations that rely on this module as part of their critical infrastructure, it would be helpful to know that security vulnerabilities will be patched and bugs will be fixed. Please consider seeking out new maintainers or adding a deprecation notice.
Thank you!
cc @bobzoller @swettk
@trentm Please disclose your roadmap or looking for active maintainers.
Looking at @trentm's profile page he seems to be very much alive – just focused on other projects.
If @trentm needs additional maintainers/co-maintainers, then I'll happily volunteer – we're using bunyan fairly heavily at @Sydsvenskan and I'll happily contribute more than I have done in the past.
@ORESoftware That's not a good comment. That is extremely repugnant of you. His github profile page is still active. His latest commit was just earlier. What the f are you thinking? And saying CNN is not good enough for me to believe it. Cite an actual source that has a link of it. Sorry I'm not one of those guys where you can persuade with fake news.
I think @ORESoftware was being funny. Dying on the Oregon Trail is surely a reference to the computer game from the 1970s. (I played it in the 80s). I don't think @trentm is actually dead. :)
https://en.m.wikipedia.org/wiki/The_Oregon_Trail_(video_game)#Death
On Fri, Apr 27, 2018, 6:10 PM xyz [email protected] wrote:
@ORESoftware https://github.com/ORESoftware That's not a good comment. That is extremely repugnant of you. His github profile page is still active. His latest commit was just earlier. What the f are you thinking?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/trentm/node-bunyan/issues/586#issuecomment-385138594, or mute the thread https://github.com/notifications/unsubscribe-auth/AABB0ljpJzZ8pn2_a70xsur-UH9HoHhAks5ts-uvgaJpZM4TZVbC .
All joke aside, it is concerning if this project is not being maintained.
I came here looking to open a pull-request yesterday, and saw this thread and other signs that this project is not active. ☠️
I have an immediate need, so I've started working on a compatible (same core API, same output format) alternative. This is a slimmed down offering, only supporting Node (server-side) environment and without some bells and whistles, but so far I was able to drop it into a production application that was previously using bunyan, with no issues. See: zebulonj/feller-buncher. If there's interest from the community, I'll prioritize documentation and I'm open to feature requests.
@zebulonj Nice 👍 I myself have been looking at moving to: http://getpino.io/ & https://github.com/pinojs/pino
It's a:
Very low overhead Node.js logger, inspired by Bunyan.
Thanks for introducing me to pino. If @trentm is MIA, I'll switching over.
Any news about this?
node-bunyan is surely a nice project, but the lack of maintenance is fairly noticeable at this point.
Anything we can do to help?
@trentm Please update the README to clarify the state of the project. It presently states:
"master" is currently for coming Bunyan 2.x work. For now, 2.x releases are published to npm with the "beta" tag, meaning that npm install bunyan is still 1.x for now. To install 2.x use npm install bunyan@2 or npm install bunyan@beta.
But as master has received no commits for almost 2 years, it'd seem Bunyan 2 isn't going to happen? That's fine, just let new users that arrive here know that development has halted, and if the project is still actually maintained(bug fixes and the like). If no development or maintenance is to be done, please make it clear that this project is deprecated, and potentially place it in archive status.
1.x branch suggests that is getting no love either.
https://github.com/trentm/node-bunyan/releases/tag/2.0.4 release is out. should this ticket be closed?
Looks like someone reached out privately to @trentm to disclose a vulnerability and they patched the module. While they were here for the first time in years, they fixed CI and a couple other things along the way. I don't know if that suddenly makes this repo maintained. It's up to @trentm to make that verdict.
More meaningful update here: https://github.com/trentm/node-bunyan/issues/335#issuecomment-648583828
That does seem to answer the question pretty meaningfully, yep! Thanks @gurpreetatwal.