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

List:       kde-community
Subject:    [kde-community] Should we allow non-KDE projects to participate in GSoC under KDE?
From:       Martin Klapetek <martin.klapetek () gmail ! com>
Date:       2016-02-03 19:58:54
Message-ID: CAPLgePrn-Hbs7J6XFHh1PFSSED5+Gyc0T2uchEFFg0usbeWfpA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hey,

so in the couple previous years we have collectively and
repeatedly rejected the idea of other projects, that are not
KDE projects by the Manifesto, to participate in KDE GSoC.
Namely we rejected Tupi and SubSurface solely because
"not a KDE project", GCompris became a KDE project and
then we let it participate.

Last year we got a non-KDE project in our GSoC despite the
previous years decisions, nobody really noticed and then there
was a huge discussion if that's ok or not, but by that time it was
a bit late.

So I'd like to have this cleared - does the community agree to
have non-KDE projects, those that do not follow the Manifesto,
participate in our GSoC this year and in the following years?

Imho this goes against the Manifesto as the projects gets to
"enjoy the benefits" without the complying with "commitments"
of the Manifesto. It's also less transparent overall (not able to
monitor progress as it's not on KDE infrastructure), can lead
to cheating and possibly kicking KDE out of GSoC in the worst
possible outcome.

On the other hand, every accepted project gets the mentoring
organization some extra money, which is always handy.

Cheers
-- 
Martin Klapetek | KDE Developer

[Attachment #5 (text/html)]

<div dir="ltr">Hey,<div><br></div><div>so in the couple previous years we have \
collectively and</div><div>repeatedly rejected the idea of other projects, that are \
not</div><div>KDE projects by the Manifesto, to participate in KDE \
GSoC.</div><div>Namely we rejected Tupi and SubSurface solely \
because</div><div>&quot;not a KDE project&quot;, GCompris became a KDE project \
and</div><div>then we let it participate.</div><div><br></div><div>Last year we got a \
non-KDE project in our GSoC despite the</div><div>previous years decisions, nobody \
really noticed and then there</div><div>was a huge discussion if that&#39;s ok or \
not, but by that time it was</div><div>a bit late.</div><div><br></div><div>So \
I&#39;d like to have this cleared - does the community agree to</div><div>have \
non-KDE projects, those that do not follow the Manifesto,</div><div>participate in \
our GSoC this year and in the following years?</div><div><br></div><div>Imho this \
goes against the Manifesto as the projects gets to</div><div>&quot;enjoy the \
benefits&quot; without the complying with &quot;commitments&quot;</div><div>of the \
Manifesto. It&#39;s also less transparent overall (not able to</div><div>monitor \
progress as it&#39;s not on KDE infrastructure), can lead</div><div>to cheating and \
possibly kicking KDE out of GSoC in the worst</div><div>possible \
outcome.</div><div><br></div><div>On the other hand, every accepted project gets the \
mentoring</div><div>organization some extra money, which is always \
handy.</div><div><br></div><div><div>Cheers</div>-- <br><div \
class="gmail_signature"><div><span style="color:rgb(102,102,102)">Martin Klapetek | \
KDE  Developer</span></div></div> </div></div>


[Attachment #6 (text/plain)]

_______________________________________________
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]