We welcome all correspondence! Please send us your confused questions, bug reports, feature requests, and interesting examples. An informative subject line would be appreciated.
To report a possible bug in Dyna, email bugs at dyna dot org. Thank you!
If you're having trouble installing, using, or understanding Dyna, send your questions to help at dyna dot org.
Suggestions, flames, testimonials, offers of help, user stories, related work, and other comments should be sent to comments at dyna dot org.
User mailing lists
We plan to set up discuss and announce mailing lists that you can subscribe to. When you download Dyna, you can already check a box to be added to these lists when they are set up.
You can use one of the following addresses at dyna dot org if you want to be extra-helpful. This may also get a faster response, since it immediately notifies the appropriate developer(s), without us having to re-route your email to one of the following addresses ourselves (as we do if you email the general bugs address).
- Getting started
- documentation: Missing, confusing, or possibly incorrect documentation that you can't fix yourself.
- distro: Getting Dyna running on your machine (licensing, version numbers, packages, installation, portability).
- dynac: The dynac command that invokes the compiler, and its options. Also the preprocessor.
- server: Web and email services provided by dyna.org (wiki, bug tracker, mailing lists).
- The Dyna language and how it works
- syntax: Stream input and output of programs and data. Specifically, how terms may be written, the parser that reads them, the methods that print them out, and which terms count as legal Dyna code. This includes character encodings (Unicode), tokenization, and the default operator table and how to change it.
- inference: Evaluation of terms with values; rules that define values; policies that control when values are computed and stored; back-propagation.
- storage: The classes that represent terms. Specifically, type declarations, the Dyna and C++ APIs to the generated term classes, declarations that control storage of terms and memos, namespaces, garbage collection, memory mapping and other disk I/O.
- transforms: Source-to-source transformations that dynac can perform, including type inference and optimizations.
- Support packages
- reading: Papers or projects that are relevant to Dyna, which you think the Dyna developers should read about.
- bugs: Uncategorized bug reports (see above).
- help: Uncategorized requests for help (see above).
- comments: Uncategorized comments (see above).
- misc: Anything that doesn't fit in another category.
If you're not positive which address to use, please just send to bugs and we'll figure it out. Also, the address only matters for the first email about an issue -- any followup emails are tracked by the subject line instead.
Again, all these addresses are at dyna dot org.
Developers should usually use the targeted addresses above, or use the web interface and specify a queue.
If you just want to comment on a ticket without replying to the requestor, email your reply to bugs-comment rather than bugs, or use the web interface.
More documentation about the ticket tracker is at Developers/RT.