Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Agenda for 2016-04-15 #89

Closed
pelson opened this issue Apr 13, 2016 · 29 comments
Closed

Agenda for 2016-04-15 #89

pelson opened this issue Apr 13, 2016 · 29 comments

Comments

@pelson
Copy link
Member

pelson commented Apr 13, 2016 •
edited
Loading

Please add comments for agenda items.

Minutes to follow in this description.

Uncertain if the invite link works: https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MDhiNGpydHF1ZTFiNTI2ODFjMjYxZ2Q1bjhfMjAxNjA0MTVUMTQwMDAwWiBwZWxzb24ucHViQG0&tmsrc=pelson.pub%40gmail.com

Hangout link: https://hangouts.google.com/call/7fxvcgjutfg4po6c4jpwyitwi4e
Time: 1400-1500 UTC/GMT

We will happily help with any pertinent packaging problems that people have in these meetings, but the primary focus must be geared towards the underlying infrastructure being directed appropriately for conda-forge package maintainers.

Agenda summary:

  • Welcome
  • How do we manage agendas and minutes?
  • conda-forge: where are we
  • Next meeting?
  • PyPI metadata redundancy
  • Python3 vs Python==3
  • External developers to github.com/continuum repos
  • Centos5 vs Centos6
  • Features and where they sit with feedstocks
  • Complex licenses (e.g. MKL)
  • Packaging python itself
  • conda-forge docs
  • VC features
  • yum requirements
  • Low level packaging
  • NetCDF
@pelson
Copy link
Member Author

pelson commented Apr 13, 2016

First item: How should we manage our agenda and minutes

@pelson
Copy link
Member Author

pelson commented Apr 13, 2016

Second item: Where are we with conda-forge (N users, packages etc.)? Where are our bottlenecks? What are the perceived issues that we should address before attempting even more exposure?

@pelson
Copy link
Member Author

pelson commented Apr 13, 2016

Item: Based on feedback from http://doodle.com/poll/5wuiges2s5u3u6uk, when should we have our next meeting?

@pelson pelson mentioned this issue Apr 13, 2016
Merged
@jakirkham
Copy link
Member

Could we pick a regular occurring time that we stick with for a little while? Having it floating from week to week is a bit challenging for me. I understand we are getting more feedback from others, which requires some adjustment potentially, but it would nice to have something we can plan around.

@takluyver
Copy link

Item: I don't want conda-forge to duplicate a lot of PyPI metadata, and I certainly don't want it to duplicate metadata and then get out of date because people forget to update it. How can we make this more automatic? I suggested that for typical pure-Python packages, we could have a list of package names and a bot that checks for new versions on PyPI and converts wheels to conda packages. Discussion on conda-forge/staged-recipes#323.

