[OpenAFS-Doc] PR Pamphlet

[Esther Filderman]

--- I started working on a PR pamphlet for OpenAFS. The idea is
that if we ever have a booth at a conference or somesuch (like, say,
the upcoming Ohio Linux Fest, or even SCALE), we can have something
informative to pass out.

The pamphlet is your standard six section foldout thingy. Right now I've got
- the cover
- "Who uses OpenAFS?" [which I'll make sure to get permission from
the places before I use 'em; right now I have placeholders]
- "Why Use OpenAFS?" [two sections, because I found that one section
just didn't work right]

That's 4 out of 6. Ideas for the other two?

Remember that it needs to be general, yet informative. We don't want
to overwhelm folks.

I'll try to send along my in-progress mess asap.

--- FWIW, I also continue to take swipes at the FAQ section of the
Wiki. The grand plan there is to eventually have a new "one shot" FAQ
that can be quickly read & posted places. It's definitely waay too
much for the pamphlet.

--- Also, BTW, I am specifically posting this here and *not* to -info
because a) this is the right crowd to talk about wording 'n' at and b)
I'd prefer the help from a smaller, more focused group of people.

--- Lastly, and possibly most importantly, the cover currently says:

OpenAFS
The Best Cross Platform,
Open Source, Secure,
Distributed Filesystem

I'm open to ideas on how to change that, or what to change it to.
Even better, I'd like to come up with something that we can then shove
at the Elders and say, "We recommend this be used in general for a
slogan/mantra/whatever."

[&, yes, I do realize that at least 3 of the Elders are reading this
list. So there.]

Thanks, folks!

[Christopher D. Clausen]

Post by Esther Filderman
--- I started working on a PR pamphlet for OpenAFS. The idea is
that if we ever have a booth at a conference or somesuch (like, say,
the upcoming Ohio Linux Fest, or even SCALE), we can have something
informative to pass out.

I might actually be able to go to the Ohio Linux fest... Does OpenAFS
have a booth?

Post by Esther Filderman
- "Who uses OpenAFS?" [which I'll make sure to get permission from
the places before I use 'em; right now I have placeholders]
- "Why Use OpenAFS?" [two sections, because I found that one section
just didn't work right]
That's 4 out of 6. Ideas for the other two?

Some of the most common questions on #openafs involve people assuming
that OpenAFS does read-write replication. People go through the huge
hassle of setting up a cell only to find that AFS does not replicate RW.
That being said, I do not know how to put in a good way a list of things
that AFS does not support. Especially for a pamphlet.

Probably would be good to get some space on the pamphlets for sponsors
to cover printing costs. Assuming there are companies that would want
to cover printing costs.

A list of things in AFS that are anonymously accessible (and that people
would care about) might be good.

Post by Esther Filderman
--- FWIW, I also continue to take swipes at the FAQ section of the
Wiki. The grand plan there is to eventually have a new "one shot" FAQ
that can be quickly read & posted places. It's definitely waay too
much for the pamphlet.

http://grand.central.org/twiki/bin/view/AFSLore/WebHome states that the
wiki is down. (The links from http://grand.central.org point here.)

Is http://www.dementia.org/twiki/bin/view/AFSLore/ the correct, official
location? I don't supose that something simple like
http://wiki.openafs.org could redirect to there? Or even
http://www.openafs.org/wiki ?

<<CDC

[Esther Filderman]

Post by Christopher D. Clausen
Some of the most common questions on #openafs involve people assuming
that OpenAFS does read-write replication. People go through the huge
hassle of setting up a cell only to find that AFS does not replicate RW.
That being said, I do not know how to put in a good way a list of things
that AFS does not support. Especially for a pamphlet.

I always say "Replication of non-static data" or "non-volitile data"
but perhaps that's too... advanced? for PR blather. Hrm. Will
ponder this.

Post by Christopher D. Clausen
Probably would be good to get some space on the pamphlets for sponsors
to cover printing costs. Assuming there are companies that would want
to cover printing costs.

I hadn't thought of this; I expect the cost or printing the pamphlets
to be less than printing the "quick ref" cards. But I'm probably
wrong and they'll both be $$$. But I bet I can find sponsors, between
SNA, AC&NC, Teradactyl, etc....

Post by Christopher D. Clausen
A list of things in AFS that are anonymously accessible (and that people
would care about) might be good.

Huh. Like?

Post by Christopher D. Clausen
Is http://www.dementia.org/twiki/bin/view/AFSLore/ the correct, official
location? I don't supose that something simple like
http://wiki.openafs.org could redirect to there? Or even
http://www.openafs.org/wiki ?

The short answer to the longer story [i'll tell you on IRC] is that it
"should be moved back into openafs.org land any time now."

And tomorrow I'll wake up with a supermodel's body. *cough*. Ahem. Sorry.
I'll beat jhutz up about this some more.

[Jason Edgecombe]

Post by Esther Filderman
--- I started working on a PR pamphlet for OpenAFS. The idea is
that if we ever have a booth at a conference or somesuch (like, say,
the upcoming Ohio Linux Fest, or even SCALE), we can have something
informative to pass out.
The pamphlet is your standard six section foldout thingy. Right now I've got
- the cover
- "Who uses OpenAFS?" [which I'll make sure to get permission from
the places before I use 'em; right now I have placeholders]
- "Why Use OpenAFS?" [two sections, because I found that one section
just didn't work right]
That's 4 out of 6. Ideas for the other two?
Remember that it needs to be general, yet informative. We don't want
to overwhelm folks.
I'll try to send along my in-progress mess asap.
--- FWIW, I also continue to take swipes at the FAQ section of the
Wiki. The grand plan there is to eventually have a new "one shot" FAQ
that can be quickly read & posted places. It's definitely waay too
much for the pamphlet.
--- Also, BTW, I am specifically posting this here and *not* to -info
because a) this is the right crowd to talk about wording 'n' at and b)
I'd prefer the help from a smaller, more focused group of people.
OpenAFS
The Best Cross Platform,
Open Source, Secure,
Distributed Filesystem
I'm open to ideas on how to change that, or what to change it to.
Even better, I'd like to come up with something that we can then shove
at the Elders and say, "We recommend this be used in general for a
slogan/mantra/whatever."
[&, yes, I do realize that at least 3 of the Elders are reading this
list. So there.]
Thanks, folks!
_______________________________________________
OpenAFS-doc mailing list
https://lists.openafs.org/mailman/listinfo/openafs-doc

Please include which platforms we have clients and servers for. OpenAFS
has got to be the most cross-platform network filesystem next to smb.

Jason

[Esther Filderman]

Post by Jason Edgecombe
Please include which platforms we have clients and servers for. OpenAFS
has got to be the most cross-platform network filesystem next to smb.

Got it. Also that a server can "run on Windows, MacOSX, and most any
Unix or Linux platform".

Thanks!

[Jason Edgecombe]

Post by Esther Filderman

Post by Jason Edgecombe
Please include which platforms we have clients and servers for. OpenAFS
has got to be the most cross-platform network filesystem next to smb.

Got it. Also that a server can "run on Windows, MacOSX, and most any
Unix or Linux platform".
Thanks!

Don't say an FAS server can run on windows. The windows server isn't
stable or well maintained.
but we have clients for nearly every OS

Jason

[Lars Wilke]

Post by Esther Filderman
--- I started working on a PR pamphlet for OpenAFS. The idea is
that if we ever have a booth at a conference or somesuch (like, say,
the upcoming Ohio Linux Fest, or even SCALE), we can have something
informative to pass out.
The pamphlet is your standard six section foldout thingy. Right now I've got
- the cover
- "Who uses OpenAFS?" [which I'll make sure to get permission from
the places before I use 'em; right now I have placeholders]
- "Why Use OpenAFS?" [two sections, because I found that one section
just didn't work right]
That's 4 out of 6. Ideas for the other two?

What about the last page for addresses, URLs etc.

For the RW Replication thing, instead of saying AFS does not do this, one
could write: Does RO Replication to spread load or something like that.

cheers

--lars

[Jeffrey Altman]

Post by Lars Wilke
For the RW Replication thing, instead of saying AFS does not do this, one
could write: Does RO Replication to spread load or something like that.

Lars has the right idea. Avoid the use of negatives. Explain how AFS
can supplement existing file system deployments. Highlight AFS'
strengths by describing three or four deployment scenarios that AFS
excels at.

* Federated WAN access to read-write data from heterogeneous clients
(Windows, MacOS X, Linux, Solaris, HP-UX, AIX, BSD, ...) for the purpose
of collaboration.

* Dynamic demand driven content distribution to web servers via the use
of the AFS client's cache.

* The use of @sys and mount points to read only volumes to distribute
platform specific content and deploy new versions without disturbing
running applications. (use new volumes for each software release)

and don't forget to mention somewhere:

* The ability to use volume management to complete planned system
maintenance without incurring downtime for end users.

...

[Esther Filderman]

Post by Jeffrey Altman
Lars has the right idea. Avoid the use of negatives. Explain how AFS
can supplement existing file system deployments. Highlight AFS'
strengths by describing three or four deployment scenarios that AFS
excels at.

Agreed.

Post by Jeffrey Altman
* Federated WAN access to read-write data from heterogeneous clients
(Windows, MacOS X, Linux, Solaris, HP-UX, AIX, BSD, ...) for the purpose
of collaboration.

oooh, collaboration is a good buzzword.

Post by Jeffrey Altman
* Dynamic demand driven content distribution to web servers via the use
of the AFS client's cache.

another good one

Post by Jeffrey Altman
platform specific content and deploy new versions without disturbing
running applications. (use new volumes for each software release)

Oh yeah, software releasing!

Post by Jeffrey Altman
* The ability to use volume management to complete planned system
maintenance without incurring downtime for end users.

That one I already have.

thanks!

e.

[Jason Edgecombe]

Post by Esther Filderman

Post by Jeffrey Altman
Lars has the right idea. Avoid the use of negatives. Explain how AFS
can supplement existing file system deployments. Highlight AFS'
strengths by describing three or four deployment scenarios that AFS
excels at.

Agreed.

Post by Jeffrey Altman
* Federated WAN access to read-write data from heterogeneous clients
(Windows, MacOS X, Linux, Solaris, HP-UX, AIX, BSD, ...) for the purpose
of collaboration.

oooh, collaboration is a good buzzword.

Post by Jeffrey Altman
* Dynamic demand driven content distribution to web servers via the use
of the AFS client's cache.

another good one

Post by Jeffrey Altman
platform specific content and deploy new versions without disturbing
running applications. (use new volumes for each software release)

Oh yeah, software releasing!

Post by Jeffrey Altman
* The ability to use volume management to complete planned system
maintenance without incurring downtime for end users.

That one I already have.
thanks!

hmmm, it comes with an integrated backup system?

Jason

[Jeffrey Altman]

Post by Jason Edgecombe
hmmm, it comes with an integrated backup system?

not exactly one of AFS' strong points.

[Russ Allbery]

Post by Jason Edgecombe
hmmm, it comes with an integrated backup system?

I'm not sure the values of "integrated" and "backup" for buserver are
sufficiently large that we'd want to draw a lot of attention to it. :)

[Jason Edgecombe]

Post by Russ Allbery

Post by Jason Edgecombe
hmmm, it comes with an integrated backup system?

I'm not sure the values of "integrated" and "backup" for buserver are
sufficiently large that we'd want to draw a lot of attention to it. :)

ok.

Jason

[chas williams - CONTRACTOR]

Post by Jason Edgecombe
Please include which platforms we have clients and servers for. OpenAFS
has got to be the most cross-platform network filesystem next to smb.

well, i think nfs might have the edge there actually.