Override group discomfort #197
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The current implementation of the discomfort calculator uses two concepts related to group relationships:
nil
for unrelated groups (we can think of it as infinity), or the maximum distance to a common ancestor otherwise.Calculating the discomfort as a function of the distance is fine for an initial approach, but users should be able to override that behavior. For example, say you have a group Work with three subgroups per department, say Accounting, Sales, and Finance. Since all three groups have the same parent, the distance between them is 1, and the discomfort is (1/2). However, we are assuming that the three groups are equally comfortable with each other, which may not be the case. Maybe Sales and Finance are super close, and their discomfort would be zero, or Sales and Accounting are long-time enemies and their discomfort would go beyond 1 if that was possible.
We need to allow users configure the discomfort between groups, not as a function, but as an arbitrary value. In this issue we are suggesting the following criteria:
All decimal numbers between 0 and 2 are allowed to represent different levels of affinity between groups. It is OK that the software suggests a value by default (calculated using the existing formulas), but these should be editable with a UI.
Having N groups in a wedding, the maximum number of affinities to store will be
N(N-1) / 2
. However, the matrix of affinities may not be dense, as there may be many groups that are unrelated, and thus have neutral affinity with each other (discomfort 1). Therefore, we may choose to implement affinities in a way the value is only stored if it's not equal to 1, and assume the value is 1 if not overriden.Override group distanceto Override group discomfortbustikiller referenced this issue2024-12-26 19:29:48 +00:00
Implemented in #215