-
Notifications
You must be signed in to change notification settings - Fork 423
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
Mentor conda maintainers by packaging practitioners #4707
Comments
@kenodegard @beeankha I think you mentioned that you're interested to dive into conda-build a little, do you mind being assigned to this to make sure we're following up on it? |
@kenodegard I'm thinking if the conversations between @mbargull and @kenodegard could be the start of this ticket? Who else would be great at mentoring conda maintainers? |
@kenodegard @beeankha Do you feel like you're making progress on this? |
@jezdez Yes, I feel like progress is being made on this; we've been meeting regularly with @ryanskeith and will most likely be expanding the learning sessions to more stakeholders soon (we wanted to keep things small at first so the meetings wouldn't be overwhelming). Below are some PRs that got filed during our learning sessions, just to give you an idea of the things we're already doing to get into conda-build's internals and try to improve/clean things up: |
Do you want to keep us up-to-date here or should we close this? |
I think there's enough momentum re: conda-build learning to be able to close this issue! |
I agree. We are making slow and steady progress. |
Sounds great, thank you! |
In working to upskill the current maintainers of conda-build with real-world usage of conda-build, we should start building bridges between the various stakeholders and report back here on progress.
The text was updated successfully, but these errors were encountered: