Skip to content

Write a chapter on running community meetings #245

Description

@semioticrobotic

Running community calls/meetings is an essential aspect of growing a contributor community. But in the guidebook, we currently offer very little guidance on this practice. This chapter could change that.

Activity

  1. semioticrobotic commented on May 19, 2025

    @semioticrobotic
    MemberAuthor

    Whoever decides to pick this up will find a draft chapter file already in progress on the community-meetings branch.

    I think @resonantspectrum might be the original author of the material?

    Thinking of tapping @LauraHilliger on the shoulder, as I know this is a topic near and dear to her heart.

  2. funnelfiasco commented on May 23, 2025

    @funnelfiasco

    If @LauraHilliger does not want to do this, I could add it to my queue. There's an entire chapter of my book devoted to the concept and I could rewrite it in such a way as to not violate my publisher's copyright interests.

  3. semioticrobotic commented on May 23, 2025

    @semioticrobotic
    MemberAuthor

    A co-written chapter would be a welcome addition!

  4. LauraHilliger commented on May 26, 2025

    @LauraHilliger

    I'm here! Let's co-write! @funnelfiasco what would be a good process for you? I prefer something with comment function and suggestions so we can see each others edits...If we work in git I promise to break everything regularly. We could just copy/paste the existing chapter plus stuff from our other articles/chapters into a open gdoc?

  5. funnelfiasco commented on May 27, 2025

    @funnelfiasco

    That sounds perfect, @LauraHilliger. I'll email you to try to find a time for us to perhaps have a quick chat about how we want to approach it at a high level and split the work and also because I miss your face.

  6. semioticrobotic commented on May 28, 2025

    @semioticrobotic
    MemberAuthor

    This makes me very happy! Thanks to you both! As always, let me know how I can best be of service.

    @funnelfiasco: When the time comes, current best practice for review is to create a new branch and put the chapter material on it. We have a working branch for this material underway. But if you want/need me to hop into the Google Doc for earlier review, I can do that too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions