CC by nc sa mikep @flickr
There was a long pause during the strategy process. Now the strategy team is working on it again. News are coming the next days. Stay tuned.
About research, KDE, openSUSE, education and the rest of life
"Krogh, Spaeth and Lakhani analyzed the characters of potential new contributors in mailing lists.[12] Based on that work three types could be found.Even the headline of one of the post gives you a hint which type might be behind the post in question. Visionaries often use words like "it should", "you have to" etc. instead of "I have done" or "I am going to do".
- Proactive problem-solver: They use the program, find a bug, and work out the solution. In the first mail to the list they send the patch. These people are very successful in communities and often become continuous contributors.
- Waiting volunteer: This group offers their abilities to the community and waits until they get a job allocated. In general this character is not very active. Most communities can not integrate them successfully.
- Visionary: They use the program and have ideas on how the program should be improved. Although visions and aims are important in communities, the character-type visionary is not successful. In the past his/her visions were not identical with the ideas of the code developers. The resulting costs of conflicts exceed the benefits of the discussion."
As I mentioned in my previous post I can't mentor GSoC students myself and therefore are looking for a developer to jump in for me.![]() |
I recently mentored some students during the Google Code In project. Now the preparations for Google Summer of Code have begun. Unfortunately I am not a hacker, I am a promo guy and I can't mentor here. Nevertheless I have some ideas for GSoC and I hope to scratch somebodies itch so she or he will mentor that idea.