NixOS / NixOS/foundation

Define an efficient way of communicating on the board activities

Open
#65 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

epic
Dominant language
No language data
Stars
141
Forks
17
PR merge metrics
No merged PRs in 30d

Description

We currently publish the meeting notes on discourse and have some extra communication every once in a while (on discourse, with public panels, etc.).

Evidence shows that this isn't enough as not everyone follows the meeting notes (quite understandably) and the extra communication tends to arrive a bit too late. For instance the work on the trademark is something we've started several months ago, yet a number of community members – for which this was quite relevant – weren't aware of it until recently. Also, this is all mostly a one-way communication (not in theory since people can always answer in most channels, but in practice it tends to be).

So we need to define some clear efficient communication channels to make sure that community members can see what the board does, and express themselves

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked Discourse meeting notes and the communication examples mentioned in the issue, including public panels and trademark updates. Define a clear, efficient, two-way communication approach for board activities, with community members able to stay informed and express themselves.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.