2018-03-20 conda-forge meeting¶
Attendence: Eric, CJ, John, Michael, Jonathan, Filipe
Policy for pulling/moving packages to broken
Okay with current setup but when package is part of the stack should be more careful.
Use conda verify to catch some of the issue that cause us to pull packages.
pip 9.0.2 https://github.com/pypa/pip/issues/5081 and https://gitter.im/conda-forge/conda-forge.github.io?at=5ab12c6b6f8b4b99464b3c37
Should new version of packages with API incompatible changes should we hold off upgrades for the benefit of the ecosystem?
Many linux distributions avoid this by having a testing vs stable
Document policy, open issue to track long term plan Eric/Jonathan/John
stable repository of packages or latest versions that might be broken?
Related (old) proposal: +Staged Releases
Is conda forge a place where we make a good-faith effort to have interoperable packages or a place where we allow developers to release their code without as much concern for how well those packages interoperate? (This feels like a CFEP)
Policy for orphan packages (packages with no maintainer)
archive the repository (this blocks pull requests)
what do we do with the packages ?
They are unmaintained and are not getting security updates.
Have the core team maintain the package indefinitely
Have a group of foster maintainers who can help.
Have the bot look for recipes that have no maintainers, add an issue to that repo that says “this package is unmaintained and will be archived in 90 days. post here if you want to be a maintainer or submit a PR that adds you as a maintainer blah blah blah”
All the bob-feedstocks are archived and the bob-packages were moved to “broken” label.
Creation of staged-recipes subteams for different languages
PR template that enumerates who to ping for each team
Add to the docs on conda-forge.orgT
Make the subteams [Done]
Make issue for people to tell us which subteams they want to be on [Done]
We’ll try zoom for the next meeting:
Zoom can handle more people than Hangouts
Zoom needs native client, does include linux (linux: https://support.zoom.us/hc/en-us/articles/204206269-Linux-Installation)
Try Zoom next week, see which is better
join the “ericdill” meeting
Go over +AnacondaCon agenda
Win32 poll results: https://docs.google.com/forms/d/1DbPWfHw1AhYWNsfsYzEo1AxZzKOpxoc-b7zaqY_AMls/edit?usp=sharing 91 responses, 5 are using Win32, only 1 is using Win32 exclusively.
Collaboration (or at least communication) with the pypi/warehouse devs
How do we want the bot to handle non-release releases (alpha/beta/dev/pre/etc.) https://github.com/regro/cf-scripts/issues/86 and https://github.com/conda-forge/conda-forge-enhancement-proposals/pull/3 and https://github.com/conda-forge/matplotlib-feedstock/pull/24#issuecomment-221496870
John suggested (on gitter) that we reach out to intel and NVIDIA to get copies of their toolchains and development libraries.
Adding people to cf/staged-recipes
Marius van Niekerk offered to help review on staged-recipes
Optionally building wheels for some packages. ( https://github.com/conda-forge/conda-smithy/issues/608 )
flit install as build step?