[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-telepathy
Subject: Re: New maintainers wanted: KDE Telepathy, KAccounts, Plasma Notifications and others
From: Martin Klapetek <martin.klapetek () gmail ! com>
Date: 2019-03-04 14:42:11
Message-ID: CAPLgePohjFR5medJPAz05Co-ZG_5w8OqPBftDP1b4Z6rLX5zwQ () mail ! gmail ! com
[Download RAW message or body]
On Mon, Mar 4, 2019 at 9:32 AM Alexander Akulich <akulichalexander@gmail.com>
wrote:
> Hi Martin and everyone.
>
> I would like to take over the KDE Telepathy maintainership.
>
> I understand that Telepathy is a huge and complex project that needs a
> lot of manpower to actually come back, but there is no other project
> with the same goals and capabilities. For me, Telepathy is not the
> exact specification, but an idea of IM system with replaceable
> components that give you a freedom to combine whatever you want across
> operation systems, desktop environments, and programming languages
> with the best rate of shared code and system integration.
>
> I can spend two hours and write a long list of reasons why Telepathy
> is the right thing to do, but please let me spend this time on the
> development to prove my arguments by deed and not by words.
> On the other hand, I don't want to fail someone's expectations, so
> please continue to not expect much. :)
>
> I think that in the current era of proprietary IM services, such
> integrated and yet distributed solution has a chance to prove itself
> with open protocols such as Matrix, Telegram (MTProto), XMPP, Tox,
> Slack, IRC, SIP (reSIProcate), Gitter, Rocket.Chat, Signal, Discord
> and so on. For sure the list can meet the demands of some users.
>
> I have interest, ideas, experience, and prototypes. Now I have some
> time to start checking out features one by one. I'm already a
> maintainer of TelepathyQt (I released the last three versions), but
> the library and services mean nothing without a client. I have some
> pending reviews for 10 months [1] and if nobody reviews them then
> maybe it will be right to become a maintainer and start to land them.
>
> As a maintainer, I'll also take responsibility for bug fixing (as a
> start I committed three bug fixes at the last three days).
>
> P.S.: If you're going to support Matrix then please, please! develop a
> good library. I don't want to offend anyone, but QMatrixClient needs a
> lot of improvements and maybe you can help. With a good library (such
> as QXmpp) a Telepathy service implementation would consist of about 2k
> lines of code.
>
> [1] https://phabricator.kde.org/D12751
Yes please! You've already proven yourself throughout the years
with all your contributions, so you have my blessing :)
Thanks for stepping up!
Cheers
--
Martin Klapetek
[Attachment #3 (text/html)]
<div dir="ltr"><div dir="ltr"><div><div dir="ltr" class="gmail_signature" \
data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr">On Mon, Mar 4, 2019 at \
9:32 AM Alexander Akulich <<a \
href="mailto:akulichalexander@gmail.com">akulichalexander@gmail.com</a>> \
wrote:<br></div></div></div></div></div><div class="gmail_quote"><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Hi Martin and everyone.<br> <br>
I would like to take over the KDE Telepathy maintainership.<br>
<br>
I understand that Telepathy is a huge and complex project that needs a<br>
lot of manpower to actually come back, but there is no other project<br>
with the same goals and capabilities. For me, Telepathy is not the<br>
exact specification, but an idea of IM system with replaceable<br>
components that give you a freedom to combine whatever you want across<br>
operation systems, desktop environments, and programming languages<br>
with the best rate of shared code and system integration.<br>
<br>
I can spend two hours and write a long list of reasons why Telepathy<br>
is the right thing to do, but please let me spend this time on the<br>
development to prove my arguments by deed and not by words.<br>
On the other hand, I don't want to fail someone's expectations, so<br>
please continue to not expect much. :)<br>
<br>
I think that in the current era of proprietary IM services, such<br>
integrated and yet distributed solution has a chance to prove itself<br>
with open protocols such as Matrix, Telegram (MTProto), XMPP, Tox,<br>
Slack, IRC, SIP (reSIProcate), Gitter, Rocket.Chat, Signal, Discord<br>
and so on. For sure the list can meet the demands of some users.<br>
<br>
I have interest, ideas, experience, and prototypes. Now I have some<br>
time to start checking out features one by one. I'm already a<br>
maintainer of TelepathyQt (I released the last three versions), but<br>
the library and services mean nothing without a client. I have some<br>
pending reviews for 10 months [1] and if nobody reviews them then<br>
maybe it will be right to become a maintainer and start to land them.<br>
<br>
As a maintainer, I'll also take responsibility for bug fixing (as a<br>
start I committed three bug fixes at the last three days).<br>
<br>
P.S.: If you're going to support Matrix then please, please! develop a<br>
good library. I don't want to offend anyone, but QMatrixClient needs a<br>
lot of improvements and maybe you can help. With a good library (such<br>
as QXmpp) a Telepathy service implementation would consist of about 2k<br>
lines of code.<br>
<br>
[1] <a href="https://phabricator.kde.org/D12751" rel="noreferrer" \
target="_blank">https://phabricator.kde.org/D12751</a></blockquote><div><br></div><div>Yes \
please! You've already proven yourself throughout the years</div><div>with all \
your contributions, so you have my blessing :)</div><div><br></div><div>Thanks for \
stepping up!</div><div><br></div><div>Cheers</div><div><div><span \
style="color:rgb(102,102,102)">--</span></div><div><span \
style="color:rgb(102,102,102)">Martin Klapetek</span></div></div></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic