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.

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 a sponsor button with a link to the Consortium page. #10240

Closed
wants to merge 1 commit into from

Conversation

Zimmi48
Copy link
Member

@Zimmi48 Zimmi48 commented May 24, 2019

Kind: documentation / infrastructure.

For reference about sponsor buttons, see https://help.github.com/en/articles/displaying-a-sponsor-button-in-your-repository.
And here is the list of supported funding models (most of them are mostly directed towards individual maintainers):

# These are supported funding model platforms

github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
patreon: # Replace with a single Patreon username
open_collective: # Replace with a single Open Collective username
ko_fi: # Replace with a single Ko-fi username
tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
custom: # Replace with a single custom sponsorship URL

Note: we could also consider opening an Open Collective https://opencollective.com/ if this helps us get smaller contributions from individuals or companies.

Note: we could also consider opening an Open Collective
https://opencollective.com/ if this helps us get smaller contributions
from individuals or companies.
@Zimmi48 Zimmi48 added kind: documentation Additions or improvement to documentation. kind: infrastructure CI, build tools, development tools. labels May 24, 2019
@Zimmi48 Zimmi48 added this to the 8.11+beta1 milestone May 24, 2019
@Zimmi48 Zimmi48 requested a review from maximedenes as a code owner May 24, 2019 19:58
@maximedenes
Copy link
Member

Thanks, I like the idea, of course. I'm not 100% comfortable linking with the current page knowing that we are not ready to take new subscribers for academic memberships, and are also not ready to send a Consortium agreement. @ybertot what do you think we should do?

@maximedenes maximedenes self-assigned this May 27, 2019
@Zimmi48
Copy link
Member Author

Zimmi48 commented May 27, 2019

I'm perfectly fine about waiting to merge this. I was actually expecting this kind of answer. What do you think of the open collective idea? (Maybe we can discuss this IRL next week.)

@maximedenes maximedenes removed their assignment Aug 19, 2019
@ejgallego
Copy link
Member

@ppedrot ppedrot modified the milestones: 8.11+beta1, 8.12+beta1 Oct 31, 2019
@Zimmi48
Copy link
Member Author

Zimmi48 commented Nov 29, 2019

Can we have a Consortium status point at the next WG?

@maximedenes
Copy link
Member

Can we have a Consortium status point at the next WG?

We can, but there's no update yet.

@Zimmi48
Copy link
Member Author

Zimmi48 commented Nov 29, 2019

Too bad, well maybe a very brief recap then.

@Zimmi48
Copy link
Member Author

Zimmi48 commented Dec 6, 2019

Closing until the situation with the consortium changes.

@Zimmi48 Zimmi48 closed this Dec 6, 2019
@coqbot coqbot removed this from the 8.12+beta1 milestone Dec 6, 2019
@Zimmi48 Zimmi48 deleted the sponsor-link branch March 21, 2020 17:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: documentation Additions or improvement to documentation. kind: infrastructure CI, build tools, development tools.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants