What problems should we focus on?

For this year's company Hackathon we propose to pick one of these 3 areas of improvement (categories):

• Better integrate designers in the workflow with developers. e.g. create a plugin to sync Figma design tokens with React's theme, create UI blocks, POC a new composition API, etc.
• Bring in a fancy upvoted pain on GitHub. e.g. rewrite the Select to be composable and performant, bring in the first charts, make the demos editable in the docs, add new components, etc.
• Help developers to build apps, faster. e.g; build a https://openchakra.app/, build a theme builder, etc.

How do we run it?

We have scheduled 12 hours of work to allocate to the problem during the week (see the "MUI time-off" Google agenda). It's not a lot, it will require finding a quick and original solution to the problem: to hack.

I have invited the whole company (except Sebastian that is going on holiday this week) to these Google events.

• Monday 20th: we create the squads
• Tuesday 21th 13:00 UTC: we kick-off the hackathon with a meeting
• Thursday 23th 15:30 UTC: we wrap the hackathon with a demo and a vote on the best project

Creating squads

We propose to form 3 squads. Each squad should have:

1. at least one member of the Core team and the X team
2. between 2 and 4 people, ideally 3

The squads will be created in three phases:

1. First, individuals that want to lead the work on a specific initiative will create a new entry in the table below. He's/She's the owner.
2. Once we have all the proposed initiatives, interested individuals will fill the "Interested members" column with the pains that are interested in solving. You can pick up to three initiatives.
3. Lastly, a negotiation will have to happen to finally land with only three squads, with the above constraints (a. and b.)

Squads proposals

Demo time

https://twitter.com/olivtassinari/status/1441773885259583491