I don't know how relevant this note may be, but I found it interesting to share it. Here the link in English, http://freininghaus.wordpress.com/2012/07/04/dolphin-2-1-and-beyond/, I don't manage well with that language, so I got help from a translator:
You have probably heard last week that Pedro Penz is no longer a Dolphin maintainer. I would like to thank you for the good collaboration we have had over the past years. It was a great pleasure working with him, and I think his departure is a great loss to KDE.
He entrusted me with the future maintenance of Dolphin, so I will do my best to keep him in good shape. I think ease of use and stability is what users appreciate the most about Dolphin, and want to make sure it stays that way.
My most important medium-term goal is to attract new developers. I think this is vitally important for a number of reasons:
- Any software project with a low bus number is in great danger.
- I'm the maintainer now, but that doesn't mean I can increase the amount of time I can spend developing in Dolphin. I'm going to try to read all the input bug reports (note that it may take a while until I see a recently reported bug - even maintainers have a real life and go on vacation sometimes) and try to reproduce, at minus the ones that can be reproduced with my hardware and software setup. I will also try to fix a couple of bugs for each version. But I can't implement all the major new features if I have to do it all alone.
- I don't like working alone. I've always enjoyed discussions of the code with Pedro and other developers, and I quite like the idea that all commits need to be reviewed. Obviously, speaking of patches and review for everyone is only possible if the number of people contributing to the project on a regular basis is greater than one.
To make it easier for potential new contributors to find something to work on, I'd like to start a joint effort to go through all the Dolphin bug reports, close to the outdated ones, and assign useful keywords to those that can be easily reproduced. Real life will keep me busy for the next couple of weeks, but then I'll get in touch with the Bug Squad and get something organized. Any help is welcome. I think participating in a joint bug triage session is a good way to start contributing to a free software project - as I mentioned in a previous post, my participation in KDE started with two days of Konqueror a couple of years ago. .
Not just code contributions, but help in other areas is appreciated, of course. These include:
- Triage bug reports at bugs.kde.org. It really helps a lot to add useful information to bug reports, point out duplicates, ask the reporter for more information, and therefore reduce the number of bug reports that require attention from the manager. It is also good for users that their reports can get quick responses, even when the manager is busy with other things.
- User support in the forum. It is amazing to see how quickly a group of dedicated forum members answers the questions of the majority of users and solves many of them. I think this improves the user experience considerably.
- Documentation and translation. Burkhard Lück especially does a great job of keeping Dolphin documentation (and other applications) in good order.
If you want to contribute to Dolphin or KDE in general, but don't want to write code, getting involved in one of these areas is a great way to help the project move forward.