Item: A python3 package - ways to use Python 3 applications with python=2 environments (conda-forge/staged-recipes#339)

@jakirkham
Copy link
Member

Item: Opening up of some Continuum controlled repos? Heroku buildpack? Base build image?

Status Update: CentOS 5 (or glibc version constraint older than CentOS 6) usage survey.

Item: Feature support in conda-forge. Primarily BLAS support (ignoring MKL for now). How do we write recipes that support multiple BLASes? Do we need multiple feedstocks (for each package e.g. numpy_openblas and numpy_atlas) here, changes to conda-smithy, etc.? What granularity of BLAS selection do we want?

Item: Looking into dependencies with more complex licensing. For example, CUDA (not too bad), cuDNN, MKL, etc.

@jjhelmus jjhelmus mentioned this issue Apr 14, 2016
Closed
@jjhelmus
Copy link
Contributor

Item: Packaging software already in the default channel, #22. Specifically Python, conda and related packages which would allow for the creation of a custom conda-forge distribution using only conda-forge packages, #90.

@jakirkham
Copy link
Member

Is there somewhere we could open source our last meeting agenda? I'd like to put it in a repo somewhere at least so people can see it before our next meeting. @pelson @ocefpaf, thoughts on this?

@jakirkham
Copy link
Member

Item: Hosting docs somewhere? Related issue ( #91 ).

@jakirkham
Copy link
Member

jakirkham commented Apr 14, 2016 •
edited
Loading

Item: VC package (Python free). See this proposed recipe ( conda-forge/staged-recipes#363 ) or maybe this ( conda-forge/staged-recipes#365 ).

@jakirkham jakirkham mentioned this issue Apr 14, 2016
Merged
3 tasks
@jakirkham
Copy link
Member

Item: Discuss yum requirements. See this issue ( #82 ). This PR ( conda-forge/conda-smithy#134 ) and discussion within. Also, this PR ( conda-forge/staged-recipes#346 ), this PR ( conda-forge/conda-smithy#135 ), and this example application PR ( conda-forge/pyopengl-feedstock#3 ).

@jakirkham
Copy link
Member

Does anyone want to raise any other tabled issues from last time, @pelson @ocefpaf @msarahan?

@jakirkham
Copy link
Member

Item: Low level packaging ( #81 ). How far is too far? Should system tools be packaged? When should they packaged? How/when should they be used? How should they be organized (same channel, different channel, subchannel)?

@pelson
Copy link
Member Author

pelson commented Apr 15, 2016

Item: NetCDF is broken... conda-forge/staged-recipes#213

@jakirkham
Copy link
Member

Item: NetCDF is broken... conda-forge/staged-recipes#213

Yeah, we have to get that out of the backlog it is causing all sorts of grief for people. I was just looking at it again earlier.

@ocefpaf
Copy link
Member

ocefpaf commented Apr 15, 2016

Item: NetCDF is broken... conda-forge/staged-recipes#213

Thanks for adding that. I am really concerned about this since we added our own version of hdf5.

We just got zlib out and I am working in hdf4 BTW.

@jakirkham
Copy link
Member

Is the version of zlib the same or different from the one in defaults?

@ocefpaf
Copy link
Member

ocefpaf commented Apr 15, 2016

Is the version of zlib the same or different from the one in defaults?

Version? Yes. Build method? Unknown.

@jakirkham
Copy link
Member

Yep, looks to be the same version that HDF5 was built with so shouldn't have any weird linkage issues. If we do, I can bump the build number on HDF5.

@takluyver
Copy link

Sorry, I was planning to join, but there seems to be something up with the wifi. I can get a wired network connection, but only in the open plan office, and I don't want to disturb other people.

@ericdill
Copy link
Member

Link to the hackpad for meeting notes: https://hackpad.com/conda-forge-meeting-2016-04-15-WZIa4PBQ6sz

@ericdill
Copy link
Member

Suggestion regarding the hackpad: One top-level heading (#) per meeting and then just keep this as the running notes for the meetings

@jakirkham
Copy link
Member

jakirkham commented Apr 15, 2016 •
edited
Loading

Sorry, I was planning to join, but there seems to be something up with the wifi. I can get a wired network connection, but only in the open plan office, and I don't want to disturb other people.

Sorry you weren't able to make it, @takluyver. We have held off on discussing the issues you raised because we are interested in hearing your thoughts on them and discussing them with you. Our next meeting with be on 29 April at the same time (2PM UTC), so if you are able to make it then we would be interested in talking with you more in person. 😉

@takluyver
Copy link

I think I should be able to make it then - thanks for postponing those points!

@pelson
Copy link
Member Author

pelson commented Apr 15, 2016

Sorry you couldn't join us @takluyver. I've added your items onto the next agenda.

To everybody: Please feel free to add other items at https://hackpad.com/conda-forge-hangouts-WZIa4PBQ6sz

@pelson pelson closed this as completed Apr 15, 2016
@pelson
Copy link
Member Author

pelson commented Apr 15, 2016

P.S. Minutes proposed as a PR at #94

@jakirkham
Copy link
Member

Docs ( #95 ) very much in progress.

@ocefpaf ocefpaf mentioned this issue Apr 16, 2016
Closed
@jakirkham
Copy link
Member

Added an organizational hackpad. See issue ( #101 ) for details.

@jakirkham jakirkham mentioned this issue Apr 18, 2016
Merged
@jakirkham
Copy link
Member

Correction @takluyver @ericdill @jjhelmus and others, I meeting next week is schedule for Friday not Thursday. The time will remain the same 1400 UTC.

This has been updated on the Hackpad and the errata addressed in the archived minutes in this repo.

Hope everyone can still make it. Sorry for the confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@takluyver @pelson @ocefpaf @jjhelmus @jakirkham @ericdill