@tb Since you've been contributing to axum, would you want to become a "proper" reviewer / maintainer (write access)?
=> More informations about this toot | More toots from jplatte@social.tchncs.de
@jplatte I'm not opposed, but what would be the expectations from such a role? I guess since crates.io is using axum I could probably spend a bit of work time on it every now and then, but I'd need to know what I'm getting myself into :D
=> More informations about this toot | More toots from tb@hachyderm.io
@tb none other than keeping your GitHub account reasonably secure. If you have just a little bit of time to review PRs, at work or not, that already helps.
There's often trivial stuff to do like approving / merging additions to ECOSYSTEM.md, new clippy fixes, doc improvements; also converting Q&A issues to discussions.
If you can dedicate more time (at work), review of larger things would be great too of course, but not a requirement.
=> More informations about this toot | More toots from jplatte@social.tchncs.de
@jplatte @tb For diesel we separated the review process mostly from the merging rights. We encourage users to join the review team, so that there are many potential reviewers. The right to merge is then given to persons that contribute consistently over a certain time. I personally have often another quick look at the changes before merging, especially for new reviewers. Otherwise that works well enough in practice. I think bevy uses a similar model.
=> More informations about this toot | More toots from weiznich@social.weiznich.de
@jplatte sounds good. feel free to add me :)
=> More informations about this toot | More toots from tb@hachyderm.io
@tb invite sent :)
=> More informations about this toot | More toots from jplatte@social.tchncs.de This content has been proxied by September (3851b).Proxy Information
text/gemini