Session Proposal Template

[RichardLitt]

For each proposed session, we'll have 1 issue, with the "Session Proposal" label, with the following template.

Session Proposal Template

Post an issue with this template:

• Title: (a short title)
• Led by: (who is leading this?)
• Description: (the why? the how? and the what?)
• Goal(s): (list the goal(s) of the session, with a list of checkboxes)
• Target Participants: (Everyone, people interested in js, etc..)
• Related Sessions: (link to other sessions (if any) this one is related to-- to aid scheduling them back to back)
• Proposed Length: (choose one of: 15min, 30min, 45min, 60min, 90min)
• Links to review beforehand: (anything people should read before coming)

Example

• Title: The HTTP API Spec
• Led by: @RichardLitt
• Description: I would like to see @RichardLitt talk about the HTTP-API-Spec, available at ipfs/http-api-spec, and how it works.
• Goal(s):
  • Overview of Apiary
  • Overview of how .apib files work
  • An example log from IPFS and how to update the HTTP API Spec
• Target Participants: Everyone
• Related Sessions: None.
• Proposed Length: 30min
• Links to review beforehand:
  • https://github.com/ipfs/http-api-spec
  • docs.ipfs.apiary.io/#

[daviddias]

Let's try to get some of the sessions in that we already know we want to have. Could the primary leads open the issues for those, please?

• Packet Switching @lgierth
• Data Importers
• IPLD Selectors @nicola
• Migration path to IPLD
• Key Revocation and Rotation for IPRS
• Scalable P2P pubsub
• API Tokens for the HTTP-API @Kubuxu
• Peergos Integration
• Bitswap strategies, make the block exchange even more efficient (Alternative BitSwap strategies ipfs/notes#20)