Skip to main content

2019-10-16 conda-forge core meeting

Attendees​

Agenda​

Your agenda items​

(Filipe) Should we try GSoC? If so, should we try under the NumFOCUS umbrella? Deadline is Monday, October 28 at 17:00 UTC! Discussion:

  • Ideas?
    • Should be straightforward to get started
    • Should have a meaningful impact
    • Should have a meaningful endpoint
  • Willing to mentor?
  • Start creating/tagging issues GSoC or maybe build a project of issues
  • Need to find students
    • CJ: Put out feelers
    • Can be undergrad or grad
    • Anthony: Tweet out we're looking for people who want to champion GSOC?

(CJ) Python 3.8 progress Discussion:

Subteam updates​

Bot​

  • (CJ) License bot is operational.
    • Upstream to conda skeleton? Show Filipe that part of the code link
    • List of all feedstocks that dont have a license: link
  • (CJ) libnetcdf and zstd migrations are up
  • (CJ) CFEP9 docs went up, seemed to help new users with issuing PRs

ARM​

Docs​

staged-recipes​

website​

CI infrastructure​

Compiler upgrade​

CFEP updates​

How do we start getting traction on these?

cfep-03 Manual upload of builds​

  • Filipe to review, fix any text and merge it in.

cfep-04 X11 and CDT policy​

cfep-05 dev/rc builds​

  • It seems that the conda install label::package syntax gives some odd/unexpected results
  • Maybe we should build a cron job that tests some expected environments?
  • discussion:
    • doesn't
    • automated dev builds: opt-in?
    • enable maintainers to ask for a new PR to be created for a dev release.

cfep-06 Staged-recipes review lifecycle​

cfep-08 Too Big To Fail​

  • Tabled for the time being
  • CJ: Merge this in with the Deferred Status.

cfep-10 Feedstock statuses, unmaintained​

  • How to handle being a collection of packages "which work" and/or an archival store.
  • Epoching of the conda-forge channel
    • Epoching in conda
      • two indexes current_repodata.json and repodata.json
      • Build on this idea for more epochs
    • Shallow graph thing
    • Put time slice repodata.json file on CDN?
    • enable conda install package -date=Jan2019
  • Purpose of conda-forge: Reproducibility vs replicability vs new stuff that just works
    • Ways in which we can help with reproducibility:
      • label all packages with "reproducible" or "all"
      • lock/freeze your environment
      • conda create with locked environment pointing to the "all" channel of conda-forge
      • Best Practices on using conda, conda files, environment.yml, construct.yml, anaconda.org, local channels, etc.

Discussion​

Check in on previous action items​

Copy previous action items from last meeting agenda.

2 meeting​

  • (Eric) Email out to see if we can get more engagement on regular dev meetings.
  • (Sophia) Set up meeting to talk about Condafile stuff.
  • (CJ) write blog post on bot work and compiler migration
  • (Filipe) Ping Bjorn to try and get Debian community more involved with conda-forge
  • (Eric) Scheduling Anaconda <-> conda-forge sync on anaconda.org requirements gathering
  • (Anthony) Reach out to NumFocus to figure out legal ramifications of not including licenses in files.

3 meetings ago​

  • (Filipe) Progress on setting up a self-hosted blog
    • Medium seems to be generally downvoted
    • Host your own blog seems to be generally positive
    • Can we mimic what Dask does for their dev blog? https://github.com/dask/dask-blog
  • (Needs Owner) Searching on our website is a little difficult
  • (Filipe, Anthony) Improve docs on releasing conda-smithy. Currently says "use rever". Would be good to fill out more info there for those of us that are unfamiliar with rever.

3 meetings ago​

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.