Fwd: [gnome-women] Fwd: GNOME Journal Issue 17 Status Updates Needed (And Editors Wanted!)

---------- Forwarded message ----------
From: Cathy <cathy zareason com>
Date: Wed, Nov 4, 2009 at 5:50 PM
Subject: Re: [gnome-women] Fwd: GNOME Journal Issue 17 Status Updates Needed (And Editors Wanted!)
To: Stormy Peters <stormy gnome org>


Here you go! Thanks for asking me to do this.

I have a few photos to send later tonight if they are useful.

--Cathy Malmrose

On Fri, Oct 23, 2009 at 3:42 PM, Stormy Peters <stormy gnome org> wrote:
Hi Cathy,

The writing guidelines are here, http://live.gnome.org/GnomeJournal, and I included them below. Articles are due on Nov 1.

Thanks for the update on Kory's project. We have several schools that want the computers!


Writing guidelines

Write more than 750 words (which is a little bit too short) and less than 2000 (a little bit too long). In between 1000 to 1750 words is fine.

The usual rules apply. For a good overview, see The Elements of Style. In particular, don't use 'is' if you can replace it by 'does' ('acts', 'uses', 'handles' etc.).


Submit simple ASCII texts; no OpenOffice.org documents, and no Word documents ('shudder'). Use 'Textile' as a mark-up language if possible. You can learn it by using Textism. Please DO NOT include line breaks in your documents except at paragraph breaks. The text needs to be able to wrap naturally in HTML.

Don't embed images into the text. Sent them seperately with a link in the text. Use PNG as a format. For images larger than 400x120, make a thumbnail - not a resized/resampled version but a cropped one of the most important details.


  1. If you're unsure if your article idea will fit into the GNOME Journal, ask on our mailing list. You can sent messages to the list, even if you're not a member, but it may take a day until it appears in the archives. You can also email to the release coordinator or the editor-in-chief.
  2. If your idea fits into the GNOME Journal, start writing! Please add an entry in the /ArticleSubmissionQueue .

  3. After you've finished your article, check the spelling with gEdit (American English). Additionally, have it proof-read by somebody else if possible. Don't worry if English is not your primary language! Ask on the mailing list for a native speaker. If this fails, our editor will proof-read the article.
  4. Submit your article to the release coordinator or the editor-in-chief.
  5. The release coordinator uploads the article to the CMS, and updates your article status.
  6. Editors check for correct spelling, grammar, and possible errors. If extended changes are necessary because content is difficult to understand, a corrected version of the article will be sent back to the author for approval.
  7. When the release date is due, the edition/issue will be published.

On Fri, Oct 23, 2009 at 10:40 AM, Cathy <cathy zareason com> wrote:
Thanks Stormy! This article has been a *delight* to write.

What day is the article due next week?

Word count?

I must have missed the specs...

Also, an update on Tech Transfer project (that's you, right?), Kory & his team are doing their first step this weekend, getting the computers from KIPP in SF and bringing them to the shop for some fun fixing.

--Cathy Malmrose

On Fri, Oct 23, 2009 at 6:59 AM, Stormy Peters <stormy gnome org> wrote:
It's time! We are on for our GNOME Journal articles - they are due next week. The GNOME Journal team will help edit them.

Let me know if you need any help.



---------- Forwarded message ----------
From: Paul Cutler <pcutler gnome org>
Date: Fri, Oct 23, 2009 at 8:33 AM
Subject: GNOME Journal Issue 17 Status Updates Needed (And Editors Wanted!)

Hi GNOME Journal and GNOME Women team!

GNOME Journal Issue 17 (Women in GNOME) is one week away from articles being due!  I just wanted to check-in and see how the articles are coming.  Articles are due 11/1 and editors will a week to ten days to review and then we have a few days for formatting in our CMS.

We'll also need a handful of editors to review the articles, including structure, grammar and spelling.  Our editors work with the writers and ask questions for clarity.

I'm very excited about this issue and if anyone has any questions, please let me know.



PS - Stormy or Marina - if any of the writers are not subscribed to the GNOME Women list can you please forward?  Thanks!

gnome-women-list mailing list
gnome-women-list mail gnome org

The Un-Scary Screwdriver

One early spring day, as we were walking home from the bakery on the corner, we passed by a neighbor and struck up a conversation. He complained about his desktop being constantly attacked by viruses. We suggested Ubuntu. As a professional man in his 50s, he said he wanted to try installing a Linux distro on his desktop but that, “it looks too complicated. I probably couldn't install Ubuntu. I don't want the hassle.”

My little five year old daughter had been snuggled in my arms while I was talking to this neighbor. She had been listening closely. When we got home, she said, “Mom, I can install Ubuntu. I bet I can. Can I try? Can I try?” 

As a mother who wants to foster her children's interests in all things technical and scientific, I dropped the loaf of french bread and turned on a nearby desktop. I did a quick back-up and wiped the system. I handed my daughter, Anna, an install CD and said, “Here you go.”

Then I walked away. 

From the kitchen, I watched the install unfold. She insert the CD. She read what she could on-screen and pressed Enter a lot. When she couldn't read something, she called her brother who was only one year older, but who could read a few more words than she could. She yelled, “Jake! Come here and tell me what this says!” Together they figured out, “Hey, if you just press Enter, it usually works out fine.” 

With a little bit of help from her six year old brother, Anna successfully installed Ubuntu on a desktop. When she was done, I came in and asked, while trying to squelch my pride, “So, sweetie, how did it go?” 

Anna's reply, “Easy baceasy! That old foggy is just being silly. I can install Ubuntu, so he can install it too.” 

We have had many similar experiences of successful interaction between little kids and software that is well built. The most recent experience was sparked when we noticed far too many small form factor desktops accumulating in our aptly named, “We don't want it; you want it?” pile at our computer shop, ZaReason. We had not had time to do a run to the local electronics recycling center so we called a few friends to clear out some hardware and we set up two projects to clean out a few of the nicest desktops. 

A little background: My parents are in the generation where we hear questions such as “Where's the On button?” and, “Oh, those newfangled computers are just too complicated.” Still, my parents are gutsy enough and smart enough to try new things. They also have endurance and persistence. They have had a few brief introductions to Linux, but none of them stellar. 

Recently, my dad has been putting in the hours to preserve family home videos, and called me one day asking for advice for which new desktop he could buy. Since I had been staring down a pile of excess, but still quite usable hardware, I asked my dad, “Hey, can you wait a few weeks and your granddaughter will build you a desktop that will be ideal for video editing?” The reply was a supportive, loving, “Sure!” It was such a pleasing thought to me in particular, that my parents would be the only ones on their block with a desktop built by their little granddaughter. I hoped they would have many good laughs about it with their friends.

Since there were plenty of small form factor desktop cases and plenty of components, I asked Anna if she wanted to have a building party with a friend. One Saturday, her friend Tora came to our little shop and the dads worked alongside their daughters with each father-daughter team assembling their own desktop. The girls had an interesting way of building. It went like this: 

Anna finds two screwdrivers, hands one to Tora. 

They both look for something to unscrew. They get the screws off then wiggle the case off. The dads have to help with sliding the case off. 

The girls run around for a few minutes talking about how, “I opened it up and we can see its guts!” After they calmed down again, they came back to the table and asked, “What's next?” 

The dads, being the awesome teachers they are, said, “I don't know. What do you think is next?” 

The girls put in the memory sticks, then did somersaults. 

They did the goo on their CPUs, seated them, then spun around on the office chairs until they were sickeningly dizzy. 

They put their fans in place, then ran around for a bit. 

Tora had question after question. “What's this? What does it do? Why do we need this? Why is that metal thingy there? Is it ok if I touch these spikies?” 

The most interesting aspect of the build was that the girls seemed to have an innate understanding of the hardware that was a level higher than what I had anticipated. They had so much fun building these desktops that they decided to keep them for themselves. 

We invited over another friend, Lizzie, for another build session, hoping that this time the desktop would go to Grandma and Grandpa. The build session was similar except that Lizzie was focused and did not take breaks between components. She talked the entire time. The girls also focused on only one computer at a time. Lizzie built hers first with Anna helping and watching, then Anna built hers with Lizzie helping and watching.

These two girls' determined focus was balanced by a sweet team-building camaraderie. They were doing each build on a child-height blue IKEA table in the middle of our shop with a massive overhead skylight providing sweet sunlight on their work station. One parent was sitting nearby and another was working over on a different table. The girls worked with a minimal amount of adult direction. 

I was in the upper level loft helping my eldest son with his college application, so I had a bird's eye view of the experience. I could hear their soft voices saying, “Here Lizzie... yeah... you got it!” and “Anna, do you have an extra screw for this? The case was missing one#.” Every time I peeked over the loft ledge, I could see them sitting beside each other, working as partners. It wasn't like they were drawing together or doing other types of work together. They were interacting as if they were co-painting a canvas together.

For both builds, the girls lost interest during the software install. It was too easy. They went on to playing and running around the shop. For each of the builds, a fully functional desktop was “born” to live another full life in a new home. For all three girls, they now understand that if there is a problem with their desktop, they can open it up and replace a part. They are empowered to fix it themselves. 

We have enjoyed the delightful payoff for providing this type of opportunity for people of all ages. When you open a desktop, you realize that the internals are not scary. You have a greater appreciation for keeping the components healthy. Try opening a system that has been working without being cleaned for three or four years and you'll find enough dust to make you shudder. Once you see that the insides need care, just like the insides of a human body, an automobile, even the inside of a house, you have a greater appreciation for the functionality of the desktop. 

As I write this article, my daughter is home sick. She is watching Pink Panther on Hulu, using a desktop that has a failing hard drive. Several times, she started up the system only to see “Disk Boot Failure”. Soon, she will probably ask, “Mom, what does this mean?” and rather than rebooting until it starts properly, she will think, “Hey, I can replace the hard drive. Myself.” I am curious to see how long it takes before she seeks out a screwdriver and asks, “Hey, mom, do you have an extra hard drive I can use?”

There are many natural ways to take away the scary factor from computing. The more we can present various Linux distros as being “easy” and “workable” the more we can reduce stress in computing with those we love. 

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]