[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 14:40:39
Message-ID: CAPLgePoEECB_+Cs75+sgSs1Q6sjGGSeG+Gf9KH36_h53_Wh3bA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Fri, Feb 5, 2016 at 8:42 AM, Teo Mrnjavac <teo@kde.org> wrote:
> On Thursday, February 4, 2016 11:53:48 AM CET Ivan Čukić wrote:
> > > Just FTR, we don't give away our own slots, but we ask for slots after
> > > we decide how many projects we are going to select.
> >
> > And with that I'm completely fine.
>
> I just found myself physically shaking my head at some of the more
> authoritarian-bent emails in this thread.
>
> In KDE we have a GSoC team that's been taking care of GSoC and other
> student
> programs for years now, and these people are intimately familiar with GSoC
> dynamics on slot allocation and are thoroughly aware of the costs and
> benefits
> of allowing external projects to take part in GSoC under the KDE umbrella.
>
That doesn't mean you can do whatever you want though,
even more so when it's a small group with no outer access.
> It would be toxic to try to micromanage the Krita team, the sysadmin team
> or
> the WikiToLearn team: KDE has historically worked best when those who do
> the
> work decide how it's done.
>
> So here's a novel idea: how about we let the GSoC team do what they are
> good
> at and come up with their own policies and decisions in GSoC-related
> matters?
> At best, any concerns should be brought up with them on the relevant
> mailing
> list, rather than appointing ourselves as overseers in this thread.
>
I did last week and where I got told to post it here. After all
it should be a community decision.
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 8:42 AM, Teo Mrnjavac <span dir="ltr"><<a href="mailto:teo@kde.org" \
target="_blank">teo@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 Thursday, February 4, 2016 11:53:48 AM CET Ivan Čukić wrote:<br> > \
> Just FTR, we don't give away our own slots, but we ask for slots after<br> \
> > we decide how many projects we are going to select.<br> ><br>
> And with that I'm completely fine.<br>
<br>
</span>I just found myself physically shaking my head at some of the more<br>
authoritarian-bent emails in this thread.<br>
<br>
In KDE we have a GSoC team that's been taking care of GSoC and other student<br>
programs for years now, and these people are intimately familiar with GSoC<br>
dynamics on slot allocation and are thoroughly aware of the costs and benefits<br>
of allowing external projects to take part in GSoC under the KDE \
umbrella.<br></blockquote><div><br></div><div>That doesn't mean you can do \
whatever you want though,</div><div>even more so when it's a small group with no \
outer access.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> It would be toxic to try to \
micromanage the Krita team, the sysadmin team or<br> the WikiToLearn team: KDE has \
historically worked best when those who do the<br> work decide how it's done.<br>
<br>
So here's a novel idea: how about we let the GSoC team do what they are good<br>
at and come up with their own policies and decisions in GSoC-related matters?<br>
At best, any concerns should be brought up with them on the relevant mailing<br>
list, rather than appointing ourselves as overseers in this \
thread.<br></blockquote><div><br></div><div>I did last week and where I got told to \
post it here. After all</div><div>it should be a community \
decision.</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