Reorganize labels

[Pwuts]

For increased accessibility and transparency of the project, we should assign more distinctive names to sub-projects and use consistent labeling to indicate the scope of issues.

An additional consideration: PRs can be auto-labeled based on the files changed. Issues have to be labeled by hand.

Project parts

• Platform
  • Technical sections
    • Frontend
    • Backend
      • Blocks
      • Executor
      • Scheduler
      • DB
      • API
        • internal
        • external
  • UX sections
    • Library
    • Marketplace
    • Builder
      • Blocks
    • User env (settings etc.)
    • Login/Signup
    • Admin panel(s)
    • Onboarding

Draft list of labels

State

• waiting for design
• good first issue (✅ already in place)

Type (✅ already in place)

• tech debt
• bug
• feature
• (improvement)

Size (✅ already in place; needs sync with Linear)

• size/xs
• size/s
• size/m
• size/l
• size/xl

General Scopes (for issues and PRs)

• platform
  • platform/library
  • platform/marketplace
  • platform/builder
    • platform/blocks (✅ already in place)
  • platform/user-env
  • platform/admin
  • platform/onboarding
  • platform/API/external
• documentation

Technical Scopes (for code)

• platform
  • platform/blocks (✅ already in place)
  • platform/frontend (✅ already in place)
  • platform/backend (✅ already in place)
    • platform/API
      • platform/API/external
    • platform/executor (✅ already in place)
    • platform/scheduler
    • platform/DB

Please drop your thoughts below!

Auto-labeling

• Update the auto-labeling bot to auto-assign all of the above scope labels where applicable
• Set up synchronization between Linear ticket issue and GitHub issue size label

[Pwuts]

This is a re-try of #7515