Call for maintainers

[rosston]

This project is fairly popular (40,000-50,000 downloads per week on npm), but it doesn't really have an active maintainer at the moment. I was (more or less) keeping up with issues and pull requests for a while, but my ability/interest in contributing has been low for the past year or so.

If anyone is interested in maintaining this project, please speak up! Responsibilities would basically be triaging/responding to/closing issues and handling incoming PRs. From a skills standpoint, you would benefit from some knowledge of JavaScript (don't think you have to be an expert!), patience in handling issues and PRs, and an understanding of the balancing act between new features and stability.

The project is not in a dire situation at the moment. It generally works as advertised, although there might be some clunkiness around the current winston@3 support (see #189 and #190). The biggest debt on the project is the number of unhandled issues and PRs open, which doesn't actively hurt the currently-deployed code. But the project could use some love, which I'm not able to give it.

[bithavoc]

@rosston we may get more attention if we add this to the Readme.me I think

[rosston]

Currently working to add a link to here from the README.

[crellison]

I'm interested in helping maintain this package. What is your process for making decisions on that front?

[bithavoc]

@crellison I don't think we have a process for making decisions, that's one thing we should start working on. However, one requirement I think it's important is being using this package.

Are you using the package?

[crellison]

@bithavoc Sorry for the delayed response. I am using the package, though currently on a closed-source project. I can put together something you can look at if you want to validate that I know what I'm doing.

[bithavoc]

sorry I was off for a few days. If you're using express-winston that's the only thing that matters. I'm gonna make you contributor so you can start addressing pull requests and issues in the repo.

[bithavoc]

We need more maintainers.

[rosston]

@crellison (and any other possible maintainers that crop up) I should've noted this in the first place, but I'm happy to help by providing backup, a second eye, or any background around express-winston. I'm not able to put a ton of time towards this module, but I can absolutely provide support to other maintainers. I worked on a lot of the structure of the test suite, so especially feel free to reach out with any questions about confusing things there.

[crellison]

That all sounds good. What's the process for publishing to NPM? I'm looking to close #190, but want to make sure the changes get published so we can close some of the winston 3.x compatibility issues

[bithavoc]

@crellison I can assist publishing to NPM, it takes me less than a minute to do so.

[rosston]

Y'all are welcome to decide differently, but I've tried to keep the changelog updated (manually) when releasing to npm in the past.

[bithavoc]

@rosston is right, we need to keep it updated

[crellison]

@bithavoc I forgot to mention that the Changelog has been updated. Feel free to release 3.0.1 when you can!

[bithavoc]

@crellison [email protected] 🚀

[nagapavan]

I am interested in contributing. I am using the package for work.

[bithavoc]

@nagapavan good, you can start by going through the pull requests and vetting them to see what we should be merging or closing. you can summon @crellison if something needs more reviewing.

[jlomas-stripe]

:lurkyturkey: 👋 I haven't contributed in a really long time, and I don't think I'm going to be able to any time soon either unfortunately, but this recent event is something to keep in mind as you work on finding someone else to own this.

❤️

[bithavoc]

@jlomas-stripe Thanks for the reminder, yes I saw that one in HN. Unlike event-stream I still retain NPM publishing rights and check what we publish.

[DManavi]

I'm somehow new on github.

I'm really intrested in this project and find it so cool.

I'm available to be an active maintainer on this project.

Here is a my framework (as an example).

https://github.com/ItemsJS

[dhruvdutt]

Can help contribute and being an active maintainer. ✋

[lonix1]

Needs to be a link from the main winston readme, to this package.

A section called "ecosystem" or something like that. I'm sure many people don't even know about this lib. If there were more users, maybe there'd be more interest in maintenance.

[jblevins1991]

I would like to help maintain this package. I like it a lot. I am using it for an open-source project currently and will probably make it something I use in all express-based projects. I can be on weekends and some weekdays.

[yinzara]

I made a pretty large pull request #222 . Is anyone still maintaining this library? Did anyone take over?

[bithavoc]

@yinzara Unfortunately we still don't have active maintainers for the library, the most active maintainer right now is @golopot and me, but as soon as a I saw that the PR had a breaking change then I deferred for review when I had some more free time(like today Saturday, a weekend).

After your PR gets merged, and if you volunteer, we can definitely promote you. Sounds good?

I'm still reviewing all the PR's and Releasing the versions to NPM for now.

[yinzara]

I mean, what's another library to maintain? :-) Why not!?

[bithavoc]

@yinzara releasing two new versions right now, sorry it took me so long, I had a busy weekend.

[yinzara]

I think I'm still technically a contributor as I can't close any issues. Would love to get rid of all the old stuff that isn't valid anymore.

[jblevins1991]

What do I need to do to become a contributor? Anything special? Or can I just start looking through PRs?

[bithavoc]

@jblevins1991 basically just look through PR and watch the repo for new issues and PRs, yes.

[rfm-bot]

🚧 Is this repo looking for support?
Hello, we created this issue becuase the user @sospedra told us you are calling for maintainers.
✅ If you're looking for collaborators no action is required.
👮🏻‍♂️ If this repo is well-supported please put a comment here sospedra/rfm#58 and we'll close it immediately.
Sorry for any inconvinience. We understand this message can feel spammy but we really think is good to double-check first with the current owners :)

[BeauBouchard]

@bithavoc I have been using this repo for a while. I had some free time and wanted to update a few things since i saw this #192 call for maintainers i would like to offer to do some repo maintenance.

If you don't mind I am going to create a few issues and solve a few existing.
Please let me know if you would like to setup any time to talk or have an review / references.

[DhanushNehru]

@bithavoc I am active user of this repo. I wanted to contribute to this repo by solving few issues especially this one #240

Do let me know if I can contribute.

[BeauBouchard]

@bithavoc nudging you a little bit again this year :D I am still available to make contributions, also an active user of this repo and would love to tidy it up a bit.

[breck7]

Is this project still maintained? If not, is there a fork or alternative that people recommend?