Call for help: more maintainers wanted #574
Comments
|
🙋 |
|
@adamgreig I am relatively new to rust. Bit have been writing C/C++ for a while. I have been using cross and would be interested in contributing |
|
I'm new to Rust but would like to contribute in any way possible. |
|
I'd love to help. |
|
I would like to contribute |
|
I'd love to help as well. We use cross on some of our internal libraries and also made some images for it. |
|
I would love to help :P |
|
i was just looking into this project 7 months ago to create something like goreleaser for rust lang. the project idea is really nice, would love to help if possible. |
|
I would like to contribute as well! |
|
🙋 I've forked the cross and made it support the substrate base project. |
|
So does cross now have a new official maintainer/primary care taker with access to the DockerHub account and the crate on crates.io? |
|
I'll gladly become a maintainer, however, since I only submitted a few issues (and I don't believe have any PRs merged), I'll go through the issue tracker and try to start adding significant contributions before I put my name into serious consideration. I've used cross extensively, and some of the outdated images have started causing issues in recent months, so I'll look to see if I can contribute in significant ways. I use cross to test a fairly popular Rust libraries, including those used as Nom dependencies, so I would love to contribute in any way I can. |
|
Hello all, is there any news on this? We seem to have many people offering to help but no activity yet. Is there any ETA to move on? |
|
@adamgreig friendly ping :) |
|
Hi all, Sorry for the prolonged wait, and a huge thank you to everyone who's volunteered to help, in this thread and privately. Thanks also to @svenstaro for the reminders and prompting me to do something about this. I've set up a cross-rs Matrix channel for coordination and will bring this up in the weekly working group meeting tomorrow (Tues 9th Nov) at 8pm Berlin time in the WG Matrix channel. I think my preferred outcome would be a new GitHub organisation which could entirely manage the crate and access, but an alternative is a new team in the rust-embedded org which also gets access, either way including publish access on crates.io. Unfortunately the current crates.io owner is only the tools team, so we can't immediately change owners, but I've contacted crates.io to try and improve this situation. I can administrate the DockerHub profile (I'm not sure if it can be moved to a new organisation or not, though) but I'm not sure about the Azure Pipelines access; perhaps that would be better ported to GHA. I'm not really sure what the best way to pick from the volunteers is. Possibly start with anyone who's opened a PR or had commits merged and see how it goes from there? If anyone's able to make the meeting tomorrow to help discuss, please feel free to join in, or add comments here beforehand. Fingers crossed we can move forwards with a new release soon! |
|
Just adding this here:
I've been a comaintainer of cross before it was taken over by embedded WG
and I prefer to continue as a co-maintainer.
I would prefer a separate organisation as it makes it easier for access and
other stuff instead of waiting for the embedded WG to process it which
hasn't happened smoothly in the past.
…On Tue, 9 Nov 2021 00:49 Adam Greig, ***@***.***> wrote:
Hi all,
Sorry for the prolonged wait, and a huge thank you to everyone who's
volunteered to help, in this thread and privately. Thanks also to
@svenstaro <https://github.com/svenstaro> for the reminders and prompting
me to do something about this. I've set up a cross-rs Matrix channel for
coordination <https://matrix.to/#/%23cross-rs:matrix.org> and will bring
this up in the weekly working group meeting tomorrow (Tues 9th Nov) at 8pm
Berlin time in the WG Matrix channel
<https://matrix.to/#/%23rust-embedded:matrix.org>.
I think my preferred outcome would be a new GitHub organisation which
could entirely manage the crate and access, but an alternative is a new
team in the rust-embedded org which also gets access, either way including
publish access on crates.io. Unfortunately the current crates.io owner is
only the tools team, so we can't immediately change owners, but I've
contacted crates.io to try and improve this situation. I can administrate
the DockerHub profile (I'm not sure if it can be moved to a new
organisation or not, though) but I'm not sure about the Azure Pipelines
access; perhaps that would be better ported to GHA.
I'm not really sure what the best way to pick from the volunteers is.
Possibly start with anyone who's opened a PR or had commits merged and see
how it goes from there?
If anyone's able to make the meeting tomorrow to help discuss, please feel
free to join in, or add comments here beforehand. Fingers crossed we can
move forwards with a new release soon!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#574 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC6MJNKYOIP66OFZVM4WVS3ULBOXHANCNFSM5A62SZDA>
.
|
|
databend depends The problems I'm interested to fix include: |
590: RFC for moving cross to its own organisation r=adamgreig a=adamgreig [Rendered](https://github.com/rust-embedded/wg/blob/cross-rfc/rfcs/0590-new-cross-org.md). This RFC is for the attention of `@rust-embedded/tools` who currently maintain the `cross` crate. cc cross-rs/cross#574 Co-authored-by: Adam Greig <adam@adamgreig.com>
|
Thanks for moving this to its own GH org! This should ensure smoother sailing in the future. Where are we at in terms of bringing on more maintainers? |
|
I think we still should have more reviewers and maintainers, if you are interested, feel free to join the matrix room as previously mentioned and help review prs! I think we need someone to do some triaging also, so if thats your jam do tell :) |
|
I've been trying to review and help. |
|
I've started adding a few new labels for various architectures, OSes, and runners, to help categorize issues for simpler triaging. I'm currently going through old issues to try to close issues that no longer reproduce, are currently invalid, or have since been fixed. Let me know if the new labels (such as |
Hello,
crossusers and contributors!This project was originally written to help with building Rust projects for embedded targets that were not supported by upstream Rust. Since then, many common embedded targets have become officially supported, so for many embedded users there is no longer any need for
cross. However, due to this history it's still maintained by the rust-embedded working group and the tools team specifically.Today,
crossis still used widely for many different targets and projects, but the rust-embedded working group doesn't have much bandwidth to spend on its maintenance, so many issues and PRs are going unloved. We'd love to have some new maintainers to help ensurecrossgets the attention it deserves, especially from people who are currently finding it useful.Specifically we'd also love to get another release out, which requires investigating and/or fixing broken Windows support and perhaps getting some more open PRs or issues merged. I know a lot of users would love to get a new release as a bunch of important fixes have been merged since the last one.
If you're interested, please comment here, or message me privately on Matrix (
@adamgreig:matrix.org), especially if you've already made some contributions to this repo. If you have any other ideas for ongoing maintenance and development that would be great too!The text was updated successfully, but these errors were encountered: