Follow-up from "Refactor Message Module"
The following discussion from !887 (merged) should be addressed:
RE: #515 (closed) @zommuter
In springer team conversations there used to be BOTH regular and springer members after adding/saving the team list. Right now there are only springer members.
In normal teams there only were normal members. This is still correct in my eyes.
I'm only 90% sure with this. Can anybody confirm?
Hm I can understand it makes sense to have BOTH in the springer conversations... I would still be really glad for a definition (also for people using foodsharing) what the suggested use case is :D Chris Oelmueller Chris Oelmueller @ChrisOelmueller · 15 hours ago Developer
For now, I would suggest only jumpers + store managers as most obvious use case: store managers asking jumpers whether one of them could sign into a certain slot that's not filled yet (or was created spontaneously). What purpose would a chat including all regular team members serve? Johannes Johannes @jofranz · 15 hours ago Maintainer
As we don't seem to understand it fully I would recommend to recreate previous behaviour. Regular non-store-manager members can use this chat to reach the whole team to hand over food to those "springer" members being on hold waiting for a chance to help out. Edited by Johannes 15 hours ago Chris Oelmueller Chris Oelmueller @ChrisOelmueller · 14 hours ago Developer
Yeah, but is that even the previous behavior? Right now from testing on Beta and Prod it seems that the current behavior is: the only members I can reach with the springer chat are some current or previous store managers. That's neither intentional nor useful, so I don't think it should be recreated.
Can we try to figure out:
what would the best functionality be for store managers? what would the best functionality be for jumper members? is there anyone not in those two groups that would message that chat group?
Johannes Johannes @jofranz · 14 hours ago Maintainer
Also unverified members should be taken into consideration Matthias Larisch Matthias Larisch @NerdyProjects · 14 hours ago Owner
can we live with this for now and fix it in a separate MR before a production merge?