Decide the Mesh CIP-30 tutorial before the stale bot closes it
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, github-actions
- Domain
- developer-experience
Research direction
Read this issue alongside #265 and the repository’s stale job configuration. Determine whether the CIP-30 tutorial remains in scope, then ask a maintainer to either keep #265 open with the requested labels or close it with wontfix and a reason. Done when #265 has a maintainer decision and the stale job will not close it while it is listed as a good first issue.
Written by the indexing model from the issue text.
Description
Summary
#265 is the only open issue that already carries the stale label. It is also good first issue, documentation, enhancement, and Medium Priority: a hands-on CIP-30 wallet connect and first preview transaction with Mesh.
The stale job closes an issue 14 days after the label is applied. A good first issue that the bot closes reads as abandoned, not as a decision.
What to change
- If the tutorial is still in scope, remove
stale, leavegood first issue, and addpinneduntil someone starts it. - If it is not in scope, close it with
wontfixand one sentence on why, instead of waiting for the bot.
Acceptance
- #265 is either actively kept open or closed by a maintainer
- It is not closed by the stale job while it is still listed as a good first issue
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 24
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 34
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from IntersectMBO/developer-experience
-
documentation enhancement Low Priority
Difficulty 1/5 Under an hour Newbie friendliness 72/100
IntersectMBO/developer-experience#397 ·
Maintainers usually reply within 2 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
IntersectMBO/developer-experience#376 ·
Maintainers usually reply within 2 days
-
documentation pinned
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
IntersectMBO/developer-experience#363 ·
Maintainers usually reply within 2 days
-
documentation pinned
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
IntersectMBO/developer-experience#362 ·
Maintainers usually reply within 2 days
-
documentation pinned
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
IntersectMBO/developer-experience#360 ·
Maintainers usually reply within 2 days
All issues in IntersectMBO/developer-experience
Similar issues
-
bug parity
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
WenyuChiou/agent-board#1489 ·
Maintainers usually reply within 1 day
-
area: bazaar bug complexity: medium
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
accensa/x402-facilitator-stellar#779 ·
Maintainers usually reply within 1 day
-
bug good first issue P4 size:S web-ui
Difficulty 2/5 Half a day Newbie friendliness 85/100
josephfung/curia#2600 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cloudflare/partykit#444 ·