It seems useful to have a clearance by Legal before doing this.

I'm just saying, this would be massively useful for creating mockups for non-WMF volunteers. Having to manually create each element is a nightmare and also leads to inaccuracies.

One point to clarify is licensing. Both of the files and of sharing them out via Figma community. It seems that one can decide which license the files are shared (example CC BY 4.0).
FWIW, in the Design Style Guide we currently state about our icon files being CC BY 4.0 as well.

We want to start sharing our Figma libraries with the Figma community and I've posted some open questions to solve in the task description.

Which libraries or Figma files do we want to share with the community?

• Components library: Codex, OOUI or both? Since Codex is the library (and demo) we are improving, I would share this one with the community. We could share the OOUI library too but it could create confusion and also we should explain that it's not the main library we are improving in the Design System. So I lean towards sharing just the Codex component's library

• Assets library (icons, logos and illustrations) I agree with sharing this library.

• Design Tokens library (Figma styles) I agree with sharing this library and explain that these styles are being used within our libraries and design projects.

• Component’s exploration file template We could share this Figma file since it's the template used in our design contribution guidelines and designers could use it to create new components.

Which other Figma files could we share with the Figma community? @ldelench_wmf @CCiufo-WMF let us know your thoughts on this.

On “Components library: Codex, OOUI or both?” – I would only opt for Codex in order to

1. not confuse folks with two very similar but in small and important things different library
2. not to populate OOUI as it's been designated to be deprecated in future
3. keep the maintenance burden when updating lower

I'd suggest to keep the updates to a 1-2 months cadence, meaning we'd have 6-10 updates per year. Maybe even longer depending on how complex such update is.

In T288370#8653691, @Volker_E wrote:

On “Components library: Codex, OOUI or both?” – I would only opt for Codex in order to

1. not confuse folks with two very similar but in small and important things different library
2. not to populate OOUI as it's been designated to be deprecated in future
3. keep the maintenance burden when updating lower

Totally agree!

@bmartinezcalvo @Volker_E is there a renewed interest in doing this soon? To further avoid confusion, I think it might be worth timing with T324228, although I don't think it's strictly necessary.

In T288370#8673183, @CCiufo-WMF wrote:

@bmartinezcalvo @Volker_E is there a renewed interest in doing this soon? To further avoid confusion, I think it might be worth timing with T324228, although I don't think it's strictly necessary.

This came from a session with the Design Team some weeks ago where each designer needed to choose one action item to do to engage with the design community. I chose the one to share our Figma libraries as Figma community files (some time ago we started this conversation but our Figma libraries were not enough prepared at that moment).

I think we could share the libraries now and then update them if needed if we do some changes when creating Codex as DS (e.g. name changes in the libraries). Since libraries will need to be updated regularly in the Figma community, this is something we could do.

In T288370#8673259, @bmartinezcalvo wrote:

In T288370#8673183, @CCiufo-WMF wrote:

@bmartinezcalvo @Volker_E is there a renewed interest in doing this soon? To further avoid confusion, I think it might be worth timing with T324228, although I don't think it's strictly necessary.

This came from a session with the Design Team some weeks ago where each designer needed to choose one action item to do to engage with the design community. I chose the one to share our Figma libraries as Figma community files (some time ago we started this conversation but our Figma libraries were not enough prepared at that moment).

FWIW this is not necessarily something that needs to be done with any urgency.

@CCiufo-WMF @bmartinezcalvo Additionally with pairing with Codex as design system activities, I'd also suggest, with all our widening outreach activities, to wait until we have our higher priority inward-oriented house clean. Like basic components implemented, both in Vue and CSS-only. And tokens done.
Community facing activity, here a non-Wikimedia community will only bring profit if we care about community requests. And I don't see lots of over-capacity for us currently to do so. Quite the opposite.