1 / 5
"The team is launching a local developer user group" — what distinguishes a user group from a conference?
-
-
-
-
Option D is correct. User groups are defined by regular cadence and low barriers — not company affiliation.
User group vs. conference:| Dimension | User group | Conference |
|---|
| Frequency | Monthly or bi-monthly | Annual or bi-annual |
| Cost | Free or token fee | Paid tickets (€100–€1000+) |
| Format | Informal, local, 20–100 people | Formal programme, 100–10,000+ |
| Examples | GDG chapters, CNCF local chapters | KubeCon, PyCon, JSConf |
Key vocabulary: user group, local chapter, organiser, community cadence
2 / 5
"The conference is looking for sponsors" — what does sponsorship provide and what do sponsors expect?
-
-
-
-
Option A is correct. Sponsorship is a community investment — not a content control mechanism.
Typical sponsorship tier deliverables:| Tier | Typical deliverables |
|---|
| Gold / Platinum | Large logo, exhibition booth, sponsored talk slot (clearly labelled) |
| Silver | Medium logo, shared booth, mention in opening remarks |
| Bronze | Small logo in programme, social shoutout |
Community expectation: sponsored talks must be clearly labelled and must not be pure product pitches.
Key vocabulary: sponsorship tier, logo placement, community goodwill investment
3 / 5
"We need to track community health metrics" — which metrics best indicate a healthy developer community?
-
-
-
-
Option B is correct. The CHAOSS framework defines community health beyond vanity metrics.
Vanity metrics vs. health metrics:| Vanity metric ✗ | Health metric ✓ |
|---|
| Total GitHub stars | New contributor retention rate (do first-timers come back?) |
| Twitter followers | Time to first contribution (TTFC) |
| Total commits ever | Breadth of active contributors (bus factor) |
| Forum post count | Community sentiment trend |
Key vocabulary: CHAOSS metrics, contributor retention, TTFC, community bus factor
4 / 5
"The project needs a Code of Conduct (CoC)" — what is its purpose?
-
-
-
-
Option C is correct. A CoC establishes safety norms — it is not a technical or legal document.
Code of Conduct components:| Section | Purpose |
|---|
| Expected behaviour | Sets positive norms — what "good" looks like |
| Unacceptable behaviour | Explicit list — no grey areas at boundaries |
| Reporting process | How to report; who handles it; confidentiality |
| Consequences | Warning → temporary ban → permanent ban |
The
Contributor Covenant is the most widely adopted CoC template in OSS (
contributor-covenant.org).
Key vocabulary: Code of Conduct, Contributor Covenant, CoC enforcement, reporting mechanism
5 / 5
"Building a sustainable community requires recognising contributors" — what are the most effective practices?
-
-
-
-
Option B is correct. Meaningful recognition is personal and public — not automated or metric-based.
Recognition practices:| Practice | Why it works |
|---|
| Release note shoutouts | Public, permanent record — shareable by contributor |
| First-time contributor welcome | Reduces drop-off after first PR; signals the community is welcoming |
| All Contributors bot | Tracks non-code contributions (docs, design, testing, translation) |
| Lines-of-code leaderboard ✗ | Harmful — incentivises padding, devalues docs and reviews |
Key vocabulary: All Contributors spec, non-code contributions, first-time contributor welcome