Re: [kde-community] Open Public Consultation: Revision of the European Interoperability Framework

2016-05-11 Thread Teo Mrnjavac
On mercoledì 11 maggio 2016 11:25:00 CEST Jos van den Oever wrote:
> The EU is asking input from its citizens on the next version of the European
> Interoperability Framework.
> 
> KDE has a traditional position in Europe and would benefit from a clear
> direction towards completely open standards (*not* FRAND which make FOSS
> implementations nearly impossible) and strong preference for FOSS.
> 
> I think members of KDE have the right knowledge for filling in this
> consultation. Please take some time to do so.
> 
> http://ec.europa.eu/isa/consultations/
> 

Done. This is very important, thank you for bringing it up.

Cheers,
-- 
Teo Mrnjavac
http://teom.org | t...@kde.org
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

Re: [kde-community] Should we allow non-KDE projects to participate in GSoC under KDE?

2016-02-05 Thread Teo Mrnjavac
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.

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.

Cheers,
-- 
Teo Mrnjavac
http://teom.org | t...@kde.org
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

Re: [kde-community] Have repo maintainers opt-in for github mirroring (was: Re: Official KDE mirror on github)

2015-09-19 Thread Teo Mrnjavac
On Saturday, September 19, 2015 13:04:55 David Edmundson wrote:
> > > I was under the impression they were disabled by the options we had
> > > selected. Unfortunately that is not the case.
> > 
> > Thanks for clarifying on this.
> > 
> > I hope they can still be disabled.
> > 
> > They can't. I had spent some time looking before. Sorry.
> 
> However, we have solid hard data that it's a non-issue.
> 
> Gnome has been mirrored on github for nearly 2 years, in that time GTK has
> had a grand total of 4 pull requests over time.
> Most others (gedit, cheese, epiphany) have had 0.
> 
> Interestingly they have had literally hundreds of github "forks", which
> implies it has led to sustantiable numbers of patches back using the
> traditional methods
> 
> I've made a wiki page, which says how to turn a pull request into a
> reviewboard submission.
> https://techbase.kde.org/Development/GithubMirror
> 
> If we get any questions we can then just copy and paste that, and don't
> need to spend any time explaining. Bam, done.
> 

Thank you David, for your get-things-done approach in this controversial and 
tense situation. It is really much easier to solve than it seems from all 
these threads.

I'm personally in favor of letting projects decide whether to allow GitHub 
pull requests or not, but regardless of the final decision it is good to 
already have practical solutions like this techbase entry.

I find it unfortunate that some long time KDE contributors feel that KDE goals 
are threatened by all this. I understand their concerns, but I assign those 
concerns a different priority score. In fact, the inflexible policy towards 
3rd party (including proprietary) infrastructure and processes we have in KDE 
deters me from bringing some of my own (currently GitHub-hosted) work under 
the KDE umbrella, as this would hinder some very productive working 
relationships with our downstreams and potentially result in *less* free open 
source software being produced, deployed and used.

It is also a fact that KDE is an aging community, and in its future I expect a 
slow decline unless we find a way to bring in a steady influx of new 
contributors. Recruiting a new generation of hackers is something that's just 
not happening fast enough at this point (our yearly GSoC stats are an 
indication of that). GitHub could be a very powerful instrument in turning 
this trend around by tapping into a huge talent pool and pushing people 
towards our own infrastructure while still allowing them to get started 
through an environment they already know.

Cheers,
-- 
Teo Mrnjavac
http://teom.org | t...@kde.org
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

Re: [kde-community] Have repo maintainers opt-in for github mirroring

2015-09-19 Thread Teo Mrnjavac
On Saturday, September 19, 2015 16:25:13 Luigi Toscano wrote:
> Teo Mrnjavac ha scritto:
> > It is also a fact that KDE is an aging community, and in its future I
> > expect a slow decline unless we find a way to bring in a steady influx of
> > new contributors. Recruiting a new generation of hackers is something
> > that's just not happening fast enough at this point (our yearly GSoC
> > stats are an indication of that). GitHub could be a very powerful
> > instrument in turning this trend around by tapping into a huge talent
> > pool and pushing people towards our own infrastructure while still
> > allowing them to get started through an environment they already know.
> 
> I disagree on this point. Other non-aging projects are staying successfully
> away from Github.
> 

KDE can indeed be a non-aging project without GitHub, I never meant to imply 
otherwise. This is not an all or nothing situation. I'm in favor of improving 
recruiting through other channels as well.

But I believe a GitHub mirror with the option of pull requests can contribute 
to growth, and I'm in favor of using it for this reason.

-- 
Teo Mrnjavac
http://teom.org | t...@kde.org
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community