Tag Archives: elementary

Shotwell, elementary, and Pantheon Photos: What it all means

Last Friday Daniel Foré made an announcement on elementary’s mailing list that has generated a considerable amount of interest:

Shotwell needs a new maintainer. … After some discussion with Jim, we think the best course of action is for elementary to fork Shotwell.

OMG! Ubuntu reported later that day (and with surprising speed) that “Elementary To Take Over Shotwell Development”.  I’ve received emails from people wondering what this means for the future of Shotwell.

To be clear, Yorba remains the maintainer of Shotwell.  elementary has not taken it over.  Yorba recently took the rather large step of moving Shotwell and all its associated work (including our ticket database, wiki pages, architecture guidelines, and more) into the GNOME infrastructure. We didn’t do all that work just to hand the keys over to another group on another platform.  We made the move because, when we did all the calculus, we agreed GNOME was the best location for the future of Shotwell.  Going into the GNOME infrastructure opened (and is still opening) a lot of doors for us.  However, Yorba’s resources are limited, and as of late we’ve not been focused full-time on improving Shotwell.

This put us into a bind, and so I began looking for outside individuals or groups who would be capable and willing of contributing to Shotwell in a more substantial way.  I kept coming back to a group that has shown a great deal of energy and motivation in the past and a willingness to work with us: elementary.  They expressed a lot of interest in improving Shotwell, and so we began a discussion about how that situation might look.  In the end, we reached an understanding:

  • Shotwell will continue to be maintained by Yorba.  We’ll triage bugs, take patches, fix critical bugs, ensure it builds with the latest versions of Vala and supporting libraries, and runs on the major distros.  Yorba will continue to release Shotwell on a six-month schedule.
  • elementary agreed to jump in and improve Shotwell, but stated that all of their development must occur on Launchpad.  They also wanted to rebrand the project to fit under their design umbrella.  This includes integration with Contractor and other technologies they’re building for their OS.
  • It was agreed that they would fork the project to Launchpad and rename it Pantheon Photos to distinguish it from Shotwell.  The pragmatic reason for this is to prevent name collisions with packaging.  This also allows for elementary to customize Shotwell to their own platform and brand it separately.
  • As Shotwell maintainers, we’ll evaluate elementary’s work and look for commits that are useful to Shotwell users.  We’ll cherry-pick that work and merge it into the Shotwell base.
  • elementary agreed not to relicense Shotwell, so its current license (LGPL 2.1) stands.

While elementary has big plans for Pantheon Photos, none of that work is happening in private and we’re free to take improvements as we wish (and likewise they’re free to pull improvements from Shotwell’s code base).

Additionally, this situation already exists, and has existed for years, with Ubuntu: they maintain their own fork of Shotwell to provide integration with Ubuntu Online Accounts.  (I’ve referenced that situation before.)  elementary is doing this on a larger scale, admittedly, but it’s not unique in the world of open-source and shouldn’t be a source of alarm.

(I regret that Daniel wrote “Shotwell needs a new maintainer.”  I was privy to that email before it was posted and should’ve asked he reword it.  That was my fault, not his.)

I can’t emphasize enough that Shotwell is not being discontinued or end-of-lifed, and elementary has not “taken over” Shotwell.  We’ll continue to maintain Shotwell and release versions with our usual distribution targets.  This is why I tweeted that this situation is a win for everyone (a sentiment echoed by Bryan Landuke) — users won’t necessarily have to pick-and-choose which app they want to use, or even which distribution, in order to manage their photos.

Geary 0.4.2 backport for Precise 12.04 / Luna now available

geary-yorbaLast month I announced Yorba was sponsoring a $500 bounty to backport Geary 0.4 to Precise Pangolin 12.04 and elementary’s Luna.  I’m pleased to announce two new developments toward that goal.

First, since then six forward-thinking people added another $100 to the bounty, making the total pot $600.  Thank you!  This was the part of the experiment I was most interested in.  Backporting Geary to 12.04 was a highly-requested task, and I wondered if the people who wanted it would be willing to contribute a little money toward that goal.  At least some people did think it worthwhile enough, and collectively they added 20% to Yorba’s initial offer.

Second, I’m pleased to announce that the goal has been reached.  Tom Beckmann put in a lot of hours and considerable blood, sweat, and tears to port Geary back to 12.04, but he did it and so he claims the bounty.  I’ve run his version of Geary on both Precise and elementary Luna and am quite impressed.  It uses our new symbolic icon layout, it’s integrated with Precise’s message indicator, and offers every feature in Geary 0.4, including full-text search and the stability improvements we added to 0.4.1.  Best of all, he packaged it up on a Launchpad PPA, meaning it’s a snap to install.

If you’re running Precise Pangolin 12.04 or elementary Luna and you’d like to upgrade your version of Geary, I recommend the following directions.  Open a terminal window and type the following:

$ sudo add-apt-repository ppa:tombeckmann/geary
$ sudo apt-get update
$ sudo apt-get install geary

If you’re already running Geary 0.3.1, this new version will update your old database and you’ll be good to go.

A few notes about this release:

  • This is not an official Yorba release of Geary.  Please note the version number in the About box (Geary 0.4.2+backport).
  • Yorba will not be proactively fixing bugs or adding features to this backport.  If there’s sufficient interest in keeping the backport alive, we’re hoping the community will work together to maintain and update it.
  • If you encounter a bug with the backport, your best bet is to use the Geary mailing list to report it.  Please indicate in your email that you’re using the backport.  There’s no official bug tracking system for this backport at this time.

(One further note: due to some technical issues, the original Bountysource.com page was moved here.  Other than the URL, all details have remained the same.)

Congratulations Tom, and thanks!

Would you like to see Geary 0.4 available on Ubuntu 12.04 / elementary Luna?

geary-yorbaWe’ve received a lot of complaints from users that Geary 0.4 isn’t available for Ubuntu 12.04 (Precise Pangolin) and elementary Luna.  It wasn’t an arbitrary decision on our part.  As we developed Geary 0.4, we learned that more and more components that Geary relied on were changing or simply unavailable in 12.04/Luna.  There’s a tangible engineering cost to maintaining backward compatibility.  At some point this summer we realized it was too much work to maintain support for 12.04/Luna as well as newer versions of Ubuntu, Fedora, and all the other distros out there.

But Ubuntu 12.04 and elementary Luna (which is based off of 12.04) has a steady fan base who would really like to run Geary 0.4.  What to do?

We have limited resources, but we don’t want to leave users out in the cold.  We believe this is a problem both Yorba and the community can solve.  So we’ve created a bounty for the problem — if someone out there (or a group of people) solves this problem for us (and therefore everyone else!), they’re rewarded with cold, hard cash.  It’s that simple.

If you’re interested, read on:

There’s two pages you should read: the issue ticket at Yorba’s project server (which details the problem and the stipulations for collecting the bounty) as well as the bounty page at Bountysource.com (where the promised funds are listed).

If you want to see Geary 0.4 work on 12.04/Luna, you can help.  Go to the bounty page at Bountysource.com and pledge what you can.  The more the community offers, the more motivation developers have to take on this challenge.  It’s not easy what we’re asking for — whomever takes this on deserves a reward for their time, energy, and expertise.  What’s more, if no one solves this problem, you get your money back (minus Bountysource.com’s fee).

If you have the right stuff to backport Geary 0.4 to 12.04/Luna, dive right in.  Make sure you read the issue ticket first for all the stipulations.  This isn’t a simple matter of getting Geary to compile on 12.04.  You have to make sure anyone running 12.04 can install it via their package manager.  Yorba’s developers are willing to guide you along, offer advice, point out resources or commits that you might be interested in.  But you need to make it happen.

Just to show that we’re serious about this, Yorba has already pledged $500 toward this bounty.  We’re hoping the community will toss in more money to further sweeten the pot.  If everyone who has asked us to backport Geary 0.4 to 12.04/Luna offered $10, $25, or $50 toward the job, there would be no problem finding someone to do the work.

(Note: Yorba employees are prohibited from collecting any bounty money for Yorba-related projects.)