secondlife / secondlife/viewer
Technical Debt
Open
Nobody has claimed this yet.
stale
- Dominant language
- C++
- Stars
- 299
- Forks
- 146
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 88
Description
Description
Various chunks of the client that needs regular updating (3p), various bits that need refreshing, and so on.
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 #4967 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by inventorying the client’s third-party dependencies and the other chunks described as needing refresh, then determine a specific scope and acceptance criteria before making changes. Done cannot be established from the current issue because its KPIs are still TBD.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100