seed the project & community track #13
Conversation
| startTime="09:15" | ||
| speakers=["@lidel"] | ||
| title="Lightweight RFC Process" | ||
| description="A walkthrough of the new RFC process and its motivations, updated specs repository, and how you can submit an RFC." |
There was a problem hiding this comment.
pumped for this one. I still need to read ipfs/specs#289
I have a history with setting up an RFC process, and would recommend covering at least a few things in this talk:
- Guidance for community members on when to write an RFC, in contrast to when to file a pull request on a specific implementation.
- Try to sell folks on why they should write an RFC, being explicit about benefits. (maybe ipfs.io has to follow the spec, and this is the way to finally deal with getting stuff into that specific gateway? cc @aschmahmann)
- Try to write lay out a specific plan of how we're going to get the community to engage with this.
| speakers=["TBD, maybe @b5 and @mishmosh"] | ||
| title="Fireside chat: Funding and Sustainability" |
There was a problem hiding this comment.
In! It'd be great to do some homework for this one to make sure we're leaving folks with useful info. This will be happening after https://fundingthecommons.io/ which might be great to try to build upon.
| @@ -19,7 +19,7 @@ date = "2022-07-14" | |||
| days = 1 | |||
|
|
|||
| # the event times (shows up in the event card) | |||
| times = "09:00 - 17:00" | |||
| times = "09:00 - 12:00" | |||
There was a problem hiding this comment.
@mishmosh do you have any objection to making yourself the dri above?
on another note: I think targeting a half day would be fantastic.
There was a problem hiding this comment.
sounds good. i will be scouting aggressively for a replacement dri for 2023.
|
|
||
| [[timeslots]] | ||
| startTime="10:00" | ||
| startTime="09:45" |
There was a problem hiding this comment.
@bmann is going to be attending (although I haven't confirmed he'll be there on Friday), and I've been talking with the fission folks about a rather spicy take on resource allocation that I think would be really interesting to dig into. Paraphrasing:
Why are we pouring resources into re-writing the same thing in x # of different languages? Wouldn't it be better to pool our efforts & write a kick-ass reference implementation in one language and write libraries in each language that wrap that impl?
I for one really want to hear the case laid out for such a thing. Maybe this is the right forum?
| startTime="10:45" | ||
| speakers=["@mishmosh"] | ||
| title="Reorienting the website" | ||
| description="IPFS's public presence predominantly communicates that there are 2 IPFS implementations, js-ipfs and go-ipfs. It also communicates that the project is essentially PL-owned. During this session, we will re-orient some key landing pages toward today's Cambrian explosion of new implementations. This is intended to a fairly surgical co-working session, with a short discussion to kick off and then each participant creating PRs." |
There was a problem hiding this comment.
might make sense to have this one go last so hack time can run into lunch / move into the common space?
This PR seeds the project & community track:
The duration is changed to 1/2 day until or unless we have enough material for a full day of programming. #12 also edits the same file and should be merged first, but there should be no merge conflicts.