[Proposal] Scaling A Codeless Open Source Swift Community #22
Conversation
Proposals/0001-bas-broek.md
Outdated
| @@ -0,0 +1,49 @@ | |||
| # Scaling A Codeless Open Source Swift Community with Bas Broek | |||
|
|
|||
| * Proposal: [will add PR#](will add PR link) | |||
Proposals/0001-bas-broek.md
Outdated
|
|
||
| * Authors: [Garric Nahapetian](https://github.com//garricn) | ||
|
|
||
| * Review Manager: [will add name](will add profile link) |
There was a problem hiding this comment.
I need a review manager @JohnSundell @lattner
There was a problem hiding this comment.
I can do this (though I'm not sure what is involved :-).
There was a problem hiding this comment.
I think at the very least the Review Manager would ensure that the topic meets some guideline. What does a Swift Evolution Review Manager do?
Proposals/0001-bas-broek.md
Outdated
| ## Source compatibility | ||
|
|
||
| This episode fits with the overall theme of the podcast in the following ways: | ||
| - sheds light on another Swift community project |
There was a problem hiding this comment.
perhaps "highlights" instead of "sheds light"?
Proposals/0001-bas-broek.md
Outdated
|
|
||
| Brief description of your motivation behind this episode | ||
|
|
||
| The Swift Community Podcast is an experiment and is in its infancy and one of the biggest challenges is how to effectively scale the project through adequate community engagement. A codeless open source community may present challenges that are distant from code centric ones and so Bas maybe have some valuable insight into this given his experience with shepherding the Swift Weekly Brief. |
There was a problem hiding this comment.
I think it is also part of the motivation to increase collaboration and drive contributors to the Brief as well.
Proposals/0001-bas-broek.md
Outdated
|
|
||
| ## Introduction | ||
|
|
||
| Garric, Chris, and Bas will use Bas's experience as the steward of Swift Weekly Brief as a jumping off point to discuss the challenges and lessons learns with scaling a mostly code-less open source Swift community. |
Proposals/0001-bas-broek.md
Outdated
|
|
||
| Brief description of your motivation behind this episode | ||
|
|
||
| The Swift Community Podcast is an experiment and is in its infancy and one of the biggest challenges is how to effectively scale the project through adequate community engagement. A codeless open source community may present challenges that are distant from code centric ones and so Bas maybe have some valuable insight into this given his experience with shepherding the Swift Weekly Brief. |
There was a problem hiding this comment.
Bas maybe have -> Bas maybe has
Proposals/0001-bas-broek.md
Outdated
|
|
||
| Brief description of your motivation behind this episode | ||
|
|
||
| The Swift Community Podcast is an experiment and is in its infancy and one of the biggest challenges is how to effectively scale the project through adequate community engagement. A codeless open source community may present challenges that are distant from code centric ones and so Bas maybe have some valuable insight into this given his experience with shepherding the Swift Weekly Brief. |
|
Heh, a proposal formatted like a SE document. 😛 |
|
|
||
| * Proposal: [PR#22](https://github.com/SwiftCommunityPodcast/podcast/pull/22) | ||
|
|
||
| * Authors: [Garric Nahapetian](https://github.com//garricn) |
There was a problem hiding this comment.
So it seems like these URLs work regardless, but both this one and Chris' (in the review manager line) have two forward slashes; I think that should just be one?
|
|
||
| - Co-hosts: Chris Lattner, Bas Broek | ||
|
|
||
| - Editor: open |
There was a problem hiding this comment.
Is it too late to volunteer for the editor role? I'm a little bit confused now because the recording date happened before the PR is merged 😅
There was a problem hiding this comment.
ping @garricn, I think he's currently working on this.
And yes, the episode has already been recorded. We're still figuring out the whole process 😅
There was a problem hiding this comment.
Is it too late to volunteer for the editor role? I'm a little bit confused now because the recording date happened before the PR is merged 😅
@VojtaStavik Thank you for offering! Let's see if we can get you to be an editor on the next one.
|
This is ready to merge, I think? Sent with GitHawk |
|
@garricn ? |
In an effort to validate the concepts proposed in #18 and #19 this PR would add a proposal for a future episode. In reality, this episode is going to be episode 2, but I think going through this exercise will be helpful.
There are some open roles so please leave a comment if you want to fill one of them.
If you want to participate in the Q&A section, leave a comment with your question on this PR.
Also:
Proposalsdirectory.gitignore