Weekly Team Meetings: Jan-Jun 2024

[ericsnekbytes]

Here is a record of the agenda/minutes for our weekly meeting. Everyone is welcome to join.

Navigation:

• Previous 6 months (Jan-Jun 2024) here

Let's avoid using this thread for discussion. If you'd like to discuss something in the minutes, open a separate issue and reference this thread.

[ericsnekbytes]

January 10, 2024

name	org	username
Eric Gentry	Anaconda	@ericsnekbytes

Agenda

• No items

[ericsnekbytes]

January 17, 2024

name	org	username	your Jupyter "Aha" moment
Eric Gentry	Anaconda	@ericsnekbytes
Carlos Brandt		@chbrandt
Rosio Reyes	Anaconda	@RRosio

Agenda

• Eric G

  • Charter acceptance: Hooray!
    • Bring your ideas! How do we best do our work, follow our mission?
      • Moots, RFC for content spanning multiple docs for instance? Meeting structure, other activities...it's all open to new ideas
  • Emphasize
    • We are helpers, everything we do relies on consensus
    • Collaborative to the bone (work with subprojects, solicit ideas from others and the community, etc)
    • We're a Jupyter-wide group...
      • We can try to blaze trails, for how to best do work on a project-wide level (work processes, materials, etc)
      • We will face unique challenges
      • Getting people to agree on content, etc. may be difficult at times
      • North star:
        • Envisioning our role: As each subproject succeeds, so does Jupyter...each subproject adds something important to different stakeholders, and contributes to the overall health and success of Jupyter. If we can approach subprojects from a place of advocating for their needs, we will have partners to help achieve our goals.
  • Tie up loose ends from early in the proposal process
    • Make issues for anything that isn't recorded yet
    • Make our (Docs WG) materials great, lead by example
    • Add any other needed documents (restrict standards-setting powers to council vote, other rules, guidance for new members and contributors, record some of these thoughts to illustrate how the group should operate, issue labels, etc.)

• Carlos

  • Prototype for documentation issues tracking
    • Discussed in 20/Dec, commented in issue 31
    • Periodically collect "documentation" issues from subprojects
    • https://github.com/chbrandt/jupyter-docs-test/blob/main/jupyter_docs_issues.csv
  • ToDo:
    • automate creation of "reference" issues linking to originals
    • create "docs-tracking" repository
    • refine automation to avoid duplication and update occasional (original issue) title changes
    • set permissions in "docs-tracking" repo issues to block comments in there (tracking issues are not meant to host discussions, their goal is just to work as an index)

[ericsnekbytes]

January 31, 2024

name	org	username	your Jupyter "Aha" moment
Carlos Brandt		@chbrandt
Eric Gentry
Jeremy Tuloup	QuantStack	@jtpio

Agenda

• Carlos

  • Here is the table of (some) subprojects documentation issues:
    • https://github.com/chbrandt/docs-team-compass/tree/main/workflows
    • https://github.com/chbrandt/docs-team-compass/blob/main/workflows/issues.md
    • (csv and md files available, linked in the README is the markdown table.)

    Notice the repository linked above is a fork of docs-team-compass

  • Last week we've discussed about a dedicated repository for those actions, but maybe it's just better keep things in one place (ie, docs-team-compass) and have a clear README to direct people.

• Eric G

  • Write proposal for Jupyter Office Hours
    • Jeremy: a prior issue with a similar idea, although the meetings never took place: Office Hours notebook-team-compass#13
  • Still working on Dual Compatibility Document

Notes

• (by Jeremy) Office Hours: Office Hours notebook-team-compass#13

[ericsnekbytes]

February 07, 2024

name	org	username	your Jupyter "Aha" moment
Carlos Brandt		@chbrandt
Eric Gentry
Ana Ruvalcaba	Cal Poly University	@Ruv7
Jeremy Tuloup	QuantStack	@jtpio

Agenda

• Eric G

  • Use the old Notebook meeting for "Office Hours" for maintainers + community members Use old Notebook meeting slot for open "Office Hours" with the community + each other (maintainers) jupyterlab/frontends-team-compass#237

• Carlos

  • PR for list of documentation issues Implement GH workflow to compile list of projects docs issues #36
  • https://github.com/jupyter/docs-team-compass/blob/main/workflows/documentation_issues.md

• Mike

  • GSoC documentation video generator?
  • https://github.com/jupyterlab/team-compass/wiki/GSoC-2024
  • Switch to using gifs in Jupyterlab documentation jupyterlab/jupyterlab#8776

• Ana

  • Proposal: to create documentation with best practices for hosting/leading meetings in Jupyter community. Collaboration with DEI standing committee (JDEI) and Community Building working group (JCB). Martha Cryan will reach out to connect.
  • Idea: I would encourage collaboration among the groups doing community work (DEI, Media Strategy, Community Building, Docs, etc)

Notes

[ericsnekbytes]

February 14, 2024

name	org	username
Eric Gentry	Anaconda	@ericsnekbytes
Carlos Brandt		@chbrandt

Agenda

• Discussed some subproject 'documentation' issues
  • Personas Jupyter #683
  • Diagram standardization Jupyter #667
    • use editable formats for collaboration in the drawings of diagrams. Excalidraw is the proposed tool.
      • should we bound that with some standard? Considering the different projects and their workflows.
      • we could layout the problem, alternatives and suggest through a PoC with existing diagrams. For instance, layout the workflow improving the process.
• ^The items above are recommendations for developers to use, how do we want to do these kinds of standardization efforts? Could do work as described above, follow up on tickets with solutions, post our work to the meta docs? We need to do work toward restructuring the meta docs to make it a friendly and efficient place for devs to go for resources like this
• Update copyright on Jupyter.org?
• Think about how we can gather more contributors and grow the docs wg
• Interesting "docu-mentor" ML model for docs https://www.anyscale.com/blog/building-an-llm-powered-github-bot-to-improve-your-pull-requests

Additional Discussion

[ericsnekbytes]

February 21, 2024

name	org	username
Carlos Brandt		@chbrandt
Eric Gentry	Anaconda	@ericsnekbytes

Agenda

• Carlos
  • WG mailing list
    • Is there a mailing list for this working group? #35
  • Disable actions in forks?
    • Mike pointed out (and showed) that forks have actions disabled by default (so, problem solved).

Notes

• Mike Krassowski
  • docs.jupyter outdated
    • releasing ipython outdated
    • Clean up first
  • security page can be added after
• Carlos notes marimo.io is a new interesting notebook technology