2019-09-04 conda-forge core meeting

---

Attendees

List the attendees for the meeting

• Filipe
• Eric
• Sophia C.
• Dougal
• Lori
• Anthony
• Marius

Agenda

Pre-arranged stuff to talk about.
Email core team on Monday of the week of the dev meeting to ask for things to talk about.

• NumFOCUS summit. Can send 2 people with their funding. Can apply for 1 numfocus award.

  • What's the numfocus award? "Outstanding new contributor award". Every project gives out an award to their best new member / contributor. That is up to the project to determine. This is a "welcome, hey, you're doing a great job" sort of thing. Last year we gave it to CJ.
    • Anthony will own the nominations and voting.
  • Two people to send with funding:
    https://www.eventbrite.com/e/2019-numfocus-summit-tickets-68012012761
    • Filipe
    • Sophia C.
  • Time: November 1st-3rd. (Fri-Sun). Pydata: Nov 4th-6th (M-W)

• conda-forge talk at pydata nyc? Marius will check and see if there's interest from the organizing committe.
  - conda-forge tutorial at pydata nyc?

• Discussed how to set up a blog. Options are probably Medium / host your own on the conda-forge website.

  • Medium seems to be generally downvoted
  • Host your own blog seems to be generally positive
  • Issues raised: Searching on our website is a little difficult.

• New conda-smithy release? haven't cut one in months. Anthony will cut a new release of conda-smithy.

  • Do we have docs on releasing conda-smithy? There are some instructions in the readme. Anthony and Filipe will sync later on getting this done (and maybe the docs updated)

• (Filipe) ESIP funds. Gave good feedback on packages. They weren't really sure what it was that we did behind the scenes.

• (Filipe) Pangeo meeting last week. Folks are generally happy with conda-forge. They're struggling with channels, strict, and are generally not interested in engaging us with issues.

  • How can we get users to engage us and open issues?
    • Something to think about: If you know nothing about conda-forge, the website does not necessarily give you clear instructions on how to understand where your issue might be.
    • Would be good to improve the entry points for folks
    • https://github.com/conda-forge/conda-forge.github.io/issues/852

Subteam updates

Bot

ARM

Docs

staged-recipes

CI infrastructure

Your agenda items

Discussion

Notes from todays dev meeting

Check in on previous action items

Numbers in parentheses indicate how many meetings these action items have been carried over. If they make it to 3 (4?) then our default is to get rid of them as action items and open up an issue on the conda-forge.github.io issue tracker.

Last meeting

• Filipe: contact Chris Roth about interesting in helping in create a blog
  Done. No opinion on platform and no experience with blogging.
• John K: Create, or link, google doc with survey questions
• Marius: Begin migration from AppVeyor, see topic for breakout items
  • TODO: Make this an issue and outline the things that are going to happen.
    This can serve as a centralized info spot for the community.
  • Get list of packages to KEEP on Appveyor
  • Change the default fo Azure.
• Anthony and Filipe: conda smithy release for linux-armv7l
• Anthony + Sophia: Statuspage RSS
• Anthony: Who is going to champion the CZI funding initiative? May be useful to turn this into a github issue
  • 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) https://chanzuckerberg.com/rfa/essential-open-source-software-for-science/. Mid-December 2019. Mid-June 2020
  • (Filipe) Was at pangeo and met some of the CZI folks.
    If we joined with bioconda it would make our application stronger.
  • Thread on gitter https://gitter.im/bioconda/core-x-conda-forge

2 meetings ago

• 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.
  All done.
• 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: Open issue on conda-forge.github.io noting work done on the kubernetes cluster. Did some kubernetes work at scipy.
• Marius: reach out to internal IT to clean up some Zoom hiccups. Still in progress 2019-09-04
• Marius: intel compiler architecture repo update.
  • Will set up linux hosts.
  • 2019-09-04. Talked with Azure DevOps to get them to help with image building. There's someone here in NYC that Marius has met with to give better support to extend existing build containers. Then we can add the intel compiler into it as opposed to building it ourselves.
  • Eric: Move this to a conda-forge.github.io issue.
• 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.
  • 2019-09-04. Anthony: More or less resolved. Waiting on someone to approve (beckermr). Then will go through another round of review with numfocus
• Eric: Set up meeting to talk through the conda-forge feature set requirements for the new Anaconda.org
• 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 anaconda.org

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.

[ ] List resultant action items here