Jon: Can we use JupyText? Tony: Sure, at least in most cases. Jim: Seems like it would be great, to me.
Jon:
Released Dash HoloViews
Planning / consensus-building on HoloData
Dash HoloViews webinar on Wednesday, Dec 16th.
Philipp:
Been working on Tabulator full time.
To ship in Panel 0.11 or 0.2 sometime in December
2020-12-07 Triaging meeting
Phillip and Chris triaging Panel
Jim triaging and releasing Datashader
Jean-Luc and Tony triaged geoviews, pyviz_comms and spatialpandas, dealing with all current issues.
2020-11-30 Triaging meeting
Phillip, Jean-Luc, and Jon triaged the hv release.
2020-11-16 Triaging meeting
Discussing Github Actions and doit:
Kim: Running tests on GA is done and working fine; have merged it for HoloViews
Proposed next step: get GA working on hvPlot
Proposed following step: get hvPlot docs building
Not yet addressing building packages
Tony and Kim to look at the pairing of doit and GA; can we streamline the process?
Tony to present his work soon on building conda and pip packages from the same Python-standard specs
Chris proposes that pyctdev is too hacky and dug in; he suggests it's more practical to start a new project and switch one library to use it, then move on from there.
2020-11-13 HoloViz meeting
Agenda
Panel 0.10.2 Release
HoloViews 1.14 Release
Datashader 0.12 release
pyct/pyctdev
Updates
Pam:
hvPlot PR scatter_matrix DS support? Waiting on Jean-Luc.
Jean-Luc: please address ASAP in time for DS release
Ibis/HoloViews docs: Have outline for lazy data handling docs page from Philipp; working on that now
E.g. for Bars, which currently only have examples with nested dicts
First, Kim can make the Bars example start with Pandas, to show how to do it starting from a tidy dataframe
Tony will talk to Philipp about improving multiindex support in hv and hvPlot
JupyterLab 3.0
Tony: Miserable for people who need to write extensions, but vastly simpler for users and for ecosystem management, and may end up net simpler for maintainers since the extensions can just be installed directly (e.g. with pip)
2020-10-12 Triaging meeting
Jim and Chris triaged imagen and EarthML, completing both of them
hv 1.13.4 nearly ready for release, which is necessary for .interactive.
Preparing Panel 0.10 and associated blogpost.
Pam: Some progress on datashading scatter_matrix. Needs testing.
Jim:
Still making progress on Param docs, though nothing pushed yet.
Lots of new HoloViz based projects starting at Anaconda.
Matplotlib Datashader support for interactive use is coming along.
Kim: Working on converting hv CI to use Github Actions, which hasn't been straightforward but seems to be going forward.
Jon: Decollate PR merged; thanks for the feedback! Link_selections stream refactor is in progress, and is already working for link_selections with Datashader in Dash.
Tony: HoloViews Ibis backend is getting close to mergeable.
Chris: Minor fixes to nbsite (for API/reference manual js, build fix, made a dev release). Philipp to look at the PR from which a previous dev release was built.
Marc:
Added some Panel extensions to awesome-panel-extensions: PerspectiveViewer, PivotTable, Tabulator, some Material Design widgets.
Exploring Panel + Transcrypt, Brython, or PyIodide and Fast Design
Tony: Also consider StandardLibJS (PyIodide-like, but lighter weight; NumPy/SciPy/etc. loading dynamically)
Jean-Luc: Trying to get Val's antialiasing merged for Datashader.
Agenda
Organize sprint for 1.10 of param.
Need to finalize API before enabling warnings.
Also need to clear out the Param issues tagged 1.10.
Jim to schedule API sprint w/o 9/14, then issues sprint to follow.
Where should HoloViews Dash logic live?
Seems fine for the hv plotly backend, if it's localized there.
Would it make sense to add HoloViews elements for dropdowns/range sliders so they could be used as linked selections filters?
Philipp: seems ok if it's Param based, perhaps provided directly as streams to link_selections rather than as an Element?
Chris: It's very cool that there's a PerspectiveViewer panel widget now. The Perspective project maintains a Jupyter widget as part of their project. Interesting to compare that with what happens for Bokeh/Panel widgets. Also, has anyone tried the existing Perspective ipywidget in Panel?! ;)
Adding support for Arrow as a Bokeh CDS would help this integrate better into HoloViz, to avoid Python/JS communication.
Jim, Pam, and Tony triaged all of the remaining untriaged issues on Param, including all open PRs. Up to date for the first time ever! Now we actually need to work on some of those issues. :-)
Jean-Luc, Philipp, and Chris triaged other issues.
2020-08-24 Triaging meeting
Jim and Tony triaged older issues on Param, closing another half-dozen older issues and triaged up to #346. #349-#398 remain to be triaged. Almost there!
Jean-Luc, Pam and Chris triaged around a page worth of hvplot issues. Chris reproduced two of the issues and a couple of issues could be closed immediately.
2020-08-21 HoloViz meeting
Attendees: Jim Bednar, Philipp Rudiger, Jean-Luc Stevens, Jon Mease
Agenda
Ibis
iloc? Philipp should try again. Also will improve with a new Ibis PR to make OmniSci work
JupyterCon talk on ipywidgets+Bokeh+Panel accepted
Doing testing for Bokeh 2.2 release
Jon
"uncollate" transform PR
History stream PR
Working on refactoring link_selections to be based on uncollate-friendly Derived and History streams rather than imperative callbacks+stream.event() calls.
Jean-Luc
Datashader's spread now works for aggregates
Still updating the docs (hv and ds)
Pam
Datashading hvPlot's scatter_matrix?
Chris
About to be able to work tons and tons
2020-08-17 Triaging meeting
Jean-Luc and Philipp: Triaged all of GeoViews
Jim and Tony triaged older issues on Param, closing another half-dozen older issues and triaged up to #227. #231-#398 remain to be triaged.
2020-08-10 Triaging meeting
Jean-Luc, Pam, and Tony: Datashader
Jim, Philipp triaged older issues on Param, closing a half-dozen older issues and triaged up to #171.
2020-08-07 HoloViz meeting
Attendees: Jim Bednar, Philipp Rudiger, Jean-Luc Stevens, Jon Mease, Tony Fast, Pam Wadhwa
Agenda
Twitter social media posts
Spatialpandas release
Quansight (Brian Larson and Tyler Potts) agreed to handle packaging issues
conda-forge feedstock created
Preference for having both pyviz and conda-forge channel
Jim: Started Param docs (barely); trying to work out a good structure. Working on getting funding for various HoloViz projects, extending work with current clients.
Jean-Luc:
Continuing work on spread operation in datashader (and HoloViews)
Philipp and Marc triaged Panel in preparation for a release.
Jim triaged Spatialpandas, closing all open issues except for wishlist items and a version incompatibility that's been pinned around for now. Ready for release!
Tony and Jean-Luc worked through the process of submitting a PR for an hvplot 'good first issue' (supporting datashader in scatter_matrix).
2020-07-24 HoloViz meeting
Attendees: Jim Bednar, Philipp Rudiger, Pam Wadhwa, Jon Mease, Marc Skov Madsen, Nicole Morgan
60-second updates
Jon: Working on Dash support for HoloViews, to support Plotly
Jim: Presented HoloViz at ESIP, and invited to present at a followon ocean conference.
Philipp
Cleaning up default templates for Panel
Added visual indicators for busy/loading states to Panel
Added ECharts component to Panel
Finish REST API
Gave PyData Budapest talk
Nicole: Building penguins k-means example
Pam: Triaging, plus starting to address hvPlot issues
Marc: Working on awesome-panel extensions, to make it easier to add new components
Jean-Luc: Implementing spread for Datashader aggregates using Numba stencils; nearly done
Tony (by email): Making progress on the Ibis backend for HoloViews; working locally and soon to make a WIP PR.
Agenda
Jon: transforming a DynamicMap into a pure (non-stateful) function as a step towards Dash support for link_selections
After discussion, agreed that this work is exciting and very promising and we'd love to see it appear as a PR.
Philipp: Panel 0.10.0 release
Templates: Material, Golden, Bootstrap, Vanilla; all with similar user API that makes them interchangeable, and all support a default theme and a dark theme.
Tentative plan: release, but ask users to exercise the templates, particularly with the dark theme, and report components that don't work well (look good) yet
Philipp to add a dark theme for HoloViews Plotly plots? Matplotlib too?
Some features like REST API support aren't really ready to build on; mark them experimental?
Marc: Include Streamlit in the family of interoperable components with Bokeh/Panel and ipywidgets, to allow everyone to mix and match as needed?
Jim: If streamlit adds ipywidget support for their widgets, seems like this would be done?
2020-07-20 Triaging meeting
Pam, Jean-Luc, and Jim triaged GeoViews starting with the newest and covering up to #335.
Philipp triaged Panel's newest issues.
2020-07-13 Triaging meeting
Jean-Luc and Tony triaged Param
Jim, Philipp, and Pam triaged GeoViews; still many to go!
2020-07-06 Triaging meeting
Jim and Kim triaged Param, starting with the oldest and reaching #89. Remaining to triage: #97-#398
Jean-Luc and Nicole triaged HoloViews
2020-06-29 Triaging meeting
Jim and Kim triaged Param, starting with the newest and reaching #399.
Philipp and Tony triaged hvPlot
Jean-Luc triaged HoloViews
2020-06-22 Triaging meeting
Philipp and Kim triaged hvPlot
Jean-Luc and Pam triaged HoloViews
2020-06-15 Triaging meeting kickoff
Jim, Philipp, Jean-Luc, Kim, Pam, and Tony triaged hvPlot as a test case
Types of triaging:
Daily: Supporting users by responding as new issues come in. E.g. Dask has a rota for triaging duties for that week; other team members focus on development first, while the triager focuses on triaging first and then development
Weekly backlog triaging: Trying to catch up on the lack of daily triaging so far; hopefully to be retired someday. Now scheduled for Mondays for HoloViz projects.
Triaging is specific to each project; rota for each project should only include people interested in/committed to each project
What does triaging include?
Look at each issue and move it along to the next stage:
If filed on the wrong repo, transfer issue.
If clearly invalid or outdated, respond and close.
If a usage issue or a user question, send the user to the Discourse site for this library
If apparently a bug, tag type: bug and try to reproduce.
If able to reproduce, mention that in the comments and assign it to the next milestone (from which it will be bumped forward if needed later). Don't try to fix during triaging.
If not enough information provided to reproduce it, request information from the OP and tag needs info
If unable to reproduce, say so in a comment
If a feature request, tag type: enhancement and decide on its status:
If it's something that we feel is either urgent or easy enough that it is likely to be implemented soon, add it to the next minor or major milestone.
If it is a nice to have but not high-priority item, i.e. not something we'll put on our roadmap for now, add it to the Wishlist milestone and (if possible) tag with either effort: low, effort: medium, effort: large, plus good first issue if it's straightforward. Group agree on good first issue but not sure about effort labels.
If the request does not seem like a good fit for this library, explain that and close the issue with a wontfix label.
Once an issue has been assigned to a milestone or closed, triaging is done. Issues that cannot be reproduced or need more info from the OP stay in triage until resolved or eventually closed as being stale.
Organizing rota
Create google calendar meet links after 5 min to see who is there and what groups are needed.
Starting with hvPlot today
80 open, 198 closed
Starting with newest
Added Wishlist milestone and some labels
For now, we'll curate the hvPlot repo as the target for milestones and labels, to be copied to all other projects
Let's come back to hvPlot with one team next time and actually make backlog-triaging progress
Questions that came up
What to do with "wishlist" issues? See discussion above.
Whether/how to harmonize labels between projects? (e.g. name for "bug", for when a bug has been confirmed, etc)
Actions:
ACTION Jean-Luc: Write up proposed process as a checklist to follow while triaging.
ACTION Chris: Standardize default label and issue template across HoloViz.
ACTION Jean-Luc: Add recurring meeting for Mondays on the hour with link to a video conference. (Note: Current link is wrong for hackmd - goes through slack)
ACTION Jean-Luc: Send out google docs spreadsheet for signup to decide who wants to triage which project.
ACTION Jean-Luc: Review labels on hvPlot, adding any referred to above and proposing removing any not needed, before we copy them to the other projects
2020-06-12 HoloViz meeting
Attendees: Jim Bednar, Philipp Rudiger, Jean-Luc Stevens, Chris Ball, Pam Wadhwa, Tony Fast, Kim Pevey, Kenneth Bowen
Updates
Philipp
Working on OAuth (not fun so far), ipywidgets blog, and Ibis backend for HoloViews
Jean-Luc
PR ready to merge on Param for serialization
Thinking about serialization more broadly
eq_hist colormapper work handed over to Mateusz
Returning to work on colorbars
Kim
Has been doing triaging for Param
How to search for examples in the gallery for a given bit of functionality?
Jim: Maybe have some search link associated with each Element or Widget or function reference material, finding where that item is in use in some defined set of examples?
Tony: Maybe datasette would help? Kim and I could make some sketches.
Vision: To make Panel more awesome and lower friction of using it.
Work for Orsted as a Lead Data Science Developer. Do everything but hard core data science like ML and DL.
Total rewrite of awesome-panel.org using Material Template. Still some details I would like to implement or improve.
Bringing a lot of things from Panel PRs to awesome-panel.org as examples: WebComponent, Material widgets, Wired Widgets, Perspective, ECharts, Google ModelViewer, …
Bringing some examples from Discourse to awesome-panel.org as examples
Probably bringing Material Theme Designer, Awesome Panel Designer to awesome-panel.org
Questions for templates vision:
Can we create something easy and generic like the Streamlit template?
Are we more providing examples that users will adjust for their use case?
Are the templates simple? Or are they for a full application with progress reporting, message reporting, error handling, automatic download of data(-frames), general exploration of data(-frames) via perspective or similar, login etc.?
Jean-Luc
Working on a new serialization system in param (JSON serialization including JSON schema support)
Chris
No updates
Pam
Leading sentiment analysis tutorial at AnacondaCON
Wrote up some notes and observations as newcomer to HoloViz tools
Kenneth
Added lockfiles for most of the pyviz-topics examples, a couple of bugs related to package availability still exist, but most are working smoothly after removing nomkl
It's good that nomkl doesn't seem to be needed, as it causes problems on Windows
Working on Vanilla and GoldenLayout Panel templates (see Elvis for an example).
Tony
Waiting on Philipp to write initial prototype for a Multi-index Pandas interface
Agenda
Scheduling of triage:
Set up doodle poll
Webcomponents
Making it simple to integrate JS components as needed, without having to wait on the Panel team to make things happen.
Would be great if there is a path from there to a proper Panel/Bokeh model, so that this can be a route towards expansion of Panel functionality over time.
Marc was focusing on making a data scientist able to grab some JS library and use it to solve their own problems, without deep JS/HTML/CSS knowledge and effort.
Current state of the PR? Marc will be reviewing and testing it soon. API design? Docs?
Philipp will write up some notes about the API, then Jean-Luc can take a look.
Panel WebComponent marketplace/contrib-gallery? Marc currently adds such things to awesome-panel.
Discussion about organization of docs
Review last week's actions?
Templates vision
Actions
Jean-Luc: Set up Doodle poll for triaging
Marc: File issue about JS/TS and integration testing
Philipp: Write up issue about separating developer/user level APIs for WebComponent and how to share components
Philipp: Look at the finalize method for Jinja2 templates; ask Tony for info if needed
Philipp: Add "Good first issue" labels to all the projects
Philipp: Make list of under-documented features in Panel that would be good targets for building gallery examples
Tony: Investigate setting up a HoloViz Tweetbot? Need a way to batch review.
Platform-specific packages? skip it in .yml and mention or conditionally install in .ipynb, conditional syntax (include only on Mac/Linux?), or make a dummy package with dependency on Mac/Linux, or…?
After successfully making the lock file, can the resulting locked project actually be built on the three supported platforms?
And finally, does the resulting project still work?
EarthML update: J-L working to make user guide buildable
examples/user-guides: projects, envts, or…?
We can use anaconda-project on EarthSim and EarthML, but projects with actual Python libraries have chicken-and-egg problems with their own internal dependencies that they would then have to keep consistent between setup.py and anaconda-project.yml.
website-specific package installs? Build the website in its own environment.
VSCode support for HoloViews/Panel?
2020-04-30 HoloViz meeting
Ipywidgets: Remaining work:
Can make HoloViz tools work in VSCode, but still needs some workarounds in Panel and HoloViews (repr_mimebundle, etc.). Punt on this for now.
Supporting throttling for Bokeh models as ipywidgets, possibly by extending jupyter_bokeh. Philipp, reluctantly. Mateusz: May be appropriate to add to Bokeh itself.
Bokeh model using Jupyter's widget manager to render the widget, to address the JLab rendering issues. Philipp to address.
Handling CDS patch events for editing data tables locally, for jupyter_bokeh. Mateusz to investigate.
Write blog post (Philipp, Mateusz, and Jim)
Colormapping
Mateusz still working on the internals. J-L to meet with Jim about how to implement eq_hist as a pure colormapper.
2020-04-24 HoloViz meeting
Indicators: Panel and/or HoloViews
Reductions into text (usually with unit/label, e.g. % or $)
Might also have up/down or other unicode character
Philipp to file on ad-conda: matplotlib-base for python2
2020-03-06 Meeting Minutes
Bokeh 2.0 release
HoloViews 1.13 release
link_selections
Warn on non-supported element types?
No support for holomaps or dynamicmaps?
Later: bokeh 1 bugfix release?
HV milestone for release
2020-02-21 Meeting Minutes
Desktop GUI replacements
Promotion
Pandas 1.0
Datashader ExtensionArray test failures
Other support for EAs in HoloViz?
Bokeh 2.0 release
HoloViews 1.13 release
link_selections
Warn on non-supported element types?
No support for holomaps or dynamicmaps?
GPU
spatialpandas dask support
bokeh1/2 compatibility
Later: bokeh 1 bugfix release?
2020-02-07 Meeting Minutes
Voila
Param API migration steps:
Step 1: Update all our projects to use obj.param.* (nearly complete) and release all
Step 2: Clean up .param API (deprecate unused methods (warn), rename obvious glaring problems but leave warnings and redirects) and update all projects
Step 3: Release param 1.x with new method names and update all projects to use it
Step 4: Release param 1.x with warnings enabled
Step 5: Remove redirects and old methods and drop Python2 support
Step 6: Release param 2.0
Python2
Bokeh 2.0 release (Philipp to give go-ahead today)
Thumbnailing: should fix and release new Panel before depending on bokeh 2.0
HoloViews release: soon after that
2020-01-23 Meeting Minutes
Library release status
Datashader: 0.10.0 released by Jim
Panel: 0.8.0 ready? Need to figure out what to do with the extended Django example PR
HoloViews: waiting on some fixes by Philipp and linked selection (and GPU testing plan)
GeoViews: waiting on hv release, Philipp (also needs to file issue on cartopy about proj4), Website doc build env not solving
Param: will need a release soon after all the others
EarthML: Waiting on Jean-Luc to move projects to examples.pyviz.
SciPy submissions?
Blog posts?
Other uncompleted tasks below
2020-01-10 Meeting Minutes
Review tasks below
Library releases
HoloViews: waiting on some fixes by Philipp and linked selection (and GPU testing plan)
Datashader: Jim to finish
GeoViews: waiting on hv release, Philipp (also needs to file issue on cartopy about proj4), Website doc build env not solving
Panel: A few open PRs; nothing too ambitious.
Jupyter_bokeh, to fix using datashader with voila? Waiting on hv release.
Param release with deprecations: Jean-Luc to drive
EarthML: Waiting on Jean-Luc to move projects to examples.pyviz.
Jon
Status: reduced to half-time work this week, may soon be no time depending on projects
GPU raster and quadmesh? Committed to doing this soon (for Pangeo)
Maybe time after that for GPU datashader blog post (coordinate with Nvidia?) – maybe Jon focuses on tech (Numba, RAPIDS, etc.) and Philipp does another one focusing on the end user
Work with Quansight: updates to spatialpandas – spatial indexing approach improved (saves memory, works on s3 via ffspec), spatial joins (in certain cases), Dask support
Business-friendly Panel features (kpi, donuts, traffic lights) (Python BI blog post?) –Philipp
Triaging issues on projects
Jim and Jean-Luc historical-triage Datashader (reorganize labels, set up milestones, assign issues)
Philipp and Julia have historical-triaged hvPlot, Panel, GeoViews
Who can historical-triage HoloViews, Param?
Set up schedule for recurring ongoing reviews: Julia
SLA for new issues on HoloViews, GeoViews, Datashader, hvPlot, Panel, Param: respond in 7 business days, either:
Close (usage question, irrelevant, etc.)
Label (categorize)
Assign to milestone
Need to put a triaging task on the schedule: TODO?
Some of the projects at examples.pyviz.org are currently giving warnings or errors (e.g. the landsat project); someone should go through them and give them a quick once-over for issues like that: TODO?
Other older issues needing resolution
Need some way to publish, maintain, and test some sort of cluster-based Dask example
Fixing Histogram warts? (Rename to ContinuousBars, and deprecate Histogram)
Statistical elements
We should make the "macro" or "derived" nature of hv.Distribution, etc. explicit, eventually reworking all such Elements to be fully expressed as operations on Elements internally
Jean-Luc to make an issue outlining the plan (Done?)
Philipp to tell J.Bois to make an ECDF operation and that we'll deal with the rest
-
Any changes
Be notified of any changes
-
Mention me
Be notified of mention me
-
Unsubscribe
Subscribe