Talk:Technical communications/What you can do

A good start, but perhaps the order of the sections needs tweaking.

And probably less overall weight given to the blog section. I think we should strongly emphasize translating documentation (with much better links... the VisualEditor link is lonely and awkward) and helping out with the tech newsletter over writing blog posts. Blog posts are nice, but better docs and a regular tech newsletter are much nicer: higher impact, better fitting with the spirit of this wiki, etc.

This isn't to say that blog posts aren't nice for certain new features, but surely those (large) features will have dedicated staff members devoted to writing such posts. ;-) My two cents. --MZMcBride (talk) 03:55, 29 October 2013 (UTC)


 * MZMcBride: Hi. Thanks for the feedback :) I mostly agree with you. To provide a little context: the reason for the current bias of this list is twofold. First, the list of tasks was mostly written in preparation for Google Code-In, in which apparently translation tasks are not allowed. Also, writing a blog post is a more self-contained task than overhauling documentation.
 * The other reason is that I started with what I know :) These days, my responsibilities are mostly focused on tech news and blog posts. General documentation and its translation aren't currently in the primary scope of what I do. That said, I completely agree that this list shouldn't just be about what I do, which is why I encourage anyone to expand these sections, and add themselves as contacts. I'll reformat the page once the Code-In review process is completed to make this clearer. guillom 10:29, 31 October 2013 (UTC)