Table of Contents is DONE! and other Sprint News

In spite of spotty internet connections and wiki timeouts, the Amarok Handbook Table of Contents is done! Eternal thanks to Myriam for her help learning how to move the pages, and to the rest of the team for working out the best order for the pages. Moving the pages is a bit complicated, so if you are using Userbase, try to get your pages in the order you will want them! The Kdenlive team has already posted their QuickStart Guide, so they are well on the way to documenting their excellent application. KMix is next. Right, Christian?

Of course I still need to check the Amarok pages for the proper progress information. That shouldn't take long, and I should have it done within the week -- maybe sooner.

In non-documentation news, we had a good community-building meeting. Unfortunately none of us were quite ready, but we covered all the ground anyway, I think.

My Pictures, and Trever's pictures.

Also, the biscotti were a huge hit! Most were gone the first day. Well worth the space in my luggage. :-)

Rsync and Backup Success

A blog post started long ago, back in Oct. 2010:

If you are a reader of my blog, you might have suffered along with me through a non-existent backup. Tomorrow, I'm setting off for UDS in Orlando, Florida, and I wanted to be sure to have an up-to-date backup. So I started up my 1.5 T backup, newly formatted, and looked up a reliable article about using rsync. No more relying on GUI front-ends to it! I wanted to use it direct from the command-line, so I could see the errors right away. http://www.linux.com/news/enterprise/storage/8200-back-up-like-an-expert-with-rsync is simple and understandable, even for me. "The basic syntax for rsync is simple enough -- just run rsync [options] source destination to copy the file or files provided as the source argument to the destination."

Written in the now:

Unfortunately, I didn't finish this blog post after returning from Florida, but today a major disaster became a minor disaster by means of 1. a small screwdriver, 2. an inexpensive disk drive enclosure ($14.99 at Fry's), and 3. this simple command:

rsync -av /media/home/valorie/Music /home/valorie/Music

Disaster was my laptop power supply dying on me, without a recent backup. I know, shame on me! Instead, I used the screwdriver to take out the hard drive and attempted to put it into the HD enclosure I already have. However, it didn't fit. So I wrapped up the HD securely, and made a trip to Fry's. I showed the salesman the drive, to ensure I got the right kind of enclosure (SATA).

Once home, I put the drive into the enclosure, hooked it up to my netbook (thanks, ZaReason!) and began transferring my music from my old laptop to my new one, while continuing to work on the Amarok Handbook, which is *almost done*! I took the opportunity of a freshly installed Amarok to make some screenshots with which to finish the book! http://userbase.kde.org/Amarok/Manual

An update: One trouble I've had, besides some error messages that Sre-su helped me to figure out (thank you again, Sre-su!), is that the drive kept un-mounting. I don't know why -- bad USB connection, bad enclosure, bad HD -- but the solution is to just run the command again. Rsync checks the files it has already done, and then just charges ahead. I added -r (recursive) to be sure all music files were copied, and --progress so I can see at a glance what is going on. Also, --dry-run is cool -- it shows you what will happen, quick as a flash. Also, sre-su pointed out that I needed sudo before the command, which is now:

sudo rsync -avr --progress /media/home/valorie/Music /home/Music

I didn't catch my error in the above command until today, when I wondered why my music was STILL not in my Amarok collection! What must have happened is that while my original command was correct, the USB drive is touchy, and I needed to run it a few times. Not knowing this, I changed it, and put my Music not in /home/valorie/Music where it belongs, but in /home/Music/. Bleah.

Proper command, after all, is:

rsync -avr --progress /media/home/valorie/Music /home/valorie/Music

Amarok Quick Start Guide in Translation

Thanks to the hard work of the wonderful Amarok Promo Team, we now have the beginning of the Amarok Handbook completed, and in the able hands of the KDE Translation team (http://userbase.kde.org/Amarok/QuickStartGuide). It's quite exciting to see the completed pages roll in on #kde-www. Neverdingo has written a wonderful blog post about the procedure: http://neverendingo.blogspot.com/2010/08/amarok-translatons.html. If you love Amarok, and have ever thought about translating, now is the time to step up! This is going from our small team, to the larger team of KDE, and it is thrilling to see.

I guess we did something unusual, beginning our Handbook in the KDE wiki system. I'll have to say that comparing the process to our old way, which was using Google Docs -- it is like night and day. The one advantage of Gdocs is that you can tell who is also editing, and what they are doing, but we got around that, for the most part, by communicating in our IRC channel. There is simply nothing better than seeing your document take place marked up and looking professional! Wiki markup isn't complicated, and the guides (http://userbase.kde.org/EditMarkup and http://userbase.kde.org/Typographical_Guidelines) are easy and helpful to use.

I will never again use Google Docs for more than just text. The wiki rules! Userbase is awesome! Thank you, thank you, KDE.

I understand the next bit of this process is the DocBook markup, which sounds mysterious and scary still, since I don't know much about it. There is a guide to that as well, which I'm sure I'll be consulting often. For now, though, we'll concentrate on finishing the rest of the Handbook, for those who need more detail about the finer points of using the best music program of all time, AMAROK!

Thank you Mamarok, and Willem, Nightrose and Pete, Abhi and Adrián, Emilio and Dima for all your work. You've been GREAT.