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
I am interested in phasing out the Boolean distinction of "collaborator" and "contributor" in favor of modeling status as a continuum. I think this is more "DAO like" for our general operations
It would be useful to think of ways to support this shift. Like some type of way to vote on a time estimate and have an admin (or billing_manger) approve funding it.
Maybe a command
/time value
Also /priority value
And financier gives it a thumbs up for the bot to make it official.
It would be even cooler for the bot to understand the XP of everybody's vote to get an idea of if some task should be funded even without the admin direct approval but that can be a task for another time after more refinement.
The text was updated successfully, but these errors were encountered:
I am interested in phasing out the Boolean distinction of "collaborator" and "contributor" in favor of modeling status as a continuum. I think this is more "DAO like" for our general operations
It would be useful to think of ways to support this shift. Like some type of way to vote on a time estimate and have an admin (or billing_manger) approve funding it.
Maybe a command
/time value
Also /priority value
And financier gives it a thumbs up for the bot to make it official.
It would be even cooler for the bot to understand the XP of everybody's vote to get an idea of if some task should be funded even without the admin direct approval but that can be a task for another time after more refinement.
The text was updated successfully, but these errors were encountered: