Skip to content

community: Build an active community of users who consistently share about how they're using their PlanktoScopes #262

@ethanjli

Description

@ethanjli

This is a tracking issue for our project to build an active community of users who consistently share about how they're using their PlanktoScopes, to each other and to the internet.

Motivation

Currently, we have a Slack workspace which has some activity but is not that active. People are not really sharing with each other about all the cool things they're doing. We also have people who have recently appeared out of the blue (potentially due to our feature on Hackaday?) and filed issues. This suggests that there are people who are trying out PlanktoScope, but we don't have an active community of fellow users to connect them to.

It would be useful to have a centralized gathering location for the community to share with each other about their work, and to inspire each other to do cool things with the PlanktoScope. This can also be a place where people highlight their own long-form narratives/stories about what they're doing the PlanktoScope, so that the PlanktoScope project emphasizes its community as a community of people, not just a community of tools.

Goals

  • Have a blog with:
    • at least 4 contributors each year
    • at least half of the contributors each year coming from regular PlanktoScope community members, rather than FairScope or PlanktoScope project maintainers
    • at least 4 posts per year about updates from the PlanktoScope project and/or from FairScope; these can be announcements or work-in-progress descriptions
    • at least 4 posts per year about something cool someone is doing with the PlanktoScope
  • Have a Slack workspace with:
    • at least 6 posts per year about something cool someone is doing with the PlanktoScope

Steps

(these steps will be converted into tracking issues for stories)

Unresolved Questions

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions