-
Notifications
You must be signed in to change notification settings - Fork 128
Call for sponsors #291
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.
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
Call for sponsors #291
Conversation
font-size: 16px; | ||
footer ul { | ||
list-style: none; | ||
padding: 0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
weird indentation
#paypal { | ||
text-align: center; | ||
footer > ul > li { | ||
float: left; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same
</dd> | ||
<dd> | ||
<a href="https://pledgie.com/campaigns/14709">Pledgie</a> | ||
</dd> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let’s remove the Pledgie link here — just the PayPal link is enough.
<ul> | ||
<li> | ||
<h4>Sponsors</h4> | ||
<p>Hosting generously provided by <a href="https://m.do.co/c/b426e15331e8" target="_blank">DigitalOcean</a> and <a href="https://zeit.co/" target="_blank">Zeit</a></p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where did this link come from?
FTR: DigitalOcean gave us some much-appreciated credits, but they don’t provide us with unlimited hosting forever. That’s why there is still a necessity for a “hosting fund”. We should probably figure out how we’ll make this work. Where (i.e. which donations) do the hosting credits come from?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where did this link come from?
I logged in to our account, went to their referral program page, and clicked "Get your referral link." Hopefully if you follow the same steps, you'll get the same link. Goal was to funnel referrals to the jsPerf DO account to extend runway.
Where (i.e. which donations) do the hosting credits come from?
I thought we had enough credits to get us through 2017 so I haven't given this much thought. IMO funds for hosting should be kept separate from funds for contributors. Maybe we can clarify that Carbon Ads proceeds go towards hosting?
<a href="https://github.com/jsperf/jsperf.com" target="_blank">GitHub</a> | ||
</li> | ||
<li> | ||
<a href="https://webchat.freenode.net/?channels=jsperf" target="_blank">IRC</a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let’s remove the use of target="_blank"
everywhere. Developers can decide on their own if they choose to open a link in a new window/tab or not. (If you’d rather keep it, we should add rel=noopener
).
|
||
<p> | ||
Development of jsPerf is generously supported by contributions from individuals and corporations. If you are benefiting from jsPerf and would like to help keep the project financially sustainable, please donate to a core contributor. | ||
</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we could link to the open issues list, so that people can pick their favorite issue and sponsor the person who’s assigned to work on it, rather than randomly picking one of the core contributors in the list below?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree randomly picking someone isn't great. I'm hesitant to point to an issue list because I'm afraid it'll change sponsorship into "bug/feature bounty." That's fine if that's what motivates someone to sponsor, but we also want people to keep in mind the time it takes to...
- respond to issues
- review pull requests
- update dependencies
- monitor that the site is up
- fight spam
That ongoing effort is what they're sponsoring.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with those comments addressed.
👍
|
Can’t find the original comments anymore, so I’ll just reply here:
Agreed — ads & sponsorship deals are separate from donations. |
Update: This is now live: https://jsperf.com/sponsor
As many of you have noticed, development of jsperf.com has slowed. @mathiasbynens, @asilluron, and myself have all had personal setbacks over the past few months limiting the time we can spend on developing and operating this free and open source service. We've decided to move to a sponsorship model so we can continue working on the site in a financially sustainable way.
This PR calls out the need for sponsors in the README and on a dedicated Sponsor page. There are links to each core contributor's preferred donation service.
Our hosting is already generously provided by DigitalOcean (they gave us some credits that allow us to host the database for the near future) and Zeit (they fully sponsor our Node.js hosting!). The AMP Project made a donation to get v2 finished. Now, we're hoping other individuals and companies who benefit from jsPerf will continue supporting its development.
Please get in touch if you have ideas or questions. We're trying to be as transparent as possible during this process 💟