Skip to content

GNOME

Why I enjoy writing user help for GNOME

It’s been almost ten years since I started contributing to open source projects.  One of the big ways I’ve contributed in the past is writing user help.  Not knowing how to code then (and still really don’t know now, as hard as I try to learn Python), writing is something I enjoy and an area where I think I can make a difference.

There are a number of different places to apply a writing skill in open source.  You can write release notes, marketing copy, websites and the help documentation for an application.  Writing user help is one I enjoy.

I want to say that writing help is easy – but what’s easy for me, may not be for others.  Those who write an application might say it is easy for them – but as I’m learning, it’s not easy for me.

You can debate who might want to use a Linux desktop and not use Microsoft Windows or macOS.  To me, there are a few different use cases:

  • Developers.
  • Hobbyists.
  • Users in developing nations.

It’s these last two groups that I think having up to date user help is important. Using a Linux desktop, such as GNOME, can be a big change and paradigm shift for a user.  In developing nations, they may not be able to afford a Windows license or the applications they might want to run on Windows.  For example, Photoshop isn’t cheap – but GIMP is free.  If you’re switching to a new operating system, there may be things you don’t know how to do and if there isn’t user help available, how else are you going to learn?  Especially if you’re an area that might not have good internet access.

But having started to learn to code in the last year, I understand why developers don’t write help.  Even with my terrible skills at writing code, when I’m writing a function in Python, I’m not documenting my code as I should be, much less writing a document about how to use the finished application (if it ever gets finished).  You get in the zone and just write code and tell yourself you’ll get to it later.

But on the other hand, when I start an application and can’t figure out how to do something, my first step is to see if I can figure out how to do it myself.  I’ll check to see if there is help built into the application, if not, I’ll check the website.  Having come back to using GNOME a month ago, I was dismayed to find an application I was excited to use to not have either when I was trying to figure out how to use a feature.  (I won’t shame them publicly, and no, they aren’t an application created by GNOME, it’s an actively developed application available on Github).

Although I’ve been using macOS for the last few years, it’s not as if I stopped using open source.  I have open source applications running on my Macbook, a laptop running Fedora though I didn’t use it much, a server at home also running Fedora, and Digital Ocean droplets running CentOS and Fedora.  I strongly believe in open source and love that it’s powered both by people and companies building software in the open for anyone to use or modify.  And that last sentence is important – if anyone can modify it or make it better, why wouldn’t I help if I have the time and / or the skills?

So I did.  Jumping back in with both feet.  After my wife gave me some feedback on the app I’m building that I needed to re-architect a large part of it, I took a break from it for the last week and wrote user help for two apps in GNOME: Polari, an IRC client, and Recipes, a brand new application that does exactly what you think it does.  I’m even poking around the documentation for Builder, an IDE for building GNOME apps, and editing its developer documentation.  (I won’t even pretend I know how to write developer documentation).  It’s a nice change of pace to use a different part of my brain to write user help while my subconscious figures out how I’m going to fix the data model in my app.

Having been away from the GNOME community for a number of years, I’ve always said the one thing I missed about open source was the people – and it’s been neat to be welcomed back and see some of the same faces.  I love the collaboration.  Maybe someday after I finish my Python webapp I’ll learn GTK and make myself a desktop app out of it.  But let’s not get ahead of myself.

The macOS apps I’ll miss the most

I have been considering switching back to GNOME full-time and finally pulled the trigger last week and did, installing Fedora 25 on both my iMac and MacBook Pro. I installed GNOME on my iMac a couple months ago, but didn’t do the installation correctly and screwed up my MBR, resulting in only GNOME being an option. I’ve fixed that this time and have kept dual boot (for just in case and for iTunes on my iPhone and iPad).

The more I’ve thought about this over the last couple months, the more I have wanted to go back to GNOME. The privacy concerns I have about the big tech companies continues to nag at me and there is something about the open source ethos that appeals to me. I may even switch back to Android from iOS if this works well.

I will still be tied to the Apple ecosystem with my work laptop. That’s both good and bad as I think about the few apps that have held me back from making the switch full time. The only alternative would be to switch to Windows, which is never going to happen. I haven’t used Windows since 2004 and considering what Microsoft has done with tracking in Windows 10…

There are a handful of apps on macOS that just don’t have a Linux equivalent, or if they do, aren’t close from a usability experience. The last three are the big ones for me. I also see the irony in that those three apps are some of most expensive applications I’ve purchased through the Mac App Store. You do get what you pay for and I really shouldn’t be comparing these, especially the last two which Apple has featured as apps of the year previously, to free and open source apps. I should be grateful that there are programmers out in the open source world making applications and offering them without charge rather than trying to compare them to Mac equivalents.

In no particular order, the apps I’ll most the most:

Messages

I love text messaging from my desktop (and the immediacy of the notifications). I’m old, shouting Get Off My Lawn and just don’t like tapping on virtual keyboards compared to a real keyboard hooked up to a computer. But I can live without this.

Status: Can live without this.

Pocket

The web client is pretty good and I’ll probably continue to use the iPad as the primary reading device for Pocket. I can live without this. Firefox has a save to Pocket add-on that works just fine.

Status: Can live without this.

Reeder

Reeder is my RSS reader of choice, and there are a number of RSS readers available on Linux. Feedbin, the replacement service for Google Reader that I pay for annually, also has a decent web interface. New links open in a tab in the browser instead of Reeder’s readability feature. I’ll miss Reeder.

Status: Can live without it.

Update: I’ve found FeedReader in the Fedora 25 repositories. Version 1.6 is in the repo, but the developer has also made a Flatpak available for version 2.0 that was released two days ago and I’m now running. A few thoughts:

  • This has fantastic usability. Almost to the level of Reeder. This is a slam dunk as far as RSS readers go.
  • I installed the Flatpak because version 2.0 adds support for both Feedbin and Pocket as a read it later service. Feedbin suport is working great and after upgrading from the 2.0 beta to 2.0 final, Pocket support is working flawlessly. FeedReader automatically added Pocket as a service since I had it configured in GNOME Online Accounts.
  • A big thank you and shout out to the developers for taking the time to release a Flatpak making it easy for users to upgrade to the latest version.

Updated Status: Found a replacement that is just as good as one of the best Mac apps.

1Password

Considering all the work I did over the Christmas holiday to change weak passwords to strong passwords and removing duplicates, and also the integration with iOS, this is a big loss as there is no Linux client for 1Password. There are a few password management alternatives on Linux, but I don’t know how good they are. Ryan C. Gordon aka icculus did write a 1Password script for Linux that may be worth checking out: https://icculus.org/1pass/

Status: More research needed and may just need to switch to Encryptr or Enpass.

Tweetbot

Ouch. This one hurts. I love Twitter, it’s the only social network I’m active on. I love syncing my Twitter reading experience between all my devices, which Tweetbot does better than any other application out there, regardless of platform or operating system. I’ve installed Corebird on Fedora and it’s ok, but it’s not Tweetbot.

Status: This one hurts. I can probably confine myself to Twitter on iOS and use Pocket to save and read links.

Ulysses

I love, love, love writing in Ulysses. It’s hands down the best writing app I’ve ever used after trying Scrivener, Hemingway and others. The iCloud integration is great, making it easy to jump to and from other devices, including iOS. I am using Ulysses to not only write for my blog and journal (then importing into Day One) but also as an Evernote replacement after Evernote screwed everyone over with their privacy settings (though they would later backtrack, I’ve lost all trust in them). Like most of the great Mac apps, they’re Apple only. If I’m writing anything, I’m always starting in Ulysses.

I’m using Dropbox Paper right now to try it out as a replacement for Ulysses, and while Paper is close, it’s lack of true Markdown support while writing bugs me. It’s not too bad if I open it in its own browser window and then use it in its own workspace – this makes it feel like more of a writing app and not a browser. I’ve spent significant time learning Markdown for both Ulysses and Day One, so Dropbox Paper missing real keyboard shortcuts for Markdown kind of sucks (some work, like strong and italics, but others, like headings, don’t). I’ve installed the Markdown plugin in WordPress, making it easy to copy and paste drafts from Ulysses to my blog or to Day One. It is possible to export Dropbox Paper as Markdown and after a cursory glance there are some decent looking Markdown editors available on Linux, so there may be hope.

Status: Can probably live without it. But I’m not happy about it.

Day One

This is probably the biggest one for me. If I love Ulysses, I love Day One more. And like Ulysses, Day One is exclusively in the Apple ecosystem. Ironically, I don’t write in my journal nearly as much as I should. But I love the integration with IFTTT and use it to track all of my exercise entries from Endomondo. I spent an hour looking at journaling options on Linux last week, and there are a couple, but I don’t see a way to sync the entries between computers, which is a must have feature. One option is to continue to use Day One on my work laptop or use a Markdown editor on Linux, save in Dropbox, and then import. I’ve also come across jrnl, a command line journaling app that says it works with Day One, but I really love the user experience of Day One’s app. This one hurts the most – Day One was one of the first apps I ever bought in the Mac App Store and I have years of journal entries in there.

Status: Ouch. I really don’t want to miss this. I’m not ready to start journaling in another app, so I’ll probably just write drafts in Dropbox Paper and then use my work laptop for journal entries.

Why I’m going back to Linux after five years of using macOS

I’ve been a supporter of the Electronic Frontier Foundation since 2004. Their work on privacy, free expression and technology are all things I am passionate about. For the last year or so, I have become more concerned with privacy issues in technology. The rise in big data and how everything is tracking everything we do has given me significant concerns. I’ve been giving a lot of thought to which ecosystems I want to stay in. I’m not going to say I trust any of these technology companies, but I can control (or minimize) my footprint with some of these companies.

Last year I took a number of steps in this direction:

  • I deleted my Facebook and Instagram accounts. I don’t think I need to go into detail here, but Facebook isn’t something you would ever equate with the word “privacy”.
  • After Evernote said they would access your notes and data (only to backtrack later) I quickly stopped using Evernote.
  • I’m paying cash for most of my personal purchases and now shopping local and not online – even if I have to pay a bit more for things such as records, books or cycling gear.
  • I went through and deleted over a hundred online accounts over the Christmas break and used a password manager to make sure I wasn’t using duplicate passwords online and also that I was using secure passwords.
  • I’m no longer using Flickr (and Yahoo services in general) for my photos and I have a tough decision to make about whether I delete that account and remove access to the photos there. (Wikipedia using a number of my Green Bay Packer photos under a Creative Commons license).
  • I switched to DuckDuckGo instead of Google as my default search engine.
  • As much as I’m intrigued by Amazon’s Alexa and Google Home, I won’t buy a voice activated device. Just think about what data it knows about you – what smart devices in your house, what your saying around it – and the recent story in the news how a police department wants the data scares the shit out of me.
  • I’m not using TouchID on my iOS devices. Courts have ruled multiple times that your fingerprint is not protected under the Fifth Amendment – but a passcode is.

Yes, I sound paranoid. But at the end of the day, this is my decision and my choice. I may not have anything to hide, but I don’t believe just because we have the technology means that it always needs to be used to collect everything about you. While I will never be able to erase everything about me online or with these technology companies – nor would I necessarily want to – I can control with whom I do business and make conscious choices about it. This way I can be eyes wide open that yes, I’ve been using Gmail since it first launched and that Google knows almost everything about me. But that’s my choice to stay within Google’s ecosystem (for now). even if I start to use less of their services, such as switching to DuckDuckGo for internet searches.

I stopped using Microsoft Windows in 2003 when I switched to using Linux full time until about 2012 when I started using macOS after buying my first MacBook. I love Apple’s hardware and I like macOS – the same Unix internals underneath, lots of polish, and excellent apps. Everything just works – you don’t have to fiddle with video card drivers or wireless. But you will have to do things the way Apple wants you to (see: iTunes). Integreation with iOS is great – answer phone calls on your Mac, reply to text messages. But who knows what Apple is tracking as well as the apps you’re using (I’m looking at you Evernote). And don’t get me started on the Touch Bar on the new MacBooks. (No Escape key? Really?)

So I’m going back to using Linux on the desktop after five+ years away. There is no question that the macOS user experience is significantly better. But using the GNOME desktop on Fedora is pretty close and gets better every release. I’ll know my computing experience is secure and private. I’ll probably share some thoughts on what key applications I’ll miss most in a separate blog post. I’ll still need to use macOS at my day job, but I can control what I use at home and have the peace of mind that nothing is tracking me (outside of what’s in my web browser) when using my own computers.

How I Got Started Programming

As I attempt to learn Python, I’m fascinated by how people are able to do this as well as how they started to learn to program.

I’m not the only one, as Ryan Gordon (aka Icculus), a well known game developer who ports many games to Linux and Mac, asked a similar question on Twitter last month.

This led to a lot of interesting tweets and Ryan created a Storify page to share them. Josh “Cheeseness” Bush wrote up a great analysis of those tweets sharing graphs looking at the languages, hardware and more about the people who replied used to get started with programming.

Even though I’m just starting to formally learn to code now, my story with computers is similar to a lot of those stories.

It all started in the early 80s when my father bought a Timex Sinclair TS1000 (aka ZX81) and then a TS1500.  You could load games via tape and also buy magazines with the code to program your own games.  I spent hours handtyping machine code to create games like Breakout.

A few years later my father bought an Apple //c and I then learned Logo, Basic and others.  Nothing that I ever really stuck with from a programming stand point, but enough to learn the basics and spend hours tinkering.

After that, my father bought a an IBM clone 286.  I remember being at Sears with him and telling him to spend the extra money to get a 386, but even a 286 was at least $2,000 back then.  I remember it ran GeOS for a graphical interface and one Christmas, after I received the original Wing Comannder as a gift, I had to buy MS-DOS 5 just so I could use the himem.sys to have enough memory to run the game.

From the Apple //c on, we always had a modem as well.  Starting with a 300 baud modem to a 1200 baud modem later, I started visiting BBSes on the Apple //c and later on the IBM clone as well.  (We had a Compuserve account early on, but hourly charges!  Ouch.) As a teenager I would go to meetups and actually meet the people I was interacting with on a BBS in a real life – something I’d do twenty years later when I got involved in open source and GNOME.

Using Linux for years and being involved with GNOME, taught me how to use a shell, basic XML with Docbook, and revision control with Git.  But now it’s time to learn a formal language and make my first program.

In many ways, I still consider myself an early adopter and if it weren’t having access to computers at a young age, both in home and in school, I’d be a much different person today.

  • in GNOME
  • 1 min read

GNOME 3 is out!

I am GNOME

GNOME 3 is out! I started to writing a thank you listing out individuals but it became way too long and I was afraid I’d forget somebody. So let me just say thank you to every developer, translator, documentation writers, marketers and everyone else who’s contributed to GNOME.

Download and try it, check out the videos, the new website and Planet, the new GNOME Journal all about GNOME 3, and let us know what you think.

(And a special thanks to the sysadmins who are trying to keep the site up thanks to all the traffic we’re getting!)

My new favorite GNOME Patch

For those of us without a disability, understanding the challenge users may experience when trying to use a computer can be a foreign concept.  (Or at least it is for me.)

Browsing Reddit, of all places, this weekend I came across this story of a user with ALS who created a patch for Eye of GNOME.  The patch contributor’s son added a comment to the bug report (and a link to a picture) that is a must read.  Go read it.  Now.

This is why we write free software.  All users can contribute.  And we write software that everyone can use.  Sometimes when other stuff is going on we might forget and this is a great example of why free software is important.

  • in GNOME
  • 1 min read

GNOME T-Shirt Contest Update

(Cross-posted from the GNOME Foundation Blog)

The GNOME T-Shirt Design Contest was supposed to come to a close on January 15th.  Due to some technical issues with the submission form, we are extending the contest two weeks through the end of the month.  The contest will now close at 11:59 p.m. UTC on January 31st.

There were a few periods where the submission form was broken and your entry may not have been submitted.  If you would like to confirm we have received your entry, please email Paul Cutler to inquire.  We apologize for the inconvenience.

  • in GNOME
  • 1 min read

Thanks

Just wanted to say thanks for a couple things:

Thank you to everyone in the GNOME community who helped crowdsource editing of the 2009 Annual Report.  I received a lot of comments about lots of little things we missed and I uploaded a new version of the report a week or two ago that hopefully fixes everything.  (And thank you for the kind words on the look – Daniel deserves all the credit!)

Also a quick thank you to Baptiste for pointing out a couple little errors in the Q3 report released today.

And if you haven’t read either, check ’em out!

  • in GNOME
  • 2 min read

2009 GNOME Annual Report is out!

From the better late than never department, the 2009 GNOME Foundation Annual Report has been released.

When Lucas first asked me to help with the annual report a year and a half ago at GUADEC in Gran Canaria, one of the goals was to try and help it come out sooner. Apparently, I had the opposite effect. I have lots of excuses, but none of them good. (Though someone did point out to me that Mozilla just released their 2009 report a few weeks ago, so I felt a bit better. But not a whole lot, I hate being tardy, believe it or not).

The Annual Report wouldn’t have happened without Daniel Galleguillos C. who did all of the design and layout work and put up with my constant change requests. (Thanks to those who have already found a couple small typos – please email me with any more you find and I’ll work to get an updated copy out this weekend).

Thanks to all of our writers, including Jason Clinton, Pockey Lam, Stormy Peters and Diego Escalante Urrelo – and everyone who contributed to a quarterly report. I’d also like to thank everyone who helped with photos or re-licensed their photos so we were able to use them including Cody Russell, Chris Lord, Michael Dominic K., and Lucas Rocha. Lastly, thanks to everyone who helped edit and everyone I’m forgetting (because I know I am – especially on the photos!)

Work is already beginning on the 2010 report. It will be out sooner (I promise) and I’m also going to change it so it coincides with GNOME’s fiscal year rather than calendar year, so it may be a slightly smaller as there will be some overlap. If you want to help out, let me know!

  • in GNOME
  • 2 min read

GNOME Boston Summit 2010 kicks off

The GNOME Boston Summit 2010 kicked off a couple hours ago. Dozens of GNOME hackers are at the Tang Center at MIT.

John (J5) Palmieri and Jon McCann helped kick off the Summit.

J5 gave an overview of what the Boston Summit is. It’s different from GUADEC which is many presentations and more formal talks. The Boston Summit is much more informal and run Barcamp style. It gives hackers a chance to hack together and get stuff done. Face to face time is very important and the Boston Summit helps facilitate that.

Jon McCann continued the kickoff and thanked Stormy for her time at the GNOME Foundation as Executive Director to a rousing round of applause.

sdc10517.jpg

He then gave an update on things he’s been working on. The Control Center is actively being developed in GNOME git, new themes for GNOME Shell are coming online, and GNOME 3.0 will feature a new font! The new font is designed by David Crossland (spelling?) who is a big believer in open design and is also hosted on GNOME’s git servers.

Jon talked about Shell briefly (and Owen will talk about it more later today). New guidelines are being written for GNOME 3 applications and wiki pages discussing that as well as compatibility and messaging are in progress. He asked the crowd how many people were running GNOME Shell now and about 25% of the hands in the room went up.

Work on the new modulesets for GNOME is in progress and there is a renewed focus on GNOME’s core and a focus on what the desktop is. One conversation that he looked forward to having this weekend is what is the Core OS versus the applications that layer on top of it. A goal is to make it easier to build the core desktop. One example of this is jhbuild – jhbuild has seen its core modules reduced from 255 to 92 modules! Jon is hoping the group will continue to brainstorm on how to make that even easier.

There are 3-5 months left for development (depending on how you look at freezes) and now is a great time for the community to come together. GNOME 3.0 is a very important release for GNOME and it will take all of us.

Lastly, Jon encouraged the community to watch the video of the talk that Michael Meeks gave at Linux Plumbers this week. The talk was about how GNOME is doing open source right. GNOME has a strong message to share and other projects look to us for things such as doing design in the open, community engagement and more.

From there, people proposed talks and sessions to give Barcamp style and we voted to help prioritize the sessions and J5 started assigning rooms and times for the talks.