Open koobs opened 2 years ago
We could push to both servers if we want to keep them both.
Sounds good.
So we have BSDLabs for "BSDLabs" projects and updates (of which developing a community capability is one), and freebsd#community as a current defacto home for the team in the community to talk and discuss community initiatives/organising.
We need a list of events/changes and the -> server(s)#channel(s) mapping for where they should go.
Some goals & questions:
purpose: comms and updates are easy and quick to follow in an async way. This is a part of making internal and externals comms: effective, and transparent
goal: high signal:noise ratio
goal: events are relevant to the audience segment, server & channels. Audiences: the community team (us), the community, potential contributors who want to learn more
question: is there anything we don't want to publish? If so, do we have a place (repo) these could be made or handled.
question: once we have desired event/place mappings & segmentation, is our repo organisation currently conducive to that event and notification segmentation. Eg: might we want or need a special repo/place for external comms (like decision changelog maybe) or newly created issues (are these useful for others to see?)
in what ways can we leverage this notification mechanism as a means for marketing or recruitment purposes, or a means to tickle those curious to get involved, whether "tweeting" or otherwise, eg; we want a new logo or front end design, etc"
I setup a webhook on community repository for all events to go to Discord:bsdlabs:#general until this issue is resolves mapping events to servers fore precisely
Webhook was changed to #general -> #github-feed
Once we decide the primary Discord (FreeBSD or BSDLabs), implement and enable GitHub notifications so they're announced there so its easy for people to stay up to date
Depends on #1