Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permit a region to be the delegate of more than one other region #229

Open
jim-mcgowan opened this issue Mar 23, 2020 · 2 comments
Open

Comments

@jim-mcgowan
Copy link
Member

jim-mcgowan commented Mar 23, 2020

Currently, a region (Chapter) can be the delegate of another region. So, if Region A is a delegate of Region B, Region B can see and edit the incident reports of Region A. This can be configured in the Chapter settings under Incidents delegate chapter:

Incidents delegate chapter
In the example above, the Dakotas Region (Chapter ID = 11) is a delegate of the Chicago & Northern Illinois Region (CID = 2).

This issue requests that more than one region be permitted to edit another's incident reports. Thus, if Chicago and Northern Illinois Region AND the Minnesota Region (CID = 10) want to edit Dakotas Region incident reports, Incidents delegate chapter might read: 2, 10

@kfogel
Copy link
Member

kfogel commented May 26, 2020

This makes sense to me, and I see no reason why it can't be done.

We should probably change the language on that page to make the directionality clearer, though. Instead of "Incidents delegate chapter", maybe it should say "Allow incident delegation from region(s):" or something like that.

(Yes, I also changed "chapter" to "region" in that proposal, because of The Big 185 of course.)

A terminology question / concern:

I guess there are a couple of ways to interpret "delegate" and "delegation"? In the way I'm used to, if Region A is a delegate of Region B, that would mean that Region B can "hand off" reports to Region A for A to handle -- i.e., B can "delegate" them "to" A, and thus A is a "delegate of" B. However, in the usage you give above, "A is a delegate of B" means instead something like "B can take over from A in handling A's incidents", which is the opposite of what I would normally understand it to mean.

So maybe a different wording entirely is in order here, e.g.:

"Other regions that can handle incidents for this region:"

or something like that.

@jim-mcgowan
Copy link
Member Author

Being a delegate simply means that you (the delegate) can create and edit another Region's incident reports (you have been delegated these privileges). This is becoming less important as we get closer to the actual realignment. If this effort takes any more than an hour, I would skip it.

I realize I'm probably using the term 'privileges' inappropriately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants