-
Notifications
You must be signed in to change notification settings - Fork 312
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
Add maintainers/reviewers? #1075
Comments
@multimeric, thanks for your comments on the issues/PRs. I prefer to have @bluss's input on large design decisions, but for most things, I can merge when @bluss is away. Unfortunately, I'm very busy right now, too. I hope to have more time to work on |
I'm happy that you want to help and that you care about ndarray. It hasn't always been as easy as adding more maintainers, but I'd like to do that too. We need some more people on board. I have time mainly to work on the things I care about, which is not always matching other PRs that come up - that's also why we need other maintainers who can work on the areas they want to focus on. :) |
|
Closing this issue because #1272 is more complete. |
Hi @bluss and @jturner314. I noticed that dev has stalled a little in the past few months. In particular there are a number of useful PRs and issues that haven't been addressed. I know this is mostly because @bluss is busy/away, but ideally the burden of the whole project wouldn't rest on one person to such an extent, especially considering how important this crate is in the Rust scientific ecosystem. I'm wondering if there is the scope to add maintainers or at least people at a lower level of the organisation to optimise the workflow a little.
For example, while I'm not yet at a point where I would want to have merge permissions, I would be happy to triage issues and review PRs as I have done here: #1042 (review) and #1059 (comment). This would reduce the number of things that demand your attention, and you would only need to then review the polished PRs and think about the longer-term goals like the move to
ArrayRef
.The text was updated successfully, but these errors were encountered: