Recently i found a very interesting article about Open Source 2.0 (“Open Source 2.0: The Science of Community Management.”) in Oracle web site.
Here i submit the 3 Myths according to the article :
1) Your Open Source Community is a Meritocracy.
“Admit it, the first 10 people to join your project have much more power than the next 10 that join, even the next 100. The first UI person to the project will be “the UI guy,” it will take a serious stumble by him or a person drastically better then him to be displaced. The meritocracy myth is particularly harmful because it creates the promise that if you work really, really hard, you will have the same opportunities as everyone else in the community. Because of human nature, that’s just not true. People are generally creatures of habit and go to the people they already know. It takes real effort to expand the circle/change their ways. For more information, you can read Structurelessness, feminism and open: what open advocates can learn from second wave feminists (this is in part about why open source communities are not pure meritocracies).”
2) Open Source is about Collaboration
“The genius of open source is how *not* to work together. It’s about taking complex problems, breaking them into chunks and that individual developers can go work on and then can slide back into the whole. Collaboration is slow, expensive and high touch, community leaders should always think of ways to move from collaboration to cooperation. For example, it used to require long negotiations with the owners of the trunk to get extensions into Firefox (collaboration). With Firefox addons, community members could add functionality and users could pick it up much more easily (cooperation).”
3) Coders Don’t Need Soft Skills
“If the success of your open source project is attracting (and keeping) community members, then your soft skills are your differentiator, not your coding chops. Be aware of the assumptions you bring to every conversation (Is this a negotiation? What’s my goal? Is my goal just to prove the other guy wrong?). Your mindset can be resources are scarce, this is a battle, and eveyone else is stupid, crazy and evil. Or, you can believe that the pie can be made bigger, this is cooperative venture and people do what they believe is in their best interest. As a community leader, you can set the tone and maximize the outcome. Your job is not only to listen to what someone is saying, but to find out what are their real interests and concerns. A good solution may be closer than you think.”
The rest of the article can be found here 
True or note is another point of view , maybe not to usual ….
1) How to get involved :
2) Version control system :
3) Bug-tracking system :
Bugzilla : https://bugzilla.gnome.org/
4) Mailing Lists :
5) GNOME Translation Teams :
Jos Poortvliet , tell us about yourself. Who are you?
Hey, I’m a Dutch Free Software enthusiast living in Berlin with my Brazilian
wife Camila. I’ve been around Free and Open Source for over 10 years, mostly
active around marketing and community related things.
I’m active in marketing, helping the project communicate to the outside
world. But also internally and between SUSE and openSUSE. I am also active
on the governance side of the project, with strategy or board related things
and helping to handle conflicts if they arise.
He, good question. In the beginning, many people expected me to take charge
and play a leadership role. As that is clearly something which does fit
neither openSUSE nor me, I did not do that and made very clear that I did
not see that as my job. Instead, I presented myself as a contributor who had
to earn his place like everybody else. I think I did that, in the last
years, and today people come to me for advice mostly in the areas of
communication, marketing and conflicts – and I happily stay out of
especially technical decisions.
Depends on what you are looking for, what you want to create. If it is
something like the ARM project or a new openSUSE derivative, it SHOULD
affect the project – ARM is adding something to openSUSE, so are the
derivatives. That is good!
So, just announce it as that – a cool, new thing in openSUSE. That is not
particularly hard to communicate. I would not communicate it before it has
something to show for and in most cases that means first gathering some
people who want to work on it and making a ‘first release’, then announcing
where you plan to take it and inviting people to join.
Of course, it would be possible to create a project which might not be
naturally seen as an addition. Say, you want to ‘fork’ openSUSE into a more
stable (or more bleeding edge) version. That is an entirely different thing
and should be handled with a little more care: one can imagine that this
takes up resources which otherwise might be put in openSUSE Factory, for
example. But here, too, I think it is important to first talk to some core
people, get a team up, create a ‘proof of concept’ and simply have a clear
plan. Then, based on what objections you expect, make sure to communicate it
in a non-threatening way.
We have some statistics but these focus around the release, marketing and
user base (number of downloads, page views to our sites, number of active
installations, things like that). And we have some idea about development
(number of commits to Factory, amount of work in devel projects). We have
very little, if any, info on communication related things.
“assigned” tasks per volunteer and successfully finished task per volunteer?
I have very little idea here. First of all, because I am restricting myself
to a subset of the community: the marketing area. Second, because my work
frequently shifts and I don’t always interact with the same people. And
last, because I don’t keep metrics like that – I work very much on a one-on-
one base. I’m not saying that that is the best way to do it but I’m not much
of a number man 😉
It depends quite a bit in what area and what skills he/she brings. But you
are often looking at quite a long time – a minimum of a month but easily
half a year.
Sometimes, when I’m actually mentoring new people…
I try to catch it myself but often, I delegate based on trust. So if a
volunteer doesn’t do something, well, it doesn’t get done. That is
There are a lot of reasons – but for me, the most important part is the open
mind. Every project has people angry at the world, every project has
friendly and unfriendly people. But overall, openSUSE as a community is very
open to both newcomers and working with others. We’re not such a navel-
gazing community, we pragmatic and willing to look outside our borders,
adopting technologies from other communities and working with them on it.
That is maybe not totally unique, but certainly rare.
From 31st of January to 10th of February I participated in openSUSE 12.3 Marketing Hackathon. The Hackathon took place in SUSE Headquarters [Nuremberg,Germany] from 4/02 to 10/02. Before that we participated in FOSDEM by promoting to the crowd the openSUSE Project and the oSC13 as well. Our participation in FOSDEM was really successful cause people asked a lot of questions around the upcoming release of openSUSE and expressed their interest for this year’s openSUSE Conference. Thanks to Carlos we spread out and informed a lot of people about the oSC13.
Apart from that this year I spent more time in joining presentations. I admit that I liked more FOSDEM 2013 than FOSDEM 2012 because I found the presentations (Developer rooms especially) more interesting.
After FOSDEM we travelled to Nuremberg for the Marketing Hackathon . On the way back to Nuremberg I was impressed by the fact that openSUSE development continued even on the bus with various hackers (SUSE Employees) sitting behind their laptops, building packages. Apart from software development we drunk a lot of openSUSE beers. 🙂
Arriving to Nuremberg , after FOSDEM , we begun to work in the 12.3 RC1 release. SUSE Employees helped us by providing all the necessary equiqment [ok , coffee , meeting rooms etc] since we worked in the SUSE offices. Interacting with people from the company was really interesting , and i admit that during a release there is a lot of work to be done (bug fixing , artwork, ,writing , promotion , etc) .
Apart from the release we enjoyed a presentation by the SUSE Documentation team , where we tested a demo of the new ActiveDoc tool.ActiveDoc is used for the documentation of openSUSE and SUSE as well. Furthermore we had visits from company management , from Ralf Flaxa, VP of engineering, and Roland Haidl. During these meetings we discussed about issues around openSUSE Project , and how the project can be improved. Ralf Flaxa and Roland Haidl thanked us for our work and they confirmed their willing to help the openSUSE Project as much as they can.
As the KDE 4.10 released during the Marketing Hackathon we all joined the KDE 4.10 release party (in Wednesday). KDE president Cornelius Schumacher and Klaas Freitag, (ownCloud Senior Developer) joined us to the party. We had really interesting discussions about various aspects (KDE , ownCloud ,oSC13 etc).
Here i give a brief summary of my work
– 12.3 Screenshots (Screenshots and related wiki page) [although my laptop was broken for a while]
– 12.3 Package list and Feature (the last days)
– 12.3 Social Media messages for RC1 (and the final release as well)
– 12.3 “We are Hispanohablantes” , a new project begun , willing to centralize the Spanish speaking communities in openSUSE. Here you can find the English  and Spanish  version of the wiki page. [if you come from a Spanish spoken country , you can add stuff in the “Information Table”.]
I could blog about this experience for years , but i prefered to write a resume of what i have in my mind 🙂
. Obviously i would like to thank the following people (participants and SUSE Employees) :
Kostas , Bruno (tigerfoot – “Champignon”) , Carlos (victorck), Carlos (CarlosRibeiro), Izabel (IzabelleValverde), Marcel (tux93 or “Silent Power”), Richard (ilmehtar), Michal (|miska|).
Jos, Henne , Ralf, Roland, James, Jan, Ludwig, Cornelius, Suzanne Augustin, Will, Christopher, Adrian, , Jurgen, Kenneth, Cassio, Alberto,
(if I forget someone ,please let me know 😉 )
And yes we all love Vietnam 🙂
And don’t forget!!
A lot of Geekings to everybody,
“Power to the Geeko”