usb-creator Draft

Jonathan Jesse jjesse at gmail.com
Mon Aug 10 22:23:20 UTC 2009


Sorry for the top posting but windows phone makes it hard.
Shouldnt this guide become a part of the upstream ie the prokect itself.  Same for usb-creator-kde.  A guide should be uploadeduce as  a part of upstream 

-----Original Message-----
From: Matthew East <mdke at ubuntu.com>
Sent: Sunday, August 09, 2009 6:31 AM
To: Augustina Blair <missaugustina at gmail.com>
Cc: Evan Dandrea <evand at ubuntu.com>; ubuntu-doc <ubuntu-doc at lists.ubuntu.com>
Subject: Re: usb-creator Draft

Hi Augustina,

On Sat, Aug 8, 2009 at 5:43 PM, Augustina Blair<missaugustina at gmail.com> wrote:
>> I've taken the opportunity to make a few relatively small edits to the
>> page in the light of your invitation
>
> I think that flows much better. I tend to over-explain and then whittle
> down. Is the naming convention LiveUSB or Live USB? I think I've seen LiveCD
> as all one word which is why I referred to it as a "LiveUSB".

I don't think either LiveUSB or LiveCD should be a word. I think
someone has got used to writing words like that from the CamelCase
technique used on the wiki and it may have stuck. I'm pretty sure that
they should be two words. Wikipedia agrees:

http://en.wikipedia.org/wiki/Live_CD
http://en.wikipedia.org/wiki/Live_USB

>> What's your plan for the document?
>
> I was under the impression that this was needed for the system docs because
> USB Creator didn't have a help entry. I more than happy to update the
> corresponding wiki page if appropriate. I created a branch in bazaar and
> once the text is approved I can tag it with DocBook and have someone review
> it.

You're definitely right that this is needed for the system docs and to
give the program a help button, but the only question is where we put
it. It can either go in the usb-creator package itself or it can go in
ubuntu-docs. I think it's a definite advantage putting it in
ubuntu-docs because that means that the team can continue to maintain
it and update it as appropriate, and it can take advantage of the
translation system that we use (it's pretty unlikely to attract
translations otherwise).

If we do put it in ubuntu-docs, the question is how it slots in. It
could go in as a separate document, but I'd rather see it as part of
an existing document. For example, the jockey docs are part of the
hardware.xml document found here -
file:///usr/share/gnome/help/hardware/C/hardware.xml#jockey. The only
place that I can think of to include this material is in the new
installation guide.

How and 

[The entire original message is not included]




More information about the ubuntu-doc mailing list