Skip to content

chore: new code of conduct draft; proposed language updates to README #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
castastrophe wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: new code of conduct draft; proposed language updates to README #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
81 changes: 81 additions & 0 deletions CODE_OF_CONDUCT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
# Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to make participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, gender identity and expression, level of experience,
nationality, personal appearance, race, religion, or sexual identity and
orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment
include:

- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

- The use of sexualized language or imagery, and unwelcome sexual attention or advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or electronic
address, without explicit permission
- Any other conduct which could reasonably be considered inappropriate, discriminatory, or harmful in a professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable
behavior and must take prompt, appropriate, and fair corrective action in
response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that violate this Code of Conduct or are otherwise inappropriate, threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the maintainers directly. All complaints will be reviewed and investigated promptly and will result in a response that is deemed necessary and appropriate to the circumstances. We are committed to maintaining confidentiality for those who report incidents. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good
faith will face temporary or permanent repercussions as determined by other
members of the project's leadership.

## Consequences

Project maintainers who determine that a participant has violated this Code of Conduct may take any action they deem appropriate, up to and including:

- **Correction**: A private, written warning providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A warning may include a request for a public or private apology.

- **Warning**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

- **Temporary Ban**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

- **Permanent Ban**: A permanent ban from any sort of public interaction within the community.

