Can we please lower the temperature on this discussion a bit?
On Wed, Dec 9, 2015 at 1:54 AM, Ben Cooksley wrote:
> On Wed, Dec 9, 2015 at 4:37 AM, Jan Kundrát wrote:
>> On Tuesday, 8 December 2015 16:09:43 CET, Nicolás Alvarez wrote:
>>>
>>> It is irrelevant what our personal preference about d
I just submitted a request to Ubuntu to upgrade their list infra. I
showed Ben a sample email header and they were not compliant. I
included a link to Ben's explanatory post:
http://marc.info/?l=kde-core-devel&m=144956641505429&w=1
It took less than five minutes to file the ticket.
All the best,
Hi all,
On Thu, Mar 3, 2016 at 2:41 PM, Sebastian Kügler wrote:
> Hi Joao,
>
> On Thursday, March 03, 2016 19:36:05 Joao Matos wrote:
>> Hi Sebastian and the rest of the KDE community,
>>
>> I'd like to propose to mentor Dimitar but I have no idea what the policy of
>> the KDE project
>> is regar
I realize I'm slightly orthagonal to the original topic, but
On Sat, Mar 5, 2016 at 11:14 PM, Kai Uwe Broulik wrote:
> Hi,
>
>> Distributions set up distribution-wide "Sans", "Serif" and "Monospace"
>> aliases for a reason. The fonts are carefully selected by the distribution
>> based on a
Hello to all readers. I'm writing to you to ask you to mentor this
student who needs a primary mentor. The Dolphin maintainer and
community can't step up and do this, although the maintainer can help.
Pinak Ahuja has offered to be backup co-mentor already. Anyone
somewhat familiar with Baloo and/or
Hi folks, I have no announcements, but was thinking about our Season
of KDE and how we can enlarge and improve it. I believe we've been
thinking of it too much like GSoC, when it can be so much more.
For instance, I've seen a few announcements from maintainers wanting
to step back from a large pie
I've just finished preparing the new Ideas page for 2017:
https://community.kde.org/GSoC/2017/Ideas
It is basically the same as every other year, and has no previous
ideas on it. If you or your project plan to present a former idea
again, click on the 2016 Ideas link, and copy/paste it into the 20
On Fri, Jan 13, 2017 at 1:38 PM, Valorie Zimmerman
wrote:
> I've just finished preparing the new Ideas page for 2017:
> https://community.kde.org/GSoC/2017/Ideas
>
> It is basically the same as every other year, and has no previous
> ideas on it. If you or your project plan
Hello GSoC mentors, and teams supporting mentors,
We've asked for more time to get ramped up for GSoC, and so the
calendar has been moved back to early February. However, that means
that our Ideas page needs to be filled NOW, so that it can be taken
into consideration once the Org Applications are
Hello GSoC mentors, and teams supporting mentors,
TL;DR: Fill out https://community.kde.org/GSoC/2018/Ideas; read
https://community.kde.org/GSoC. Now.
Every year, we've asked for more time to get ramped up for GSoC, and so now
is the time for organizations to apply[1]. We have begun to write our
to it for the last email.
Valorie
On Wed, Jan 10, 2018 at 3:03 PM, Valorie Zimmerman <
valorie.zimmer...@gmail.com> wrote:
>
> Hello GSoC mentors, and teams supporting mentors,
>
> TL;DR: Fill out https://community.kde.org/GSoC/2018/Ideas; read
> https://community.kde.org
Hello folks, as you know, I'm not a coder. However, I'm interested in our
code quality, and there has been some observation that "lots of patches get
missed, and submitters get confused due to a lack of auto-populated
reviewers" on Phabricator. Nate Graham has been adding groups to the
reviewers by
On Sun, Jun 30, 2019 at 11:47 PM Kai Uwe Broulik
wrote:
> Hi,
>
> > In our move to Gitlab, we can do better.
>
> Given Gitlab emails contain even less information and context than
> Phabricator which themselves contained even less information and context
> than Reviewboard back then, I don't see
2019 at 2:53 PM Valorie Zimmerman <
valorie.zimmer...@gmail.com> wrote:
> Hello folks, as you know, I'm not a coder. However, I'm interested in our
> code quality, and there has been some observation that "lots of patches get
> missed, and submitters get confu
Hey Ben and developers,
On Fri, Oct 4, 2019 at 7:11 PM Ben Cooksley wrote:
> Hi all,
>
> Recently we had a discussion (which I think may have ended up spread
> over a couple of mailing lists in the end) concerning branches and the
> ability to force push to them.
>
> Current policy forbids force
On Sat, Nov 23, 2013 at 8:58 AM, Alexander Neundorf wrote:
> Hi,
>
> for very happy personal reasons (since Tuesday, named David :-) ) I'll have
> significantly less time for KDE in the future.
> Still I'll stick around and try my best.
>
> Alex
>
> P.S. no, it is not because of dfaure ;-)
Congra
Hello folks,
I've been reading the very intense discussion about the future of our
infrastructure, and the passion is good to see.
I hope all of the participants will keep in mind that we are thinking
together about the future of KDE, not supporting products or
positions. Already I've heard one p
Comment often heard: we've lost $person / we're missing people to
maintain/lead/do $project. This is understandable, and to be expected
in a large, mature project such as KDE.
However, in #kde and #kde-devel IRC channels we have new people almost
daily trying to find some way to get involved with
loved applications, teams, or areas in KDE.
Please add to the list here:
http://community.kde.org/KDE/Finding_The_Unloved .
All the best,
Valorie Zimmerman
Member, Community Working Group
http://about.me/valoriez
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks, last month a team of three young developers and one
non-devel were sponsored by Google to Google's first documentation
sprint, along with 3 other teams: OpenMRS, OpenStreetMaps, and Sahana
Eden. Each team wrote a book that week which was publ
20 matches
Mail list logo
