Communications

Open
#4,970 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue does not name files, tests, or an entry point; first clarify which communication feature is in scope and define the missing KPIs. Once a specific feature is chosen, identify its affected viewer area and tests, with completion tied to the agreed behavior.

Written by the indexing model from the issue text.

Description

stale
Description

Features that relate to improving communication. E.g., Discord support, social media integration, groups, patch notes, documentation, etc.

KPIs

TBD


This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #4970 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @Geenz (replace 20 with the amount, and @Geenz with the user to tip).

📖 If you want to learn more, check out our documentation.
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Contributor guide

Open the contributing guide

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.

More from secondlife/viewer

All issues in secondlife/viewer

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.