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'd like to make our product more attractive to orgs by making it's capabilities more expansive. Instead of just using us to by random contributors, the use case could grow in capability and be used to include one time grant distributions and residencies that pay over a duration of time but have an end date. In this way all contributors can be accounted for in the same instance if that was so desired. I can find an immediate argument for this in the Stacks community as we grow the advocates program, as I am onboarded as a resident, and as we continue to grow the use of SourceCred in the Stacks ecosystem.
The alternative is remembering to alter the instance in time to cancel distributions for various residents and grants ending at different times using the "SPECIAL" and "BALANCED" policies and exclusion from "RECENT" policy. That is too much to remember for an instance maintainer to want to sell this to any community at this time.
The text was updated successfully, but these errors were encountered:
To clarify, does this user story sound correct? As an instance maintainer, I want to be able to configure a grain distribution policies that have set start and end dates.
Or is there more specificity needed so the policy only applies to certain roles (i.e. residents)?
I'd like to make our product more attractive to orgs by making it's capabilities more expansive. Instead of just using us to by random contributors, the use case could grow in capability and be used to include one time grant distributions and residencies that pay over a duration of time but have an end date. In this way all contributors can be accounted for in the same instance if that was so desired. I can find an immediate argument for this in the Stacks community as we grow the advocates program, as I am onboarded as a resident, and as we continue to grow the use of SourceCred in the Stacks ecosystem.
The alternative is remembering to alter the instance in time to cancel distributions for various residents and grants ending at different times using the "SPECIAL" and "BALANCED" policies and exclusion from "RECENT" policy. That is too much to remember for an instance maintainer to want to sell this to any community at this time.
The text was updated successfully, but these errors were encountered: