<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 28/01/2026 18:14 UTC, Ben Cooksley
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+XidOE_shViPnd=Cc=ERYhcJbkKr=Yc5Au_aQ+JEqh6KxRJLg@mail.gmail.com">
<div dir="ltr">
<div dir="ltr">On Thu, Jan 29, 2026 at 3:42 AM Bernardo Negri
<<a href="mailto:b.gomes.negri@gmail.com"
moz-do-not-send="true" class="moz-txt-link-freetext">b.gomes.negri@gmail.com</a>>
wrote:</div>
<div class="gmail_quote gmail_quote_container">
<blockquote class="gmail_quote">On 27/01/2026 15:50, Bernardo
Negri wrote:<br>
> Hello,<br>
><br>
> I would like to start the incubation process for
kio-onedrive[1] and <br>
> to seek a sponsor for this process. The KDE Invent
issue to track the <br>
> incubation request is at <br>
> <<a
href="https://invent.kde.org/bernardogn/kio-onedrive/-/issues/20"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://invent.kde.org/bernardogn/kio-onedrive/-/issues/20</a>>.<br>
><br>
> kio-onedrive is a kio worker that allows applications
such as Dolphin <br>
> to access files stored on the user's Microsoft OneDrive
account and <br>
> the files stored in it, similarly to how kio-gdrive
allows Dolphin to <br>
> access the user's Google Drive.<br>
><br>
> The people committing to the project, as far as I know,
would be just <br>
> me. However, a few KDE developers have expressed
interest in the past.<br>
><br>
> I agree to follow the principles of the KDE manifesto.<br>
><br>
> This project would also advance KDE's strategy to reach
its mission by <br>
> "interoperating well with proprietary services."<br>
><br>
> However, there may be one technical hiccup: right now,
the project <br>
> needs to be compiled with Ninja as the CMake generator,
and with Clang <br>
> as the C++ compiler. When GCC 16 releases, it will be
possible to <br>
> compile kio-onedrive with GCC, but the requirement to
use Ninja as the <br>
> CMake generator will stay for the foreseeable future. I
do not believe <br>
> this is a too onerous requirement for distributions, I
have managed to <br>
> make builds for Debian, OpenSUSE Tumbleweed, Arch Linux
and Fedora[2].<br>
><br>
> Thank you,<br>
><br>
> Bernardo<br>
><br>
> [1] <a
href="https://invent.kde.org/bernardogn/kio-onedrive/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://invent.kde.org/bernardogn/kio-onedrive/</a><br>
><br>
> [2] <a
href="https://build.opensuse.org/package/show/home:bernardogn/kio-onedrive"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://build.opensuse.org/package/show/home:bernardogn/kio-onedrive</a><br>
><br>
Another thing I'd like to add: like most OAuth applications,
<br>
kio-onedrive needs a Client ID. Client IDs to access
Microsoft services <br>
need to be registered at Azure with a Microsoft account.
Right now, <br>
kio-onedrive offers the build-time option to choose what
Client ID to <br>
use (but it can be changed after building by editing the
kaccounts <br>
file), and by default it uses a Client ID associated with my
personal <br>
Microsoft account.<br>
<br>
I do not know what KDE's policy on such OAuth Client IDs is.
I'd be <br>
willing to change the default Client ID, but I think having
a default <br>
functional Client ID is useful.<br>
</blockquote>
<div><br>
</div>
<div>We don't have a policy as such, however in the case of
cloud provider services it is usually beneficial if you use
a Client ID belonging to an application registered by KDE.</div>
<div><br>
</div>
<div>This helps if permissions or other information associated
with the application need to be changed in the future, and
in the case of Microsoft specifically, also allows for
easier use with Enterprise setups as we've obtained the
appropriate registrations with Microsoft for that (already
done for Kontact)</div>
</div>
</div>
</blockquote>
<p>Thanks for the suggestion. The Kontact client id works fine,
since it also allowed to use the Files.ReadWrite.All scope.
However, if Sharepoint support is ever properly implemented, then
the Kontact app registration will also need to be updated.</p>
<p>For now, I think I will wait for Incubation to be complete before
switching to the Kontact client id, as using the Kontact client id
is using KDE branding.</p>
<blockquote type="cite"
cite="mid:CA+XidOE_shViPnd=Cc=ERYhcJbkKr=Yc5Au_aQ+JEqh6KxRJLg@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote gmail_quote_container">
<blockquote class="gmail_quote">
<br>
Cheers,<br>
<br>
Bernardo<br>
<br>
</blockquote>
<div><br>
</div>
<div>Thanks,</div>
<div>Ben </div>
</div>
</div>
</blockquote>
<p>Thanks,</p>
<p>Bernardo</p>
</body>
</html>