-
Notifications
You must be signed in to change notification settings - Fork 427
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
Set up build tools team under the conda governance policy #4698
Comments
Hey all, just an FYI, I've decided to commit to creating this team, so we can take the next steps for build-tools like conda-build. From the list of people above in the issue description, I added a number already and have checked them off because I knew they had shown interest in the past. Anyone else, I haven't spoken to in person yet and would be happy to meet and talk about it. If anyone has mistakenly made it to the list or changed their mind, I apologize and would be happy to fix it, just let me know. |
@ryanskeith @JeanChristopheMorinPerso I don't have your Matrix username to invite you to the public channel there, let me know if you want to join in the first place! |
FWIW joined the Matrix room |
@jakirkham Would you also like to join the build tools team? |
Yes please feel free to add me :) |
Invite sent, please check your emails from GitHub. |
Accepted 🙌 Thanks Jannis! 🙏 |
@danpetry Invited! |
Thanks Jannis, accepted :) |
Can you add me as well please? |
Sorry, I was out on PTO, yes! |
@marcelotrevisani Added to the team and invited to the public Matrix channel. |
Closing this as done 🥳 |
Thanks Jannis! 👏 |
We've followed a similar strategy recently with the constructor project (plus conda-standalone, conda-pack, menuinst). This led to an increase of maintenance velocity, because expert stakeholders outside of the conda maintainer team were enabled to contribute directly to the bootstrapping/installer story of conda.
conda-build is another pillar in the conda ecosystem that would benefit from more expert practitioners to more actively participate in the maintenance. There needs to be a balance struck between required maintenance ("keeping the lights on") and enabling new features ("building new shiny things").
The people I suggest adding to this team:
The text was updated successfully, but these errors were encountered: