Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Initial proposal of Sponsorship layers #516

Merged
merged 9 commits into from
Nov 24, 2023
Merged

Initial proposal of Sponsorship layers #516

merged 9 commits into from
Nov 24, 2023

Conversation

benjagm
Copy link
Collaborator

@benjagm benjagm commented Oct 31, 2023

Initial proposal of Sponsorship layers

Summary: This PR contains an initial proposal to improve our current sponsorships layers.

Do you think resolving this issue might require an Architectural Decision Record (ADR)? (significant or noteworthy)

No

@benjagm
Initial proposal of Sponsorship layers
1abaae6 
Initial proposal of Sponsorship layers
@benjagm benjagm mentioned this pull request Nov 2, 2023
Closed
13 tasks
@Julian
Copy link
Member

Julian commented Nov 2, 2023

This likely relates to #419 (comment) inasmuch as probably we want to consider whether GitHub Sponsors levels are the same -- unless there's good reason not to I guess we probably will want them to be.

@Relequestual
Copy link
Member

This likely relates to #419 (comment) inasmuch as probably we want to consider whether GitHub Sponsors levels are the same -- unless there's good reason not to I guess we probably will want them to be. - @Julian

Agreed. We don't actually have GH Sponsors set up. Partly because we don't have tiers/levels and I knew we needed to have something worthwhiel.

gregsdennis
gregsdennis reviewed Nov 2, 2023
View reviewed changes
programs/sponsors/sponsors.md Outdated Show resolved Hide resolved
programs/sponsors/sponsors.md Outdated Show resolved Hide resolved
programs/sponsors/sponsors.md Outdated Show resolved Hide resolved
@benjagm benjagm marked this pull request as ready for review November 20, 2023 11:32
@benjagm
Copy link
Collaborator Author

benjagm commented Nov 20, 2023

@Relequestual @gregsdennis I just updated the sponsorships proposal with more benefits, better wording and add GitHub Sponsors as an alternative.

@Julian
Copy link
Member

Julian commented Nov 20, 2023

This looks great! Left a few questions / comments, but yeah well done.

@Relequestual
Copy link
Member

On OpenCollective, we currently have a policy to not accept sponsorship from the following types of companies...

Adult websites, affiliate and review websites, Casinos and gambling, Insurance & financial products (credit), Pharmacy products (weight loss, anti-aging), and Essay writing services.

We could add "SEO" and "VPN/proxy services" to that list.

I think we should duplicate those items into this policy file.

Otherwise, this looks good. I left one comment.

@benjagm
Copy link
Collaborator Author

benjagm commented Nov 23, 2023

On OpenCollective, we currently have a policy to not accept sponsorship from the following types of companies...

Adult websites, affiliate and review websites, Casinos and gambling, Insurance & financial products (credit), Pharmacy products (weight loss, anti-aging), and Essay writing services.

We could add "SEO" and "VPN/proxy services" to that list.

I think we should duplicate those items into this policy file.

Otherwise, this looks good. I left one comment.

I added an acceptance policy section.

Relequestual
Relequestual approved these changes Nov 24, 2023
View reviewed changes
Copy link
Member

@Relequestual Relequestual left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work. Thanks!
Let's push these out to the sponsorship locations!

@benjagm
Copy link
Collaborator Author

benjagm commented Nov 24, 2023

Thanks everyone for the great feedback!

@benjagm benjagm merged commit cf4d4ae into main Nov 24, 2023
1 check passed
@benjagm benjagm deleted the benjagm-sponsors branch November 24, 2023 11:06
@benjagm benjagm mentioned this pull request Nov 27, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@gregsdennis gregsdennis gregsdennis approved these changes

@mwadams mwadams mwadams left review comments

@Relequestual Relequestual Relequestual approved these changes

@Julian Julian Awaiting requested review from Julian

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@benjagm @Julian @Relequestual @mwadams @gregsdennis