Hi,
Here are the various activities involved in keeping the project running.
I'm awful at asking for help, suggesting areas, managing people etc. so I figured I would just list whatever there is. (What I can think of right now at least).
You may or may not have realised that it was this lot. Right now I'm doing most of the stuff apart from internationalised things obviously.
In no particular order.
Project Management
1. Establishing the long term direction of the project.
2. Choosing the mid term direction of the project.
3. Keeping all the users suggestions in a coherent list.
4. Assessing the potential and feasibility of the all suggestions.
5. Establishing release plans.
6. Making sure the short term decisions do not confilicts with broader goals.
7. Pronouncing feature freeze - (starting point of a formal release).
8. Packaging the release and uploading it to the site.
9. Making sure the main downloading sites have the latest version.
10. Keeping up to date about latest developements in related fields to get new ideas.
Communication
1. Posting blog posts about the project and future enhancements, media coverage, etc.
2. Translating these blog post from english to french or the other way around.
3. Posting some announcements or call for help and tests in the forum. Translating these too.
4. Filling the [s]super secret[/s] contributors wiki (en) (more on that soon hopefully).
5. Webmastering the site.
6. Answering questions about software usage in the forum.
7. Writing about the software in other forums.
8. Redirecting questions about the software in personal mails to the forum.
9. Chatting about possible future enhancements in the forum.
10. Answering requests from sports federations or private companies (and having no clue how to handle that).
Translation & documentation
1. Translating interface to new languages. (to all involved: thank you so much !)
2. Proof reading interface and help files in all languages available.
3. Consolidating the various localisation efforts in the language file.
4. Creating and maintaining the documentation (help files).
Quality Assurance
1. Doing basic testing.
2. Monitoring the bug report tool, reproducing reported defects.
3. Creating test cases to avoid regressions in future releases.
Code & tools
1. Managing scripts to ease release and internationalisation process.
2. Designing architecture at various scales.
3. Implementing features.
4. Creating or selecting icons and visual elements of the interface.
5. Fixing defects found in previous versions.
6. Improving features of previous versions, possibly removing unused ones.
7. Reconsidering architecture and refactoring the code so it's easier to work with in the future.
Needless to say, this takes a lot of (my free) time.
And beside my daily work (which is unrelated), I also have other hobbies 
That is why you want to help the project moving forward.
Sure, I could do it all. But it's taking ages. The project is Open Source for this reason too.
joan at kinovea dot org
