slaxo
There's a really interesting podcast segment[1] about the Preserving Digital Worlds[2] project which tries to answer some of the questions about how to best document / preserve something who's value comes from the experiences users share with each other
[1]https://soundcloud.com/roman-mars/99-invisible-13x-game-over [2]http://pvw.illinois.edu/pvw2/
What's the best way we can contribute if we can't be there in person for the rally?
As someone who recently started using cucumber, this was definitely a frustration at first. But after a couple weeks of writing step definitions, and focusing on making them reusable (using some of the tips here: http://coryschires.com/ten-tips-for-writing-better-cucumber-... ), I ended up with a pretty good bank of general steps that I could cobble together into new features without much modification. The result was something much more readable and reusable than if I wasn't using Gherkin on top of the step definitions.
So if the measure of being a "professional designer" is someone who is paid to do design work, I think this is fine advice. A designer gets better with practice and real world work. This seems like a good starting point.
In my short few weeks of using it, the API seems better than nzbmatrix, but the community / comments on files is near nonexistent. If you're only looking for something to hook up to sickbeard / couchpotato though, it should do the job just fine.