[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-community
Subject: Re: [kde-community] Should we allow non-KDE projects to participate in GSoC under KDE?
From: Martin Klapetek <martin.klapetek () gmail ! com>
Date: 2016-02-05 16:38:34
Message-ID: CAPLgePoszXuYRE0CGyjgtNz30-_gV_YWm6pMUM1E1YOtEpULXQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Fri, Feb 5, 2016 at 11:14 AM, Ingo Klöcker <kloecker@kde.org> wrote:
> On Wednesday 03 February 2016 14:58:54 Martin Klapetek wrote:
> > 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.
>
> I'm sorry, but I completely lack the necessary information to give my
> opinion
> in this matter. From the thread I gather that there have been issues in the
> past with at least one non-KDE project. But without a list of the pros and
> cons and a short summary of the past experience with allowing non-KDE
> projects
> how am I supposed to decide?
>
If you are subscribed to kde-soc-mentor and have been in the
past, look up "About GSoC mentoring" thread from 2013.
In short: Tupi wanted to do GSoC with us, many people in that
thread said "sorry, GSoC is only for KDE projects". That same
year (and same thread) also ownCloud wanted to have a GSoC
slot for better KDE integration. Again people agreed to "sorry,
this is for KDE projects only" (and ownCloud didn't consider
themselves a KDE project). GCompris was a similar situation
but they joined in time and all was fine iirc.
Year later SubSurface wanted a slot, we again said "you either
become a KDE project or we're sorry" so they didn't get a slot.
Last year after GSoC has started, Vishesh found out that Calamares
is in our accepted GSoC projects and yet is not a KDE project
(and was put up by the GSoC admin). There was a long discussion
where it was said it is at least unfair to all those previously rejected
projects and that it was thought to be a rule to not accept non-KDE
projects based on discussions and decisions from previous years,
so how come this one got accepted etc etc etc.
This was all discussed on non-public mailing lists but I believe this
is actually a community matter as it affects the whole community
and as such the community should have a say in it. If only for the
reason that we all have our little side projects that are not in KDE
and would maybe want to join GSoC and nobody knows if it is
allowed or not.
Cheers
--
Martin Klapetek | KDE Developer
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Feb 5, 2016 \
at 11:14 AM, Ingo Klöcker <span dir="ltr"><<a href="mailto:kloecker@kde.org" \
target="_blank">kloecker@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On Wednesday 03 February 2016 14:58:54 Martin \
Klapetek wrote:<br> > So I'd like to have this cleared - does the community \
agree to<br> > have non-KDE projects, those that do not follow the Manifesto,<br>
> participate in our GSoC this year and in the following years?<br>
><br>
> Imho this goes against the Manifesto as the projects gets to<br>
> "enjoy the benefits" without the complying with \
"commitments"<br> > of the Manifesto. It's also less transparent \
overall (not able to<br> > monitor progress as it's not on KDE \
infrastructure), can lead<br> > to cheating and possibly kicking KDE out of GSoC \
in the worst<br> > possible outcome.<br>
><br>
> On the other hand, every accepted project gets the mentoring<br>
> organization some extra money, which is always handy.<br>
<br>
</span>I'm sorry, but I completely lack the necessary information to give my \
opinion<br> in this matter. From the thread I gather that there have been issues in \
the<br> past with at least one non-KDE project. But without a list of the pros \
and<br> cons and a short summary of the past experience with allowing non-KDE \
projects<br> how am I supposed to decide?<br></blockquote><div><br></div><div>If you \
are subscribed to kde-soc-mentor and have been in the</div><div>past, look up \
"About GSoC mentoring" thread from 2013.</div><div><br></div><div>In short: \
Tupi wanted to do GSoC with us, many people in that</div><div>thread said \
"sorry, GSoC is only for KDE projects". That same</div><div>year (and same \
thread) also ownCloud wanted to have a GSoC</div><div>slot for better KDE \
integration. Again people agreed to "sorry,</div><div>this is for KDE projects \
only" (and ownCloud didn't consider</div><div>themselves a KDE project). \
GCompris was a similar situation</div><div>but they joined in time and all was fine \
iirc.</div><div><br></div><div>Year later SubSurface wanted a slot, we again said \
"you either</div><div>become a KDE project or we're sorry" so they \
didn't get a slot.</div><div><br></div><div>Last year after GSoC has started, \
Vishesh found out that Calamares</div><div>is in our accepted GSoC projects and yet \
is not a KDE project</div><div>(and was put up by the GSoC admin). There was a long \
discussion</div><div>where it was said it is at least unfair to all those previously \
rejected</div><div>projects and that it was thought to be a rule to not accept \
non-KDE</div><div>projects based on discussions and decisions from previous \
years,</div><div>so how come this one got accepted etc etc \
etc.</div><div><br></div><div>This was all discussed on non-public mailing lists but \
I believe this</div><div>is actually a community matter as it affects the whole \
community</div><div>and as such the community should have a say in it. If only for \
the</div><div>reason that we all have our little side projects that are not in \
KDE</div><div>and would maybe want to join GSoC and nobody knows if it \
is</div><div>allowed or not.</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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic