On October 29, I attended the Free Software Open Source Symposium (FSOSS) at Seneca College here in Toronto. This was the second time that I attended FSOSS, and once again it was an interesting experience. Even when you take my presentation crash and burn out of the equation.
While I only sat in on three sessions this year, and only one of those sessions had any relation to technical communication, I learned quite a bit.
Here’s what I heard and learned.
by: Bill Albing
The technology we employ to manipulate and manage content is an important aspect of our work, because content is crucial in our role as communication professionals. For years, I have worked with content and the technology that delivers it to readers. I have seen automation of more of our work and I have worked with the changes that have transformed our work.
But I continue to wrangle with content, as Scott Abel says, and I continue to learn how to work with the tools of wrangling. I do not apologize for getting my hands dirty and sometimes getting rope burn trying to keep content organized and flowing. But I have, for the most part, been quite successful in working with content and the technology surrounding it. I am not a content strategist and I do not claim to manage the message in the vicissitudes of management.
This time, our guest poster is Bill Albing. Bill has some very interesting insights into technical communication to share.
If you’re curious, then check back here tomorrow to read the post.
There’s a moment that everyone who presents or speaks in public fears. And I entered that moment during a presentation last week.
I went blank.
Stage fright. Freezing up. A very pregnant pause. None of those terms really sum up what happened to me during that talk. I went all tabula. As in rasa. It wasn’t pleasant, for me or for my audience.
Here’s a look at what happened, and what I learned from the experience.
As you may or may not know, I helped organize a two-day FLOSS Manuals book sprint at this year’s Toronto Open Source Week (held at Seneca College).
If you’re not familiar with a book sprint, read this for details.
This book sprint came about because:
- For the last two years, I’ve been promising Adam Hyde (head honcho of the FLOSS Manuals project) that I’d take a more active part in a book sprint
- I thought that this would be an interesting event to hold at Toronto Open Source Week
This time around, the goal was to complete a manual for the Mozilla Thunderbird email client. I hosted the book sprint in Toronto, and Adam Hyde took overall control from Berlin (where he lives).
It was an interesting two days, to say the least. Here’s a summary of what went down.