Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

Monday Calls: May 15-21 #452

Closed
ipfs-helper opened this issue May 10, 2017 · 4 comments
Closed

Monday Calls: May 15-21 #452

ipfs-helper opened this issue May 10, 2017 · 4 comments

Comments

@ipfs-helper
Copy link

ipfs-helper commented May 10, 2017

For information about these calls and how they work, read the ipfs/pm README.

Calendar

Zoom and Stream links will be updated directly before the calls. Links to them will also be dropped in IRC, at the start of each call. If the link below seems to link to this issue, the link has not been updated yet.

Video Conference link

Monday

Endeavour Lead Notetaker Time (PST - UTC - CET) Pad
All Hands Call @victorbjelkholm @whyrusleeping 9:00 16:00 18:00 agenda and notes
Sync Between Sprints TBD TBD 10:00 17:00 19:00 agenda and notes

Please add any agenda items you have to the pad before the project-specific sprint call starts.

Note that the agenda notes do not automatically have content added to them (see tracking issue). Add this template.

The sprints for the week are available to view in the WaffleBoard for ipfs/roadmaps.

@victorb
Copy link
Member

victorb commented May 15, 2017

Anyone feel like they would like to take over the moderation/lead role from me today?

@whyrusleeping
Copy link
Member

whyrusleeping commented May 15, 2017

IPFS All Hands Call 15 May 2017

Recording: https://ipfs.io/ipfs/QmbpJLY38U94333Bk976DFX2rs6Znhr6wbhUToPYSypWDV

Moderator: @lgierth
Notetaker: @whyrusleeping
Attendees

Agenda

  • Demos

Notes:

  • Matts hair is very windblown
  • Some projects have a good process of defining how issues should be triaged and labeled. Having a clear process makes it possible for people to contribute by doing this label filtering
    • Triaging issues creates better entry points for new contributors
    • Triage itself could be a contribution, although permissions for labels, etc. might be limiting
    • How do we triage today?
      • @whyrusleeping triages most go-ipfs issues
        • Actionable vs. non-actionable
        • Bug, Enhancement, Panic
        • Aim to make something actionable or close quickly
    • Jay Carpenter interested, will need to work with core team member. Will follow issue [ipfs/pm/Improve Triaging of Issues and Contribution Guidelines #449] for news.
      • Requests for help:
  • @lgierth to add notes about labels/security tooling
  • 'latest' on the ipfs website needs updating
    • Need help sourcing news articles for the ipfs website
  • English and kurdish wikipedias are up on ipfs, havent been announced
    • Working on a process to make this all community managed
    • need to be careful about provenance of data
    • Definitely need help, if anyone is interested get in touch
  • Want to have a blogpost for each new ipfs release
    • maybe have a separate 'tech blog' for ipfs?
    • maybe the titles of blog posts can separate from an 'announcement' and an actual blog post
    • definitely need more blog posts

@flyingzumwalt
Copy link
Contributor

@whyrusleeping please submit a PR with a copy of those notes in ipfs/pm/meeting-notes

@flyingzumwalt
Copy link
Contributor

Recording: https://ipfs.io/ipfs/QmbpJLY38U94333Bk976DFX2rs6Znhr6wbhUToPYSypWDV
2017-05-15 12.04.21 IPFS All Hands Call 779351365

@ghost ghost closed this as completed Jun 12, 2017
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants