On 11/14/2013 01:08 PM, Daniel Glazman wrote:
Honestly, I am not sure "tutorial quality" and "automatic generation" live
well together. We hire tech evangelists for their ability to present well
information and make messages percolate better, and similarly good doc
requires good tech writers who only do that.
As I said earlier, a tutorial is crucial material to attract people and I
think writing talent, excellent presentation and correct readability are
need for such a tutorial. When I say "attract people" or "community", I am
of course thinking of reaching critical masses for Rust-based projects,
including Servo, and that requires making sure documentation material are
good enough to self-generate a pool of potential hires.
I tend to agree with this, think that a collaborative approach is
unlikely to produce a consistent and high quality tutorial. I don't want
to discourage anybody but my current opinion is that we should hire an
experienced technical writer to do this piece especially, with input
from the wider community. Where I think collaboration is more likely to
produce something nice is in a 'cookbook' style document, of which
several people have already worked on seperately. Also of course API
docs and the reference manual are places where individuals can plug in
their own sections without impacting the overall narrative flow.
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
