<div dir="auto">Hi kde team,<div dir="auto">My name is Shajith Bathina, and I made a proposal to the Sok26. As you mentioned, it is labelled as not accepted, but I don't know the reason. I'm not questioning you, but I saw other proposals too, and some of them are truly AI-generated. This is what I have observed. For future contributions and participation in the next Sok, I would appreciate feedback on my proposal, so please consider this a request and share some feedback and tips on how to start contributing without taking part in the Sok.</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, 22 Jan 2026, 17:30 , <<a href="mailto:kde-soc-request@kde.org">kde-soc-request@kde.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Kde-soc mailing list submissions to<br>
<a href="mailto:kde-soc@kde.org" target="_blank" rel="noreferrer">kde-soc@kde.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mail.kde.org/mailman/listinfo/kde-soc" rel="noreferrer noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/kde-soc</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:kde-soc-request@kde.org" target="_blank" rel="noreferrer">kde-soc-request@kde.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:kde-soc-owner@kde.org" target="_blank" rel="noreferrer">kde-soc-owner@kde.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Kde-soc digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. [SOK26] to-dos for new contributors (bookmark this email)<br>
(Johnny Jazeix)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 21 Jan 2026 15:18:26 +0100<br>
From: Johnny Jazeix <<a href="mailto:jazeix@gmail.com" target="_blank" rel="noreferrer">jazeix@gmail.com</a>><br>
To: KDE SoC mailing list <<a href="mailto:kde-soc@kde.org" target="_blank" rel="noreferrer">kde-soc@kde.org</a>><br>
Subject: [SOK26] to-dos for new contributors (bookmark this email)<br>
Message-ID:<br>
<<a href="mailto:CAEtcAPF7nhAZJcb_q7oKyLdg_sPYYwzEN9PUeZOB09uJ5sV2%2BA@mail.gmail.com" target="_blank" rel="noreferrer">CAEtcAPF7nhAZJcb_q7oKyLdg_sPYYwzEN9PUeZOB09uJ5sV2+A@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
Hi,<br>
<br>
This email includes important information for new contributors in Season<br>
of KDE. Please read it carefully.<br>
<br>
During SOK26 you will be communicating regularly with the community. KDE<br>
offers contributors numerous platforms to facilitate communication and<br>
collaboration. A list of to-dos and KDE services is included below.<br>
<br>
After reading this email make sure to register for new accounts in order<br>
to start communicating with the KDE community and collaborating with<br>
your team.<br>
<br>
Remember, you're not alone in your journey in SOK26! KDE is a community,<br>
and Season of KDE is a great opportunity to become more involved. Use<br>
the communication channels and mailing lists mentioned here, and those<br>
related to your projects.<br>
<br>
When you have questions, don't hesitate to ask mentors or us in the<br>
management team (kde-soc-management at <a href="http://kde.org" rel="noreferrer noreferrer" target="_blank">kde.org</a>). Mentors are here to guide<br>
you, and we're all here to help and are excited to learn about your<br>
progress!<br>
<br>
The timeline for Season Of KDE 2026 can be found here:<br>
<a href="https://mentorship.kde.org/sok/" rel="noreferrer noreferrer" target="_blank">https://mentorship.kde.org/sok/</a><br>
<br>
== TO-DOs ==<br>
<br>
_Status Reports_<br>
<br>
During SOK26 you will need to maintain a Status Report at<br>
<<a href="https://community.kde.org/SoK/2026/StatusReport" rel="noreferrer noreferrer" target="_blank">https://community.kde.org/SoK/2026/StatusReport</a>>. It is best to update<br>
this weekly.<br>
<br>
See past Status Reports in the community wiki for examples.<br>
<br>
_Blogging_<br>
<br>
You will need to blog at least twice during the 8 weeks of SOK26 --<br>
although we encourage you to blog more when you can! Blogging is how<br>
developers, artists, translators, and other KDE contributors communicate<br>
with the wider KDE community; see <a href="http://planet.kde.org" rel="noreferrer noreferrer" target="_blank">planet.kde.org</a> for examples of<br>
community blogging.<br>
<br>
(1) Your first blog post will need to be published between weeks<br>
3-5 of SOK26. This post should include information about your project,<br>
what you have achieved so far, what you plan to do before the end of<br>
work, as well as offer some reflection on what has not gone so well and<br>
how it can be improved.<br>
<br>
(2) Your second blog post will be published after the end of work<br>
on 20 March in <a href="http://mentorship.kde.org" rel="noreferrer noreferrer" target="_blank">mentorship.kde.org</a>. This will be a co-authored blog post<br>
with all other new contributors in SOK26. In this post you will celebrate<br>
your achievements and identify ways to advance the project going forward.<br>
<br>
Information about blogging platforms for you to use during SOK is<br>
provided below.<br>
<br>
_Email & Chat_<br>
<br>
Important: ask your mentor(s) about the communication channels used by<br>
your team so you can subscribe to them asap.<br>
<br>
You should already be subscribed to the 'kde-soc' mailing list at<br>
<<a href="https://mail.kde.org/mailman/listinfo/kde-soc" rel="noreferrer noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/kde-soc</a>>. Here we will officially<br>
update new contributors about Season of KDE. Many previous Season of KDE<br>
and Google Summer of Code (GSoC) contributors are subscribed to the list<br>
as well.<br>
<br>
Also, please join the mentorship Matrix room<br>
<<a href="https://matrix.to/#/%23kde-mentorship:kde.org" rel="noreferrer noreferrer" target="_blank">https://matrix.to/#/#kde-mentorship:kde.org</a>> to chat with mentors and<br>
previous SOK and GSoC contributors.<br>
<br>
It is also important to subscribe to the 'kde-community' mailing at<br>
<<a href="https://mail.kde.org/mailman/listinfo/kde-community" rel="noreferrer noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/kde-community</a>>. Here you can<br>
participate in community-wide discussions.<br>
<br>
== KDE SERVICES ==<br>
<br>
_Invent_ (GitLab)<br>
<br>
KDE's GitLab instance is found at <<a href="https://invent.kde.org" rel="noreferrer noreferrer" target="_blank">https://invent.kde.org</a>>. You should<br>
already have an account there. If not, please contact your mentors asap.<br>
<br>
*Important*: Your Invent (GitLab) credentials are used to log in to<br>
several KDE services.<br>
<br>
_Matrix_<br>
<br>
KDE uses Matrix as its primary chat platform. If you do not already have<br>
an account, follow the instructions here:<br>
<<a href="https://community.kde.org/Matrix#Registering_and_Logging_in" rel="noreferrer noreferrer" target="_blank">https://community.kde.org/Matrix#Registering_and_Logging_in</a>>. Once you<br>
have a Matrix account, please join the Matrix rooms used by your team<br>
and those rooms listed here.<br>
<br>
_Blogging_<br>
<br>
If you have one, you can use your own personal blog during SOK26. You<br>
will simply need to add it to the feed of <a href="http://planet.kde.org" rel="noreferrer noreferrer" target="_blank">planet.kde.org</a> at<br>
<<a href="https://invent.kde.org/websites/planet-kde-org" rel="noreferrer noreferrer" target="_blank">https://invent.kde.org/websites/planet-kde-org</a>>.<br>
<br>
If you do not have a personal blog, you can use <a href="http://blogs.kde.org" rel="noreferrer noreferrer" target="_blank">blogs.kde.org</a><br>
for blogging. We use Hugo for our website. Just write your blog post in<br>
markdown and make an MR at<br>
<<a href="https://invent.kde.org/websites/blogs-kde-org" rel="noreferrer noreferrer" target="_blank">https://invent.kde.org/websites/blogs-kde-org</a>>.<br>
<br>
An example blog post written in Markdown can be found at<br>
<<a href="https://invent.kde.org/websites/mentorship-kde-org/-/blob/master/content/blog/2023-12-16-sok-2024.md" rel="noreferrer noreferrer" target="_blank">https://invent.kde.org/websites/mentorship-kde-org/-/blob/master/content/blog/2023-12-16-sok-2024.md</a>>.<br>
<br>
_Collaborate_ (NextCloud)<br>
<br>
KDE's NextCloud instance is found at<br>
<<a href="https://collaborate.kde.org/login" rel="noreferrer noreferrer" target="_blank">https://collaborate.kde.org/login</a>>. Collaborate is useful for sharing<br>
and syncing files with others. You can log in to Collaborate with your<br>
Invent (GitLab) credentials.<br>
In order to access Collaborate (NextCloud), you will<br>
need to be in a group that has a shared folder there.<br>
Ask your mentors if the project has a shared folder on Collaborate, and<br>
if they do you can request to be added to that group!<br>
<br>
_Discuss_ (Discourse)<br>
<br>
KDE's forum is called Discuss, which uses the Discourse software. The<br>
forum can be found at <<a href="https://discuss.kde.org/" rel="noreferrer noreferrer" target="_blank">https://discuss.kde.org/</a>>. You can log in to<br>
Discuss with your Invent (GitLab) credentials.<br>
<br>
If you have any questions about the information above, please be in<br>
touch with us or the project mentors any time. We are here to help!<br>
<br>
Cheers,<br>
<br>
Johnny<br>
(on behalf of the mentorship team)<br>
<br>
Hashtag: #SOK26<br>
(uppercase O for screen readers)<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Kde-soc mailing list<br>
<a href="mailto:Kde-soc@kde.org" target="_blank" rel="noreferrer">Kde-soc@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-soc" rel="noreferrer noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/kde-soc</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Kde-soc Digest, Vol 187, Issue 2<br>
***************************************<br>
</blockquote></div>