Community

How to ask questions / report bugs / suggest features / contribute.


Channels

Channel Use
rho.md/feedback Bug reports / feature requests / spec questions / "how do I..." — plain words, no account needed
[email protected] Private / security / partnership / press

Reporting bugs

Before reporting

  1. Make sure you're on the latest Rho MD (the app updates itself) and try again
  2. Reduce to a minimal reproducible example

Report template

**Bug description**
(One sentence)

**Steps to reproduce**
1. Open ... in Rho MD
2. Do ...
3. See ...

**Expected behavior**
Should ...

**Actual behavior**
Actually ...

**Minimal reproduction**
\```markdown
(Minimal example)
\```

**Environment**
- Rho MD version: 1.4.x
- OS: Windows 11 / macOS 14 / Linux Ubuntu 22.04 / Android / iOS / etc.

Filing feature requests

Before filing

Read Roadmap — may already be planned.

Request template

**Problem**
(What use case are you solving?)

**Existing workaround**
(How do you currently work around this?)

**Expected behavior**
(If Rho supported this, how would you use it?)

**Priority**
(How critical for you / your team?)

Contributing code

Rho MD's source code isn't public, so we can't take code contributions. Docs fixes and examples are welcome through rho.md/feedback. The format is open (CC BY 4.0) — if you want to build on it, write your own reader: see Implementing your own reader.


Contributing docs

Docs are the easiest entry point for community contribution:

  • Fix typos / clarity
  • Add missing examples
  • Translate (CN→EN / EN→other languages)
  • Share real-world use cases

Send them through rho.md/feedback.


Question etiquette

Questions — via the feedback page

  • "I want to use Rho for X, where do I start?"
  • "Why doesn't mini DSL have if/else?"
  • "How do you use Rho in production?" experience sharing
  • "Is this use case suitable for Rho?"

Bugs and requests — via the feedback page

  • "Bug: layout cols=4 shows as 5 columns on narrow screens"
  • "Feature: hope modal supports keyboard ESC to close"
  • "Spec unclear: is annotate range 0-based or 1-based?"

Email is for

  • Security vulnerability reports (don't post them publicly)
  • Private partnership proposals
  • Press inquiries

Code of Conduct

scos-lab projects follow Contributor Covenant 2.1:

  • ✅ Respect different views / experiences / backgrounds
  • ✅ Offer constructive feedback
  • ✅ Assume good intent
  • ❌ Personal attacks / harassment / discrimination
  • ❌ Political / religious / personal attacks

Violation → email [email protected]; possible ban after investigation.


Security vulnerability reports

Don't post it publicly — security issues need patches first, then disclosure.

→ Email [email protected] with subject [SECURITY]

We reply as soon as we can, and disclose together with you after a fix.

We won't retaliate against security reporters.


Media / talks

Want to write articles / record videos / give talks introducing Rho?

  • ✅ Fully welcomed — no advance permission needed
  • ✅ Want interview / private demo → email [email protected]

Learning resources


About scos-lab

scos-lab is the maintainer of the Rho format spec / Rho MD / Rho Cloud / Rho Library.


See also