Typescript

https://www.figma.com/file/0QchRdipAVuvVoDfTjLrgQ/Adevinta---Spark-Components?node-id=0%3A1&t=Ie9Atot3dw2slkzs-1

Github actions

Opensource

Roles

There are 3 different role tiers:

Owner: Adevinta

The owner of the code is Adevinta. The [project name] will be under Adevinta Github’s public Organization. People can contribute using its personal GH user profile.

Maintainers: admin

There will be a maintainer team with an admin role. They had the governance of the project. They can take decisions, communicate changes, accelerate collaborators. They have a call to action conduct.

Collaborators

Employees: write

Adevinta employees can create PR directly without forking the repository

Others: read

• “main/master” branch is protected from forced pushes.

Contribution Strategy

We want to reduce the unnecessary bureaucracy needed for an interaction. We will follow the Ship/Show/Ask contribution strategy.

Ship

Direct contribution to master/main branch
Only for maintainers

Show

PR to master/main branch directly merged with no human revisions when CI/CD passes.
Only for maintainers

Ask

PR to master/main merged when CI/CD and human manual revision passes.
Maintainers and contributors default strategy.

MIT

[ ] Add info about "Brikke or not" in the spreadsheet #550

Stylelint

Spark

• Jest
• Testing library
• Vitest
• c8
• Istambul

ESLint

• ZeroHeight (could change in future)
• Storybook

• CJS – CommonJS
• AMD – Asynchronous Module Definition
• UMD – Universal Module Definition
• ESM – ECMAScript Modules

DEFINITION

The defined roles for the project must be:

• Owner: Adevinta®

• Maintainer: Admin

• Collaborators:

  • Inner devs: Write

  • Outer Devs: Read

Master branch protected for disallowing force pushes.

We need to add Andres Lucas (@andresin87) and Turo Lopez (@turolopezsanabria) to the organization as administrators to invite related people, create the required projects and organize whose roles.

• Chromatic
• PlayWright
• #439

• [ ]

• All components must have a default look and feel, that is valid unless a tenant overrides it with its own values
• A tenant can apply its own brand settings at application level
• A tenant can apply its own brand settings at page level
• A tenant can apply its own brand settings at component level
• A tenant can use the theming on its own components, even if they are not "spark"
• The naming convention must be shared between Dev and Design (same for Web iOS and Android)

tbd

Building tool

• Vite vs SVC
• #118

Monorepo

• NX + Lerna, vs SUI Mono
• #119