Posts Tagged ‘KDE’
A few weeks ago Adriaan De Groot (Vice President of the KDE Foundation Board) explained us in the master on libre software the different issues that are important to be taken into account in order to maintain a big community such as KDE, where there are people working together from different countries, with different timezones, culture, languages, … Looking after the KDE community is maybe the main goal of the KDE e.V. non-profit organization which was created with the aim of offering representation, support and governance to the KDE community.
Inside the KDE e.V. there are three working groups: Community, Marketing and System Administration and I was curious about the first one. KDE people are not different from the rest of human beings and sometimes they end up with problems that need a special action, these kind of issues are handled by the Community Working Group which is only three years old and it’s composed of 5 people.
This is part of the formal definition:
“The Community Working Group aims to act as a central point of contact by being available to communicate user needs and concerns to developers, and developer intentions and plans to users.
The group also acts as mediator upon request in the rare cases where the communication breaks down. If these are issues regarding expectations, the work will be closely coordinated with the Marketing Working Group.”
The CWG bases on the KDE Code of Conduct an important part of its job, this document details the social norms and expectations for the community members. The CWG members act as mediators when someone feels that the Code of Conduct has being violated, then they try to resolve the problem amicably. Sometimes this is not possible, in those extreme cases the CWG will suggest to the e.V. Board the most helpful action for the KDE community. The CWG does not, itself, take any action.
Last week I was in Karlsruhe in the ALERT kick-off meeting, this is a FP7 project funded by the European Comission. Its main goal is to create real-time & personalized help for developers based from the project’s information (SCMs, BTSs, wikis, blogs, forums and so on). The typical example of one of this aids is sending to the developer a list of suggested duplicated bugs to confirm them or even mark them as duplicated without its intervention.
I’m happy with the team, we are ten partners from different European countries and we have important communities such us KDE to test the real thing. During the next year I’ll be working on improving the tools we have to extract data from remote project resources (mainly BTS and SCM) and I’m pretty sure I’ll enjoy it.