On 23.8.2023 14.24, Paul Brown wrote:
A lot fo good ideas we can use to reach a compromise, but this ...
KDE members are of course free to participate in discussions anywhere
they want, but loading KDE resources (sysadmin team & machines) with all
possible proprietary network doesn't seem a
Ben Cooksley kirjoitti 21.6.2020 klo 6.38:
Hi all,
With the completion of Phase 1 of our move to Gitlab, all code review
activity should now be taking place on Gitlab, with only residual
reviews being cleaned out of Phabricator (which hopefully we're
already well underway with - please start
Christian Loosli kirjoitti 11.6.2020 klo 15.25:
And while IRC is improving (and you are very welcome to participate e.g. in
#ircv3 or #freenode-dev on freenode) two of the main pain points people
mention (lack of an endless scrollback / offline history, uploading media
directly) are unlikely
Bernie Innocenti kirjoitti 11.6.2020 klo 14.02:
On 11/06/2020 19.28, Ilmari Lauhakangas wrote:
Bernie Innocenti kirjoitti 11.6.2020 klo 9.38:
Doesn't Riot.im support images well enough for your use-case? It's
free software, and it's becoming fairly mature lately.
The root issue for both
Bernie Innocenti kirjoitti 11.6.2020 klo 9.38:
Doesn't Riot.im support images well enough for your use-case? It's free
software, and it's becoming fairly mature lately.
The root issue for both Telegram and Matrix seems to be that they're
bridging through a legacy platform like IRC. Would it
Kenny Duffus kirjoitti 11.6.2020 klo 11.44:
On Thursday, 11 June 2020 08:19:21 BST Ilmari Lauhakangas wrote:
As an alternative, we can also "fix" IRC, meaning to improve its UX.
For offering a KDE-hosted always-online experience to everyone, there
are modern solutions such
Nate Graham kirjoitti 11.6.2020 klo 2.16:
Carson's email about bridging #kde-devel to Telegram got me thinking: we
should have a discussion about the situation we're in regarding chat
services in KDE.
The current Matrix solution does not seem not optimal to me. I have
really tried my best to
We can consult this site: http://shouldiuseacarousel.com/
Ilmari
Niccolò Venerandi kirjoitti 8.12.2019 klo 11.58:
Could that be an appropriate use case for a carousel? It takes less
vertical space, and the user probably won't be annoyed by the automatic
change of picture as he don't probably
Elv1313 . kirjoitti 5.7.2019 klo 1.59:
I have no idea what you mean with PR<-->Issues integration problem.
The things other people mentioned (close issues when PRs are merged,
links with context on hover, etc) Plus, "in the future", maybe
improvements like being able to turn an issue in a pull
Nate Graham kirjoitti 4.7.2019 klo 20.02:
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 04.07.2019 13:41, Boudewijn Rempt wrote:
So, what gitlab issues have over bugzilla is a rich text editor and a
confidentiality flag. What bugzilla has over gitlab issues is
reasonable solid set of features that help actually tracking and
managing the bug report. It's not that I'm a huge
Nate Graham kirjoitti 3.7.2019 klo 21.23:
On 7/3/19 11:53 AM, Albert Astals Cid wrote:
If the new is much better than the old, let's just remove the old.
As said, having two things that do the same is just confusing for
everyone.
I would tend to agree, and having two is super confusing. In
Nate Graham kirjoitti 22.6.2019 klo 12.44:
2) The description section should move above the duplicates check
I think this makes the duplicates check less useful, but the underlying
issue here is that the duplicates check is itself not really as accurate
as it could be so it's not helping
Lays Rodrigues kirjoitti 27.11.2018 klo 18.25:
Let's not go in that way.
As a ~new person~ on KDE, 3 years only, we need to move to a modern web.
At least in my point of view, I really think that using old stuff
doesn't attract new people. In that I have a few ideas for some KDE
websites go
Martin Flöser kirjoitti 26.11.2018 klo 19.03:
Am 2018-11-26 09:23, schrieb Ilmari Lauhakangas:
The main problem in any case will be getting enough engagement. I
don't think I have ever received a reply from a KDE developer in the
current forums.
And that's good! Do you want that developers
Ilmari Lauhakangas kirjoitti 18.9.2018 klo 14.13:
Harald Sitter kirjoitti 18.9.2018 klo 13.40:
Anywayyy... I can throw together some automation so long as someone
tells me what exactly the process should be :P
Wait a bit as I have just been in contact with Andrew about re-using
Harald Sitter kirjoitti 18.9.2018 klo 13.40:
Anywayyy... I can throw together some automation so long as someone
tells me what exactly the process should be :P
Wait a bit as I have just been in contact with Andrew about re-using the
automation LibreOffice already has for this. I need to ask
Sorry, I don't have better suggestions. Naming things is a hard problem
in bug science.
Ilmari
Andrew Crouthamel kirjoitti 5.9.2018 klo 11.17:
I like REPORTED as well. That leaves timeframe out of the status name.
Bugs can stay REPORTED but never CONFIRMED, and that all makes sense.
Based
Andrew Crouthamel kirjoitti 5.9.2018 klo 5.28:
d. If bug is not fixable due to technical limitations, or expected
behavior, set to RESOLVED + ASDESIGNED.
WONTFIX is also typically used to refuse to implement features that are
out of scope or not aligned with a product vision. Just wanted
On 16.03.2018 17:35, Adriaan de Groot wrote:
On Friday, 16 March 2018 16:07:20 CET, Adriaan de Groot wrote:
I've now contacted the Janitor folks, so we'll see what can be updated
and/or revised, and possibly start using it -- since it *does* sound
like a very interesting service.
Please
On 16.03.2018 12:29, Adriaan de Groot wrote:
On Friday, 16 March 2018 09:20:26 CET, Ilmari Lauhakangas wrote:
KDE
Efforts:
None
WANTED: Maintaining KDE development environment image
WANTED: Hosting Janitor containers for KDE
Benefits:
Development
On 28.02.2018 16:21, Jaroslaw Staniek wrote:
My story is, more rules, more scared users ignore the BKO. A single
thing worth having is not too many rules but editing feature for *wrong*
or outdated bug comments that make understanding the report so hard.
Many years have passed since the first
ating a bug brings down my whole system like
the bug report says, I'm going to get someone's attention. But in
between that and a minor annoyance... I can't decide that.
-Scott, graybeard wannabe junior developer
On Wed, Feb 28, 2018 at 7:54 AM, Ilmari Lauhakangas
<ilmari.lauhak
rocess a wrong
re-routage, this will be complex later to maintain a project.
See the sections created in bugzilla about digiKam project for example :
https://bugs.kde.org/editcomponents.cgi?product=digikam=1
Best
Gilles Caulier
2018-02-28 12:35 GMT+01:00 Ilmari Lauhakangas
<ilmari
I am personally convinced that users do not know bug triaging is a thing
and certainly not how much they could help developers by doing it. It
would be very useful to test this by running a poll on
https://blogs.kde.org/ or somewhere.
Questions could be something along the lines of
"Did you
On 28.02.2018 12:01, Luigi Toscano wrote:
On Wednesday, 28 February 2018 10:32:58 CET Boudewijn Rempt wrote:
On Wednesday, 28 February 2018 00:14:30 CET Luigi Toscano wrote:
On bugzilla.redhat.com some teams use the Triaged keyword. I think it
would
be a good solution.
I've been trying that,
On 27.02.2018 22:06, Boudewijn Rempt wrote:
On Tuesday, 27 February 2018 20:39:31 CET Elvis Angelaccio wrote:
Exactly. Also, what Luca said: unconfirmed gives the impression that we
don't care about the bug.
My point is that confirmed/unconfirmed adds more problems than it solves.
Note
On 27.02.2018 15:45, Paul Brown wrote:
On Tuesday, 27 February 2018 13:43:17 CET Boudewijn Rempt wrote:
On Tuesday, 27 February 2018 13:30:12 CET Paul Brown wrote:
Is it true that users get confused by the bugtracking system? If so, this
is an issue, right?
Well, users can get confused by
I see it rather as not moving away from IRC, but IRC moving towards
modernity and thus remaining a viable protocol.
Regards,
Ilmari
On 21.02.2018 12:35, Ilya Bizyaev wrote:
Hello Severino! :)
I am glad you mentioned XMPP, and in fact I also see it and
https://kdetalk.net/ as an
On 14.02.2018 23:39, Nicolás Alvarez wrote:
Hi people,
The KDE Telegram-IRC bridge bot is not working anymore, and after some
troubleshooting and upgrades uhh I think I managed to break it more.
Maybe it's a problem with Telegram's servers though. I'll do some more
testing later, but for now
On 01.02.2018 12:50, Boudewijn Rempt wrote:
On Wednesday, 31 January 2018 20:44:13 CET Ilmari Lauhakangas wrote:
In LibreOffice, we only restrict priority and severity and even those
upwards from medium/normal. We monitor messy stuff with a script:
https://gerrit.libreoffice.org/gitweb?p=dev
On Monday, 29 January 12:16:07 UTC Boudewijn Rempt wrote:
On Monday, 29 January 2018 12:25:24 CET Harald Sitter wrote:
I don't like going to our bugzilla.
Me neither... But that's more because I have to triage about a 1000 bug
reports a year, and many of them are not bug reports at all, but
On 16.08.2017 14:56, Jonathan Riddell wrote:
On Wed, Aug 16, 2017 at 12:58:35PM +0300, Ilmari Lauhakangas wrote:
The work-in-progress Kiwi Next client can be tested like so:
https://kiwiirc.com/nextclient/#irc://irc.freenode.net/kde
You can add more channels separated with commas.
Looks like
On 16.08.2017 14:08, Christian Loosli wrote:
I mostly agree, even though I am unsure of how certain things could be
implemented, e.g.
* Editing messages
which IRC simply does not support. So my best guess would be that this
only
works for people using the Kiwi solution, or the IRC people
Hello you radicals. I am a KDE user and contributor and a member of The
Document Foundation. Jonathan already referred to my mail on the
LibreOffice projects list, so I might as well branch out here.
I've been working with Kiwi IRC's lead developer Darren for some weeks
now. Today I showed
35 matches
Mail list logo
