• Fix group members update by the LDAP backend
• Remove group member of user delete

• Fix tests regressions
• LDAP error handling, LDAP tests
• Group jobs tests

• Checking Group::emailExists() when creating a user/alias
• Delete groups of user delete
• Various group model fixes, added tests
• Allow groups in non-public domains only
• Fix group:info command tests

• Delete groups of user delete

• Checking Group::emailExists() when creating a user/alias

TL;DR: Make video chat app part of the main app without the app size concerns.

In D2014#22843, @vanmeeuwen wrote:

I would like to learn more about the "async" or "lazy-loading" (if that's applicable terminology), as it could be the underpinnings of our future dashboard widgety approach?

• Fix so after logout from /meet the logon page is displayed (instead of an empty page)

• OpenVidu: Fix Cockpit link in the menu

• Small API change, controller tests
• Fix browser tests regressions
• Add browser tests for subscribers feature
• Rename some css classes and functions to more appropriate names

I'm not sure. Is it an exception for this one page or this is a general rule that delete button should be on top? E.g. regarding https://bifrost.kolabsystems.com/T375653 What if the button will be in bottom-right corner?

• Fix browser tests after menu changes
• Remove webmail link from admin logon, fix padding of logon footer links

• small cleanup

• Stats: Remove the invalid extra bar on charts

• Dismissing participants from the room

• De-duplicate mandate input validation code
• Top up the wallet whn the balance is below the threshold (not 0)

• Add Room::ROLE_* constants

• Fix avg calculation

• Added tests
• Added browser tests
• Picture format and request id validation

• Comment out room locking options

Looks good, but browser tests will need some updates. Would you like to work on this?

• Stripe: Trigger auto-payment immediately after setup

• Add domain settings, and fix some db structure issues
• Store spf/greylisting settings in user/domain settings
• Add tests, rename spf -> spf_whitelist
• Added browser tests

I didn't think about where to store the settings, but still I like to have the settings/configuration input validation code in some place (and not in the controller). This way the controller can be simple and when we need to add more settings we have a separate place to do this without messing with controllers and model classes.