Is the project maintained?

[Veetaha]

@sebasmagri might I ask you whether you are still interested in maintaining this crate and if you'd like to pass the maintenance to anyone else?

[Veetaha]

cc @KodrAus

[sebasmagri]

For a long time @KodrAus has been the main maintainer of the project. So actually I'd be fine passing the maintenance/ownership of the project to him or someone he agrees on.

[jplatte]

This crate is pretty popular, I am surprised it is hardly maintained :/

@KodrAus is this on your todo list?

[KodrAus]

It is on my todo list (along with bitflagsand uuid). Unfortunately it’s been a really big year and it hasn’t managed to find its way to the top yet. I’d be up for creating a env_logger_rs org on GitHub and moving the project into it so it’s easy to add contributors and people with publish rights.

If I create the org would you be happy to migrate @sebasmagri?

[KodrAus]

In the meantime I'll do a pass through all the open PRs 👀

[sebasmagri]

Yes absolutely @KodrAus! 100% up to make it easier to onboard new collaborators.

[mainrs]

If you guys need help on PRs and issue management, I can help out :) I do already do this for a lot of Rust projects (the biggest one being spotifyd).

[KodrAus]

@sebasmagri @sirwindfield I've created an env-logger-rs repository and invited you both to it 🙂 I've opened #163 to track our progress migrating the repository into that org

[mainrs]

Awesome! Thank you!

[KodrAus]

@sebasmagri I think you’re the only one who’s got permission to move the repository 🙂

[kornelski]

The last release has been almost a year ago. It'd be nice to release latest changes.

[mainrs]

We don't have publishing rights, they haven't been granted to us. @kornelski

[kornelski]

:(

@alexcrichton @sfackler and @huonw also have crates-io ownership. Maybe they can help?

[mainrs]

If they wouldn't mind. We wanted to have the whole publisher team have access to publishing, so they'd have to run this command:

cargo owner --add github:env-logger-rs:publishers

[sebasmagri]

I tried last time and crates.io gave me some error. Will try again.

Edit:

It's still giving me some issues:

error: failed to invite owners to crate env_logger: api errors (status 200 OK): could not find the github team env-logger-rs/publishers

@sirwindfield I just checked the team and it seems to be fine. Any ideas here?

[mainrs]

No clue. But I can figure it out. You could add me for now. That way I can see what is wrong there and try to add the team myself. @sebasmagri

[kornelski]

I think github has privacy controls around team's existence and membership. You may need to log in to crates-io again and grant it access to the env-logger-rs org, so that it can scan its teams.

[mainrs]

@kornelski Ah! Did re-log and granted crates.io access to @env-logger-rs. At least crates.io is listed under authorized apps now :)

[sebasmagri]

That apparently did it! Thanks @kornelski

[Veetaha]

I'd just recommend adding publishing to CI like this

This makes the process of publishing more automated (you just push a new git tag), and more transparent (the publisher won't inject malicious code before publishing the crate).

[jplatte]

The maintenance issues have been addressed. I'm personally not sure what to think of the CI publishing suggestion, but in any case that seems like it should be a separate issue.

[jplatte]

This project has once again run out of (active) maintainers, it seems. I'm no longer using env_logger so while I'm definitely still very active in the Rust community overall, it's hard to justify spending time on this.

[Veetaha]

@jplatte are you using tracing now? I think log gets pushed back more and more by tracing, thus that's understandable

[jplatte]

Yes, I've been exclusively using tracing(-subscriber) instead of log / env_logger for quite a while now.

[epage]

@jplatte One option: the CLI-WG helps "keep the lights on" for important CLI-related crates. I think this one counts if you are up for adding us as maintainers.

[jplatte]

@epage that's great, I've added you as an org owner. Please do kick me out of the org once you have confirmed that everything works and add other people, or just move the repo to another org like rust-lang-nursery if that makes sense to you. The list of people who can publish this crate on crates.io is very long and it probably makes sense to cut it down a bit to those who are actually somewhat likely to be involved with the project in the future.

[jplatte]

Not sure why epage didn't do it yet, but I'm now removing myself from the org after having released v0.9.2. I think this can be closed again.