Yes, in general, user friendliness is a benefit that's rather important,
especially when you're trying to encourage a platform to be used by more
people.
Nate
On 6/10/20 5:14 PM, Jacky Alcine wrote:
The only "benefit" here seems to be user friendliness (HTTP is ancient and C++
is but both a
El mié., 10 de jun. de 2020 a la(s) 20:06, Carson Black
(uhh...@gmail.com) escribió:
>
> Currently, #kde-devel is not set up with an IRC bridge to Telegram,
> meaning users cannot access it from Telegram.
>
> Plugging it into our current bridge infrastructure would have the
> following benefits:
>
The only "benefit" here seems to be user friendliness (HTTP is ancient and C++
is but both are still used)
On Wed, Jun 10, 2020, at 16:07, Nate Graham wrote:
> +1 if even only for the new contributor friendliness angle. Many other
> channels are bridged to Telegram; probably this one should be a
+1 if even only for the new contributor friendliness angle. Many other
channels are bridged to Telegram; probably this one should be as well.
Nate
On 6/10/20 5:05 PM, Carson Black wrote:
Currently, #kde-devel is not set up with an IRC bridge to Telegram,
meaning users cannot access it from T
Currently, #kde-devel is not set up with an IRC bridge to Telegram,
meaning users cannot access it from Telegram.
Plugging it into our current bridge infrastructure would have the
following benefits:
- Telegram-only users (yes, those exist because neither IRC nor Matrix
are suitable for their need
El dimecres, 10 de juny de 2020, a les 18:19:36 CEST, Glen Ditchfield va
escriure:
> In the Phabricator work flow, I would submit a patch, someone knowledgeable
> would accept it, and I would `arc land` it. Clear and simple.
>
> GitLab doesn't have that "accept" step AFAIK. The KDE Wiki's Infr
On Wednesday, June 10, 2020 12:19:36 PM EDT Glen Ditchfield wrote:
> In the Phabricator work flow, I would submit a patch, someone knowledgeable
> would accept it, and I would `arc land` it. Clear and simple.
>
> GitLab doesn't have that "accept" step AFAIK. The KDE Wiki's Infrastructure/
> Git
In the Phabricator work flow, I would submit a patch, someone knowledgeable
would accept it, and I would `arc land` it. Clear and simple.
GitLab doesn't have that "accept" step AFAIK. The KDE Wiki's Infrastructure/
GitLab page says "Once the Merge Request is accepted, KDE Developers will
merge
Hi,
Thank you for your reply.
I will definitely test your library as it seems to have everything ones
need to interface with udisks.
Best regards,
Kwon-Young Choi
> Message: 1
> Date: Tue, 9 Jun 2020 12:08:18 -0300
> From: Daniel Nicoletti
> To: kde-devel@kde.org
> Subject: Re: Add loop devic
