Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this project still active? #586

Open
serhalp opened this issue Apr 18, 2018 · 20 comments
Open

Is this project still active? #586

serhalp opened this issue Apr 18, 2018 · 20 comments

Comments

@serhalp
Copy link

serhalp commented Apr 18, 2018

@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

@leolorenzoluis
Copy link

@trentm Please disclose your roadmap or looking for active maintainers.

@ORESoftware
Copy link

Trent has died on the Oregon trail bless his heart

@leolorenzoluis
Copy link

@ORESoftware Source?

@ORESoftware
Copy link

CNN

@voxpelli
Copy link

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.

@leolorenzoluis
Copy link

leolorenzoluis commented Apr 28, 2018

@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.

@bobzoller
Copy link

bobzoller commented Apr 28, 2018 via email

@iketiunn
Copy link

Don't think this repo is active now, PR hasn't been reviewed for a while.

@ORESoftware
Copy link

Trent died on the Oregon Trail and is still dead

@jerroydmoore
Copy link

All joke aside, it is concerning if this project is not being maintained.

@zebulonj
Copy link

zebulonj commented Feb 6, 2019

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.

@voxpelli
Copy link

voxpelli commented Feb 6, 2019

@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.

@jerroydmoore
Copy link

Thanks for introducing me to pino. If @trentm is MIA, I'll switching over.

@halfzebra
Copy link

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?

@ORESoftware
Copy link

@polarathene
Copy link

@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.

@vordimous
Copy link

https://github.com/trentm/node-bunyan/releases/tag/2.0.4 release is out. should this ticket be closed?

@serhalp
Copy link
Author

serhalp commented Jul 20, 2020

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.

@gurpreetatwal
Copy link

More meaningful update here: #335 (comment)

@serhalp
Copy link
Author

serhalp commented Jul 20, 2020

That does seem to answer the question pretty meaningfully, yep! Thanks @gurpreetatwal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests