Add sponsorship?

[NobodyXu]

I think we can use sponsor to:

• give incentives to developers who contributes to our project
• give some of our sponsorships to upstream developer

I also think it's a good idea to list upstream developers and encourage people to sponsor them for the hard work they've done.

[passcod]

i'm open in principle but not sure how sponsors work in github in the org context

[Milo123459]

sorry - new to this. how would we receive the money?

[NobodyXu]

We plan to use https://www.oscollective.org/ , my understanding is that any sponsor on GitHub will be stored in oscolledtive with 10% of it payed to oscollective to maintain our account.

I'm no expert in this and I found the information in https://www.oscollective.org/

[ryankurte]

hey i'm open to this in principle (love the idea of -sustainable- open source), though i think the process of using or distributing any funds might be more complex than just supporting sponsorships...

echoing @passcod's point about a mission statement, we'd need a clear policy for how any funding would be distributed both upstream and to any contributors. i think i would like to see this prioritise supporting ongoing project maintenance and infrastructure (as well as upstream projects), and that it would be important that this reflect contributions / incentivise meaningful maintenance and development effort (for example, at this point my membership is primarily bus-factor reduction and should not be considered).

are there any projects with a similar size / vibe / userbase that we could look to for policy examples?

there definitely seems to be an advantage to having one point-of-contact for supporting the project that feeds back to contributors / upstream developers / infrastructure (particularly quickinstall). one possible alternative would be to allow maintainers to add their personal sponsorship links to project readmes which would seem less ergonomic but doesn't require any specific organisational administration.

[passcod]

one possible alternative would be to allow maintainers to add their personal sponsorship links to project readmes

That might be a good first step to take? Then we could revisit later based on how that goes.

[NobodyXu]

I've applied for sponsor with my bank account, since oscollective would seem to require a separate sponsor link per project.

https://github.com/sponsors/NobodyXu

[alsuren]

Alright. I think the process here has to be:

1. get approval from every maintainer (I think including quickinstall's eg for any costs that infrastructure might need in the future): [legal terms here](https://docs.google.com/document/u/1/d/e/2PACX-1vQbiyK2Fe0jLdh4vb9BfHY4bJ1LCo4Qvy0jg9P29ZkiC8y_vKJ_1fNgIbV0p6UdvbcT8Ql1gVto8bf9/pub)

I'm happy with these terms.

I'm also happy to let @passcod and @NobodyXu share any income that the collective gets, since I'm no longer really maintaining anything (I'm mostly here for the bus factor too). Quickinstall uses purely free tier services, and I've never incurred any costs from running it.

As far as "mission statement" (these might be more like taglines?):

a) providing quick and convenient access to rust-based tools

b) lowering the bar for accessing high quality command-line tools

c) reducing duplicated work by providing pre-built programs for use in desktop and CI scenarios

d) ...

[NobodyXu]

Thanks @alsuren , yeah I think these mission statements aligns with my interest in this organisation.