Hi!

Rawstudio is rotting.

As de facto maintainer of Rawstudio I feel I have to do something.

A simple metric for measuring activity is commits per year. Here's the
numbers since the project started:

2006: 551 commits
2007: 564 commits (I got married :)
2008: 512 commits
2009: 636 commits (My first child was born)
2010: 635 commits (I started a company)
2011: 309 commits (My second child was born)
2012: 152 commits
2013: 57 commits
2014: 5 commits

I think it's safe to say that Rawstudio is rotting.

If we want to save Rawstudio, something must be done to make maintenance
easier. I propose the following 10-step reboot:

1. Move the source repository to github. It would allow for easier
collaboration with occasional contributors (if we have any left) - I'm
currently testing at https://github.com/rawstudio/rawstudio

2. Drop Bugzilla and all bugreports after salvaging relevant patches.
Start fresh.

3. Remove the following plugins from Rawstudio:
 - output-facebook
 - output-flickr
 - output-picasa
They are all somewhat broken, have exotic dependencies and are moving
targets.

4. Drop support for older versions of glib/gtk. Maybe support Ubuntu
12.04 and onward.

5. Replace all deprecated API's we're currently using (GStaticMutex,
maybe others).

6. Drop all geolocation support. It too requires exotic libraries.

7. Fix all crasher and security related bugs.

8. Make package maintainers _happy_. Check what patches downstream have
applied (in the past) and apply them.

9. Release version 2.1 as announced in 2011 (!).

10. Celebrate with champagne.

(11. Find a new maintainer)

Any thoughts?

/Anders Brander



_______________________________________________
Rawstudio-dev mailing list
[email protected]
http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev

Reply via email to