I don't even remember what I thought the last couple of times, but I
think it was something like this:
"if these are projects that we can likely bring under our umbrella, yes,
we should, if that is not going to happen, then we shouldn't"
I cannot imagine I ever thought something different, but it's possible,
and I remember someone telling me I was inconsistent, last year.
On Wed, 3 Feb 2016, Martin Klapetek wrote:
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
--
Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
