[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-community
Subject:    Re: [kde-community] QtCurve
From:       Yichao Yu <yyc1992 () gmail ! com>
Date:       2014-01-21 21:19:04
Message-ID: CAMvDr+SQ8gegG3YV7zPCF-ySu_RWpBbNj3d7EiPF9T=6WdA6+w () mail ! gmail ! com
[Download RAW message or body]

On Tue, Jan 21, 2014 at 1:18 AM, Kevin Ottens <ervin@kde.org> wrote:
>
> That *and* the incubator is also meant for projects having a "not yet part of
> KDE" team joining. For instance if VLC would ever want to join (random

Not sure how VLC ppl feel but I am happy to see that happen. =)

> example) it would go through the incubator still, even though it is "is
> already stable and have made several releases that are packaged by a number of
> distributions". The purpose of the incubator is not just technical but also to
> make sure projects are well alive, active and integrated in the community.
>
> Now, does it apply to QtCurve? At a glance I thought it did, I can't really
> say for sure and could be totally wrong. :-)
>

Sorry but I'm a little bit confused.
According to what I have heard before, supports from the sysadmin and
other teams are necessary anyway if a project want to join the KDE
community and the list on the wiki page are very similar to what I
have heard of before incubator. So what's the difference between going
through the incubator or not? Is it a new name and a more organized
procedure to deal with all that's necessary for joining the community?

Thank you for you clarification

Yichao Yu
_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
[prev in list] [next in list] [prev in thread] [next in thread]