change max_deciding of the FellowshipAdmin track to 30 #468
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes the max number of refs that can be in the
deciding
state in theFellowshipAdmin
track from 10 to 30.This is a defensive measure to allow a potential submission of 21 rank retention refs for Head Ambassadors to go into simultaneous decision.
Background and Rationale
The OpenGov community is currently discussing updates to the Ambassador Program social contract. One potential path is to begin to make use of the
demotionPeriod
parameter in theambassadorCore
to introduce a demotion period. This would then force the existing 20 collective members of rank 3 (the highest rank) to submit retention referenda to the OpenGonFellowshipAdmin
track. If the track would fill up and not allow sufficient decisions within the demotionPeriod, it could lead to unwanted demotions that are not in the intention of the DAO.To avoid this situation, this PR raises the limit to 30. This gives room for 21 retention referenda + additional room for any other potential collectives chain related refs.