Communication Channels
All Ideal modules share a set of mailing lists and a single issue tracker. No SourceHut account is required — you can participate entirely via email.
If your mail provider cannot handle the ~ character in addresses, replace ~cpradog with u.cpradog (e.g.
u.cpradog.ideal-devel@lists.sr.ht).
Mailing Lists
| List | Purpose | Address |
|---|---|---|
| ideal-discuss | End-user discussion and questions | ~cpradog/ideal-discuss@lists.sr.ht |
| ideal-devel | Development discussion and patches | ~cpradog/ideal-devel@lists.sr.ht |
| ideal-announce | Low-volume announcements | ~cpradog/ideal-announce@lists.sr.ht |
| ideal-security | Security vulnerability reports | ~cpradog/ideal-security@lists.sr.ht |
Archives are available at sr.ht/~cpradog/ideal/lists. The patches queue for ideal-devel is at lists.sr.ht/~cpradog/ideal-devel/patches.
Messages from non-subscribers are accepted on all lists except ideal-announce (restricted to maintainers).
ideal-security is a write-only list — anyone can send a report, but the archive is not publicly visible. Use this list to report security vulnerabilities privately. Do not file security issues on the public tracker.
Subscribing
Subscribing is optional — you can post to ideal-discuss and ideal-devel without subscribing. To receive all
traffic from a list, visit its archive page and use the subscribe option, or send an email to
~cpradog/<list>+subscribe@lists.sr.ht (e.g.
~cpradog/ideal-discuss+subscribe@lists.sr.ht).
To unsubscribe, send an email to ~cpradog/<list>+unsubscribe@lists.sr.ht.
Issue Tracker
Bugs and feature requests are tracked at todo.sr.ht/~cpradog/ideal.
You can browse and file tickets on the web, or interact entirely via email:
| Action | Email address |
|---|---|
| Submit a new ticket | ~cpradog/ideal@todo.sr.ht |
| Comment on ticket #N | ~cpradog/ideal/N@todo.sr.ht (or reply to the notification) |
| Subscribe to all tickets | ~cpradog/ideal/subscribe@todo.sr.ht |
| Subscribe to ticket #N | ~cpradog/ideal/N/subscribe@todo.sr.ht |
| Unsubscribe | Same as above, replacing subscribe with unsubscribe |
The subject of the email becomes the ticket title and the body becomes the description. Markdown is supported.
Cross-References
You can reference tickets from comments, descriptions, and commit messages:
#123— ticket in the same tracker.~cpradog/ideal#123— fully qualified reference (useful from other contexts).
Triage Commands
Maintainers can include triage commands as the last line of a comment email:
| Command | Effect |
|---|---|
!resolve fixed | Close as fixed |
!resolve implemented | Close as implemented |
!resolve wont_fix | Close as won't fix |
!resolve by_design | Close as by design |
!resolve invalid | Close as invalid |
!resolve duplicate | Close as duplicate |
!resolve not_our_bug | Close as not our bug |
!reopen | Reopen a closed ticket |
Email Etiquette
- Use plain-text email — HTML is not accepted. See useplaintext.email for guidance on configuring your client.
- Do not top-post. Reply inline, quoting only the relevant parts of the message. Trim text that is not necessary for context.
- Wrap lines at 72 columns. Do not reformat text quoted from other messages.
- If signing with PGP, attach the signature as a separate MIME part — do not use inline signatures.
- Keep messages focused and on-topic.
- Be respectful — see the Code of Conduct.