KubOS-Preservation-Group / KubOS-Preservation-Group/Community

Should we get an openCollective

Open
#2 0 comments 0 reactions 0 assignees View on GitHub
discussion
Dominant language
No language data
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

One of the ideas that has been bouncing around for a while is the idea of getting a domain name or otherwise being able to pay for things. I think this should be done in a way that is able to be owned by the community rather than one individual and it seem slike OpenCollective is a great platform for that.

This issue is for discussing when we think is the right time to apply for a collective, if we think we can pass the [criteria](https://www.oscollective.org/#criteria), how we can ensure that we meet all of the minimum activity and community update/posting requirements to sustainably remain a collective, and whether the tradeoffs (i.e. giving up 10% of all the money we bring in) are worth it.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or code entry points are identified in the issue. Start by reviewing the linked OpenCollective criteria and the discussion points about timing, activity requirements, community updates, and fees; done would be a documented community decision on whether and when to apply.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.