documenting in the cloud (was RE: Back on topic please

Subject: documenting in the cloud (was RE: Back on topic please
From: "McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com>
To: TechWhirl Admin <admin -at- techwhirl -dot- com>, Techwr-l <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 7 Jun 2012 15:13:06 -0400


Well, there IS the issue of cloud services (does anybody offer a HAT as
a cloud service yet?), Google Docs, accounts for storage of docs and
other files on cloudy storage (DropBox?) and the protocols and safeguards
when we access those files and in-progress docs. They have to make a
lengthy round trip, each time we access them. Or if the software is
itself in the cloud, along with the data, we need to consider how
secure that usage really is. How compartmentalized... how confident are
you that when you relinquish a cloud-based software instance, it
gets really, really, really killed, and doesn't linger to possibly
be accessed by the next person or VM assigned to that chunk of memory,
HD space, etc.

More to the point, how confident are your employers/customers?

It's really, really handy to be able to access not only your
in-progress docs (and maybe the supporting source materials),
but also the application that fondles it, from anywhere in
the world, day or night, on whichever device you have at hand.

Techwriters living the internet lifestyle. :-)

But there's that trade-off. How secure is it? How do you
compare one provider's offering with another, in terms of
that security?

This might be one of those rare cases where it DOESN'T
turn out to be better to ask forgiveness (of your customer)
than to ask permission... even though you know they'll
probably reflexively say "NO!".

> -----Original Message-----
> From: TechWhirl Admin
> Sent: June-07-12 2:24 PM
> To: Techwr-l
> Subject: Back on topic please
> I let the conversation on the LinkedIn hack go forward in the interests
> of
> protecting the list since we would all be at risk from a hacked account
> (and have had some members who have been hacked in the recent past).
> We
> have now veered completely off topic and it's time to get back to tech
> comm.
> One of the List rules states "If it relates to *computer use* but
> not technical communication, it probably isn't appropriate. Don't post
> it."
> Your first clue should be a subject line that starts with "OT." Those
> who
> continue to post to OT threads risk being moderated.
> Time to get back to hot spot graphics, the need for editors, DITA vs.
> and other tech comm topics of the day.
> Thanks
> Connie Giordano
> List Moderator

The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.

Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.

Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @


Back on topic please: From: TechWhirl Admin

Previous by Author: RE: LinkedIn phishing?
Next by Author: Developer "Best Practices" content
Previous by Thread: Back on topic please
Next by Thread: Re: documenting in the cloud (was RE: Back on topic please

What this post helpful? Share it with friends and colleagues:

Sponsored Ads