[website] List benefits for sponsors #39640
Conversation
oliviertassinari
added
the
website
Netlify deploy previewBundle size report |
| @@ -2,11 +2,9 @@ | |||
|
|
|||
| <p class="description">Support the development of new open-source projects from MUI through crowdfunding.</p> | |||
|
|
|||
| The core of MUI is our crowd-funded open-source projects, licensed under the permissive MIT license. Sponsorship increases the rate of bug fixes, documentation improvements, and feature development. | |||
| MUI Core is our crowd-funded open-source projects, licensed under the permissive MIT license. Sponsorship increases the rate of bug fixes, documentation improvements, and feature development. | |||
There was a problem hiding this comment.
| MUI Core is our crowd-funded open-source projects, licensed under the permissive MIT license. Sponsorship increases the rate of bug fixes, documentation improvements, and feature development. | |
| MUI Core contains our crowd-funded open-source projects, offered under the permissive MIT license. Sponsorship increases the rate of bug fixes, documentation improvements, and feature development. |
There was a problem hiding this comment.
I believe we have 3 options when it comes to the Open Collective:
- Creating one open-collective per open-source project: https://opencollective.com/mui is about Material UI, we would have a couple more to create. Considering the traction we have with the community, and the impact these donations tend to have (low), we have time until we need ones. So effectively, only rename https://opencollective.com/mui to https://opencollective.com/material-ui for now.
- Considering that MUI is the organization, the umbrella under which we are pushing for the work. It doesn't feel so great, as a developer would likely want to sponsor one project and not another, like Vite vs. Vitest. However, it stays broad, still allowing us to cover some of Base UI, Joy UI, and MUI X.
- Considering that MUI is one open-source project that has a large breadth. In which case, https://opencollective.com/mui wouldn't need any changes.
Even if we kill https://mui.com/joy-ui/, and we split Joy to be under Material UI (as a theme, like Material Design v3, or Material Design v2, while we work on an infra to create more theme), as well as under Base UI (as a theme), it feels like option 2 still makes the most sense right now.
The problem with option 3 is how much it can be perceived by developers as a. lacking focus, b. vendor lock-in, and c. creates confusion around use cases.
For example, when you look at Slack vs. Microsoft Team, you are more likely to use Slack as a standalone product, but overall Microsoft Team wins because it comes for free in a bundle you already purchased. So if we were to apply this straight to us, option 3 would make the most sense. However, our space is very different: 1. products are free 2. product value compounds with its community size. We are only left with the value of bundling. The main problem is how developers adopt the solutions that have the best execution. Headless UI failure is an example of this, Radix had x6 more engineering time execution, it was too far for Headless UI to thrive with its Tailwind CSS users.
One thing, maybe https://opencollective.com/mui -> https://opencollective.com/mui-org would make that intent to be clearer. In the same line of thought, going to GitHub https://github.com/mui/ -> https://github.com/mui-org/ as long as Material UI is > 50% of the product adoption of what we do. Once we have more product diversity, and we keep MUI brand pristine, I'm confident we can have MUI live as its own brand, so revert mui-org, back to the shorthand mui.
GitHub org name is not to be confused with a change on npm @mui/material -> @material-ui/core, because the npm org name is expected to be the open-source project name (I'm not aware of any project where it's not the case, we are the exception). On GitHub, the org name for popular open-source projects is quite diverse: individual, open-source project name, company name, etc.
cc @mbrookes @danilo-leal @mnajdova
As a side note, we are moving from "MUI Core" to a notion of "Core project of MUI", so I replaced a few instances.
| - the [README.md](https://github.com/mui/material-ui#sponsors) (80k+ unique visitors per month) | ||
| - the [sponsors' list](#gold-sponsors) | ||
|
|
||
| \*we accept donations, but we won't show unethical ads. |
There was a problem hiding this comment.
We should probably elaborate more here—it might not be obvious what we consider "unethical."
There was a problem hiding this comment.
I think we can keep it broad & confusing so that we can more easily reject sponsors.
github-actions
bot
added
the
PR: out-of-date
Co-authored-by: Sam Sycamore <71297412+samuelsycamore@users.noreply.github.com> Signed-off-by: Olivier Tassinari <olivier.tassinari@gmail.com>
oliviertassinari
force-pushed
the
tiers-benefits
branch
from
39f559b
to
973b18e
Compare
github-actions
bot
removed
the
PR: out-of-date
Co-authored-by: Sam Sycamore <71297412+samuelsycamore@users.noreply.github.com> Signed-off-by: Olivier Tassinari <olivier.tassinari@gmail.com>
Signed-off-by: Olivier Tassinari <olivier.tassinari@gmail.com>
Execute on mui/material-ui#39640 (comment). The first step is to make it clear that this is an umbrella OpenCollective. We will use to dedicated open-source collectives once we find it clear that something beyond Material UI works and needs its own support. Signed-off-by: Olivier Tassinari <olivier.tassinari@gmail.com>
Execute on #39640 (comment). The first step is to make it clear that this is an umbrella OpenCollective, and not the OpenCollective for Material UI. We will use to dedicated open-source collectives once we find it clear that something beyond Material UI works and needs its own support.
Execute on mui/material-ui#39640 (comment). The first step is to make it clear that this is an umbrella OpenCollective, and not the OpenCollective for Material UI. We will use to dedicated open-source collectives once we find it clear that something beyond Material UI works and needs its own support.
Execute on mui/material-ui#39640 (comment). The first step is to make it clear that this is an umbrella OpenCollective, and not the OpenCollective for Material UI. We will use to dedicated open-source collectives once we find it clear that something beyond Material UI works and needs its own support.
Execute on mui#39640 (comment). The first step is to make it clear that this is an umbrella OpenCollective, and not the OpenCollective for Material UI. We will use to dedicated open-source collectives once we find it clear that something beyond Material UI works and needs its own support.
Execute on mui#39640 (comment). The first step is to make it clear that this is an umbrella OpenCollective, and not the OpenCollective for Material UI. We will use to dedicated open-source collectives once we find it clear that something beyond Material UI works and needs its own support.
Execute on mui#39640 (comment). The first step is to make it clear that this is an umbrella OpenCollective, and not the OpenCollective for Material UI. We will use to dedicated open-source collectives once we find it clear that something beyond Material UI works and needs its own support.
The idea started from https://mui.zendesk.com/agent/tickets/13200, using https://vuejs.org/sponsor/#tier-benefits as inspiration for the execution.
Preview: https://deploy-preview-39640--material-ui.netlify.app/material-ui/discover-more/backers/