These consequences may be applied immediately and without prior warning for severe violations, such as threats of violence, sexual harassment, or discriminatory behavior. The specific consequences will be determined based on the severity and frequency of the violation, and will be communicated to the individual in question.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
available at [http://contributor-covenant.org/version/1/4][version]

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/
58 changes: 29 additions & 29 deletions profile/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,11 @@
# Web Platform Collective

> [!IMPORTANT]
> **This effort is a work in progress and is still very early stage**.
This readme is a placeholder.
But while you’re here, here’s a draft of what we’re thinking about.
> **This effort is a work in progress**.

This is a placeholder with more exciting details to come.

...But while you're here, we'd love your thoughts on this draft.

## TPAC 2025 breakout

Expand All @@ -12,74 +14,72 @@ But while you’re here, here’s a draft of what we’re thinking about.

## Mission

Web Platform Collective aims to empower web stakeholders of all sizes to have their web platform pain points addressed and to make independent standards work financially sustainable.
Web Platform Collective aims to empower web stakeholders of all sizes to address their web platform pain points and to make independent standards work financially sustainable.

Our guiding principles:

Our manifesto:
- We believe that all web stakeholders, small and large, should be able to fund web platform improvements that address their pain points without investing thousands of hours in understanding the (admittedly opaque and intimidating) web standards landscape or hiring full-time staff for this purpose.
- We believe that even smaller web stakeholders can benefit from solving their pain points directly in the web platform, rather than having to spend thousands or millions working around them ad infinitum.
- We believe that web platform design is critical, highly impactful work, and doing it well is an extremely rare, interdisciplinary skill drawing on skills and knowledge from many different disciplines such as product management, software engineering, HCI, and more.
Therefore, we believe that independent web platform designers should be able to earn a sustainable living doing what they do best — advancing the web — without being forced to choose between unpaid side work and employment at a browser vendor (which suits some, but not all).
- We believe that web platform design is critical, highly impactful work. Doing it well is an extremely rare, interdisciplinary skill requiring expertise in product management, software engineering, HCI, and more. Therefore, we believe that independent web platform designers should be able to earn a sustainable living doing what they do best — advancing the web — without being forced to choose between unpaid side work and employment at a browser vendor (which suits some, but not all).

<!--
We want to be the entity that abstracts all of this, translates web stakeholder needs into standards proposals, and champions them to wide implementation across all browsers, and we are uniquely positioned to play that role.
-->

## How does it work?

We work with organizations of any size to listen to their pain points and create an individualized plan to address them, depending on:
We work with organizations of any size to listen to their pain points and create an individual plan to address them, depending on:

1. **Status:** Are there existing solutions for this pain point, and what is their implementation status?
2. **Budget:** How much are you willing to invest to address said pain point?
This can range from a few hours of work to several months, and from one person exploring the problem space and writing a proposal to user research, spec writing, tests, docs[^1], developer outreach, implementation in browsers[^1] etc, the sky is the limit.
Obviously, the larger the investment, the higher the odds of success and the shorter the timeline.
1. **Scope:** Would addressing the pain point require a small improvement to an existing feature, or a whole new web technology? The larger the scope, the higher the risk.
This can range from a few hours of work to several months, and from one person exploring the problem space and writing a proposal to user research, spec writing, tests, docs[^1], developer outreach, implementation in browsers[^1], etc. The sky is the limit.
Obviously, the larger the investment, the higher the odds of success and the shorter the timeline.
3. **Scope:** Would addressing the pain point require a small improvement to an existing feature, or a whole new web technology? The larger the scope, the higher the risk.

[^1]: via partner organizations

## FAQ

## Who are you?
### Who are you?

The core founding team includes highly experienced web standards designers and architects with a proven track record and deep tenure across multiple standards groups, review bodies such as the TAG and the W3C Advisory Board, and broad, hands-on expertise spanning multiple web platform areas.
The core founding team includes highly experienced web standards designers and architects with a proven track record and deep tenure across multiple standards groups. Our members have served on review bodies such as the TAG and the W3C Advisory Board, and bring broad, hands-on expertise spanning multiple web platform areas.

We also collaborate with a larger network of independent web platform designers who bring specialized expertise in particular technologies.

### Are you a consortium? Or a Working Group?

Neither!
We do not aim to replace venues for standardization, like W3C, WHATWG, TC39, etc.
We envision the Web Platform Collective as a change agent in those spaces,
engaging relevant parties there to drive progress on various features on behalf of diverse web stakeholders and drawing from our breadth of expertise to connect the dots and unify efforts across different standards groups.

We do not aim to replace venues for standardization—like W3C, WHATWG, TC39, etc. Instead, we envision the Web Platform Collective as a change agent in those spaces, engaging relevant parties to drive progress on various features on behalf of diverse web stakeholders. We draw from our breadth of expertise to connect the dots and unify efforts across different standards groups.

### Are you an agency? A nonprofit? Something else?

Both!

**All web platform work is public benefit work**, regardless of the driver behind it.
Nobody can push a web platform feature forwards that does not broadly benefit web developers and users, it will simply get rejected.

Nobody can push a web platform feature forward that does not broadly benefit web developers and users; it will simply get rejected.

Some of our work may be driven by a specific company’s needs, similar to an agency.
Other work may come from our own gap analysis and then collaboratively funded by multiple web stakeholders,
which is closer to a nonprofit model.
But the web platform improvements that stem from either model benefit everyone.
Other work may come from our own gap analysis and then collaboratively funded by multiple web stakeholders, which is closer to a nonprofit model. But the web platform improvements that stem from either model benefit everyone.

### Aren’t web standards only for big companies that can play the long game? We need to ship, like yesterday! We can’t sit around and wait for standards!
### Aren't web standards only for big companies that can play the long game? We need to ship, like yesterday! We can't sit around and wait for standards

When looking at web standards timelines from the outside, it often seems like the process is slow.
However, in most cases, work stalls because no-one is driving it forward, not because of inherent resistance or dysfunction.
However, in most cases, work stalls because no one is driving it forward, not because of inherent resistance or dysfunction.

When standards work is well funded (and sometimes even when it isn't), it can move pretty fast.
There are many success stories of **major** web technologies going from conception to [baseline](https://developer.mozilla.org/en-US/docs/Glossary/Baseline/Compatibility) in less than two years (e.g. [CSS Cascade Layers](https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/Styling_basics/Cascade_layers)),
and smaller features in a matter of months.
This is shorter than many product development cycles!

Yes, it’s not instant.
You’ll still have to work around the limitation for a little bit more.
Yes, it's not instant.
You'll still have to work around the limitation for a while longer.
But _how_ you work around it can be very different:

- **Progressive enhancement**: Many web features can add value even before they are implemented in all browsers, through polyfills and/or progressive enhancement.
- **Strategy**: Knowing what the web platform landscape will look like in the near-future can help you make better product decisions today, and give you a leg up over competitors.
- **Strategy**: Knowing what the web platform landscape will look like in the near future can help you make better product decisions today and provide a competitive advantage.

----

If you want to get involved, either to get your own web platform pain points addressed or to join us, please get in touch at hello at webplatform.design.



If you want to get involved, either to get your own web platform pain points addressed or to join us, please get in touch: hello at webplatform.design.