Re: [kde-community] licence policy updates

2014-02-17 Thread Thomas Pfeiffer
On 16.02.2014 22:14, Michael Pyne wrote: On Sun, February 16, 2014 19:06:07 Lydia Pintscher wrote: On Sat, Feb 15, 2014 at 2:03 AM, Michael Pyne wrote: Perhaps something similar exists online as well. http://choosealicense.com/ (developed by github after people were annoyed that so much unli

Re: [kde-community] Fwd: praises and suggestions for the KDE team

2014-02-17 Thread Sebastian Kügler
On Friday, February 14, 2014 13:00:57 Jeff Mitchell wrote: > I thought this was a really nice letter that was sent to us, so I'm > passing it on to the community. I did already get in touch with him > about the 4.0 release, but I'm happy to forward along responses on any > other topic. Just a q

[kde-community] updating kde.org/contact

2014-02-17 Thread Jos Poortvliet
Hi, At some discussion, it came up that kde.org/contact is quite a bit outdated. Some of these folks are indeed still contact people, others are not. Another issue is that on the top of the page, it does not give much hints about where to bring what subject. It might be valuable to note that: *

Re: [kde-community] Future Git Plans

2014-02-17 Thread Alexander Dymo
That said, last time I tried it was a resource consumer monster, has that been fixed? Is it going to scale KDE size? It's a Rails app. Those tend to use more resources. But deploying with Ruby 2.1 might have a huge difference performance-wise. ___ kde

Re: [kde-community] Future Git Plans

2014-02-17 Thread Paul Gideon Dann
On Monday 17 Feb 2014 08:03:24 Alexander Dymo wrote: > > That said, last time I tried it was a resource consumer monster, has that > > been fixed? Is it going to scale KDE size? > > It's a Rails app. Those tend to use more resources. But deploying with Ruby > 2.1 might have a huge difference per

Re: [kde-community] Future Git Plans

2014-02-17 Thread Giorgos Tsiapaliokas
On 02/15/2014 05:52 AM, Jeff Mitchell wrote: This email serves two purposes: one, to inform the community of the direction we would like to go with KDE's Git hosting and request feedback; +1 :) two, to ask for volunteer projects that are willing to act as crash test dummies for the new system