Skip to content

Submit Mushi to an awesome-* list (good first issue)Β #38

Description

@kensaurus

Help next devs find Mushi πŸ›

Awesome-lists are still one of the highest-leverage discovery surfaces for OSS devtools β€” a single merged PR can compound for years. We have drafted candidate entries in docs/marketing/drip-channels.md, but each list has its own alphabetisation, badge convention, and one-line format. We need humans to read each list's contributing guide and adapt the entry.

Important: this issue is closed by an upstream PR in the awesome-list's own repo, NOT by a PR to mushi-mushi. Reply here with the upstream PR link once it is open. Automated/bulk submissions to any list (or to this repo) will be closed on sight β€” list maintainers reject them and it burns the list for everyone.

How to help (β‰ˆ 15 min per PR):

  1. Pick one awesome-list from the table in docs/marketing/drip-channels.md. Comment below to claim it so others know.
  2. Read that list's CONTRIBUTING.md β€” alphabetisation rules, badge style, one-line format.
  3. Adapt the candidate entry from drip-channels.md to the list's conventions.
  4. Open the PR upstream (in the awesome-list repo, not here). Reply here with the link.

We will thank every merged PR in the next release notes and on Bluesky.

Do not run automated bulk submissions β€” list maintainers reject those on sight, and it burns the lists for the next OSS project that needs them.


Status:

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationgood first issueGood for newcomers

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions