mandatory... I know it's unpopular in
KDE, and I advocated for "don't force a tool if you can get someone to look at
your screen or pair with you" in the past. Clearly this compromise gets
somewhat exploited and that's especially bad in the case of a fragile and
central
Hello,
On Thursday, 28 March 2019 09:41:29 CET Luca Beltrame wrote:
> In data giovedì 28 marzo 2019 09:29:22 CET, Kevin Ottens ha scritto:
> > at your screen or pair with you" in the past. Clearly this compromise gets
> > somewhat exploited and that's especially bad in
Hello,
On Thursday, 28 March 2019 10:08:54 CET Luca Beltrame wrote:
> In data giovedì 28 marzo 2019 09:50:47 CET, Kevin Ottens ha scritto:
> > I'd argue we're loosing more with the current state of PIM than we'd loose
> > with mandatory reviews.
>
> Perhaps, i
Hello,
On Thursday, 28 March 2019 10:35:37 CET Luca Beltrame wrote:
> In data giovedì 28 marzo 2019 10:32:39 CET, Kevin Ottens ha scritto:
> > OK, to be fair not 100% today's situation because of the above. It was
> > based on best judgment maybe we're missing su
programmer :-) I think this is
> especially important for projects like PIM, where most of us contribute at
> work in between waiting for CI and replying to 15 Slack threads or in the
> evening after a long day
And this too of course.
I fully support this message. ;-)
Cheers.
--
Kev
friend told me when I started
> to work on kde "We can't create a bug when we don't code..."
And this is true, writing code will create bugs, that's why responsible people
like safety nets even to the price of throughput.
Now can we use a more adult tone again? Maybe re-read Dan's email again who
has a more balanced view despite being in a similar situation?
Regards.
--
Kevin Ottens, http://ervin.ipsquad.net
signature.asc
Description: This is a digitally signed message part.
t regarding the state of the CI in PIM
components. Although it's clear from the kde-pim list that the CI is making a
lot of noise there. Either we collectively became too good at ignoring those
emails, or it's too verbose (after all it's one email per component per build
type, it piles up quickly).
Regards.
--
Kevin Ottens, http://ervin.ipsquad.net
signature.asc
Description: This is a digitally signed message part.
responsibility in carrying those duties for the well being of the project.
> IMO this specific case is also a technical issue. Akonadi makes things
> complicated (and it's already 13 years old, so it should be mature in the
> meantime).
Yes, it's byzantine really. And the user experience is still not great (to be
polite), had to setup some new hardware recently and I was honestly almost to
the point of throwing it all through the window.
Regards.
--
Kevin Ottens, http://ervin.ipsquad.net
signature.asc
Description: This is a digitally signed message part.
code style, etc.).
Regards.
--
Kevin Ottens, http://ervin.ipsquad.net
signature.asc
Description: This is a digitally signed message part.
Hello,
On Friday, 29 March 2019 09:43:44 CET Volker Krause wrote:
> On Friday, 29 March 2019 08:59:59 CET Kevin Ottens wrote:
> > On Thursday, 28 March 2019 21:53:06 CET Alexander Neundorf wrote:
> > > Having mandatory reviews for a central and complex component like
> &g
Hello,
On Tuesday 14 April 2015 09:44:19 Sandro Knauß wrote:
> > What's meant by "KDE Accounts"?
>
> well we also had a look into the code. It is a resource that will adds all
> local users from kde to your kaddressbook.
Oooh, that one... it's very important to me, I rely a lot on it. Can we
re
Hello all,
So we've been evaluating different options to modernize our tooling, and for
some reason it looks like we're still waiting on some external pressure to
pick one. I'll then try to be this external pressure with this war cry:
Phaaab! Make it happen already!
It is basically what I repo
Hello,
On Thursday, 7 July 2016 12:36:26 CEST Thomas Pfeiffer wrote:
> I'm addressing both the Plasma team and kde-devel because this issue affects
> Plasma as well as many applications, and Valentin as the current maintainer
> of KWallet as well as KSecretService, a potential replacement for it.
Hello,
On Monday, 11 July 2016 21:58:34 CEST Thomas Pfeiffer wrote:
> On 07.07.2016 19:50, Kevin Ottens wrote:
> > There's two sides to that problem in fact, use from applications and the
> > service provided by our workspace.
> >
> > I think that for ap
Hello,
On Monday, 11 July 2016 20:51:43 CEST Sune Vuorela wrote:
> On 2016-07-07, Kevin Ottens wrote:
> > There's two sides to that problem in fact, use from applications and
> > the=20
> > service provided by our workspace.
>
> One issue that I'm a bit pu
Hello,
On Friday, 12 May 2017 12:57:58 CEST Ben Cooksley wrote:
> I've now added the following to the Extragear product as requested:
>
> - Skrooge
> - Simon
> - KMyMoney & Alkimia
> - Krusader
>
> For Zanshin we have a slight hitch: it's in Playground. It's been
> around for a while now so can
On Wednesday 8 December 2010 02:51:46 Aaron J. Seigo wrote:
> On Tuesday, December 7, 2010, Benoit Jacob wrote:
> > *
> > 3. QA, Unit-testing, continuous testing (KDE: very little, Mozilla: a
> > lot)
> >
> > Let's face it, KDE has always been deficient in the QA department. In
> >
> > order
On Wednesday 8 December 2010 15:09:38 David Jarvie wrote:
> On Wed, December 8, 2010 8:38 am, Kevin Ottens wrote:
> > On Wednesday 8 December 2010 02:51:46 Aaron J. Seigo wrote:
> >> On Tuesday, December 7, 2010, Benoit Jacob wrote:
> >> > *
> >> > 3.
Hello lists,
As, Sebas pointed out we've been meeting here to work on plans to improve our
frameworks offering leading to the decision of leaving the current "kdelibs
model" behind and prepare for a more modular suite named KDE Frameworks. If
you didn't read his email yet, please do so before
Hello lists,
As, Sebas pointed out we've been meeting here to work on plans to improve our
frameworks offering leading to the decision of leaving the current "kdelibs
model" behind and prepare for a more modular suite named KDE Frameworks. If
you didn't read his email yet, please do so before
Hello all,
I have very good news, if everything goes well, I will have the opportunity to
setup student projects at the University in collaboration with KDE again!
We had a one year hiatus, and I have to admit I miss those projects dearly, so
it'd be nice to resume the effort... I'd quite some wor
act me yet, you still can send me a proposal, I'll
gladly add it to the list.
Regards.
On Tuesday 07 August 2012 19:08:18 Kevin Ottens wrote:
> Hello all,
>
> I have very good news, if everything goes well, I will have the opportunity
> to setup student projects at the Universit
Hello,
On Thursday 16 August 2012 20:23:24 Torsten Rahn wrote:
> On Donnerstag, 16. August 2012 12:12:12 Kevin Ottens wrote:
> On behalf of the Marble Team I'd like to express our highest interest in
> participation!
OK, you're on the list now! ;-)
> The two mentors we&#x
On Wednesday 07 August 2013 11:17:22 Reza Shah wrote:
> I just updated kde-workspace from framework-scratch.
> I got errors when building it as in http://paste.kde.org/pc4273542/,
> something about KStyle.
>
> How to fix these errors?
It was my fault, I just pushed a fix in kdelibs now, please u
Hello,
On Wednesday 07 August 2013 17:11:09 Reza Shah wrote:
> Below are the new codes(simplified), but i have doubt how to use
> globalShortcutChanged, and effectShortcutChanged properly.
> ---
> QList cubeShortcut;
> QList cylinderShortcut;
>
> QAction* cubeAction;
> QAc
Only have one release announcement on our website. We can call it
> Megarelease 6.XX like we did for Plasma 6/Gear 24.02 or find a better name.
> I would avoid reusing Software Collection first because the name is quite
> technical and second because these was already used in the pas
in the game
this time and already engaged in the conversation. So if you're someone who
didn't reply to this thread and have no strong opinion about the topic: keep
monitoring that thread and maybe evaluate volunteering to facilitate if we
start throwing mud at each other. ;-)
Regards
constant "learning new stuff" and "adapting to change" loop).
> > * "KDE Framework" will still exists as an entity and its ABI and API
> >
> > compatibility requirement. Only change is the release frequency and the
> >
> > introduction of a stable branch in sync with the other components.
>
> That part I'm against for the above mentioned reasons, KF's release
> frequency is a major feature of it.
Regards.
--
Kevin Ottens, http://ervin.ipsquad.net
enioka Haute Couture - proud supporting member of KDE
https://hc.enioka.com/en
signature.asc
Description: This is a digitally signed message part.
Hello,
On Monday 22 April 2024 18:08:04 CEST Carl Schwan wrote:
> On Friday, April 19, 2024 6:39:01 PM GMT+2 Kevin Ottens wrote:
> > Unsurprisingly I'll be pretty much aligned with Luigi, Sune and Volker
> > here I think. I'll try to add a couple of extra aspects to feed
> requests regarding the window decoration in breeze were closely linked to
> other changes in KDecoration. This probably would make sense even if we end
> up keeping breeze in plasma.
> - Colors: these were already moved to KColorScheme, so we could remove
> the duplication one wa
30 matches
Mail list logo
