- They already understand what kind of code base it is and already do dependency scanning for security issues
- They have payment details
- They have the "verified" payment method of a person / project (If sponsoring is enabled)
21–30 of 205 posts
- They already understand what kind of code base it is and already do dependency scanning for security issues
- They have payment details
- They have the "verified" payment method of a person / project (If sponsoring is enabled)
I really want someone to succeed at this and I like the approach but you need to run not walk to making it usable without private source code access. That’s a non-starter.
This implementation is clearly for-profit. I want to directly tip open source projects using a system that doesn't involve other third parties taking a significant cut.
It's still early for GitHub's Sponsor feature but I'm a bit surprised this is not part of it already. - They already understand what kind of code base it is and already do dependency scanning for security issues - They have payment details - They have the "verified" payment method of a person / project (If sponsoring is enabled)
Neat idea. Would it be useful to let folks analyze a repository without signing up? I'm thinking a user may want to scan a large repository and get a report (top X sponsor-enabled dependencies). This might be useful data to present during funding discussions.
How do I convince the management that it's worth spending a fraction of what 1 developer costs to give back to OSS?