Short version: We’re combining the Tell Potential Subscribers & GitHub Sponsors tasks into one new task.
What is changing and why?
If your project is on GitHub, we are now only requiring that you add our key to GitHub Sponsors to reflect that you are a lifter, and not that you add links to any of your project files as the old Tell Potential Subscribers task required. The reason for this is that after a few months of trialing GitHub Sponsors, we’ve found that GitHub Sponsors provides a more effective and uniform placement of the Tidelift partnership, and that it’s simpler for you to maintain than code snippets that must be inserted manually. This is also in preparation for some exciting news we have for you near the end of the month! Check out the screenshots at the bottom of this post to get a preview of the new task.
How will this affect you? What will you need to do?
For almost all current lifted projects this change should have very little impact.
This will not affect current or future projects that don’t use GitHub - you will still complete the parts of Tell Potential Subscribers that we previously asked for.
If you’ve already completed the GitHub Sponsors task, no action is necessary.
For the handful of you with GitHub repos who have completed the old Tell Potential Subscribers task but not the GitHub Sponsors task, you’ll need to add our key to GitHub Sponsors to ensure consistency and to keep Tidelift “above-the-fold”. This should only take a few minutes and there is a guide to doing it in the current GitHub Sponsors task which will be moving to the new task when this change is live.
For future lifted projects hosted on GitHub, you will only need to add GitHub Sponsors in order to complete the new task.
When is this changing?
Currently, September 30th. Watch out for more related news—coming soon!
Got questions or input?
As always, leave them in the comments or email email@example.com.