Strong +1 on this.

We should apply the same standards to our promo material as we do to our code. This includes:

• open: everything needs to be publicly accessible (unless there's a good reason not to) .
• freely licensed: Goes without saying.
• reusable: We don't want to create new material for each and every event. We should have generic material that fits many events.
• customizable: For some events we want to tailor our material. We need to have a way to do so without redoing it from scratch. For this we need access to the source files where applicable.
• avoiding redundancy: We should only reinvent the wheel when necessary.
• guidelines: Like we have coding style guidelines we need guidelines for visual material (think fonts, colors etc).
• community maintenance: The whole community should have a sense of responsibility for our material.

I understand that it isn't (and it shouldn't be) the job of the promo contractors to create large amounts of material. However, I think it *is* their job to do the necessary coordination and maintenance to make sure the above criteria are met.

Agreed.

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?

What would be the best approach for materials that don't have a source file? There are quite a few of those, where people just created something and sent a PDF or some other, difficult-to-edit file format. For some it might be possible to track down the source, but not for all...

Thanks!

In T11867#205420, @skadinna wrote:

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?

I'm not sure. I think having them on Nextcloud is a better solution since it provides better capabilities for file management, version history etc. My gripe with the current nextcloud folder is that it is not discoverable without knowing the link to it. It should be in a folder that is visible/navigateable from share.kde.org without knowing the exact url. Downside might be that it would possibly be only accessible with a KDE identity account (not sure this is the case), but maybe we can find a solution for this

What would be the best approach for materials that don't have a source file? There are quite a few of those, where people just created something and sent a PDF or some other, difficult-to-edit file format. For some it might be possible to track down the source, but not for all...

We should try to contact the authors where possible. If we don't get the source for everything it's not a big deal, anything is better than the status quo.

We have started to collect material we have/found in a folder.

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.

I only wanted to create a wiki page as an index/catalog of all the resources we have. It would provide direct links to source files on Nextcloud. We can also add a warning box to the wiki page about any requirements or potential obstacles to getting access, such as needing an Identity account.

Would that make sense?

If yes, I'll get on with making that page. I'll also add the folder you shared to the page.

Or... Just share the link somewhere obvious and public for now, like on the wiki. Currently, the folder is not very organised, but, with feedback, that can change. There are some things that are write only and should probably stay that way, like templates, or backups of materials, or master materials. Would that be a problem?

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

Would you consider this an improvement?

There are still a few things I need to catalog, but it would be good to know if this is the right direction. Of course, everyone is welcome to edit these wiki pages and add more things that might be missing.