burrito.space / web-commons
this repo has no description
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

HTML 91.9%
JavaScript 8.1%
1 1 0

Clone this repository

https://tangled.org/burrito.space/web-commons https://tangled.org/did:plc:7r5c5jhtphcpkg3y55xu2y64/web-commons
git@tangled.org:burrito.space/web-commons git@tangled.org:did:plc:7r5c5jhtphcpkg3y55xu2y64/web-commons

For self-hosted knots, clone URLs may differ based on your setup.

Download tar.gz
README.md

Web Platform Funding MSI#

tl;dr: Multi-stakeholder initiative for funding work on web platform changes from standards/feature development and bug fixing in existing engines and also supporting a long term goal of a web platform engine which is independent of any one company, and collectively funded, governed, developed and maintained.

Original text#

  • Status quo is largely intractable while the three web engines are captive to single-business goals.
  • The long term goal is engine commodification. We can't place one bet on a leapfrog moment where AI makes that happen soon.
  • A theory-of-change approach of walking back from that state would be engine diversity.
  • While we need to develop a shareable framework for articulating why, Servo is best choice today as 4th major engine.
  • My preference is to name and brand the org in a way that keeps the scope door open, while clearly putting Servo up front as first major urgent initiative as a way to build allies and momentum.

Problem statement#

  • There are three web engines, each controlled by a single company
  • Each of those companies have their own business model
  • Each business model supports, benefits from the web
  • Each business model is conflict with a web that puts user needs first
  • This means that the shape of the web is difficult to change
  • It is slow to meet basic business needs outside of the three engine-makers
  • And only serves the largest common denominator
  • It's slow to react in crisis conditions
  • And does not serve those at the edges who need it most
  • The three web engine companies have no incentive to share power
  • Commodification of web engines is a long way off

Scope & Activities#

two core streams:

  • features and fixes on existing web engines
  • rapidly driving towards an independent web engine

what it does

  • identifies and organizes stakeholders
  • gathers and communicates stakeholder needs
  • drives collective decision-making on annual priorities
  • collects, pools and manages funds
  • deploys funding against those priorities
  • manages an ecosystem of implementers/maintainers (funding receivers)

what it does not do

  • build software itself
  • create new standards separate from w3c/ietf/etc

outcomes

  • coalition committed to an multi-stakeholder web engine (first in history)
  • circular sustaining ecosytem for collectively-governed web engine in 5yrs

Stakeholders#

non-business

  • end users
  • policy makers / regulators
  • NGOs

business

  • developer tools (eg Tauri)
  • phone makers (eg Huawei)
  • web engine makers
  • browser makers
  • publishers
  • dev consultancis (eg Igalia)

two classes

  • non revenue generating
  • revenue generating

Operations#

structure

  • non-profit foundation in a suitable european country
  • rotating board

operations

  • staff: ED, admin
  • annual IRL meeting
  • quarterly remote stakeholder/community review meetings
  • monthly vendor meetings

TODO#

  • add timeline
  • no use of "consortium"