Skip to main content

2019-08-07 conda-forge core meeting

HackMD link


List the attendees for the meeting

  • Jonathan Helmus
  • Filipe Fernandes
  • Kai Tietz
  • Lori Burns
  • Sophia Castellarin
  • Marius van Niekerk
  • Michael Sarahan
  • Anthony Scopatz
  • John Blischak
  • Sophia Parafina


Please add new items to the meeting Agenda

ESIP update (Filipe)

  • Thread in gitter from Filipe about the ESIP funding. Annie Burgess (the coordinator of the lab incubator grant) has the following to say:

I've been pretty pleased with how the CondaForge project has gone on a couple of fronts.

I think the model of using the funding for sprints, with direct or in-kind contribution from other orgs (e.g. Anaconda) is a good model for how to get some concerted development done on some of these foundational software projects.

Also, seems they've been able to get quite a bit done at the sprints themselves.

In terms of the utility of what they've done, that is really for the community/users to decide. It would be good to seek users out to see how the added functionality is helping them accomplish their work AND to scope what next development efforts could be next, with ESIP or other funding agencies.

Start a blog

  • Thread in gitter about starting a blog that is a follow-on from the ESIP update

We have to work on the second part there. Most of the results from the latest improvements in conda-forge are "invisible" to an average user. They will get newer packages faster thanks to the migration infrastructure we have and the packages will be more stable. But most users won't even notice that. TL;DR we need to start blogging.

  • Bit of a discussion around Medium, but that doesn't easily let others contribute. Someone needs to manage the Medium account.
  • Using github to host the blog was proposed and had +1's from Marcel, Bjorn and John
  • Cross-posting blogs to the Anaconda blog is also on the table. Had a +1 from John on that. Any objections?
  • TODO: Find someone to champion running the blog and someone to do the infrastructure work to set up the blog. That can be the same person but doesn't have to be


  • Chris Roth might be interested, he has been interested in docs in the past. (Filipe will contact) Technology to use:

  • Markdown?

  • Jupyter Notebooks?

  • Let champion have final say in technology to use.

  • Need reviewers once content is created

User survey (John K)

Also in gitter, from John (plus some light editing to clarify):

How do we feel about doing a user survey? As in, a short list of questions about what people are using Conda-forge for and what things they would like to improve. Just thinking how we can address the request in the last (ESIP) paragraph (above). This should give us some tangible community-oriented goals that we can move towards over the next year (and data to back that it up in case someone asks why we spent time on some task)

  • Link to google document that John mentioned that he would be creating
  • Questions:
    • How would you feel about collecting telemetry information?
    • How do you use conda-forge
    • What architectures, platforms, etc do you use?
    • What packages are missing in conda-forge
    • What's needed here?
    • How do we conduct a user survey?
    • Who is interested in helping:
      • Conduct the user survey?
      • Collate the results?
      • Analyze the data?
      • Produce the resultant report?

Migrate away from Appveyor (Marius / Isuru)

Discussion in gitter between Marius and Isuru. Anything else needed to discuss?

  • Everything that doesn't use CMake or msbuild is a candidate to migrate off of Appveyor
  • Could use Azure API to get the builds that are successful

Using build status is not ideal since Azure logs are only available for a limited time. Can use cfgraph to determine if cmake is used. Push with "skip appveyor" to all effected feedstocks or create migrator, former seems better.

AppVeyor usage:

  • have 4 job plan
  • ~4 feedstocks added per day


  • Get list of packages to KEEP on Appveyor
  • Change the default fo Azure.

CZI (Scopatz)

Have conda-forge apply to CZI for funding. Grants up to 250k Focus on Open Source infastructure What would the topic of the grant be? Funding would not be directly under conda-forge but under another organization. NumFocus could sub-contract these funds. Could team up with bioconda (core team) Mid-December 2019 Mid-June 2020

Subteam updates



  • Need a new conda-smithy release for ARMV7



CI infrastructure

Your agenda items

Please add a level three markdown heading (###) with whatever you wish to discuss.


Record the meetings and upload them to youtube?


Notes from todays core meeting

QT recipe almost ready, needed some fixes for clang. RSS feed is available for conda-forge repository. Would be helpful to provide docs on how this should be interpreted.

Check in on previous action items

  • Filipe: Research software for audio listen only access for other members of the community that want to attend but aren't part of core.
    • I e-mailed them, no answer yet. We have a better chance asking directly during one of the meetings.
  • Filipe to open issue about fixing docs -- there were some issues that came up at the sprints. Two were fixed at SciPy. One is pending: make the use of strict clear in our docs.
  • Mike S.: pypy Next steps: Say yes / no to the spec, point out potential pitfalls, give it back to (Matti?) and say here's the work that needs to be done.
  • Marius to reach out to Wolf about robot operating systems making it to conda-forge
    • He's just done this on his own :D
  • Marius: Open issue on noting work done on the kubernetes cluster
  • Marius: reach out to internal IT to clean up some Zoom hiccups.
  • Marius: intel compiler architecture repo update.
    • Will set up linux hosts
  • Matt: source-extractor update. Follow-up with Anthony and NumFocus around the renaming issue. Update: Anthony has submitted the potential CoC violation, we are waiting to hear back. Feedback from participants at Python in Astronomy 2019 was that it is time for the name to change to source-extractor.
  • Eric: Set up meeting to talk through the conda-forge feature set requirements for the new
  • Eric: Confirm with core team that no one wants access, as long as the conda-forge feature set is included in the design of the replacement for

New Action items

Copy new action items to next meetings agenda so we can check in. Make sure each action item is assigned to someone or it will likely not get done.

  • Filipe: contact Chris Roth about interesting in helping in create a blog
  • John K: Create, or link, google doc with survey questions
  • Marius: Begin migration from AppVeyor, see topic for breakout items
  • Jonathan: conda smithy release for linux-armv7l
  • Anthony + SoPhia: Statuspage RSS