You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the current challenges of getting a collective up-and-running is the lack of understanding of how collectives work, their capabilities, and their limitations. Although the wiki currently has some information about the Technical Fellowship, a more comprehensive view of collectives is needed. This should cover their features and how they can be customized to fit the needs of individual collectives within the limits of what the collective can currently do.
I propose adding a subsection to the wiki that provides more information on collectives. This section could include:
Information on setting up a collective
An overview of collective Parameters (demotion period, minimum promotion period, offboard timeout, etc.)
Guidelines for submitting evidence
Information on collectives funding (sub-treasury and salaries)
I'd like to contribute to working on this.
The text was updated successfully, but these errors were encountered:
@abdbee thanks for adding this. Definitely the wiki would benefit from a dedicated section about collectives and then expand further into subtreasuries. We will discuss what's the best approach to do this in the Wiki and get back to you.
One of the current challenges of getting a collective up-and-running is the lack of understanding of how collectives work, their capabilities, and their limitations. Although the wiki currently has some information about the Technical Fellowship, a more comprehensive view of collectives is needed. This should cover their features and how they can be customized to fit the needs of individual collectives within the limits of what the collective can currently do.
I propose adding a subsection to the wiki that provides more information on collectives. This section could include:
I'd like to contribute to working on this.
The text was updated successfully, but these errors were encountered: