On Monday 11 November 2013 10:10:56 Thomas Zander wrote:
Could you please explain to those that don't immediately spot it how the
before and after are functionally different?
Of course.
There's two halves to the access model:
* All KDE contributor accounts must have direct write access.
On Monday 11 November 2013 10:54:52 Aaron J. Seigo wrote:
iow, it has solved nothing.
No, I believe you're actually overlooking a broader point
here. Codifying the access model is a lot less about actual
ACL, and more about the implications it has for *people*,
both existing contributors, but
On Monday 11 November 2013 11:12:12 Aaron J. Seigo wrote:
so if the ONLY clause was somehow intended to address the “second class
citizen” issue, it should be evident how it can not do so in its current
form and also remain consistent with KDE’s current, consensus culture.
It's not evident to
On Tuesday 12 November 2013 16:43:27 Cornelius Schumacher wrote:
When I read the suggestion and this explanation I wonder why we don't just
say what is meant: The canonical version of the project is hosted on KDE
infrastructure?
This doesn't cover the part that all KDE contributors have
On Tuesday 12 November 2013 22:53:18 Thomas Zander wrote:
All these may actually exclude the stuff that is used to create the
deliverables. If you use gimp to draw, the gimp file is imporant, but the
asset and deliverable is typically used for the png you export.
So I'm assuming we want the
+1 from me, too, though iirc native speakers requested 'writable by' :)
Cheers,
Eike
PS.: On vacation and off email until Tuesday.
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
Translations are always a bit 'risky' of course but I
think in the spirit of inclusiveness and internationality
they're a great idea.
I'd volunteer to work on a German translation over the
holidays unless anyone else has a stronger urge. This
kind of thing needs careful peer-review of course but
My 2 cents on this: I agree that Albert's original phrasing here
wasn't great, and I wouldn't have ignored it myself.
Assuming good intentions has to go both ways, and reacting to a
*question* (like Should we do these as Plasmoids?) with You're
going to kill my baby seals, I know it! is exactly
On Monday 20 January 2014 17:13:47 Yichao Yu wrote:
QtCurve (although being not very polished) is already stable and have
made several releases that are packaged by a number of distributions.
Is there anything I am missing here?
I think Kevin just wanted to point out there's an additional
wiki
Hi,
we get to welcome QtCurve to KDE today. \o/
The migration is done, the code now resides in kde:qtcurve
and Bugzilla and ReviewBoard have been set up as well.
The KDE i18n crew is currently working on integrating the
existing translations into their infra and letting scripty
loose on them.
On 26.08.2014 22:05, Milian Wolff wrote:
That would leave kde-devel for what it's been used for the past 15 years:
discussing development of applications that are tightly integrated with
KDE's desktop environment (i.e., Plasma desktop).
I like that suggestion!
My 2 cents: KDE is a the name
On 27.08.2014 07:11, Aaron J. Seigo wrote:
The way I've seen the goal for years is something like this:
* applications should run great everywhere they can
* applications deliver an even *better* experience when paired with Plasma
You know, a little both/and :)
+1, yeah :)
Cheers,
Eike
On 15.09.2014 14:58, Thomas Pfeiffer wrote:
Where we don't use many of our own products, though, is on the infrastructure
side.
That's not actually true, btw:
- identity.kde.org is us
- ballot (the e.v. voting software) is us
- commits.kde.org is us
- our commit hooks are us
- ditto the
On 12/08/2014 11:33 PM, Laszlo Papp wrote:
On Mon, Dec 8, 2014 at 10:02 PM, Alex Merry alex.me...@kde.org wrote:
As Valorie said, if you want more female talk submissions,
I am afraid that I am personally not yet sure whether I wish that. I
am not going to those places and events to see
On 09/19/2015 08:58 PM, Kevin Krammer wrote:
> Even using a review tool in the first place is something that the maintainer
> asks people to do.
No. We advertise ReviewBoard (and later Phab) as a general
interface to throw code at our maintainers. "I don't look
at ReviewBoard" is not a
On 09/19/2015 08:43 PM, Kevin Krammer wrote:
> Well, the github side review will make the job of the KDE contributor who
> brings the patch into KDE a lot easier, because when they put the patch up
> for
> review as "their" contribution, most of the things that the contributor knew
> about
On 09/19/2015 09:55 PM, Kevin Krammer wrote:
> Exactly.
> So why would one continue to do the prelimiary review in addition to the
> required one?
> As soon as there is a stream of patches from a new contributor, that
> contributor will be asked to get an account of their own.
> Need for
On 09/19/2015 09:13 PM, Jaroslaw Staniek wrote:
> Could you mention at least one KDE git repo that belongs to multiple
> projects? And thus maybe multiple even multiple groups of maintainers?
I have previously in the thread: Different subfolders in
plasma-desktop.git have different maintainers,
On 09/19/2015 09:36 PM, Kevin Krammer wrote:
> So, right now, a maintainer is expected to check reviewboard even if they are
> content with all holders of commit accounts to push directly.
> But that as soon as there is a second option, then not checking reviewboard
> becomes acceptable?
On 09/19/2015 08:13 PM, Kevin Krammer wrote:
> I am afraid my understanding of the technical background of this is still too
> hazy.
> How would review "move" from KDE to github?
> If review on reviewboard is required (per project's unwritten social
> contract), it cannot not happen.
> If it
On 09/19/2015 08:25 PM, Kevin Krammer wrote:
> Saying "I don't look at the KDE review tool" would be like saying "I am not
> interested in your patch".
Saying "My personal productivity and efficiency matters more
to me in the long-run than your patch, so please use the tool
I prefer to reach
On 09/01/2015 10:08 PM, Boudhayan Gupta wrote:
> Ladies and gentlemen, I'll take a decision on this in the next couple
> of days. As it stands now, Pixie is a universal favourite but we can't
> use it for copyright reasons.
>
> Kapture seems to have the most number of votes, so if nothing
On 09/18/2015 08:47 PM, Boudhayan Gupta wrote:
> While it is a bit late now (the repository rename was done yesterday),
> I'm still in love with the word Selfie (for the above reasons and
> more). I'm heavily considering requesting another rename to Selfie.
FWIW I feel bad about causing more
On 09/18/2015 09:12 PM, Sune Vuorela wrote:
> Yes. I'm against. And I'm also against mirroring on github, but I didn't
> voice my opinion by that because it was said that issues and pull
> requests are not to be enabled.
>
> We should not proprietarize our development workflow. We should not
On 09/20/2015 01:31 PM, Anne Wilson wrote:
> Hehe! Only on a KDE list could an exhortion to stop bikeshedding become
> the latest bikeshed!
The Debian community is currently having a bikeshed over
whether to call a new community tool Bikeshed. We can't
hope to compete.
> Anne
Cheers,
Eike
On 09/20/2015 02:26 PM, Loïc Grobol wrote:
> Let's try not to be extreme. If someone was able to post a pull
> request, they should be able to switch to Phab if they want to
> participate when notified.
Let's not be naive, either. People are lazy. That's been
one of the arguments for enabling
On 09/19/2015 02:12 PM, Myriam Schweingruber wrote:
> Some of you wanted the mirror on Github because apparently there are
> developers out there who are too lazy (or too dumb) to learn to use
> new tools. Are those developers we want?
Developer recruitment should be our #1 problem for the
next
On 09/19/2015 11:35 AM, Vishesh Handa wrote:
> Then we will deal with them on a case-by-case basis. Lets not take
> blanket bans on new ideas just because of their potential destructive
> power. Each action of ours has positive and negative benefits. How
> about we focus on the positive?
You're
On 09/19/2015 07:32 PM, techie.raj...@yahoo.in wrote:
> I search apps on google all the time, some time in youtube to see a demo of
> it.. Searching for selfie will result in all the smartphones, all the
> different
> selfie related stuff which is currently viral among the masses.
Yeah. And
On 09/19/2015 07:52 PM, Kevin Krammer wrote:
> You mean that a KDE project would ignore your review request it it comes from
> reviewboard/phabricator?
I think that's a realistic, even likely concern. We already
know that some devs don't like using multiple code review
sites concurrently from
On 09/19/2015 10:32 PM, Kevin Krammer wrote:
> I don't see there this github review is coming from.
Review is an interactive process where you ask for changes and
iterate. Once you open the door to doing it on GitHub, you will:
* Have a hard time making some contributors understand why
they
On 09/19/2015 06:22 PM, Martin Graesslin wrote:
> And how do we do that? Can we enforce this technically or will that be
> weakened over the time the same way as we just turned the mirror into "let's
> accept pull requests"?
This wishy-washy stuff is nonsense. The sole argument for enabling
On 09/19/2015 06:53 PM, Riccardo Iaconelli wrote:
> On Saturday, September 19, 2015 06:44:24 PM Martin Graesslin wrote:
>> No reality would be that it slowly moves code review from KDE to github. And
>> I think we have here quite some people in the discussion who would love to
>> see that
>
>
On 09/19/2015 06:57 PM, Vishesh Handa wrote:
>> The topology of 'project' is not a match to our repository
>> topology, which is incidental and an implementation detail.
>> It's not possible to cleanly turn GitHub on or off along
>> the - ever-shifting - social boundaries involved.
>>
>
On 09/19/2015 05:54 PM, Riccardo Iaconelli wrote:
> while rejecting them autmatically isjust a great way to drive potential
> contributors away...
Which is a good reason why the mirror shouldn't have happened
- regret being on vacation during that time.
Cheers,
Eike
On 09/19/2015 05:58 PM, Vishesh Handa wrote:
> We already use some other forms of code review -
>
> * IRC
> * Email
> * IM
> * Google+ Hangouts (Just discussed some things related to the Baloo
> KCM a week ago)
> * Knocking on David's door and screaming "I need you to look at some code"
I
On 04/27/2016 01:58 AM, Teo Mrnjavac wrote:
This, so much. I see no reason not to expand our presence in different
segments of the e-mail clients market, if Thunderbird wishes to join us. The
more, the merrier.
I'm not sure they're a good fit for us, unless they bring significant
On 04/27/2016 06:36 PM, Daniel Vrátil wrote:
I like the idea of having Thunderbird in KDE. It shows that we are an open
community and welcoming towards "outside" projects and of course it would be
also a good PR for both sides.
No, it wouldn't. The message wouldn't be "KDE community is open
On 04/27/2016 10:13 PM, Jos van den Oever wrote:
Looking at the commit logs of Thunderbird, the programs certainly does not
seem dead at all. Last month there were on average two commits per day by 18
authors.
Have a look at the actual commit logs. There's a gap between December
'15 and
On 04/27/2016 04:02 AM, Laszlo Papp wrote:
I would even go further claiming that many (most?) KDE projects have
never made it to that level, so for me, Thunderbird as a project is
something to look upon even if it is currently having issues to be resolved.
Yes yes, I get you're very eager to
On 04/27/2016 03:20 AM, Laszlo Papp wrote:
Given how respected, appreciated and well-used Thunderbird has been in
my experience, including industrial environments (only dream for certain
KDE subprojects?), I would suggest having a bit more good faith at this
point. Such early conclusions have
Some badly sorted (it's too late and we're tired!) impromptu impressions from
our birthday get-together at the Han river!
Event prep: http://imgur.com/a/zB5Tu
Main event: http://imgur.com/a/1w7sg
Cheers,
Eike
I'm proud of:
* Collectively making tons of software that has real users. I consider
my profession as an engineer to be a tool-maker who enables others; our
line of operation is to build civilization and facilitate culture.
Making and shipping software that people use is the most concrete way we
On 12/12/2016 07:27 PM, Elvis Angelaccio wrote:
> On Sun, Dec 11, 2016 at 10:35 PM, Luigi Toscano
> wrote:
>> I would introduce an ASSIGNED state so that developers that want to mark that
>> they have acknowledged it and they are going to work on it can do it.
>
>
On 08/15/2017 07:47 AM, Lydia Pintscher wrote:
> On Mon, Aug 14, 2017 at 4:48 PM, Mirko Boehm - KDE wrote:
>> I have seen only agreement and support for the porposal. What would be the
>> required steps to make an official announcement, and encourage people to
>> participate?
>
On 08/09/2017 07:19 AM, Thomas Pfeiffer wrote:
> Must-have:
- dfaure is there so I can ask KIO questions
(IRC fails that currently.)
Cheers,
Eike
I've given some more thought to Matrix as a contender and I'm
increasingly liking this option among the available contenders.
The available Matrix clients are currently not quite as polished
as their competition (specifically Slack/Discord), but Matrix
does have their features in its scope,
On August 11, 2017 4:22:04 AM GMT+09:00, Thomas Pfeiffer
wrote:
>On Donnerstag, 10. August 2017 20:38:11 CEST Christian Loosli wrote:
>> Am Donnerstag, 10. August 2017, 20:31:22 CEST schrieb Thomas
>Pfeiffer:
>> > On Donnerstag, 10. August 2017 18:40:34 CEST Christian
On 08/12/2017 04:22 AM, Boudewijn Rempt wrote:
> On Fri, 11 Aug 2017, Boudhayan Gupta wrote:
>
>> Here's a radical proposal: why don't we just work towards improving the IRC
>> protocol, make the protocol available over WebSockets, and try to push the
>> whole thing as a W3C informational RFC?
On 08/14/2017 05:30 PM, Ivan Čukić wrote:
> Hi all,
>
> While I do see the point behind 'off-by-default', I think it will ruin
> the purpose since nobody will turn it on.
>
> I'd propose having it on by default (at least) for pre-releases.
I'm not convinced. KDE publically runs on a platform
On August 16, 2017 6:58:35 PM GMT+09:00, Ilmari Lauhakangas
wrote:
>I want to note that I was intrigued by Eike's mail about a possible Qt
>Quick -based Konversation reboot. I suggested I could try and gather
>funding to get it to a releasable state, but he
I guess as KDE's "IRC guy" (I maintain Konversation) I should chime
in here.
I like IRC. I regard IRC as important. I think without IRC none of
the past 20 years of KDE would have happened, and the reasons for
IRC being a successful technology for us and many others start
with "chatting is nice"
FWIW, I didn't keep up with Matrix to well in recent times, but
I remember having a look at it back when it made its first
splash (the LWN article at all) and at the time I considered
it the most promising-looking IRC replacement attempt yet.
It had some of the traits of other attempts that
On 08/09/2017 01:16 AM, Luigi Toscano wrote:> We have an alternative
already working, which bridges IRC (freenode.net and
> OFTC): matrix.org.
> I don't know how many times I should repeat this, but many people are already
> using successfully (I monitor few channels, for example).
>
> So -1
FWIW, I moderate a ~300k subscriber subreddit on the side, and that community
substantially migrated away from Snoonet to Discord. I see that a lot on reddit
now.
Cheers,
Eike
--
Plasma, apps developer
KDE e.V. vice president, treasurer
Seoul, South Korea
On August 9, 2017 9:10:15 PM GMT+09:00, Jos van den Oever
wrote:
>Op woensdag 9 augustus 2017 13:50:46 CEST schreef Harald Sitter:
>> On Wed, Aug 9, 2017 at 1:39 PM, Boudewijn Rempt
>wrote:
>> > On Wed, 9 Aug 2017, Riccardo Iaconelli wrote:
>> >> This is
etc.)
Team Kit
* Crew shirt - please wear whenever doing KDE duties (booth, room)
* Name tag - affix to shirt
Team Communication
Telegram group: https://telegram.me/joinchat/Azsz2AFTa7HE0h8CLPzFpQ
Team Coordinator
Eike Hein <h...@kde.org>
IRC: Sho_
Telegram: @eikehein
Phone: +821028995948
B
On September 5, 2017 8:15:47 AM GMT+09:00, Thomas Pfeiffer
wrote:
>Here are the results of the survey:
>https://sessellift.wordpress.com/2017/09/05/results-of-the-requirements-survey-for-a-kde-wide-chat-solution/
>Now it's time for us to find a solution that fits the
Heya,
Paul opened a Phab task on the KDE Promo workboard which I think
we can use to coordinate content:
https://phabricator.kde.org/T6840
I've added a few people there and seeded the ticket with a recap
of what I think we need to communicate to the audience at QtWS.
If you're interested in
On 08/21/2017 06:13 PM, Paul Brown wrote:
> We'll co-ordinate with Jens so that the content matches the format of the
> flyer.
Here's the Phab task used for coordination:
https://phabricator.kde.org/T6840
Everyone interested in working on flyer/demo content or expecting to do
booth duty and
Hi everyone!
Text input is the foundational means of human-computer interaction: We
configure or systems, program them, and express ourselves through them
by writing text. It's how our software is made, and it's how it's
consumed. It's how users and developers connect with each other.
Yet text
Hi!
I decided to start a new thread because no one reads monster threads :)
Things to talk about:
(1) QtWS KDE team
Currently I have gotten responses from:
* Eike (yes I talk to myself)
* Helio
* Rohan
* Adriaan
* Aleix
* Sune
* Mirko
* Leinir
* Boud
* Bhushan
* Scarlett
That's 11 people,
On 08/25/2017 05:05 PM, Clemens Toennies wrote:
> Hi,
>
> I know I'm late, but if it's of interest I could bring an Odroid C1+ ARM
> board and ARM64 Pinebook with latest Plasma for demonstration purposes
> at the booth.
Not late at all!
We still have several slots for people we can bring. If
On 09/05/2017 08:15 AM, Thomas Pfeiffer wrote:
> Here are the results of the survey:
> https://sessellift.wordpress.com/2017/09/05/results-of-the-requirements-survey-for-a-kde-wide-chat-solution/
> Now it's time for us to find a solution that fits the profile!
Here's some thoughts from the
I'm planning to continue my work to modernize the user interface of
Konversation and adding Matrix support.
Based on the IM Survey we did recently spearheaded by Thomas Pfeiffer,
we know the community has a problem with the increasing fragmentation
and migration of KDE's comm channels to
Hi,
I'm happy to announce we're going to have another Plasma sprint
in a few months, from April 21st to April 27th in Berlin, Germany.
Join the sprint to make all things Plasma even better in an
intense-but-fun week of planning, designing and hacking!
The sprint will be held at the offices of
On 07/19/2018 09:25 PM, Jonathan Riddell wrote:
> As I say I am aware of the process and the need for restrictions. But
> I have access to KDE social media and have done since we started
> having any. But for some reason I am being blocked from this one
> account. Nobody has yet said who by
Hi,
I agree the "unnamed" and not having good docs (hello again, topic)
on this is bad.
There's a long history of the web presence being treated in a special
way, though. Even in the good old CVS/SVN days, you needed a special
permission bit to be able to commit to www/ doled out by sysadmin
Hi Boud,
I think the main missing context here is that this email doesn't mean this is
the only thing we are considering spending resources on, nor does it indicate
priority.
We've collected a lot of ideas from all over the community and are analyzing
them and investigating them. In the case
On 10/29/18 1:31 PM, Jonathan Riddell wrote:
> More coverage on last week's LWN
> https://lwn.net/Articles/768483/
>
> Discussing it in person it was pointed out that we do already use
> Phabricator Workboards for much discussion and it might well overlap
> there, although I don't think that
Hi,
Qt World Summit 2018 is coming soon - this year it'll be a
smaller-scale, single-day event. Again in the bcc in Berlin, on December
6th.
Last year we managed to significantly raise the bar of KDE's presence at
the event, with a coordinated visual theme backed by assets such as crew
shirts,
Hi,
of course "being insulted" is very much in the eye of the beholder.
I'm very tired of this accusation being thrown around, so let's do real talk
and summarize the situation according to my best knowledge of events:
Jonathan Riddell sold KDE mechandising (t-shirts) at FOSDEM to attendees.
Hi,
the e.V. board will definitely discuss this issue as well in this week's
call, to put some thought into the legal side vis-a-vis GDPR compliance.
I think the community will here is clear and non-controversial, we
collectively just need to think about how to do it properly. We'll
report
On 2/21/19 6:56 AM, Boudewijn Rempt wrote:
* Matrix now logs #krita on freenode (well, it has been doing so for quite some
time, since the first bridge user appeared)
* We have always tried to make sure #krita has no permanent logs; we don't want
that.
It's possible in the channel
On 2/21/19 8:46 PM, Filipe Saraiva wrote:
2. What are the reasons to use a server owned by a company, not by us? I
don't want to start a flamewar, just know the reasons and motivations.
Hosting a Matrix server currently requires a quite beefy box, and is
also somewhat
On 2/21/19 6:59 PM, Boudewijn Rempt wrote:
Do you know how I can do that? I have no idea myself...
1. Log into Matrix, join #krita:kde.org
2. Log into your freenode nickserv account from Matrix - upon doing #1
you'll have gotten an automatic private chat called "Freenode Bridge
Status"
On 3/18/19 6:38 PM, Boudewijn Rempt wrote:
I'm sure people are working hard on fixing things up, but right now
webchat.kde.org just does not work. If I look in at the Krita channel on
webchat.kde.org, the last message is from 23:01 yesterday.
The Matrix folks told us they're working with
On 2/20/19 7:04 PM, Boudewijn Rempt wrote:
There's the
https://kde.modular.im/_matrix/consent?h=6fc7fefb99181b28ffdf2be32225ead05a8cd6c148da23482edbcc4b08ce7ddd=boud
page you need to agree to before one can join. And it asks people to confirm that
they're older than 16.
Why do we have
On 2/20/19 7:14 PM, Boudewijn Rempt wrote:
Maybe the text could be changed to "You're over 16 or have parental permission"
?
Matthew @ Matrix says since it's our own server the legal responsibility
can pass on to us, and it's possible to set any age threshold we want.
So we can do it;
Maybe we could do a static mirror and keep it up read-only?
Cheers,
Eike
On February 3, 2019 6:29:49 PM GMT+09:00, Kenny Duffus wrote:
>On Sunday, 3 February 2019 09:25:32 GMT Kenny Duffus wrote:
>> On Saturday, 2 February 2019 19:45:40 GMT Ben Cooksley wrote:
>> > We'll be shutting this
I'm a bit conflicted about this. Random drive-by patches are one thing,
but when I engage with new contributors, my hope is they'll be coming
back and walk a path to a dev account and a long-term commitment to the
KDE developer community.
To me, the KDE developer community is one built on
I think this discussion has sort of strayed, if understandably so. Maybe this
helps:
- A lot of projects currently use Phabricator tasks and rely on them heavily.
- The GitLab equivalent are Issues.
- We're trying to replace Phabricator with GitLab.
- If Issues are disabled, we can't import the
ate a category for it and allow to filter, as we
>already
>allow to filter by language.
>
>Kind regards,
>
>Christian
>
>Am Donnerstag, 5. Dezember 2019, 13:36:36 CET schrieb Eike Hein:
>> If and when the Planet becomes majority political content, that's a
>prob
against reading a cycling trip in Europe (just an
>example
>from the past) which is not so divisive as politics and Brexit in
>particular.
>
>On Thu, Dec 5, 2019 at 12:36 PM Eike Hein wrote:
>
>> If and when the Planet becomes majority political content, that's a
>> probl
Hi,
Let's remember we had this debate before and it lead to the rules in the "Add
Your Blog" popup, under which this blog post is currently fine.
If you want the rules changed you need to make a good case for why the
situation is different and warrants reevaluation, otherwise you're tilting at
But they don't, so your calculation is about solving a problem that doesn't
currently exist.
Cheers,
Eike
On December 5, 2019 1:21:08 PM GMT+01:00, Christian Loosli
wrote:
>For me it's a rather simple calculation: if every contributor on planet
>would
>post as many articles on politics as
with
something.
Cheers,
Eike
On December 5, 2019 1:26:58 PM GMT+01:00, Christian Loosli
wrote:
>Am Donnerstag, 5. Dezember 2019, 13:24:30 CET schrieb Eike Hein:
>> But they don't, so your calculation is about solving a problem that
>doesn't
>> currently exist.
>
>I conside
feigning concern.
This strikes me as agitated and emotional at best, and destructive and immature
behavior at worst.
This is not the venue for mudslinging of this kind, and if you want to have a
productive discussion of your topic you should own up and apologize for it
before engaging further.
Dear community,
Happy new year!
Recently, we've gotten approached a few times with offers of venues for KDE
events/sprints. One such case was the MBition office, which resulted in the
recent Frameworks 6 sprint held there. Another is the foss-north 2020 Community
Day, which Adriaan sent an
4, 2020 6:06:50 PM GMT+01:00, Nate Graham wrote:
>Could this large venue suffice for Akademy?
>
>Nate
>
>
>On 1/4/20 7:01 AM, Eike Hein wrote:
>> Dear community,
>>
>> Happy new year!
>>
>> Recently, we've gotten approached a few times with o
to navigate
this complex situation together. We've had opportunities to be invited to some
of the KFQF meetings and participate directly, which we would like to thank the
entire KFQF for.
The update reflects our shared view on the subject.
Best regards,
Eike Hein
-
KDE e.V. Vice President
since I wouldn’t be pulling the load this should be treated as “random
> dude talking”.
>
> Sent from Phone, hence short mail
>
>> On 9 Apr 2020, at 16:27, Eike Hein wrote:
>>
>>> Let's not throw the baby out with the bathwater.
>>
>> This
Even in the best of times, it's always a good idea for stakeholders
in the open Qt ecosystem to maintain open lines of communication.
The KDE e.V. board can be reached at kde-ev-bo...@kde.org and is
happy to receive meeting inquiries.
Best regards,
Eike Hein
-
KDE e.V. Vice President
will
continue to do what we do best - work closely together in
the open for the benefit of Qt and its users.
That is to say to others -- Qt Open Governance has been a
collaborative and coordinated effort with close
communication and will continue to be.
Best regards,
Eike Hein
-
KDE e.V. Vice President
> Let's not throw the baby out with the bathwater.
This is very true.
The KFQF with all representatives remains actively
working on the issues with the same mission state-
ment, too.
Cheers,
Eike
-
KDE e.V. Vice President
Hi everyone,
As announced during the board report at Akademy, one of the board's
goals for 2020 is to support an open source-friendly hardware ecosystem,
spurned by the KDE community's successful foray into more hardware
partnerships over recent years.
In this context, we'd like to point out
reports[0] or to reach out to me
directly.
0 = https://ev.kde.org/reports/ev-2019/
Cheers,
Eike Hein
-
KDE e.V. Vice President, Treasurer
Hi everyone,
Some time ago, KDE e.V. decided to contract work to help the KDE community with
its efforts to maintain and improve KDE's technical documentation, broadly
similar to how KDE e.V. also contracts work within the KDE Promo community
already. Juan Carlos Torres was hired to set the
for the discussion and (b)
doesn't welcome it when it comes.
Best regards,
Eike Hein
-
KDE e.V. vice president, treasurer
on our website:
https://mbition.io/wp-admin/admin-ajax.php?action=full_job_ad_page=9575277
If you have any questions about the position or the company,
please feel free to get in touch.
Cheers,
Eike Hein
-
Principal System Architect, MBition GmbH
PS.: I'm also very happy to be able to announce
1 - 100 of 103 matches
Mail list logo