-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add endorsements #103
Comments
Feel free to add my testimonial. OSS Pledge is a gateway to sponsoring open source developers who are working hard to develop projects for the ecosystem |
Thank you @Delta456. 🙏 |
@chadwhitacre Love it. What if we had minor variations to break the regularity? Right now all testimonials have an Let me know when you’re happy with the design and I can implement it ASAP. |
We now also have permission from Johannes and Raymmar. Honestly I think a shorter quote from each would have more impact. Something like: "I can't overstate how excited I am about this. ❤️" —Johannes Link for full context. |
What's the need to link? I think that's enough validation we have there. |
The link is so people can follow up to check the original source and context. |
Ok, makes sense |
@chadwhitacre Are we still iterating on the design or shall I go ahead and get this implemented? |
Go for it. :) |
I've asked Xavier for permission, we are good to go from Johannes and Raymmar. |
Let's broaden this into "Endorsements" and include both personal (as above) and institutional (e.g., OSI, etc.; cf. #37) endorsements. |
Sounds good, do we have any endorsements we can share from foundations/ecosystem partners, or not yet? |
I expect we'll be able to pull some from the blog posts that are supposed to go out on Tuesday. |
e.g.
https://x.com/schickling/status/1832361798130954335
https://x.com/raymmar_/status/1832464000996548806
https://x.com/xdamman/status/1837021472499343492
Others?
Let's also include ecosystem partner endorsements, e.g., OSI, OC, Ruby Central, etc.
Should rotate one on the homepage and collect multiple on an /endorsements page.
The text was updated successfully, but these errors were encountered: