This category is for community projects that use the Monty code base.
Having proposed this category, I’d like to make some usage suggestions.
Exposition format
Forum threads work well for discussion, but IMHO they aren’t so great for formal exposition. l also like to have a bit of control over the description format, etc. However, creating a full-on GitHub repo is a bit heavyweight for an early, speculative notion.
So, my plan is to create a Gist for each (proposed) project, then link to it in a forum posting. The ensuing thread can handle comments, suggestion, and such, leaving the Gist free to document, summarize, etc. Of course, once a project actually has Real Code (TM), it can go into GitHub. Note that both Gists and repos can be edited, providing version history, etc.
Needed capabilities
Some projects may need specific capabilities that Monty doesn’t yet support. So, I plan to include a section that lists needed capabilities, including a hashtag and a terse explanation, e.g.:
- #multiobj - Various types of plants will appear in the same image(s).
FYI, the Capabilitles/Measures/Benchmarks column in the Monty Project Overview spreadsheet includes a hashtag for each listed item.
Other sections
I could easily imagine including sections such as Background, Benefits, Caveats, Contributors, Precis, Project Status, Related Work, etc. Season to taste…