Here's 2 cents from a quiet observer:

If you're still taking suggestions, I'd like to point out a small but important detail: giving proper credit. This should be included in the guidelines section. If available, licensing information should be included in each post, and if we're posting something that's not our own original content, we should always indicate/credit the author.

Hi everyone, I know it's sad that we haven't been able to organize a sprint last year. Perhaps it will be better this year!

Is everyone OK with these suggestions? I can update the page, but I really don't want people to complain and tell me I shouldn't have done it two days after :/

This is great, Carl! Thank you so much for your work 👍 🙏

The part that remains is transferring information from here to the Community wiki: https://techbase.kde.org/Development/Guidelines/CIG

Since archiving and removing old resources from wiki pages seemed to cause some displeasure, I have tried a different approach.

I've added everything I could find to this page, including direct links to assets folders on Nextcloud: https://community.kde.org/Promo/Material

In T11835#207572, @lydia wrote:

@skadinna Should you be the assignee of this task? Are you handling anything for FOSDEM?

Hey @nicolasfella I'm sorry, perhaps I wasn't clear enough. I didn't mean to host the resources on the wiki. The majority of our current materials is already on Nextcloud anyway, so it wouldn't make much sense to move all that to an inferior solution.

@ognarb @vladimirmikulic That latest version looks really great!!

I've started collecting all the materials we have from previous events, and the plan is to create a list on a wiki page with direct links to source files. Would that work?

Minor update.

In T7844#203470, @ognarb wrote:

Let's close this task for now if I find deadlinks I usually fix them directly. I could reopen it if one day I have the motivation to do check all the pages.

@ognarb is the information from this task useful to you? Or do you already have another task that covers the same thing?

This task is still open - does it make sense to revisit in light of (upcoming) changes related to Release Service mentioned in T11767?

What happened with this task? I can't remember if we came to some kind of a decision about it or not...and it's assigned to me :(

Sadly, I don't have the technical know-how to help with this, but based on user feedback and discussions I've seen, I can tell you people are going to LOVE it. So with my Promo hat on, I fully support this idea! :)

There seems to be an overlap with this task: https://phabricator.kde.org/T6842

Before I start writing the draft, just wanna check: do we want a single Dot story covering all three round 1 goals, or should we write a separate closure story about each goal?

Looks amazing! Thank you so much for creating this layout, Paul!
The only issue I noticed is the address on the cover page - I think it's misspelled, so it might be worth double-checking. Everything else is great.

Here's a cleaned-up version of the draft, including feedback from your comments. This one is shorter because we removed the parts that were just repeating the same thing.

Topic suggestion: Improving the release announcement process and our relationship with developers

Great suggestions, @derkits!! Thanks so much. I think Paul is also aiming to make the whole thing shorter, so the next version of the draft should reflect that.

Here's also the first layout idea I put together. This one's a bit simplistic, so if we're going to do a new one, it should probably be more exciting and varied.

The text with some minor edits and reorganized sections is here (it's an ODT file):

I was working on it on-and-off with some major breaks in between, so it's unfortunately not done yet. I'll try to complete it this week so we have a small window for reviews before sending it out.

Hi David! Nice to meet you. I'm very glad to hear you're interested in improving KDE's documentation.

These past few days I've been looking into transforming and improving this proposal based on the feedback I received during last week's office hours. I have also tried to realistically assess my upcoming obligations for the next 6 months or so. Unfortunately, I don't think I would be able to fully commit to leading this goal if it were selected. :( It would be unfair to drag everyone down and waste people's time by promising and planning something, and then failing to deliver meaningful work.

Sure they do. But their text size to image size ratio is much more balanced than in your example, their text is spaced better, and their page width seems larger than in your example. If you want to do it this way, then the images from your example should be a lot smaller. Ideally it would be 50:50; it looks like the elementary example is pretty close to that.

Definitely put the text under images - not just on mobile, but on the desktop version as well. It doesn't look good at all when it's offset like that.

There is already a task that covers suggestions like this one: https://phabricator.kde.org/T10034

In T11243#192184, @KonqiDragon wrote:

I think that is how should look the area about new version of Plasma. But it's not perfect and needs to be improved.
<image>

Lots of great ideas here! I would just warn you about two things:

Thank you for the update, Neofytos. I'm wondering if there's anything we can do in the meantime, while we wait. Otherwise it might be all rushed if we get very close to the official announcement date without anything prepared in advance.

Hi everyone, I'm bumping this in priority and moving it to active tasks - if we really wanna do this. Since there hasn't been much activity on the ticket, I'm guessing there are no volunteers for writing the draft of the Dot story? :)

I'm not a reviewer, but you have a few minor issues:

In T11096#190705, @nicolasfella wrote:

maybe we could merge this task with T11117 (KDE is All About the Apps).

I don't think those two tasks have a large overlap, especially not the developer documentation part of this. It may make more sense to just merge the user documentation part of the task.