3:39 p.m.
There are many ways to introduce Fedora Core so I am asking for
suggestions on how best to do so, I want to do it so it's not too dry
or too "Microsoft"-like, somewhere in-between is what I had in mind
with a funny Dilbert-style image on the front. What is the best FC-
supported Screen Capture Tool so I can provide the Opening Desktop
Screen of FC6? Based upon what I write
for the Introduction, what would be an appropriate Conclusion?
I would like to strongly suggest that fedoraforum.org be the
unofficial Fedora Handbook site where all the Fedora web sites submit
"How-tos" and Solutions into one single forum known as "The Fedora
Handbook." The purpose of this is for those who aren't busy on the
Documentation Project gather what has already been written and have
it combined on the fedoraforum "Handbook" Site and once that is
successful, someone or some team will have a completed PDF ready 3
months before the next FC release. It is just a suggestion, nothing
more....
Mark McLaughlin - marknetproductionsentrance.blogspot.com
4:39 p.m.
On Sun, 2006-10-08 at 16:39 -0400, Markus McLaughlin wrote:
There are many ways to introduce Fedora Core so I am asking for
suggestions on how best to do so, I want to do it so it's not too dry
or too "Microsoft"-like, somewhere in-between is what I had in mind
with a funny Dilbert-style image on the front. What is the best FC-
supported Screen Capture Tool so I can provide the Opening Desktop
Screen of FC6? Based upon what I write
for the Introduction, what would be an appropriate Conclusion?
You can get screencaps by using PrtSc on your keyboard, or Alt+PrtSc to
get just a single (current) running application window. The GConf
key /apps/gnome-screenshot/include_border (a boolean) will allow you to
choose whether you want window decoration in the latter case.
I would like to strongly suggest that fedoraforum.org be the
unofficial Fedora Handbook site where all the Fedora web sites submit
"How-tos" and Solutions into one single forum known as "The Fedora
Handbook." The purpose of this is for those who aren't busy on the
Documentation Project gather what has already been written and have
it combined on the fedoraforum "Handbook" Site and once that is
successful, someone or some team will have a completed PDF ready 3
months before the next FC release. It is just a suggestion, nothing
more....
I vehemently disagree. The whole point of the existing Docs space on
the wiki, and the CVS repository for the FDP, is to gather these
materials. Putting them elsewhere causes unnecessary process
fragmentation and a drain on already scarce resources. We are trying to
bring more people *into* the FDP, so the best way to do that is to
encourage them to use our existing resources here. Licensing and
maintaining overall project standards is also a concern.
We have a really big tent here, with plenty of ice-cold lemonade, water,
cookies, and BBQ for all. Let's try to make use of what we have first!
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Project Board: http://fedoraproject.org/wiki/Board
Fedora Docs Project: http://fedoraproject.org/wiki/DocsProject
5:03 p.m.
On Sun, 2006-10-08 at 17:39 -0400, Paul W. Frields wrote:
On Sun, 2006-10-08 at 16:39 -0400, Markus McLaughlin wrote:
> I would like to strongly suggest that fedoraforum.org be the
> unofficial Fedora Handbook site where all the Fedora web sites submit
> "How-tos" and Solutions into one single forum known as "The Fedora
> Handbook." The purpose of this is for those who aren't busy on the
> Documentation Project gather what has already been written and have
> it combined on the fedoraforum "Handbook" Site and once that is
> successful, someone or some team will have a completed PDF ready 3
> months before the next FC release. It is just a suggestion, nothing
> more....
I vehemently disagree. ...
I agree with your disagreement, but I will add some additional notes
that address the future of possibilities.
* Some people are not going to work on the formal Fedora Project, for
any number of reasons
* Our processes and tools should be exportable and usable outside of the
Fedora Project
The Fedora Unity project exemplifies this. They have licensing and
tools that are the same as Fedora Project, so any content they produce
can be easily shifted into formal Fedora space. *And* vice-versa, they
can receive anything from formal Fedora space.
Fedora Extras has this potential for outside groups to maintain their
own build systems that mirror the FE systems, making it easier to
migrate packages and patches and such between systems.
I would like to see us move toward being able to share content across
the formal and informal Fedora spaces. That is something we can work
toward. In the meantime, as Paul says, if we want to get something done
currently, it is probably best to have all the work happen under one
umbrella. Please. :)
- Karsten
--
Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
5:12 p.m.
On Sun, 2006-10-08 at 16:39 -0400, Markus McLaughlin wrote:
There are many ways to introduce Fedora Core so I am asking for
suggestions on how best to do so, I want to do it so it's not too dry
or too "Microsoft"-like, somewhere in-between is what I had in mind
with a funny Dilbert-style image on the front.
Agreed that we want to strike a tone that is neither too formal nor too
informal. Writing that is too casual causes distrust in the reader.
Too formal doesn't sound human ... although it does translate easier!
For you, I'd recommend trying for slightly more formality, and see how
that sounds. Try to avoid the second-person pronoun, especially where
it forces you to add extra words:
"You can right-click on the desktop background to get a context
menu ..."
"Right-click on the desktop background to get a context menu ..."
The second is more directive, which is reassuring. It shows what is
happening right in front of the user, rather than what "will happen" or
what "can happen".
The Introduction, being not about how-to fare but more what-is, do some
exploring and see what sounds right, and we can iterate from there.
What is the best FC-
supported Screen Capture Tool so I can provide the Opening Desktop
Screen of FC6? Based upon what I write
for the Introduction, what would be an appropriate Conclusion?
Perhaps we should base an answer to that on what you actually do write?
I would like to strongly suggest that fedoraforum.org be the
unofficial Fedora Handbook site where all the Fedora web sites submit
"How-tos" and Solutions into one single forum known as "The Fedora
Handbook." The purpose of this is for those who aren't busy on the
Documentation Project gather what has already been written and have
it combined on the fedoraforum "Handbook" Site and once that is
successful, someone or some team will have a completed PDF ready 3
months before the next FC release. It is just a suggestion, nothing
more....
I think you can follow the same theory, just do it on the
fedoraproject.org Wiki instead, such as in the Docs/Drafts/Handbook
namespace. The GUI editor in the upcoming update for the Wiki is going
to make it as easy to edit as the fedoraforum.org editor.
The advantage here is that we have tools and processes for converting
from the Wiki into DocBook XML. We need that XML to get translated and
output multiple formats such as HTML, PDF, RTF, TXT, Braille, etc. :)
Another advantage is that many of us watch the changes in the Wiki.
Editors can help get on top of style changes and suggestions early. A
forum is not conducive to editing and change tracking the way a Wiki is.
cheers - Karsten
--
Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
5:24 p.m.
O/H Karsten Wade έγραψε:
On Sun, 2006-10-08 at 16:39 -0400, Markus McLaughlin wrote:
> There are many ways to introduce Fedora Core so I am asking for
> suggestions on how best to do so, I want to do it so it's not too dry
> or too "Microsoft"-like, somewhere in-between is what I had in mind
> with a funny Dilbert-style image on the front.
Agreed that we want to strike a tone that is neither too formal nor too
informal. Writing that is too casual causes distrust in the reader.
Too formal doesn't sound human ... although it does translate easier!
For you, I'd recommend trying for slightly more formality, and see how
that sounds. Try to avoid the second-person pronoun, especially where
it forces you to add extra words:
"You can right-click on the desktop background to get a context
menu ..."
"Right-click on the desktop background to get a context menu ..."
The second is more directive, which is reassuring. It shows what is
happening right in front of the user, rather than what "will happen" or
what "can happen".
The Introduction, being not about how-to fare but more what-is, do some
exploring and see what sounds right, and we can iterate from there.
> What is the best FC-
> supported Screen Capture Tool so I can provide the Opening Desktop
> Screen of FC6? Based upon what I write
> for the Introduction, what would be an appropriate Conclusion?
Perhaps we should base an answer to that on what you actually do write?
> I would like to strongly suggest that fedoraforum.org be the
> unofficial Fedora Handbook site where all the Fedora web sites submit
> "How-tos" and Solutions into one single forum known as "The Fedora
> Handbook." The purpose of this is for those who aren't busy on the
> Documentation Project gather what has already been written and have
> it combined on the fedoraforum "Handbook" Site and once that is
> successful, someone or some team will have a completed PDF ready 3
> months before the next FC release. It is just a suggestion, nothing
> more....
I think you can follow the same theory, just do it on the
fedoraproject.org Wiki instead, such as in the Docs/Drafts/Handbook
namespace. The GUI editor in the upcoming update for the Wiki is going
to make it as easy to edit as the fedoraforum.org editor.
The advantage here is that we have tools and processes for converting
from the Wiki into DocBook XML. We need that XML to get translated and
output multiple formats such as HTML, PDF, RTF, TXT, Braille, etc. :)
Another advantage is that many of us watch the changes in the Wiki.
Editors can help get on top of style changes and suggestions early. A
forum is not conducive to editing and change tracking the way a Wiki is.
+1 to all points Karsten and Paul raised.
You will be *amazed* on how much the docs guys will help you when you get this
started. Trust me, I've been there and these guys rock.
If you feel `Docs/Drafts/Handbook` is too formal/watched for your draft ideas,
you could put them into your own wiki space, under `MarkusMcLaughlin/DocIdeas`
for example and move it into the Docs space when and if you feel so.
-d
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
6:12 p.m.
Dimitris Glezos wrote:
O/H Karsten Wade έγραψε:
>On Sun, 2006-10-08 at 16:39 -0400, Markus McLaughlin wrote:
>
>
>>There are many ways to introduce Fedora Core so I am asking for
>>suggestions on how best to do so, I want to do it so it's not too dry
>>or too "Microsoft"-like, somewhere in-between is what I had in mind
>>with a funny Dilbert-style image on the front.
>>
>>
>Agreed that we want to strike a tone that is neither too formal nor too
>informal. Writing that is too casual causes distrust in the reader.
>Too formal doesn't sound human ... although it does translate easier!
>
>For you, I'd recommend trying for slightly more formality, and see how
>that sounds. Try to avoid the second-person pronoun, especially where
>it forces you to add extra words:
>
>"You can right-click on the desktop background to get a context
>menu ..."
>"Right-click on the desktop background to get a context menu ..."
>
>The second is more directive, which is reassuring. It shows what is
>happening right in front of the user, rather than what "will happen" or
>what "can happen".
>
>The Introduction, being not about how-to fare but more what-is, do some
>exploring and see what sounds right, and we can iterate from there.
>
>
>
>>What is the best FC-
>>supported Screen Capture Tool so I can provide the Opening Desktop
>>Screen of FC6? Based upon what I write
>>for the Introduction, what would be an appropriate Conclusion?
>>
>>
>Perhaps we should base an answer to that on what you actually do write?
>
>
>
>>I would like to strongly suggest that fedoraforum.org be the
>>unofficial Fedora Handbook site where all the Fedora web sites submit
>>"How-tos" and Solutions into one single forum known as "The Fedora
>>Handbook." The purpose of this is for those who aren't busy on the
>>Documentation Project gather what has already been written and have
>>it combined on the fedoraforum "Handbook" Site and once that is
>>successful, someone or some team will have a completed PDF ready 3
>>months before the next FC release. It is just a suggestion, nothing
>>more....
>>
>>
>I think you can follow the same theory, just do it on the
>fedoraproject.org Wiki instead, such as in the Docs/Drafts/Handbook
>namespace. The GUI editor in the upcoming update for the Wiki is going
>to make it as easy to edit as the fedoraforum.org editor.
>
>The advantage here is that we have tools and processes for converting
>from the Wiki into DocBook XML. We need that XML to get translated and
>output multiple formats such as HTML, PDF, RTF, TXT, Braille, etc. :)
>
>Another advantage is that many of us watch the changes in the Wiki.
>Editors can help get on top of style changes and suggestions early. A
>forum is not conducive to editing and change tracking the way a Wiki is.
>
>
+1 to all points Karsten and Paul raised.
You will be *amazed* on how much the docs guys will help you when you get this
started. Trust me, I've been there and these guys rock.
If you feel `Docs/Drafts/Handbook` is too formal/watched for your draft ideas,
you could put them into your own wiki space, under `MarkusMcLaughlin/DocIdeas`
for example and move it into the Docs space when and if you feel so.
-d
Take a look at "The Complete PD Maintenance Guide" by Mark Minasi for an
example of good writing.
I got it when I had to fix my first computer. It's about 1500 pages
long. I read straight thru it. It was a good read. It covered just about
everything. To bad Minasi does not write Linux stuff.
6410
days inactive
6410
days old
5 comments
5 participants
participants (5)
-
Dimitris Glezos -
Karsten Wade -
Markus McLaughlin -
Paul W. Frields -
Thomas w. Cranston