On 2023-06-15 11:13, Ben Cooksley wrote:
On Thu, Jun 15, 2023 at 6:34 AM Christoph Cullmann (cullmann.io [1])
wrote:
On 2023-05-14 22:50, Christoph Cullmann (cullmann.io [1]) wrote:
Hi,
given the last activity is one or two years ago,
would it make sense to move the stuff in
https
On 2023-05-14 22:50, Christoph Cullmann (cullmann.io) wrote:
Hi,
given the last activity is one or two years ago,
would it make sense to move the stuff in
https://invent.kde.org/wikitolearn
to
https://invent.kde.org/unmaintained
and archive it there until it is revived?
Given nobody
Hi,
given the last activity is one or two years ago,
would it make sense to move the stuff in
https://invent.kde.org/wikitolearn
to
https://invent.kde.org/unmaintained
and archive it there until it is revived?
Greetings
Christoph
--
Ignorance is bliss...
https://cullmann.io |
On 2022-10-28 22:57, Ben Cooksley wrote:
Hi all,
Following some additional analysis of the situation I've now adjusted
the policy surrounding enforced use of 2FA.
Going forward it will only be enforced on people who are one of the
following:
- KDE Developers
- KDE e.V. Members (including the
On 2022-10-25 20:53, Albert Astals Cid wrote:
> > Hi,
> >
> > whereas I can see the security benefit, this raises the hurdle for one
> > time contributors again a lot.
> >
> > Before you already had to register to get your merge request,
> > now you need to setup this too (or at least soon it is
On 2022-10-25 21:29, Christoph Cullmann (cullmann.io) wrote:
On 2022-10-25 20:53, Albert Astals Cid wrote:
i concur - after spending so long trying to attract casual
contributors,
putting up a huge barrier like this is just not helpful. So, 2FA for
people
who area able to actually mess stuff
On 2022-10-25 20:53, Albert Astals Cid wrote:
i concur - after spending so long trying to attract casual
contributors,
putting up a huge barrier like this is just not helpful. So, 2FA for
people
who area able to actually mess stuff up, absolutely, we have
responsibility
here and that's fine,
On 2022-10-25 14:55, Ahmad Samir wrote:
On 25/10/22 14:31, Christoph Cullmann (cullmann.io) wrote:
On 2022-10-25 13:52, Ahmad Samir wrote:
On 25/10/22 13:29, Harald Sitter wrote:
On Tue, Oct 25, 2022 at 1:22 PM Ahmad Samir
wrote:
Can a first time contributor create a fork, create multiple
On 2022-10-25 13:52, Ahmad Samir wrote:
On 25/10/22 13:29, Harald Sitter wrote:
On Tue, Oct 25, 2022 at 1:22 PM Ahmad Samir
wrote:
Can a first time contributor create a fork, create multiple/100 MR's
and spin up CI jobs? if yes,
then, first time contributors can disrupt the system.
On 2022-10-24 11:23, Ingo Klöcker wrote:
On Montag, 24. Oktober 2022 09:19:49 CEST Christoph Cullmann
(cullmann.io)
wrote:
I think it is rather worse that now first time contributors have this
requirement.
Do you have proof for this, e.g. a study, or is this just your
Bauchgefühl
(gut
Hi,
Could the 2FA stuff perhaps be limited to people with developer role
or
such?
It is technically possible to only apply the mandatory 2FA rules to
only certain groups as Developer accounts are simply membership in
teams/kde-developers.
See
On 2022-10-23 08:32, Ben Cooksley wrote:
Hi all,
This afternoon I updated invent.kde.org [1] to the latest version of
Gitlab, 15.5.
Release notes for this can be found at
https://about.gitlab.com/releases/2022/10/22/gitlab-15-5-released/
There isn't much notable feature wise in this release,
On 2021-07-05 21:00, Noah Davis wrote:
It was great to have you!
Yeah, you brought our websites from the stone age header/footer
PHP hell I and others left to rot to something
a lot more maintainable and nicely i18n'able ;))
Thanks a lot for all the work on that (and NeoChat & Co.)!
On 2021-06-19 16:21, Nate Graham wrote:
Hello everyone!
Some time ago, we instituted a restriction preventing normal Bugzilla
users from being able to change the Severity field of Bugzilla
tickets. The reason for this change was to stop users with excessive
ego from marking their own tickets
On 2021-06-15 15:59, Kenny Duffus wrote:
On Tuesday, 15 June 2021 14:50:51 BST Andrius Štikonas wrote:
Given the imposion today, can we not just close old matrix rooms with
m.room.tombstone and point them to new rooms linked to Libera?
In the short term that might be a bit disruptive because
On 2021-04-23 21:04, Ben Cooksley wrote:
My personal suggestion would be to pick a few applications and try
to work
with them to get the tooling up. E.g. Krita, Kate, KWrite and
Okular. And try
to automate. Don't have the application developers maintain all
those
variants. It's too much! Maybe
On 2021-02-15 15:36, Nate Graham wrote:
On 2/15/21 6:01 AM, Jonathan Riddell wrote:
Here at KDE we've always struggled a bit with branding and the
announcement of formats for the bunch of releases that was originally
"KDE" then "KDE SC" then "KDE Applications" and at Akademy 2019 we
decided
On 2021-02-14 15:18, Christoph Cullmann wrote:
Hi,
during some reviewing of what we link from e.g. kde.org and Co. I
stumbled
over the current state of the WikiToLearn wikis.
It seems most of the recent changes (of at least the last 30 days)
are spam ( see links in
https://invent.kde.org
Hi,
during some reviewing of what we link from e.g. kde.org and Co. I
stumbled
over the current state of the WikiToLearn wikis.
It seems most of the recent changes (of at least the last 30 days)
are spam ( see links in
https://invent.kde.org/websites/kde-org/-/issues/9 ).
The development
Hi,
On 2020-09-23 00:53, Carl Schwan wrote:
Hello everyone,
Nate gave an excellent talk at the Akademy about how we can konquer the
world
and reach new horizons with our software. One of the first steep for
Nate is
for the e.V. to start paying more developers to work on core KDE
On 2020-08-17 17:47, Ivan Čukić wrote:
> I've read now multiple times about projects replacing their use of
> LGPLv3 [1] with MPL2 [2]. I would be interested in what people in the
> KDE community think about that.
Maybe an alternative to MPL could be these:
1) GPL with runtime exception (if
On 2020-07-09 20:10, Nicolás Alvarez wrote:
El jue., 9 de jul. de 2020 a la(s) 10:49, Christoph Cullmann
(christ...@cullmann.io) escribió:
There is no evidence that this upload contains any virus/miner/...
And even for the GPL it is enough if he provides the sources on
request
and only
.
Greetings
Christoph
On Thu, Jul 9, 2020, 10:27 AM Jack
wrote:
On 7/9/20 9:48 AM, Christoph Cullmann wrote:
On 2020-07-09 14:18, Jonathan Riddell wrote:
On Thu, 9 Jul 2020 at 12:29, Christoph Cullmann
wrote:
You might be able to do that, but as soon as you start to try to
keep
people
from using
On 2020-07-09 14:18, Jonathan Riddell wrote:
On Thu, 9 Jul 2020 at 12:29, Christoph Cullmann
wrote:
You might be able to do that, but as soon as you start to try to
keep
people
from using the names, the cost-free, bureaucracy-free and layer free
zone ends.
Sending an e-mail
On 2020-07-09 13:14, Jonathan Riddell wrote:
On Wed, 8 Jul 2020 at 17:51, Paul Brown wrote:
Should we add ™ next to the app names?
I don't think putting TM next to the name is enough, though. IANAL,
so take
the following with a grain of salt: in my experience (I had to
register
several
On 2020-07-09 01:23, Nate Graham wrote:
On 7/8/20 4:27 PM, Johannes Zarl-Zierl wrote:
On Mittwoch, 8. Juli 2020 20:27:58 CEST Christoph Cullmann wrote:
Otherwise we must keep in mind we are open source and yes, this is
possible.
(and perhaps promote the KDE e.V. uploaded stuff better)
+1
On 2020-07-08 20:20, Ben Cooksley wrote:
On Thu, Jul 9, 2020 at 6:09 AM Christoph Cullmann
wrote:
On 2020-07-08 18:12, Jonathan Riddell wrote:
> Recently we've noticed some KDE apps ending up on the Microsoft Store
> uploaded by unknown third parties. Maybe to up some credit
On 2020-07-08 18:12, Jonathan Riddell wrote:
Recently we've noticed some KDE apps ending up on the Microsoft Store
uploaded by unknown third parties. Maybe to up some credit score for
their developer account. Maybe to install bitcoin miners. We don't
know the motivations. Since it's all
Hi,
I just want to express my big thanks for all the work that went into
this!
Thanks to all people involved in making this happen and
maintaining/improving all
our other infrastructure.
Besides, happy Easter and become/stay healthy!
Greetings
Christoph
On 2020-04-11 11:35, Ben Cooksley
Hi,
just one quick question about this part:
But last week, the company suddenly informed both the KDE e.V. board
and the
KDE Free QT Foundation that the economic outlook caused by the Corona
virus
puts more pressure on them to increase short-term revenue. As a result,
they
are thinking
On 2020-04-08 15:39, Boudewijn Rempt wrote:
On woensdag 8 april 2020 13:13:41 CEST Jens wrote:
The issue is for KDE is that we can't prepare ourselves. We can't fork
Qt,
because we lack the manpower to safely do so currently.
But if we work together with other participants in the Qt
On 2020-02-25 19:22, Albert Astals Cid wrote:
El dimarts, 25 de febrer de 2020, a les 18:47:16 CET, Nate Graham va
escriure:
I find myself in agreement.
I have access to the kuserfeedback data and to be honest I'm rather
dissatisfied with its actionability. There's nothing detailed like "x
On 2020-02-25 18:47, Nate Graham wrote:
I find myself in agreement.
I have access to the kuserfeedback data and to be honest I'm rather
dissatisfied with its actionability. There's nothing detailed like "x
percentage of users change the default wallpaper" or "y percentage of
users switch to
On 2020-02-02 12:27, Christoph Cullmann wrote:
Hi,
I created some initial merge request for basic user feedback
integration into Kate:
https://invent.kde.org/kde/kate/merge_requests/60
To do this properly like described in
https://community.kde.org/Policies/Telemetry_Policy
I would like
Hi,
I created some initial merge request for basic user feedback integration
into Kate:
https://invent.kde.org/kde/kate/merge_requests/60
To do this properly like described in
https://community.kde.org/Policies/Telemetry_Policy
I would like to have people review this change and raise issues
On 2019-12-08 21:12, Ingo Klöcker wrote:
Hi,
is this still a legal issue if one anonymizes the IPs during
processing?
I don't think it matters whether it would be legal. What matters is
that
people whose browsers are set to send "Do Not Track" (or who have opted
out of
tracking some other
On 2019-12-08 18:12, Ben Cooksley wrote:
If you want any form of statistics, then it has to be Piwik (now
called Matomo btw)
Processing of our logs for web statistics purposes is not permitted by
our privacy policies (see https://kde.org/privacypolicy.php).
It is also much more problematic to
On 2019-12-07 23:52, Nate Graham wrote:
This looks excellent.
I have just a few suggestions:
The Applications section could be simplified by omitting the 2x3 grid
of apps on the top, since those same apps are then presented with nice
screenshots and text immediately below.
The Community
15:24 von david.hu...@mailbox.org:
Date: Tue, 29 Oct 2019 21:57:42 +0100
From: Christoph Cullmann
On 2019-10-29 12:18, cahfof...@tuta.io wrote:
> Dear KDE Community,
>
> On 29th of November, the fourth global climate strike will take place.
>
> For the last global climate st
then any sense.
For the state of discussions about climate impact: I think we have not
yet reached
any decision there e.V. internally.
Greetings
Christoph
Sincerely yours
cahfofpai
30. Okt. 2019, 15:24 von david.hu...@mailbox.org:
Date: Tue, 29 Oct 2019 21:57:42 +0100
From: Christoph
On 2019-11-02 22:11, Carl Schwan wrote:
Hello KDE community,
I'm contributing since more than a year to KDE. Mostly doing wiki
work and websites development but also promotion and more general
development. And I would like to become a KDE e.V. member.
If I correctly understand
On 2019-10-29 12:18, cahfof...@tuta.io wrote:
Dear KDE Community,
On 29th of November, the fourth global climate strike will take place.
For the last global climate strike, a banner was placed on the website
(https://web.archive.org/web/20190921055543/https://kde.org/
Hi,
btw., the 20th is over, shall we perhaps remove the banner again?
Looks somehow strange now.
Greetings
Christoph
--
Ignorance is bliss...
https://cullmann.io | https://kate-editor.org
Hi,
I learn by social media that KDE is now endorsing this very strike.
Well, I
obviously do not. There are better activities actually worth endorsing.
Too
bad some people think they can simply go and speak on whole of KDE's
behalf? I
feel bitter having to distance myself from a "KDE"
Hi,
On 2019-07-04 22:49, Boudewijn Rempt wrote:
On donderdag 4 juli 2019 22:18:32 CEST Elv1313 . wrote:
Ok, lots of email in the last few hours, lets recap a bit.
1. "Top" projects don't like GitLab issues because they are too
simple. Can we try to make a comprehensive list of issues on a pad
On 2019-07-04 19:02, Nate Graham wrote:
On 7/4/19 10:39 AM, Boudewijn Rempt wrote:
Is it really true that gitlab makes reporting bugs easier for our
users? I.e., does it offer easier login, an easier way to add screen
shots and screen recordings or crash logs?
In my experience, yes. Being
On 2019-07-04 18:11, Boudewijn Rempt wrote:
On donderdag 4 juli 2019 17:54:23 CEST Nate Graham wrote:
If so, then it seems like the ideal state of affairs would be to
replace
Bugzilla with GitLab issues as a new bug-reporting front-end for
users,
and then there would be a separate back-end
On 2019-07-04 13:35, Luca Beltrame wrote:
Il giorno Thu, 4 Jul 2019 13:31:49 +0200
Wolthera ha
scritto:
community to handle, so it is probably more efficient to wait for
bugzilla 6 in any case.
Speaking of that: does anyone know if there is a roadmap for Bugzilla
6? I'd say the comparison
On 2019-07-04 12:08, Luca Beltrame wrote:
It does, see above why. As a downstream I don't want to chase the
projects to see which platform they use for reporting bugs. And yes, I
have direct experience professionally with another, unrelated FOSS
project (Bioconductor) which doesn't have a
Hi,
Overall, I think KDE in general should be more active and confident in
taking steps to consolidate and modernize its software offerings and
technical landscape, especially if adoption of key future
infrastructure
solutions seems to be happening already in many comparable places
(e.g.
On 2019-07-02 15:14, David Edmundson wrote:
Plasma Mobile projects are not included in bugzilla. So, gitlab issues
is the only "decent" alternative for bug tracking. If we disable
issues, then the only alternative I see is to report issues to
Phabricator, which, from my point of view, should be
Hi,
Whether or not we can be sure that a string is a name should not be
relevant to us.
Just answering to say that this is actually what we're actually
discussing in this thread.
Can/Should we accept anonymous contributions (and thus we should not
care about a string being a name) or not?
I
Hi,
On 2019-04-12 21:43, Sune Vuorela wrote:
On 2019-04-12, Eike Hein wrote:
Pseudonyms don't jive with that for me. Someone not entrusting me with
their real name feels regressive vs. our current community standards.
It's a bit uncomfortable.
I have kind of the same feeling. Though real
Hi,
I tried to re-license parts of KTextEditor in the past.
Real names help close to nothing if the mail addresses are no longer
valid or the people don't respond, even if valid.
You just can't track them, unfortunately there are more "Max Schmidt"s
around on the world then lets say
them, unfortunately there are more "Max Schmidt"s
around on the world then lets say "Christoph Cullmann"s.
If you want to re-license and the last known mail addresses don't work
out for you, you are doomed with or without names.
Actually, from a legal stand-point I am not even
ml
https://community.kde.org/Incubator/Projects/QupZilla
But this process is only at its early stage.
Greetings
Christoph
--
- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com
Science Park 1 Tel: +49-681
-
> by-default.
I would vote for "off-by-default", too.
At the moment, we can not even judge how much data we receive with that
policy, we can still re discuss that if we really see we get not enough
feedback to have usable data.
Greetings
Christoph
--
- Dr.-Ing. Christ
g well with our
> community.
Yes, and given we want to lower the maintainance effort in other parts of the
server
setup we have, I don't really see why we open here yet another can of worms.
Greetings
Christoph
--
- Dr.-Ing. Christoph Cullmann -
AbsInt
d this
>> > keyserver to your list of keyservers.
>>
>> Is this reachable also on port 80? My workplace blocks hkp ports.
>>
>> --
>> Luca Beltrame - KDE Forums team
>> KDE Science supporter
>> GPG key ID: 6E1A4E79
>>
>>
--
---
___
>> kde-community mailing list
>> kde-community@kde.org
>> https://mail.kde.org/mailman/listinfo/kde-community
>
> ___
> kde-community mailing list
> kde-community@kde.org
> https://mai
sually full on Saturdays, so we would need to
> make a reservation.
will be in Berlin from the 1th, so you can count me in, too.
Just point me to the place to go ;=)
Greetings
Christoph
--
----- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik GmbH
; kde-community@kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
--
- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrü
.
+1 ;)
Looks quiet nice.
Greetings
Christoph
--
- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681
?
+1, if his family would be ok with that.
Greetings
Christoph
--
- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken
am happy to know: If somebody has KDE SC x.y installed, he has
the state of Kate
from that time.
Greetings
Christoph
--
- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com
Science Park 1
65 matches
Mail list logo
