Ps4 Macedo Github

[Latrina Mosely]

As an open source maintainer, you should create a quality GitHub Sponsors Profile because you deserve to earn money for your valuable contributions to technology. You've given your time, money, and energy into supporting corporations and individual developers for very little compensation in return (even though you may have other things going on like a family or a full-time job). Meanwhile, well-funded corporations use your tooling to make even more money. Let's explore how we can make it easy for folks to give back to us in return!

Stripe is one of few organizations leading the charge on investing in open source projects. Corporations like Stripe invest in projects that they depend on or help to increase their revenue. For example, Stripe sponsors Nick DeJesus because his use-shopping-cart library makes it easier to manage shopping cart state and logic for Stripe checkout.

I recently met a portion of the Stripe Developer Advocacy team in real life (which was so cool)! During our meeting, I spent a significant time listening to Chris Traganos, the Developer Advocacy Engineering Manager at Stripe. He passionately spoke about how he believes organizations should fund open source maintainers. He believes open source maintainers need to develop GitHub Sponsors Profiles that make people interested in supporting their work.

Creating a GitHub Sponsors profile is part of marketing and increasing your project's visibility to attract more supporters. Although marketing can feel inauthentic, the reality is good marketing is vital to your project's longevity and success. Think about it: if no one knows your project exists, they will never see it. Also, the better you tell your story and make it easier for people to support you, the more people will give. The concept is similar to writing good contributing guidelines and a good README. Curating these documents helps folks understand your project's objectives and how they can get involved. This blog post will give you top tips on creating a GitHub Sponsors profile that will better appeal to potential sponsors.

The mission of GitHub Sponsors is to provide opportunities to participate in and build on open source. The advent of GitHub Sponsors and other third-party sponsorship models helps our industry take the right steps in making open source careers possible. GitHub Sponsors offers a native solution for individuals and corporations to sponsor open source maintainers and contributors.

To enable GitHub Sponsors for your profile or organization, you have to join the waitlist. The waitlist exists because the GitHub Sponsors team reviews applications to ensure they comply with GitHub's policies. Head over to this link. It will show you a list of your organizations and profiles that are eligible to join the waitlist for GitHub Sponsors, similar to the image below:

Meet the Team (for organizations) - For organizations, it's nice to highlight the team members who brought the vision to life! It can bring a more human element to the project, inspiring potential sponsors. The below image shows how dj-stripe opted to highlight their team members.

Highlight the accounts sponsoring you - To show your gratitude, highlight the folks who sponsor you. This may also indicate that your project is worth supporting if other folks sponsor you. Check out what highlighting accounts that sponsor you may look like:

After you build your profile, set up a funding.yml file in a .github folder at the root of your project. This special file exists so that when people click the sponsor button, it will show a list of funding options for your open source project. The various funding options can include multiple GitHub accounts, GitHub organizations, and third-party funding options like Patreon or Tidelift.

I co-hosted a Twitter Space alongside Denise Yu, Senior Engineering Manager for GitHub Sponsors, listening to maintainers about their experience with Sponsors. The guest panel included Bekah Hawrot Weigel, Santosh Yadav, Joshua K. Goldberg, Ankur Tyagi, and Logan Kilpatrick. You can listen to the raw recording and read the transcript here.

3a8082e126