You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Show sponsors in the README or on the website. #377
This is part of the requirements to be able to use the platforms that could be used in the performance group (see expressjs/perf-wg#5 (comment)). I'm opening this issue to track it, since a decision needs to be made about where this should be displayed (@wesleytodd likely has more context on the terms).
I suppose @expressjs/docs-wg should be involved here as well, since this involves the website.
For services that we get for free from an open source plan, we can always reach out to them to be sure they are satisified with what we have done.
My preference is that we do it in the repo for the project which is literally using the services. AKA, if the perf-wg is using Digital ocean, and they want a repo shoutout, shoutout can go into that repo to thank them for their generosity for the project..
We use netlify previews for the website, so we have a badge on the website to thank them for the deploy previews, per their policy.
Activity
bjohansebas commentedon Jul 14, 2025
@wesleytodd, do you know what the requirements are to use the platforms that are going to be used?
jonchurch commentedon Jul 21, 2025
For services that we get for free from an open source plan, we can always reach out to them to be sure they are satisified with what we have done.
My preference is that we do it in the repo for the project which is literally using the services. AKA, if the perf-wg is using Digital ocean, and they want a repo shoutout, shoutout can go into that repo to thank them for their generosity for the project..
We use netlify previews for the website, so we have a badge on the website to thank them for the deploy previews, per their policy.