[SOK26] status reports / blog posts

[Johnny Jazeix]

Le jeu. 19 mars 2026 à 14:08, Johnny Jazeix <jazeix at gmail.com> a écrit :
>
> Hi SoK mentees!
>
> We are approaching the end of work for SoK this Friday, 20 March. [1]
>
> Unless you have requested an extension, results for SoK26 will be
> announced 27 March.
>
> There are 3 important to-dos and 1 very short final summary before
> finishing this season:
>
>     1. Wrap up and document your work
>     2. Complete your status reports
>     3. Make sure your blog post is published
>
>     4. And finally, after 1-3 are done, to complete SoK please write a
> 3-6 sentence general summary of what you achieved, check the text with
> your mentors, and then send it to Johnny (jazeix at gmail.com). This
> short text will be the basis for the final blog
> post celebrating your achievements. Please send this before *Sunday 5
> April*!
> For reference, here is the blog post from last year:
> https://mentorship.kde.org/blog/2025-05-04-sok-conclusion/
>

Hi,
I'm still missing 2 status reports
(https://community.kde.org/SoK/2026/StatusReport) and 10 missing blog
posts summaries
(https://invent.kde.org/websites/mentorship-kde-org/-/merge_requests/46/diffs#4a71c3088bbe7780f228e302fc60d96167a34051_0_15).
Please send them before the 8th.
If I don't have the status reports, I'll override the decision on the
projects and I'll mark them as non-completed.
If I don't have the summaries, I won't send the goodies to the
corresponding people.

Cheers,
Johnny



> _Details_
>
> To-do #1: Wrap up any unfinished work for SoK. If this is not doable
> before Friday 20 March, document what you did in the project and what still
> needs to be done so the work can be completed beyond SoK! And of course,
> you are cordially invited to continue contributing well beyond 20 March.
> People like you are what make this community so great!
>
> To-do #2: Make sure you have completed your Status Reports. This is not
> optional: it is how KDE documents what was done in SoK.
> Mentors, please make sure they work on it before the end of the project.
>
>     https://community.kde.org/SoK/2026/StatusReport
>
> To-do #3: If you have not done so already, you need to write a detailed
> blog post about the exciting work you did in SoK. Many have done so
> already, but some have not. I cannot stress how important this is. The
> blog posts are a way inform other contributors about what you are doing,
> what works and what does not work, and the posts let the world know all
> the cool and cutting-edge work that are happening at KDE. Please don't
> be afraid to get technical in your post: this is a technical community
> and we all benefit from the documentation these blog posts provide.
> And note that the important part is not the result, it's the journey and what
> you learnt (what failed, why, what worked, why this solution instead
> of another...).
>
> Most importantly, thank you for all that you have done so far and all
> that you will do for KDE and Free & Open Source Software. May this just
> be the beginning of a long journey with the KDE community!
>
> Cheers,
>
> Johnny