Replace worker-loader with built-in Webpack 5 support for web workers

.editorconfig

@@ -1,8 +1,16 @@
-#   Copyright 2024 New Vector Ltd.
 #   Copyright 2017 Aviral Dasgupta
 #
-#   SPDX-License-Identifier: AGPL-3.0-only OR GPL-3.0-only
-#   Please see LICENSE files in the repository root for full details.
+#   Licensed under the Apache License, Version 2.0 (the "License");
+#   you may not use this file except in compliance with the License.
+#   You may obtain a copy of the License at
+#
+#       http://www.apache.org/licenses/LICENSE-2.0
+#
+#   Unless required by applicable law or agreed to in writing, software
+#   distributed under the License is distributed on an "AS IS" BASIS,
+#   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+#   See the License for the specific language governing permissions and
+#   limitations under the License.
 
 root = true
 
@@ -19,6 +27,3 @@ indent_size = 4
 
 [package.json]
 indent_size = 2
-
-[*.tsx.snap]
-trim_trailing_whitespace = false

.env.example

@@ -0,0 +1,16 @@
+# To enable CSS hot-reload, set the following variable to 1.
+CSS_HOT_RELOAD=1
+# To use the full page error dialog, set this to 1. Please report false positives to
+# the issue tracker for handling.
+FULL_PAGE_ERRORS=0
+# To use a single theme, uncomment the line with the theme you want to hot-reload.
+MATRIX_THEMES='light'
+#MATRIX_THEMES='dark'
+#MATRIX_THEMES='legacy-light'
+#MATRIX_THEMES='legacy-dark'
+#MATRIX_THEMES='light-custom'
+#MATRIX_THEMES='dark-custom'
+# You can also enable multiple themes by using a comma-separated list.
+# When multiple themes are enabled, switching between them may require a full page reload.
+# Note that compilation times are proportional to the number of enabled themes.
+#MATRIX_THEMES='light,dark'

.eslintignore

@@ -1,8 +1,4 @@
 src/vector/modernizr.js
-test/end-to-end-tests/node_modules/
-test/end-to-end-tests/element/
-test/end-to-end-tests/synapse/
-test/end-to-end-tests/lib/
 # Legacy skinning file that some people might still have
 src/component-index.js
 # Auto-generated file

.eslintrc-module_system.js

@@ -45,12 +45,24 @@ module.exports = {
                                 name: "matrix-js-sdk/src/index",
                                 message: "Please use matrix-js-sdk/src/matrix instead",
                             },
+                            {
+                                name: "matrix-react-sdk",
+                                message: "Please use matrix-react-sdk/src/index instead",
+                            },
+                            {
+                                name: "matrix-react-sdk/",
+                                message: "Please use matrix-react-sdk/src/index instead",
+                            },
                         ],
                         patterns: [
                             {
                                 group: ["matrix-js-sdk/lib", "matrix-js-sdk/lib/", "matrix-js-sdk/lib/**"],
                                 message: "Please use matrix-js-sdk/src/* instead",
                             },
+                            {
+                                group: ["matrix-react-sdk/lib", "matrix-react-sdk/lib/", "matrix-react-sdk/lib/**"],
+                                message: "Please use matrix-react-sdk/src/* instead",
+                            },
                         ],
                     },
                 ],

.eslintrc.js

@@ -1,6 +1,6 @@
 module.exports = {
     plugins: ["matrix-org"],
-    extends: ["plugin:matrix-org/babel", "plugin:matrix-org/react", "plugin:matrix-org/a11y"],
+    extends: ["plugin:matrix-org/babel", "plugin:matrix-org/react"],
     parserOptions: {
         project: ["./tsconfig.json"],
     },
@@ -8,281 +8,87 @@ module.exports = {
         browser: true,
         node: true,
     },
-    globals: {
-        LANGUAGES_FILE: "readonly",
-    },
     rules: {
         // Things we do that break the ideal style
-        "no-constant-condition": "off",
-        "prefer-promise-reject-errors": "off",
-        "no-async-promise-executor": "off",
-        "no-extra-boolean-cast": "off",
-
-        // Bind or arrow functions in props causes performance issues (but we
-        // currently use them in some places).
-        // It's disabled here, but we should using it sparingly.
-        "react/jsx-no-bind": "off",
-        "react/jsx-key": ["error"],
-
-        "no-restricted-properties": [
-            "error",
-            ...buildRestrictedPropertiesOptions(
-                ["window.innerHeight", "window.innerWidth", "window.visualViewport"],
-                "Use UIStore to access window dimensions instead.",
-            ),
-            ...buildRestrictedPropertiesOptions(
-                ["*.mxcUrlToHttp", "*.getHttpUriForMxc"],
-                "Use Media helper instead to centralise access for customisation.",
-            ),
-            ...buildRestrictedPropertiesOptions(["window.setImmediate"], "Use setTimeout instead."),
-        ],
-        "no-restricted-globals": [
-            "error",
-            {
-                name: "setImmediate",
-                message: "Use setTimeout instead.",
-            },
-        ],
-
-        "import/no-duplicates": ["error"],
-        // Ban matrix-js-sdk/src imports in favour of matrix-js-sdk/src/matrix imports to prevent unleashing hell.
-        // Ban compound-design-tokens raw svg imports in favour of their React component counterparts
-        "no-restricted-imports": [
-            "error",
-            {
-                paths: [
-                    {
-                        name: "@testing-library/react",
-                        message: "Please use jest-matrix-react instead",
-                    },
-                    {
-                        name: "matrix-js-sdk",
-                        message: "Please use matrix-js-sdk/src/matrix instead",
-                    },
-                    {
-                        name: "matrix-js-sdk/",
-                        message: "Please use matrix-js-sdk/src/matrix instead",
-                    },
-                    {
-                        name: "matrix-js-sdk/src",
-                        message: "Please use matrix-js-sdk/src/matrix instead",
-                    },
-                    {
-                        name: "matrix-js-sdk/src/",
-                        message: "Please use matrix-js-sdk/src/matrix instead",
-                    },
-                    {
-                        name: "matrix-js-sdk/src/index",
-                        message: "Please use matrix-js-sdk/src/matrix instead",
-                    },
-                    {
-                        name: "emojibase-regex",
-                        message:
-                            "This regex doesn't actually test for emoji. See the docs at https://emojibase.dev/docs/regex/ and prefer our own EMOJI_REGEX from HtmlUtils.",
-                    },
-                ],
-                patterns: [
-                    {
-                        group: [
-                            "matrix-js-sdk/src/**",
-                            "!matrix-js-sdk/src/matrix",
-                            "!matrix-js-sdk/src/crypto-api",
-                            "!matrix-js-sdk/src/types",
-                            "!matrix-js-sdk/src/testing",
-                            "!matrix-js-sdk/src/utils/**",
-                            "matrix-js-sdk/src/utils/internal/**",
-                            "matrix-js-sdk/lib",
-                            "matrix-js-sdk/lib/",
-                            "matrix-js-sdk/lib/**",
-                            // XXX: Temporarily allow these as they are not available via the main export
-                            "!matrix-js-sdk/src/logger",
-                            "!matrix-js-sdk/src/errors",
-                            "!matrix-js-sdk/src/utils",
-                            "!matrix-js-sdk/src/version-support",
-                            "!matrix-js-sdk/src/randomstring",
-                            "!matrix-js-sdk/src/sliding-sync",
-                            "!matrix-js-sdk/src/browser-index",
-                            "!matrix-js-sdk/src/feature",
-                            "!matrix-js-sdk/src/NamespacedValue",
-                            "!matrix-js-sdk/src/ReEmitter",
-                            "!matrix-js-sdk/src/event-mapper",
-                            "!matrix-js-sdk/src/interactive-auth",
-                            "!matrix-js-sdk/src/secret-storage",
-                            "!matrix-js-sdk/src/room-hierarchy",
-                            "!matrix-js-sdk/src/rendezvous",
-                            "!matrix-js-sdk/src/indexeddb-worker",
-                            "!matrix-js-sdk/src/pushprocessor",
-                            "!matrix-js-sdk/src/extensible_events_v1",
-                            "!matrix-js-sdk/src/extensible_events_v1/PollStartEvent",
-                            "!matrix-js-sdk/src/extensible_events_v1/PollResponseEvent",
-                            "!matrix-js-sdk/src/extensible_events_v1/PollEndEvent",
-                            "!matrix-js-sdk/src/extensible_events_v1/InvalidEventError",
-                            "!matrix-js-sdk/src/crypto",
-                            "!matrix-js-sdk/src/crypto/keybackup",
-                            "!matrix-js-sdk/src/crypto/deviceinfo",
-                            "!matrix-js-sdk/src/crypto/dehydration",
-                            "!matrix-js-sdk/src/oidc",
-                            "!matrix-js-sdk/src/oidc/discovery",
-                            "!matrix-js-sdk/src/oidc/authorize",
-                            "!matrix-js-sdk/src/oidc/validate",
-                            "!matrix-js-sdk/src/oidc/error",
-                            "!matrix-js-sdk/src/oidc/register",
-                            "!matrix-js-sdk/src/webrtc",
-                            "!matrix-js-sdk/src/webrtc/call",
-                            "!matrix-js-sdk/src/webrtc/callFeed",
-                            "!matrix-js-sdk/src/webrtc/mediaHandler",
-                            "!matrix-js-sdk/src/webrtc/callEventTypes",
-                            "!matrix-js-sdk/src/webrtc/callEventHandler",
-                            "!matrix-js-sdk/src/webrtc/groupCallEventHandler",
-                            "!matrix-js-sdk/src/models",
-                            "!matrix-js-sdk/src/models/read-receipt",
-                            "!matrix-js-sdk/src/models/relations-container",
-                            "!matrix-js-sdk/src/models/related-relations",
-                            "!matrix-js-sdk/src/matrixrtc",
-                        ],
-                        message: "Please use matrix-js-sdk/src/matrix instead",
-                    },
-                    {
-                        group: ["emojibase-regex/emoji*"],
-                        message:
-                            "This regex doesn't actually test for emoji. See the docs at https://emojibase.dev/docs/regex/ and prefer our own EMOJI_REGEX from HtmlUtils.",
-                    },
-                    {
-                        group: ["@vector-im/compound-design-tokens/icons/*"],
-                        message: "Please use @vector-im/compound-design-tokens/assets/web/icons/* instead",
-                    },
-                ],
-            },
-        ],
-
-        // There are too many a11y violations to fix at once
-        // Turn violated rules off until they are fixed
-        "jsx-a11y/aria-activedescendant-has-tabindex": "off",
-        "jsx-a11y/click-events-have-key-events": "off",
-        "jsx-a11y/interactive-supports-focus": "off",
-        "jsx-a11y/media-has-caption": "off",
-        "jsx-a11y/mouse-events-have-key-events": "off",
-        "jsx-a11y/no-autofocus": "off",
-        "jsx-a11y/no-noninteractive-element-interactions": "off",
-        "jsx-a11y/no-noninteractive-element-to-interactive-role": "off",
-        "jsx-a11y/no-noninteractive-tabindex": "off",
-        "jsx-a11y/no-static-element-interactions": "off",
-        "jsx-a11y/role-supports-aria-props": "off",
-
-        "matrix-org/require-copyright-header": "error",
+        quotes: "off",
     },
-    overrides: [
-        {
-            files: ["src/**/*.{ts,tsx}", "test/**/*.{ts,tsx}", "playwright/**/*.ts"],
-            extends: ["plugin:matrix-org/typescript", "plugin:matrix-org/react"],
-            rules: {
-                "@typescript-eslint/explicit-function-return-type": [
-                    "error",
-                    {
-                        allowExpressions: true,
-                    },
-                ],
-
-                // Things we do that break the ideal style
-                "prefer-promise-reject-errors": "off",
-                "no-extra-boolean-cast": "off",
-
-                // Remove Babel things manually due to override limitations
-                "@babel/no-invalid-this": ["off"],
-
-                // We're okay being explicit at the moment
-                "@typescript-eslint/no-empty-interface": "off",
-                // We disable this while we're transitioning
-                "@typescript-eslint/no-explicit-any": "off",
-                // We'd rather not do this but we do
-                "@typescript-eslint/ban-ts-comment": "off",
-                // We're okay with assertion errors when we ask for them
-                "@typescript-eslint/no-non-null-assertion": "off",
-            },
-        },
-        // temporary override for offending icon require files
-        {
-            files: [
-                "src/SdkConfig.ts",
-                "src/components/structures/FileDropTarget.tsx",
-                "src/components/structures/RoomStatusBar.tsx",
-                "src/components/structures/UserMenu.tsx",
-                "src/components/views/avatars/WidgetAvatar.tsx",
-                "src/components/views/dialogs/AddExistingToSpaceDialog.tsx",
-                "src/components/views/dialogs/ForwardDialog.tsx",
-                "src/components/views/dialogs/InviteDialog.tsx",
-                "src/components/views/dialogs/ModalWidgetDialog.tsx",
-                "src/components/views/dialogs/UploadConfirmDialog.tsx",
-                "src/components/views/dialogs/security/SetupEncryptionDialog.tsx",
-                "src/components/views/elements/AddressTile.tsx",
-                "src/components/views/elements/AppWarning.tsx",
-                "src/components/views/elements/SSOButtons.tsx",
-                "src/components/views/messages/MAudioBody.tsx",
-                "src/components/views/messages/MImageBody.tsx",
-                "src/components/views/messages/MFileBody.tsx",
-                "src/components/views/messages/MStickerBody.tsx",
-                "src/components/views/messages/MVideoBody.tsx",
-                "src/components/views/messages/MVoiceMessageBody.tsx",
-                "src/components/views/right_panel/EncryptionPanel.tsx",
-                "src/components/views/rooms/EntityTile.tsx",
-                "src/components/views/rooms/LinkPreviewGroup.tsx",
-                "src/components/views/rooms/MemberList.tsx",
-                "src/components/views/rooms/MessageComposer.tsx",
-                "src/components/views/rooms/ReplyPreview.tsx",
-                "src/components/views/settings/tabs/room/SecurityRoomSettingsTab.tsx",
-                "src/components/views/settings/tabs/user/GeneralUserSettingsTab.tsx",
-            ],
-            rules: {
-                "@typescript-eslint/no-var-requires": "off",
-            },
-        },
-        {
-            files: ["test/**/*.{ts,tsx}", "playwright/**/*.ts"],
-            extends: ["plugin:matrix-org/jest"],
-            rules: {
-                // We don't need super strict typing in test utilities
-                "@typescript-eslint/explicit-function-return-type": "off",
-                "@typescript-eslint/explicit-member-accessibility": "off",
-
-                // Jest/Playwright specific
-
-                // Disabled tests are a reality for now but as soon as all of the xits are
-                // eliminated, we should enforce this.
-                "jest/no-disabled-tests": "off",
-                // Also treat "oldBackendOnly" as a test function.
-                // Used in some crypto tests.
-                "jest/no-standalone-expect": [
-                    "error",
-                    {
-                        additionalTestBlockFunctions: ["beforeAll", "beforeEach", "oldBackendOnly"],
-                    },
-                ],
-            },
-        },
-        {
-            files: ["playwright/**/*.ts"],
-            parserOptions: {
-                project: ["./playwright/tsconfig.json"],
-            },
-        },
-    ],
     settings: {
         react: {
             version: "detect",
         },
     },
-};
+    overrides: [
+        {
+            files: ["src/**/*.{ts,tsx}", "test/**/*.{ts,tsx}", "scripts/*.ts"],
+            extends: ["plugin:matrix-org/typescript", "plugin:matrix-org/react"],
+            // NOTE: These rules are frozen and new rules should not be added here.
+            // New changes belong in https://github.com/matrix-org/eslint-plugin-matrix-org/
+            rules: {
+                // Things we do that break the ideal style
+                "prefer-promise-reject-errors": "off",
+                "quotes": "off",
 
-function buildRestrictedPropertiesOptions(properties, message) {
-    return properties.map((prop) => {
-        let [object, property] = prop.split(".");
-        if (object === "*") {
-            object = undefined;
-        }
-        return {
-            object,
-            property,
-            message,
-        };
-    });
-}
+                // We disable this while we're transitioning
+                "@typescript-eslint/no-explicit-any": "off",
+                // We're okay with assertion errors when we ask for them
+                "@typescript-eslint/no-non-null-assertion": "off",
+
+                // Ban matrix-js-sdk/src imports in favour of matrix-js-sdk/src/matrix imports to prevent unleashing hell.
+                "no-restricted-imports": [
+                    "error",
+                    {
+                        paths: [
+                            {
+                                name: "matrix-js-sdk",
+                                message: "Please use matrix-js-sdk/src/matrix instead",
+                            },
+                            {
+                                name: "matrix-js-sdk/",
+                                message: "Please use matrix-js-sdk/src/matrix instead",
+                            },
+                            {
+                                name: "matrix-js-sdk/src",
+                                message: "Please use matrix-js-sdk/src/matrix instead",
+                            },
+                            {
+                                name: "matrix-js-sdk/src/",
+                                message: "Please use matrix-js-sdk/src/matrix instead",
+                            },
+                            {
+                                name: "matrix-js-sdk/src/index",
+                                message: "Please use matrix-js-sdk/src/matrix instead",
+                            },
+                            {
+                                name: "matrix-react-sdk",
+                                message: "Please use matrix-react-sdk/src/index instead",
+                            },
+                            {
+                                name: "matrix-react-sdk/",
+                                message: "Please use matrix-react-sdk/src/index instead",
+                            },
+                        ],
+                        patterns: [
+                            {
+                                group: ["matrix-js-sdk/lib", "matrix-js-sdk/lib/", "matrix-js-sdk/lib/**"],
+                                message: "Please use matrix-js-sdk/src/* instead",
+                            },
+                            {
+                                group: ["matrix-react-sdk/lib", "matrix-react-sdk/lib/", "matrix-react-sdk/lib/**"],
+                                message: "Please use matrix-react-sdk/src/* instead",
+                            },
+                        ],
+                    },
+                ],
+            },
+        },
+        {
+            files: ["test/**/*.{ts,tsx}"],
+            rules: {
+                // We don't need super strict typing in test utilities
+                "@typescript-eslint/explicit-function-return-type": "off",
+                "@typescript-eslint/explicit-member-accessibility": "off",
+                "@typescript-eslint/ban-ts-comment": "off",
+            },
+        },
+    ],
+};

.git-blame-ignore-revs

@@ -1,3 +1,2 @@
 # prettier
-526645c79160ab1ad4b4c3845de27d51263a405e
 7921a6cbf86b035d2b0c1daecb4c24beaf5a5abc

.github/CODEOWNERS

@@ -1,18 +1,4 @@
-*                         @element-hq/element-web-reviewers
-/.github/workflows/**     @element-hq/element-web-team
-/package.json             @element-hq/element-web-team
-/yarn.lock                @element-hq/element-web-team
-
-/src/SecurityManager.ts                           @element-hq/element-crypto-web-reviewers
-/test/SecurityManager-test.ts                     @element-hq/element-crypto-web-reviewers
-/src/async-components/views/dialogs/security/     @element-hq/element-crypto-web-reviewers
-/src/components/views/dialogs/security/           @element-hq/element-crypto-web-reviewers
-/test/components/views/dialogs/security/          @element-hq/element-crypto-web-reviewers
-/src/stores/SetupEncryptionStore.ts               @element-hq/element-crypto-web-reviewers
-/test/stores/SetupEncryptionStore-test.ts         @element-hq/element-crypto-web-reviewers
-
-# Ignore translations as those will be updated by GHA for Localazy download
-/src/i18n/strings
-# Ignore the synapse plugin as this is updated by GHA for docker image updating
-/playwright/plugins/homeserver/synapse/index.ts
-
+*                         @vector-im/element-web
+/.github/workflows/**     @vector-im/element-web-app-team
+/package.json             @vector-im/element-web-app-team
+/yarn.lock                @vector-im/element-web-app-team

.github/ISSUE_TEMPLATE/enhancement.yml

@@ -5,7 +5,7 @@ body:
     - type: markdown
       attributes:
           value: |
-              Thank you for taking the time to propose an enhancement to an existing feature. If you would like to propose a new feature or a major cross-platform change, please [start a discussion here](https://github.com/element-hq/element-meta/discussions/new?category=ideas).
+              Thank you for taking the time to propose an enhancement to an existing feature. If you would like to propose a new feature or a major cross-platform change, please [start a discussion here](https://github.com/vector-im/element-meta/discussions/new?category=ideas).
     - type: textarea
       id: usecase
       attributes:

.github/PULL_REQUEST_TEMPLATE.md

@@ -2,7 +2,17 @@
 
 ## Checklist
 
--   [ ] Tests written for new code (and old code if feasible).
--   [ ] New or updated `public`/`exported` symbols have accurate [TSDoc](https://tsdoc.org/) documentation.
--   [ ] Linter and other CI checks pass.
--   [ ] I have licensed the changes to Element by completing the [Contributor License Agreement (CLA)](https://cla-assistant.io/element-hq/element-web)
+-   [ ] Tests written for new code (and old code if feasible)
+-   [ ] Linter and other CI checks pass
+-   [ ] Sign-off given on the changes (see [CONTRIBUTING.md](https://github.com/vector-im/element-web/blob/develop/CONTRIBUTING.md))
+
+<!--
+If you would like to specify text for the changelog entry other than your PR title, add the following:
+
+Notes: Add super cool feature
+
+For PRs which *only* affect the desktop version, please use:
+
+Notes: none
+element-desktop notes: Add super cool feature
+-->

.github/cfp_headers

@@ -11,6 +11,3 @@
 
 /apple-app-site-association
   Content-Type: application/json
-
-/.well-known/assetlinks.json
-  Content-Type: application/json

.github/labels.yml

@@ -1,266 +0,0 @@
-- name: "A-Aliases"
-  color: "bfd4f2"
-- name: "A-Authentication"
-  color: "bfd4f2"
-- name: "A-Autocomplete"
-  color: "bfd4f2"
-- name: "A-Breadcrumbs"
-  color: "bfd4f2"
-- name: "A-Bridge"
-  color: "bfd4f2"
-- name: "A-Broadcast"
-  description: "Broadcast-style voice messages"
-  color: "bfd4f2"
-- name: "A-Create-Room"
-  description: "Create room flow, user suggestions, etc."
-  color: "bfd4f2"
-- name: "A-DevTools"
-  description: "/devtools, show hidden events, etc."
-  color: "bfd4f2"
-- name: "A-Dialogs"
-  color: "bfd4f2"
-- name: "A-Disambiguation"
-  color: "bfd4f2"
-- name: "A-DM-Start"
-  description: "Creating a DM with another user"
-  color: "bfd4f2"
-- name: "A-E2EE-Dehydration"
-  color: "8CC59A"
-- name: "A-Electron"
-  color: "bfd4f2"
-- name: "A-Element-Call"
-  description: "Group calls via Element Call"
-  color: "bfd4f2"
-- name: "A-Element-R"
-  description: "Issues affecting the port of Element's crypto layer to Rust"
-  color: "bfd4f2"
-- name: "A-ELS"
-  description: "Event List Summary (and Membership ELS, MELS)"
-  color: "bfd4f2"
-- name: "A-Emotes"
-  color: "bfd4f2"
-- name: "A-EMS"
-  description: "Issues related to EMS"
-  color: "bfd4f2"
-- name: "A-Error-Message"
-  color: "bfd4f2"
-- name: "A-Federation"
-  color: "bfd4f2"
-- name: "A-Feedback-Reporting"
-  description: "Reporting process for bugs, debug logs (rageshakes), suggestions"
-  color: "bfd4f2"
-- name: "A-File-Download"
-  color: "bfd4f2"
-- name: "A-File-Panel"
-  color: "bfd4f2"
-- name: "A-Identity-Server"
-  color: "bfd4f2"
-- name: "A-Indexing"
-  description: "Indexing messages via Seshat"
-  color: "bfd4f2"
-- name: "A-IRC-Layout"
-  color: "bfd4f2"
-- name: "A-Jump-To-Date"
-  description: "Jump to date headers or slash command"
-  color: "bfd4f2"
-- name: "A-Lazy-Loading"
-  color: "bfd4f2"
-- name: "A-Light-Box"
-  description: "UI when viewing an image"
-  color: "bfd4f2"
-- name: "A-Location-Sharing"
-  color: "bfd4f2"
-- name: "A-Logout"
-  description: "Logout, sign out, etc."
-  color: "bfd4f2"
-- name: "A-Maths"
-  description: "Render LaTeX maths in messages"
-  color: "bfd4f2"
-- name: "A-Memory"
-  description: "Memory leaks, leak hunting tools"
-  color: "bfd4f2"
-- name: "A-Message-Forwarding"
-  color: "bfd4f2"
-- name: "A-Message-Pinning"
-  color: "bfd4f2"
-- name: "A-Message-Previews"
-  color: "bfd4f2"
-- name: "A-Message-Starring"
-  description: "Saving favourite messages for later"
-  color: "bfd4f2"
-- name: "A-Modules"
-  description: "Module system related"
-  color: "bfd4f2"
-- name: "A-New-Search-Experience"
-  description: "The new search dialog available in Labs"
-  color: "bfd4f2"
-- name: "A-Packaging"
-  description: "Packaging, signing, releasing"
-  color: "bfd4f2"
-- name: "A-Peeking"
-  color: "bfd4f2"
-- name: "A-Picture-in-Picture"
-  color: "bfd4f2"
-- name: "A-Power-Levels"
-  description: "The permissions that users have in rooms and spaces"
-  color: "bfd4f2"
-- name: "A-Replies"
-  description: "reply"
-  color: "bfd4f2"
-- name: "A-Session-Mgmt"
-  description: "Session / device names, management UI, etc."
-  color: "bfd4f2"
-- name: "A-Share"
-  color: "bfd4f2"
-- name: "A-Shortcuts"
-  description: "Keyboard shortcuts"
-  color: "bfd4f2"
-- name: "A-Sliding-Sync"
-  description: "Also known as Sync v3 - https://github.com/matrix-org/sliding-sync"
-  color: "bfd4f2"
-- name: "A-Soft-Logout"
-  description: "https://github.com/element-hq/element-web/issues/10224"
-  color: "bfd4f2"
-- name: "A-Spaces-Settings"
-  color: "bfd4f2"
-- name: "A-SSO"
-  color: "bfd4f2"
-- name: "A-Status-Bar"
-  description: "Unsent messages warning and 'Connectivity to the server has been lost'"
-  color: "bfd4f2"
-- name: "A-Storage"
-  description: "Storage layer of the app, including IndexedDB, local storage, etc."
-  color: "bfd4f2"
-- name: "A-Technical-Debt"
-  color: "bfd4f2"
-- name: "A-Testing"
-  description: "Testing, code coverage, etc."
-  color: "bfd4f2"
-- name: "A-Themes-Custom"
-  description: "Custom theme variables or support"
-  color: "bfd4f2"
-- name: "A-Themes-Official"
-  description: "Official themes (light, dark)"
-  color: "bfd4f2"
-- name: "A-Theming"
-  color: "bfd4f2"
-- name: "A-Timeline-Jumpy-Scroll"
-  description: "Stable timeline dream ✨"
-  color: "bfd4f2"
-- name: "A-Timesheet-1"
-  description: "Log any time spent on this into the A-Timesheet-1 project"
-  color: "5319E7"
-- name: "A-Toast"
-  color: "bfd4f2"
-- name: "A-Tooltips"
-  description: "Anything related to tooltips"
-  color: "bfd4f2"
-- name: "A-UI-Customisation"
-  description: "UIFeatures etc. for customising entire parts of the UI"
-  color: "bfd4f2"
-- name: "A-URL-Previews"
-  color: "bfd4f2"
-- name: "A-User-Menu"
-  description: "The top left main menu with the user's name and avatar"
-  color: "bfd4f2"
-- name: "A-User-Search"
-  description: "The start DM or invite to room dialogs (things dealing with `/user_directory/search`)"
-  color: "bfd4f2"
-- name: "A-Video-Rooms"
-  description: "Persistent group calls"
-  color: "bfd4f2"
-- name: "A-Voice-Messages"
-  color: "bfd4f2"
-- name: "A-Welcome-Page"
-  color: "bfd4f2"
-- name: "backport staging"
-  description: "Label to automatically backport PR to staging branch"
-  color: "B60205"
-- name: "Dependencies"
-  description: "Pull requests that update a dependency file"
-  color: "0366d6"
-- name: "Hacktoberfest"
-  description: "Issues which are suitable for Hacktoberfest PRs: https://hacktoberfest.digitalocean.com/"
-  color: "ff7518"
-- name: "P4"
-  description: "[OBSOLETE LABEL] Interesting — Not yet scheduled, will accept patches"
-  color: "d1e5f0"
-- name: "spam"
-  color: "B60205"
-- name: "Sponsored"
-  color: "ffc8f4"
-- name: "T-Deprecation"
-  description: "A pull request that makes something deprecated"
-  color: "98e6ae"
-- name: "T-Other"
-  description: "Questions, user support, anything else"
-  color: "98e6ae"
-- name: "Team: App"
-  color: "FFA500"
-- name: "X-Blocked"
-  color: "ff7979"
-- name: "X-Cannot-Reproduce"
-  color: "ff7979"
-- name: "X-Command"
-  description: "Created using the !github command"
-  color: "ff7979"
-- name: "X-Community-Supported-Platform"
-  description: "This issue occurs in a platform not directly supported by us, but by a community project elsewhere"
-  color: "ff7979"
-- name: "X-Upcoming-Release-Blocker"
-  description: "This does not affect the current release cycle but will affect the next one"
-  color: "e99695"
-- name: "Z-Actions"
-  color: "ededed"
-- name: "Z-Cache-Confusion"
-  description: "Related to internal cache (clearing helps / causes the issue)"
-  color: "ededed"
-- name: "Z-Community-PR"
-  description: "Issue is solved by a community member's PR"
-  color: "ededed"
-- name: "Z-Element-R-Blocker"
-  description: "A blocker for enabling Element R by default"
-  color: "ededed"
-- name: "Z-Experimental"
-  color: "ededed"
-- name: "Z-Fixed by Element Call"
-  description: "Issues which can be closed when we move to Element Call"
-  color: "ededed"
-- name: "Z-Fixed-By-OIDC"
-  description: "Issues which can be closed when we move to OIDC"
-  color: "ededed"
-- name: "Z-Flaky-Test"
-  description: "A test is raising false alarms"
-  color: "ededed"
-- name: "Z-FOSDEM"
-  description: "Issues in chat.fosdem.org"
-  color: "ededed"
-- name: "Z-Gitter"
-  description: "Issues relating to or coming out of the Gitter migration, feature parity, etc"
-  color: "ededed"
-- name: "Z-Legacy-Crypto"
-  description: "Issues affecting the legacy crypto stack"
-  color: "EEEEEE"
-- name: "Z-Maximised-Widgets"
-  color: "ededed"
-- name: "Z-Papercuts"
-  description: "Visible. Impactful. Predictable to action."
-  color: "ededed"
-- name: "Z-Power-Users"
-  color: "ededed"
-- name: "Z-Rageshake"
-  description: "Has attached rageshake (not for log submission process)"
-  color: "ededed"
-- name: "Z-RICE"
-  color: "ededed"
-- name: "Z-Soft-Crash"
-  description: "React soft crash caught by an error boundary"
-  color: "ededed"
-- name: "Z-Spec-Compliance"
-  description: "An area where Element doesn't correctly implement the spec"
-  color: "ededed"
-- name: "Z-t3chguy"
-  color: "ededed"
-- name: "Z-Flaky-Test-Disabled"
-  description: "The flaking test has been disabled"
-  color: "ededed"

.github/release-drafter.yml

@@ -1,3 +0,0 @@
-_extends: matrix-org/matrix-js-sdk
-version-resolver:
-    default: patch

.github/workflows/build.yml

@@ -3,8 +3,6 @@ on:
     pull_request: {}
     push:
         branches: [develop, master]
-    merge_group:
-        types: [checks_requested]
 # develop pushes and repository_dispatch handled in build_develop.yaml
 env:
     # These must be set for fetchdep.sh to get the right branch
@@ -37,7 +35,6 @@ jobs:
             - uses: actions/setup-node@v4
               with:
                   cache: "yarn"
-                  node-version: "lts/*"
 
             # Workaround for yarn install timeouts, especially on Windows
             - run: yarn config set network-timeout 300000

.github/workflows/build_debian.yaml

@@ -17,8 +17,8 @@ jobs:
 
             - name: Download package
               run: |
-                  wget "https://github.com/element-hq/element-web/releases/download/$VERSION/element-$VERSION.tar.gz"
-                  wget "https://github.com/element-hq/element-web/releases/download/$VERSION/element-$VERSION.tar.gz.asc"
+                  wget "https://github.com/vector-im/element-web/releases/download/$VERSION/element-$VERSION.tar.gz"
+                  wget "https://github.com/vector-im/element-web/releases/download/$VERSION/element-$VERSION.tar.gz.asc"
 
             - name: Check GPG signature
               run: |
@@ -33,11 +33,10 @@ jobs:
               run: |
                   mkdir -p debian/tmp/DEBIAN
                   find debian -maxdepth 1 -type f -exec cp "{}" debian/tmp/DEBIAN/ \;
-                  mkdir -p debian/tmp/usr/share/element-web/ debian/tmp/etc/element-web/
+                  mkdir -p debian/tmp/usr/share/element-web/
 
                   tar -xf "element-$VERSION.tar.gz" -C debian/tmp/usr/share/element-web --strip-components=1 --no-same-owner --no-same-permissions
-                  mv debian/tmp/usr/share/element-web/config.sample.json debian/tmp/etc/element-web/config.json
-                  ln -s /etc/element-web/config.json debian/tmp/usr/share/element-web/config.json
+                  mv debian/tmp/usr/share/element-web/config{.sample,}.json
 
             - name: Write changelog
               run: |
@@ -58,10 +57,11 @@ jobs:
             - name: Build deb package
               run: |
                   VERSION=$(cat package.json | jq -r .version)
+                  chmod -R u=rw,go=r debian/tmp/usr/share/element-web/
                   dpkg-gencontrol -v"$VERSION" -ldebian/tmp/DEBIAN/changelog
                   dpkg-deb -Zxz --root-owner-group --build debian/tmp element-web.deb
 
-            - uses: actions/upload-artifact@v4
+            - uses: actions/upload-artifact@v3
               with:
                   name: element-web.deb
                   path: element-web.deb
@@ -69,7 +69,7 @@ jobs:
 
             - name: Publish to packages.element.io
               if: github.event.release.prerelease == false
-              uses: element-hq/packages.element.io@master
+              uses: vector-im/packages.element.io@master
               with:
                   file: element-web.deb
                   github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}

.github/workflows/build_develop.yml

@@ -13,7 +13,7 @@ jobs:
     build:
         name: "Build & Deploy develop.element.io"
         # Only respect triggers from our develop branch, ignore that of forks
-        if: github.repository == 'element-hq/element-web'
+        if: github.repository == 'vector-im/element-web'
         runs-on: ubuntu-latest
         environment: develop
         env:
@@ -26,7 +26,6 @@ jobs:
             - uses: actions/setup-node@v4
               with:
                   cache: "yarn"
-                  node-version: "lts/*"
 
             - name: Install Dependencies
               run: "./scripts/layered.sh"
@@ -48,7 +47,7 @@ jobs:
 
             - run: mv dist/element-*.tar.gz dist/develop.tar.gz
 
-            - uses: actions/upload-artifact@v4
+            - uses: actions/upload-artifact@v3
               with:
                   name: webapp
                   path: dist/develop.tar.gz
@@ -85,21 +84,14 @@ jobs:
                   AWS_ACCESS_KEY_ID: ${{ secrets.CF_R2_ACCESS_KEY_ID }}
                   AWS_SECRET_ACCESS_KEY: ${{ secrets.CF_R2_TOKEN }}
 
-            # We may be trying to deploy the same webapp bundles again, we need to ensure that the live bundles
-            # are not present in the _redirects file and instead accessed directly from Cloudflare Pages.
-            - name: Trim _redirects
-              working-directory: _deploy
-              run: |
-                  find bundles -type d -mindepth 1 -maxdepth 1 -exec sed -i "\:{}:d" _redirects \;
-
             - name: Wait for other steps to succeed
-              uses: t3chguy/wait-on-check-action@18541021811b56544d90e0f073401c2b99e249d6 # fork
+              uses: t3chguy/wait-on-check-action@05861d3a448898eb33dfce34153bd1ecb9422fb9 # fork
               with:
                   ref: ${{ github.sha }}
                   running-workflow-name: "Build & Deploy develop.element.io"
                   repo-token: ${{ secrets.GITHUB_TOKEN }}
                   wait-interval: 10
-                  check-regexp: ^((?!SonarCloud|SonarQube|issue|board|label|Release|prepare|GitHub Pages).)*$
+                  check-regexp: ^((?!SonarCloud|SonarQube|issue|board|label).)*$
 
             # We keep the latest develop.tar.gz on R2 instead of relying on the github artifact uploaded earlier
             # as the expires after 24h and requires auth to download.

.github/workflows/dockerhub.yaml

@@ -7,9 +7,6 @@ on:
         # This job can take a while, and we have usage limits, so just publish develop only twice a day
         - cron: "0 7/12 * * *"
 concurrency: ${{ github.workflow }}-${{ github.ref_name }}
-
-permissions:
-    id-token: write # needed for signing the images with GitHub OIDC Token
 jobs:
     buildx:
         name: Docker Buildx
@@ -29,30 +26,27 @@ jobs:
               with:
                   fetch-depth: 0 # needed for docker-package to be able to calculate the version
 
-            - name: Install Cosign
-              uses: sigstore/cosign-installer@4959ce089c160fddf62f7b42464195ba1a56d382 # v3
-
             - name: Prepare
               if: matrix.prepare
               run: ${{ matrix.prepare }}
 
             - name: Set up QEMU
-              uses: docker/setup-qemu-action@49b3bc8e6bdd4a60e6116a5414239cba5943d3cf # v3
+              uses: docker/setup-qemu-action@68827325e0b33c7199eb31dd4e31fbe9023e06e3 # v3
 
             - name: Set up Docker Buildx
-              uses: docker/setup-buildx-action@988b5a0280414f521da01fcc63a27aeeb4b104db # v3
+              uses: docker/setup-buildx-action@f95db51fddba0c2d1ec667646a06c2ce06100226 # v3
               with:
                   install: true
 
             - name: Login to Docker Hub
-              uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567 # v3
+              uses: docker/login-action@343f7c4344506bcbf9b4de18042ae17996df046d # v3
               with:
                   username: ${{ secrets.DOCKERHUB_USERNAME }}
                   password: ${{ secrets.DOCKERHUB_TOKEN }}
 
             - name: Docker meta
               id: meta
-              uses: docker/metadata-action@8e5442c4ef9f78752691e2d8f8d19755c6f78e81 # v5
+              uses: docker/metadata-action@96383f45573cb7f253c731d3b3ab81c87ef81934 # v5
               with:
                   images: |
                       vectorim/element-web
@@ -64,8 +58,7 @@ jobs:
                       ${{ matrix.flavor }}
 
             - name: Build and push
-              id: build-and-push
-              uses: docker/build-push-action@4f58ea79222b3b9dc2c8bbdd6debcef730109a75 # v6
+              uses: docker/build-push-action@0565240e2d4ab88bba5387d719585280857ece09 # v5
               with:
                   context: .
                   push: true
@@ -73,20 +66,8 @@ jobs:
                   tags: ${{ steps.meta.outputs.tags }}
                   labels: ${{ steps.meta.outputs.labels }}
 
-            - name: Sign the images with GitHub OIDC Token
-              env:
-                  DIGEST: ${{ steps.build-and-push.outputs.digest }}
-                  TAGS: ${{ steps.meta.outputs.tags }}
-              run: |
-                  images=""
-                  for tag in ${TAGS}; do
-                      images+="${tag}@${DIGEST} "
-                  done
-                  cosign sign --yes ${images}
-
             - name: Update repo description
-              if: matrix.variant == 'vanilla'
-              uses: peter-evans/dockerhub-description@e98e4d1628a5f3be2be7c231e50981aee98723ae # v4
+              uses: peter-evans/dockerhub-description@dc67fad7001ef9e8e3c124cb7a64e16d0a63d864 # v3
               continue-on-error: true
               with:
                   username: ${{ secrets.DOCKERHUB_USERNAME }}

.github/workflows/docs.yml

@@ -22,7 +22,7 @@ jobs:
             - name: Fetch element-desktop
               uses: actions/checkout@v4
               with:
-                  repository: element-hq/element-desktop
+                  repository: vector-im/element-desktop
                   path: element-desktop
 
             - name: Fetch element-web
@@ -30,6 +30,12 @@ jobs:
               with:
                   path: element-web
 
+            - name: Fetch matrix-react-sdk
+              uses: actions/checkout@v4
+              with:
+                  repository: matrix-org/matrix-react-sdk
+                  path: matrix-react-sdk
+
             - name: Fetch matrix-js-sdk
               uses: actions/checkout@v4
               with:
@@ -40,17 +46,16 @@ jobs:
               with:
                   cache: "yarn"
                   cache-dependency-path: element-web/yarn.lock
-                  node-version: "lts/*"
 
             - name: Generate automations docs
               working-directory: element-web
               run: |
                   yarn install --frozen-lockfile
-                  yarn ts-node ./scripts/gen-workflow-mermaid.ts ../element-desktop ../element-web ../matrix-js-sdk > docs/automations.md
+                  yarn ts-node ./scripts/gen-workflow-mermaid.ts ../element-desktop ../element-web ../matrix-react-sdk ../matrix-js-sdk > docs/automations.md
                   echo "-   [Automations](automations.md)" >> docs/SUMMARY.md
 
             - name: Setup mdBook
-              uses: peaceiris/actions-mdbook@v2
+              uses: peaceiris/actions-mdbook@v1
               with:
                   mdbook-version: "0.4.10"
 
@@ -68,6 +73,9 @@ jobs:
                   mv element-web/docs/lib docs/
                   mv element-web/docs "docs/Element Web"
 
+                  mv matrix-react-sdk/README.md matrix-react-sdk/docs/
+                  mv matrix-react-sdk/docs "docs/Matrix React SDK"
+
                   mv matrix-js-sdk/README.md matrix-js-sdk/docs/
                   mv matrix-js-sdk/docs "docs/Matrix JS SDK"
 
@@ -91,7 +99,7 @@ jobs:
               run: mdbook build
 
             - name: Upload artifact
-              uses: actions/upload-pages-artifact@v3
+              uses: actions/upload-pages-artifact@v2
               with:
                   path: ./book
 
@@ -104,4 +112,4 @@ jobs:
         steps:
             - name: Deploy to GitHub Pages
               id: deployment
-              uses: actions/deploy-pages@v4
+              uses: actions/deploy-pages@v2

.github/workflows/end-to-end-tests-netlify.yaml

@@ -1,43 +0,0 @@
-# Triggers after the playwright tests have finished,
-# taking the artifact and uploading it to Netlify for easier viewing
-name: Upload End to End Test report to Netlify
-on:
-    workflow_run:
-        workflows: ["End to End Tests"]
-        types:
-            - completed
-
-concurrency:
-    group: ${{ github.workflow }}-${{ github.event.workflow_run.head_branch || github.run_id }}
-    cancel-in-progress: ${{ github.event.workflow_run.event == 'pull_request' }}
-
-jobs:
-    report:
-        if: github.event.workflow_run.conclusion != 'cancelled'
-        name: Report results
-        runs-on: ubuntu-22.04
-        environment: Netlify
-        permissions:
-            statuses: write
-            deployments: write
-        steps:
-            - name: Download HTML report
-              uses: actions/download-artifact@v4
-              with:
-                  github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
-                  run-id: ${{ github.event.workflow_run.id }}
-                  name: html-report
-                  path: playwright-report
-
-            - name: 📤 Deploy to Netlify
-              uses: matrix-org/netlify-pr-preview@v3
-              with:
-                  path: playwright-report
-                  owner: ${{ github.event.workflow_run.head_repository.owner.login }}
-                  branch: ${{ github.event.workflow_run.head_branch }}
-                  revision: ${{ github.event.workflow_run.head_sha }}
-                  token: ${{ secrets.NETLIFY_AUTH_TOKEN }}
-                  site_id: ${{ vars.NETLIFY_SITE_ID }}
-                  desc: Playwright Report
-                  deployment_env: EndToEndTests
-                  prefix: "e2e-"

.github/workflows/end-to-end-tests.yaml

@@ -1,190 +0,0 @@
-# Produce a build of element-web with this version of react-sdk
-# and any matching branches of element-web and js-sdk, output it
-# as an artifact and run end-to-end tests.
-name: End to End Tests
-on:
-    pull_request: {}
-    merge_group:
-        types: [checks_requested]
-    push:
-        branches: [develop, master]
-    repository_dispatch:
-        types: [element-web-notify]
-
-    # support triggering from other workflows
-    workflow_call:
-        inputs:
-            skip:
-                type: boolean
-                required: false
-                default: false
-                description: "A boolean to skip the playwright check itself while still creating the passing check. Useful when only running in Merge Queues."
-
-            matrix-js-sdk-sha:
-                type: string
-                required: false
-                description: "The Git SHA of matrix-js-sdk to build against. By default, will use a matching branch name if it exists, or develop."
-
-concurrency:
-    group: ${{ github.workflow }}-${{ github.ref }}-${{ github.event_name }}
-    cancel-in-progress: true
-
-env:
-    # fetchdep.sh needs to know our PR number
-    PR_NUMBER: ${{ github.event.pull_request.number }}
-
-jobs:
-    build:
-        name: "Build Element-Web"
-        runs-on: ubuntu-22.04
-        if: inputs.skip != true
-        steps:
-            - name: Checkout code
-              uses: actions/checkout@v4
-              with:
-                  repository: element-hq/element-web
-
-            - uses: actions/setup-node@v4
-              with:
-                  cache: "yarn"
-                  node-version: "lts/*"
-
-            - name: Fetch layered build
-              id: layered_build
-              env:
-                  # tell layered.sh to check out the right sha of the JS-SDK & EW, if they were given one
-                  JS_SDK_GITHUB_BASE_REF: ${{ inputs.matrix-js-sdk-sha }}
-              run: |
-                  scripts/layered.sh
-                  JSSDK_SHA=$(git -C matrix-js-sdk rev-parse --short=12 HEAD)
-                  VECTOR_SHA=$(git rev-parse --short=12 HEAD)
-                  echo "VERSION=$VECTOR_SHA--js-$JSSDK_SHA" >> $GITHUB_OUTPUT
-
-            - name: Copy config
-              run: cp element.io/develop/config.json config.json
-
-            - name: Build
-              env:
-                  CI_PACKAGE: true
-                  VERSION: "${{ steps.layered_build.outputs.VERSION }}"
-              run: |
-                  yarn build
-                  echo $VERSION > webapp/version
-
-            - name: Upload Artifact
-              uses: actions/upload-artifact@v4
-              with:
-                  name: webapp
-                  path: webapp
-                  retention-days: 1
-
-    playwright:
-        name: "Run Tests ${{ matrix.runner }}/${{ strategy.job-total }}"
-        needs: build
-        if: inputs.skip != true
-        runs-on: ubuntu-22.04
-        permissions:
-            actions: read
-            issues: read
-            pull-requests: read
-        strategy:
-            fail-fast: false
-            matrix:
-                # Run multiple instances in parallel to speed up the tests
-                runner: [1, 2, 3, 4, 5, 6]
-        steps:
-            - uses: actions/checkout@v4
-              with:
-                  persist-credentials: false
-                  repository: element-hq/element-web
-
-            - name: 📥 Download artifact
-              uses: actions/download-artifact@v4
-              with:
-                  name: webapp
-                  path: webapp
-
-            - uses: actions/setup-node@v4
-              with:
-                  cache: "yarn"
-                  cache-dependency-path: yarn.lock
-                  node-version: "lts/*"
-
-            - name: Install dependencies
-              run: yarn install --frozen-lockfile
-
-            - name: Get installed Playwright version
-              id: playwright
-              run: echo "version=$(yarn list --pattern @playwright/test --depth=0 --json --non-interactive --no-progress | jq -r '.data.trees[].name')" >> $GITHUB_OUTPUT
-
-            - name: Cache playwright binaries
-              uses: actions/cache@v4
-              id: playwright-cache
-              with:
-                  path: |
-                      ~/.cache/ms-playwright
-                  key: ${{ runner.os }}-playwright-${{ steps.playwright.outputs.version }}
-
-            - name: Install Playwright browsers
-              if: steps.playwright-cache.outputs.cache-hit != 'true'
-              run: yarn playwright install --with-deps
-
-            - name: Run Playwright tests
-              run: yarn playwright test --shard ${{ matrix.runner }}/${{ strategy.job-total }}
-
-            - name: Upload blob report to GitHub Actions Artifacts
-              if: always()
-              uses: actions/upload-artifact@v4
-              with:
-                  name: all-blob-reports-${{ matrix.runner }}
-                  path: blob-report
-                  retention-days: 1
-
-    complete:
-        name: end-to-end-tests
-        needs: playwright
-        if: always()
-        runs-on: ubuntu-22.04
-        steps:
-            - uses: actions/checkout@v4
-              if: inputs.skip != true
-              with:
-                  persist-credentials: false
-                  repository: element-hq/element-web
-
-            - uses: actions/setup-node@v4
-              if: inputs.skip != true
-              with:
-                  cache: "yarn"
-                  node-version: "lts/*"
-
-            - name: Install dependencies
-              if: inputs.skip != true
-              run: yarn install --frozen-lockfile
-
-            - name: Download blob reports from GitHub Actions Artifacts
-              if: inputs.skip != true
-              uses: actions/download-artifact@v4
-              with:
-                  pattern: all-blob-reports-*
-                  path: all-blob-reports
-                  merge-multiple: true
-
-            - name: Merge into HTML Report
-              if: inputs.skip != true
-              run: yarn playwright merge-reports --reporter=html,./playwright/flaky-reporter.ts,./playwright/stale-screenshot-reporter.ts ./all-blob-reports
-              env:
-                  # Only pass creds to the flaky-reporter on main branch runs
-                  GITHUB_TOKEN: ${{ github.ref_name == 'develop' && secrets.ELEMENT_BOT_TOKEN || '' }}
-
-            # Upload the HTML report even if one of our reporters fails, this can happen when stale screenshots are detected
-            - name: Upload HTML report
-              if: always() && inputs.skip != true
-              uses: actions/upload-artifact@v4
-              with:
-                  name: html-report
-                  path: playwright-report
-                  retention-days: 14
-
-            - if: needs.playwright.result != 'skipped' && needs.playwright.result != 'success'
-              run: exit 1

.github/workflows/issue_closed.yml

@@ -9,7 +9,7 @@ jobs:
         name: Tidy closed issues
         runs-on: ubuntu-latest
         steps:
-            - uses: actions/github-script@v7
+            - uses: actions/github-script@v6
               id: main
               with:
                   # PAT needed as the GITHUB_TOKEN won't be able to see cross-references from other orgs (matrix-org)
@@ -141,7 +141,7 @@ jobs:
                           });
                         }
                       }
-            - uses: actions/github-script@v7
+            - uses: actions/github-script@v6
               name: Close duplicate as Not Planned
               if: steps.main.outputs.closeAsNotPlanned
               with:

.github/workflows/localazy_download.yaml

@@ -1,8 +1,6 @@
 name: Localazy Download
 on:
     workflow_dispatch: {}
-    schedule:
-        - cron: "0 6 * * 1,3,5" # Every Monday, Wednesday and Friday at 6am UTC
 jobs:
     download:
         uses: matrix-org/matrix-web-i18n/.github/workflows/localazy_download.yaml@main

.github/workflows/netlify.yaml

@@ -1,48 +0,0 @@
-# Triggers after the layered build has finished, taking the artifact
-# and uploading it to netlify
-name: Upload Preview Build to Netlify
-on:
-    workflow_run:
-        workflows: ["End to End Tests"]
-        types:
-            - completed
-jobs:
-    deploy:
-        if: github.event.workflow_run.conclusion != 'cancelled' && github.event.workflow_run.event == 'pull_request'
-        runs-on: ubuntu-22.04
-        environment: Netlify
-        steps:
-            - name: 📝 Create Deployment
-              uses: bobheadxi/deployments@648679e8e4915b27893bd7dbc35cb504dc915bc8 # v1
-              id: deployment
-              with:
-                  step: start
-                  token: ${{ secrets.GITHUB_TOKEN }}
-                  env: Netlify
-                  ref: ${{ github.event.workflow_run.head_sha }}
-                  desc: |
-                      Do you trust the author of this PR? Maybe this build will steal your keys or give you malware.
-                      Exercise caution. Use test accounts.
-
-            - name: 📥 Download artifact
-              uses: actions/download-artifact@v4
-              with:
-                  github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
-                  run-id: ${{ github.event.workflow_run.id }}
-                  name: webapp
-                  path: webapp
-
-            - name: 📤 Deploy to Netlify
-              uses: matrix-org/netlify-pr-preview@v3
-              with:
-                  path: webapp
-                  owner: ${{ github.event.workflow_run.head_repository.owner.login }}
-                  branch: ${{ github.event.workflow_run.head_branch }}
-                  revision: ${{ github.event.workflow_run.head_sha }}
-                  token: ${{ secrets.NETLIFY_AUTH_TOKEN }}
-                  site_id: ${{ vars.NETLIFY_SITE_ID }}
-                  deployment_env: ${{ steps.deployment.outputs.env }}
-                  deployment_id: ${{ steps.deployment.outputs.deployment_id }}
-                  desc: |
-                      Do you trust the author of this PR? Maybe this build will steal your keys or give you malware.
-                      Exercise caution. Use test accounts.

.github/workflows/pending-reviews.yaml

@@ -1,10 +1,8 @@
 name: Pending reviews automation
 on:
-    # The bot exceeded its API rate limit. Disabling for now (adding workflow dispatch so the workflow file stays valid & we can test to see if it starts working again)
-    workflow_dispatch: {}
     # We run it on a schedule instead of on pull_request_* events to not create confusing messaging in the PR
-    #schedule:
-    #    - cron: "*/10 * * * *"
+    schedule:
+        - cron: "*/10 * * * *"
 concurrency: ${{ github.workflow }}
 jobs:
     bot:
@@ -12,10 +10,10 @@ jobs:
         runs-on: ubuntu-latest
         environment: Matrix
         env:
-            URL: "https://github.com/pulls?q=is%3Apr+is%3Aopen+repo%3Amatrix-org%2Fmatrix-js-sdk+repo%3Amatrix-org%2Fmatrix-react-sdk+repo%3Aelement-hq%2Felement-web+repo%3Aelement-hq%2Felement-desktop+review-requested%3A%40me+sort%3Aupdated-desc+"
-            RELEASE_BLOCKERS_URL: "https://github.com/pulls?q=is%3Aopen+repo%3Amatrix-org%2Fmatrix-js-sdk+repo%3Amatrix-org%2Fmatrix-react-sdk+repo%3Aelement-hq%2Felement-web+repo%3Aelement-hq%2Felement-desktop+sort%3Aupdated-desc+label%3AX-Release-Blocker+"
+            URL: "https://github.com/pulls?q=is%3Apr+is%3Aopen+repo%3Amatrix-org%2Fmatrix-js-sdk+repo%3Amatrix-org%2Fmatrix-react-sdk+repo%3Avector-im%2Felement-web+repo%3Avector-im%2Felement-desktop+review-requested%3A%40me+sort%3Aupdated-desc+"
+            RELEASE_BLOCKERS_URL: "https://github.com/pulls?q=is%3Aopen+repo%3Amatrix-org%2Fmatrix-js-sdk+repo%3Amatrix-org%2Fmatrix-react-sdk+repo%3Avector-im%2Felement-web+repo%3Avector-im%2Felement-desktop+sort%3Aupdated-desc+label%3AX-Release-Blocker+"
         steps:
-            - uses: actions/github-script@v7
+            - uses: actions/github-script@v6
               env:
                   HS_URL: ${{ secrets.BETABOT_HS_URL }}
                   ROOM_ID: ${{ secrets.ROOM_ID }}
@@ -62,15 +60,16 @@ jobs:
                       }
 
                       const repos = [
-                          "element-hq/element-desktop",
-                          "element-hq/element-web",
+                          "vector-im/element-desktop",
+                          "vector-im/element-web",
+                          "matrix-org/matrix-react-sdk",
                           "matrix-org/matrix-js-sdk",
                       ];
                       const teams = [
-                          "matrix-org/element-web-team",
-                          "matrix-org/element-web-reviewers",
-                          "element-hq/element-web-team",
-                          "element-hq/element-web-reviewers",
+                          "matrix-org/element-web-app-team",
+                          "matrix-org/element-web",
+                          "vector-im/element-web-app-team",
+                          "vector-im/element-web",
                       ];
 
                       let issueCount = 0;

.github/workflows/playwright-image-updates.yaml

@@ -1,45 +0,0 @@
-name: Update Playwright docker images
-on:
-    workflow_dispatch: {}
-    schedule:
-        - cron: "0 6 * * *" # Every day at 6am UTC
-jobs:
-    update:
-        runs-on: ubuntu-22.04
-        steps:
-            - uses: actions/checkout@v4
-
-            - name: Update synapse image
-              run: |
-                  docker pull "$IMAGE"
-                  INSPECT=$(docker inspect --format='{{index .RepoDigests 0}}' "$IMAGE")
-                  DIGEST=${INSPECT#*@}
-                  sed -i "s/const DOCKER_TAG.*/const DOCKER_TAG = \"develop@$DIGEST\";/" playwright/plugins/homeserver/synapse/index.ts
-              env:
-                  IMAGE: ghcr.io/element-hq/synapse:develop
-
-            - name: Create Pull Request
-              id: cpr
-              uses: peter-evans/create-pull-request@5e914681df9dc83aa4e4905692ca88beb2f9e91f # v7
-              with:
-                  token: ${{ secrets.ELEMENT_BOT_TOKEN }}
-                  branch: actions/playwright-image-updates
-                  delete-branch: true
-                  title: Playwright Docker image updates
-                  labels: |
-                      T-Task
-
-            - name: Enable automerge
-              run: gh pr merge --merge --auto "$PR_NUMBER"
-              if: steps.cpr.outputs.pull-request-operation == 'created'
-              env:
-                  GH_TOKEN: ${{ secrets.ELEMENT_BOT_TOKEN }}
-                  PR_NUMBER: ${{ steps.cpr.outputs.pull-request-number }}
-
-            - name: Enable autoapprove
-              run: |
-                  gh pr review --approve "$PR_NUMBER"
-              if: steps.cpr.outputs.pull-request-operation == 'created'
-              env:
-                  GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-                  PR_NUMBER: ${{ steps.cpr.outputs.pull-request-number }}

.github/workflows/pull_request.yaml

@@ -2,8 +2,6 @@ name: Pull Request
 on:
     pull_request_target:
         types: [opened, edited, labeled, unlabeled, synchronize]
-    merge_group:
-        types: [checks_requested]
 jobs:
     action:
         uses: matrix-org/matrix-js-sdk/.github/workflows/pull_request.yaml@develop

.github/workflows/pull_request_base_branch.yaml

@@ -1,16 +0,0 @@
-name: Pull Request Base Branch
-on:
-    pull_request:
-        types: [opened, edited, synchronize]
-jobs:
-    check_base_branch:
-        name: Check PR base branch
-        runs-on: ubuntu-22.04
-        steps:
-            - uses: actions/github-script@v7
-              with:
-                  script: |
-                      const baseBranch = context.payload.pull_request.base.ref;
-                      if (!['develop', 'staging'].includes(baseBranch) && !baseBranch.startsWith('feat/')) {
-                          core.setFailed(`Invalid base branch: ${baseBranch}`);
-                      }

.github/workflows/release-drafter.yml

@@ -1,9 +0,0 @@
-name: Release Drafter
-on:
-    push:
-        branches: [staging]
-    workflow_dispatch: {}
-concurrency: ${{ github.workflow }}
-jobs:
-    draft:
-        uses: matrix-org/matrix-js-sdk/.github/workflows/release-drafter-workflow.yml@develop

.github/workflows/release-gitflow.yml

@@ -1,14 +0,0 @@
-# Gitflow merge-back master->develop
-name: Merge master -> develop
-on:
-    push:
-        branches: [master]
-concurrency: ${{ github.repository }}-${{ github.workflow }}
-jobs:
-    merge:
-        uses: matrix-org/matrix-js-sdk/.github/workflows/release-gitflow.yml@develop
-        secrets:
-            ELEMENT_BOT_TOKEN: ${{ secrets.ELEMENT_BOT_TOKEN }}
-        with:
-            dependencies: |
-                matrix-js-sdk

.github/workflows/release.yml

@@ -1,62 +0,0 @@
-name: Release Process
-on:
-    workflow_dispatch:
-        inputs:
-            mode:
-                description: What type of release
-                required: true
-                default: rc
-                type: choice
-                options:
-                    - rc
-                    - final
-concurrency: ${{ github.workflow }}
-jobs:
-    release:
-        uses: matrix-org/matrix-js-sdk/.github/workflows/release-make.yml@develop
-        secrets:
-            ELEMENT_BOT_TOKEN: ${{ secrets.ELEMENT_BOT_TOKEN }}
-            GPG_PRIVATE_KEY: ${{ secrets.GPG_PRIVATE_KEY }}
-            GPG_PASSPHRASE: ${{ secrets.GPG_PASSPHRASE }}
-        with:
-            final: ${{ inputs.mode == 'final' }}
-            gpg-fingerprint: ${{ vars.GPG_FINGERPRINT }}
-            asset-path: dist/*.tar.gz
-            expected-asset-count: 3
-
-    notify-downstream:
-        name: Trigger release drafter downstream
-        needs: release
-        runs-on: ubuntu-latest
-        steps:
-            - name: Notify element-desktop repo that element-web release has completed to re-trigger release-drafter
-              uses: benc-uk/workflow-dispatch@e2e5e9a103e331dad343f381a29e654aea3cf8fc # v1
-              with:
-                  workflow: release-drafter.yml
-                  repo: element-hq/element-desktop
-                  ref: staging
-                  # Required when using the `repo` option. Either a PAT or a token generated from the GitHub app or CLI
-                  token: "${{ secrets.ELEMENT_BOT_TOKEN }}"
-
-    check:
-        name: Post release checks
-        needs: release
-        runs-on: ubuntu-latest
-        steps:
-            - name: Wait for dockerhub
-              uses: t3chguy/wait-on-check-action@18541021811b56544d90e0f073401c2b99e249d6 # fork
-              with:
-                  ref: master
-                  repo-token: ${{ secrets.GITHUB_TOKEN }}
-                  wait-interval: 10
-                  check-name: "Docker Buildx (vanilla)"
-                  allowed-conclusions: success
-
-            - name: Wait for debian package
-              uses: t3chguy/wait-on-check-action@18541021811b56544d90e0f073401c2b99e249d6 # fork
-              with:
-                  ref: master
-                  repo-token: ${{ secrets.GITHUB_TOKEN }}
-                  wait-interval: 10
-                  check-name: Build package
-                  allowed-conclusions: success

.github/workflows/release_prepare.yml

@@ -12,6 +12,11 @@ on:
                 required: true
                 type: boolean
                 default: true
+            matrix-react-sdk:
+                description: Prepare matrix-react-sdk
+                required: true
+                type: boolean
+                default: true
             matrix-js-sdk:
                 description: Prepare matrix-js-sdk
                 required: true
@@ -25,7 +30,7 @@ jobs:
               uses: actions/checkout@v4
               if: inputs.element-desktop
               with:
-                  repository: element-hq/element-desktop
+                  repository: vector-im/element-desktop
                   path: element-desktop
                   ref: staging
                   fetch-depth: 0
@@ -35,12 +40,22 @@ jobs:
               uses: actions/checkout@v4
               if: inputs.element-web
               with:
-                  repository: element-hq/element-web
+                  repository: vector-im/element-web
                   path: element-web
                   ref: staging
                   fetch-depth: 0
                   fetch-tags: true
                   token: ${{ secrets.ELEMENT_BOT_TOKEN }}
+            - name: Checkout Matrix React SDK
+              uses: actions/checkout@v4
+              if: inputs.matrix-react-sdk
+              with:
+                  repository: matrix-org/matrix-react-sdk
+                  path: matrix-react-sdk
+                  ref: staging
+                  fetch-depth: 0
+                  fetch-tags: true
+                  token: ${{ secrets.ELEMENT_BOT_TOKEN }}
             - name: Checkout Matrix JS SDK
               uses: actions/checkout@v4
               if: inputs.matrix-js-sdk
@@ -52,56 +67,15 @@ jobs:
                   fetch-tags: true
                   token: ${{ secrets.ELEMENT_BOT_TOKEN }}
 
-            - name: Prepare Git
+            - name: Resolve repos
+              run: |
+                  echo "REPOS=$(ls . | tr '\n' ' ')" >> $GITHUB_ENV
+
+            - name: Merge develop
               run: |
                   git config --global user.email "releases@riot.im"
                   git config --global user.name "RiotRobot"
-
-            - name: Merge Element Desktop
-              if: inputs.element-desktop
-              run: |
-                  git -C "element-desktop" merge origin/develop
-            - name: Merge Element Web
-              if: inputs.element-web
-              run: |
-                  git -C "element-web" merge origin/develop
-            - name: Merge JS SDK
-              if: inputs.matrix-js-sdk
-              run: |
-                  git -C "matrix-js-sdk" merge origin/develop
+                  for REPO in $REPOS; do git -C "$REPO" merge origin/develop; done
 
             - name: Push staging
-              run: for REPO in $REPOS; do [ -d "$REPO" ] && git -C "$REPO" push origin staging; done
-
-            - name: Wait for matrix-js-sdk draft
-              if: inputs.matrix-js-sdk
-              uses: t3chguy/wait-on-check-action@18541021811b56544d90e0f073401c2b99e249d6 # fork
-              with:
-                  ref: staging
-                  repo: matrix-org/matrix-js-sdk
-                  repo-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
-                  wait-interval: 10
-                  check-name: draft
-                  allowed-conclusions: success
-
-            - name: Wait for element-web draft
-              if: inputs.element-web
-              uses: t3chguy/wait-on-check-action@18541021811b56544d90e0f073401c2b99e249d6 # fork
-              with:
-                  ref: staging
-                  repo: element-hq/element-web
-                  repo-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
-                  wait-interval: 10
-                  check-name: draft
-                  allowed-conclusions: success
-
-            - name: Wait for element-desktop draft
-              if: inputs.element-desktop
-              uses: t3chguy/wait-on-check-action@18541021811b56544d90e0f073401c2b99e249d6 # fork
-              with:
-                  ref: staging
-                  repo: element-hq/element-desktop
-                  repo-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
-                  wait-interval: 10
-                  check-name: draft
-                  allowed-conclusions: success
+              run: for REPO in $REPOS; do git -C "$REPO" push origin staging; done

.github/workflows/sonarqube.yml

@@ -10,10 +10,6 @@ concurrency:
 jobs:
     sonarqube:
         name: 🩻 SonarQube
-        if: github.event.workflow_run.conclusion == 'success' && github.event.workflow_run.event != 'merge_group'
         uses: matrix-org/matrix-js-sdk/.github/workflows/sonarcloud.yml@develop
         secrets:
             SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
-            ELEMENT_BOT_TOKEN: ${{ secrets.ELEMENT_BOT_TOKEN }}
-        with:
-            sharded: true

.github/workflows/static_analysis.yaml

@@ -3,19 +3,12 @@ on:
     pull_request: {}
     push:
         branches: [develop, master]
-    merge_group:
-        types: [checks_requested]
     repository_dispatch:
         types: [element-web-notify]
-concurrency:
-    group: ${{ github.workflow }}-${{ github.ref }}-${{ github.event_name }}
-    cancel-in-progress: true
-
 env:
     # These must be set for fetchdep.sh to get the right branch
     REPOSITORY: ${{ github.repository }}
     PR_NUMBER: ${{ github.event.pull_request.number }}
-
 jobs:
     ts_lint:
         name: "Typescript Syntax Check"
@@ -26,7 +19,6 @@ jobs:
             - uses: actions/setup-node@v4
               with:
                   cache: "yarn"
-                  node-version: "lts/*"
 
             - name: Install Dependencies
               run: "./scripts/layered.sh"
@@ -34,50 +26,9 @@ jobs:
             - name: Typecheck
               run: "yarn run lint:types"
 
-            - name: Switch js-sdk to release mode
-              working-directory: node_modules/matrix-js-sdk
-              run: |
-                  scripts/switch_package_to_release.cjs
-                  yarn install
-                  yarn run build:compile
-                  yarn run build:types
-
-            - name: Typecheck (release mode)
-              run: "yarn run lint:types"
-
-            # Temporary while we directly import matrix-js-sdk/src/* which means we need
-            # certain @types/* packages to make sense of matrix-js-sdk types.
-            #- name: Typecheck (release mode; no yarn link)
-            #  if: github.event_name != 'pull_request' && github.ref_name != 'master'
-            #  run: |
-            #      yarn unlink matrix-js-sdk
-            #      yarn add github:matrix-org/matrix-js-sdk#develop
-            #      yarn install --force
-            #      yarn run lint:types
-
     i18n_lint:
         name: "i18n Check"
         uses: matrix-org/matrix-web-i18n/.github/workflows/i18n_check.yml@main
-        with:
-            hardcoded-words: "Element"
-            allowed-hardcoded-keys: |
-                console_dev_note
-                labs|element_call_video_rooms
-                labs|feature_disable_call_per_sender_encryption
-                voip|element_call
-                error|invalid_json
-                error|misconfigured
-                welcome_to_element
-
-    rethemendex_lint:
-        name: "Rethemendex Check"
-        runs-on: ubuntu-22.04
-        steps:
-            - uses: actions/checkout@v4
-
-            - run: ./res/css/rethemendex.sh
-
-            - run: git diff --exit-code
 
     js_lint:
         name: "ESLint"
@@ -88,7 +39,6 @@ jobs:
             - uses: actions/setup-node@v4
               with:
                   cache: "yarn"
-                  node-version: "lts/*"
 
             # Does not need branch matching as only analyses this layer
             - name: Install Deps
@@ -106,33 +56,14 @@ jobs:
             - uses: actions/setup-node@v4
               with:
                   cache: "yarn"
-                  node-version: "lts/*"
 
-            # Does not need branch matching as only analyses this layer
-            - name: Install Deps
-              run: "yarn install"
+            # Needs branch matching as it inherits .stylelintrc.js from matrix-react-sdk
+            - name: Install Dependencies
+              run: "./scripts/layered.sh"
 
             - name: Run Linter
               run: "yarn run lint:style"
 
-    workflow_lint:
-        name: "Workflow Lint"
-        runs-on: ubuntu-latest
-        steps:
-            - uses: actions/checkout@v4
-
-            - uses: actions/setup-node@v4
-              with:
-                  cache: "yarn"
-                  node-version: "lts/*"
-
-            # Does not need branch matching as only analyses this layer
-            - name: Install Deps
-              run: "yarn install --frozen-lockfile"
-
-            - name: Run Linter
-              run: "yarn lint:workflows"
-
     analyse_dead_code:
         name: "Analyse Dead Code"
         runs-on: ubuntu-latest
@@ -142,7 +73,6 @@ jobs:
             - uses: actions/setup-node@v4
               with:
                   cache: "yarn"
-                  node-version: "lts/*"
 
             - name: Install Deps
               run: "scripts/layered.sh"

.github/workflows/sync-labels.yml

@@ -1,21 +0,0 @@
-name: Sync labels
-on:
-    workflow_dispatch: {}
-    schedule:
-        - cron: "0 1 * * *" # 1am every day
-    push:
-        branches:
-            - develop
-        paths:
-            - .github/labels.yml
-jobs:
-    sync-labels:
-        uses: element-hq/element-meta/.github/workflows/sync-labels.yml@develop
-        with:
-            LABELS: |
-                element-hq/element-meta
-                .github/labels.yml
-            DELETE: true
-            WET: true
-        secrets:
-            ELEMENT_BOT_TOKEN: ${{ secrets.ELEMENT_BOT_TOKEN }}

.github/workflows/tests.yaml

@@ -0,0 +1,41 @@
+name: Tests
+on:
+    pull_request: {}
+    push:
+        branches: [develop, master]
+    repository_dispatch:
+        types: [element-web-notify]
+env:
+    # These must be set for fetchdep.sh to get the right branch
+    REPOSITORY: ${{ github.repository }}
+    PR_NUMBER: ${{ github.event.pull_request.number }}
+jobs:
+    jest:
+        name: Jest
+        runs-on: ubuntu-latest
+        steps:
+            - name: Checkout code
+              uses: actions/checkout@v4
+
+            - name: Yarn cache
+              uses: actions/setup-node@v4
+              with:
+                  cache: "yarn"
+
+            - name: Install Dependencies
+              run: "./scripts/layered.sh"
+
+            - name: Get number of CPU cores
+              id: cpu-cores
+              uses: SimenB/github-actions-cpu-cores@97ba232459a8e02ff6121db9362b09661c875ab8 # v2
+
+            - name: Run tests with coverage
+              run: "yarn coverage --ci --max-workers ${{ steps.cpu-cores.outputs.count }}"
+
+            - name: Upload Artifact
+              uses: actions/upload-artifact@v3
+              with:
+                  name: coverage
+                  path: |
+                      coverage
+                      !coverage/lcov-report

.github/workflows/tests.yml

@@ -1,110 +0,0 @@
-name: Tests
-on:
-    pull_request: {}
-    merge_group:
-        types: [checks_requested]
-    push:
-        branches: [develop, master]
-    repository_dispatch:
-        types: [element-web-notify]
-    workflow_call:
-        inputs:
-            disable_coverage:
-                type: boolean
-                required: false
-                description: "Specify true to skip generating and uploading coverage for tests"
-            matrix-js-sdk-sha:
-                type: string
-                required: false
-                description: "The matrix-js-sdk SHA to use"
-concurrency:
-    group: ${{ github.workflow }}-${{ github.ref }}-${{ github.event_name }}
-    cancel-in-progress: true
-
-env:
-    ENABLE_COVERAGE: ${{ github.event_name != 'merge_group' && inputs.disable_coverage != 'true' }}
-    # fetchdep.sh needs to know our PR number
-    PR_NUMBER: ${{ github.event.pull_request.number }}
-
-jobs:
-    jest:
-        name: Jest
-        runs-on: ubuntu-22.04
-        strategy:
-            fail-fast: false
-            matrix:
-                # Run multiple instances in parallel to speed up the tests
-                runner: [1, 2]
-        steps:
-            - name: Checkout code
-              uses: actions/checkout@v4
-              with:
-                  repository: ${{ inputs.matrix-js-sdk-sha && 'element-hq/element-web' || github.repository }}
-
-            - name: Yarn cache
-              uses: actions/setup-node@v4
-              with:
-                  node-version: "lts/*"
-                  cache: "yarn"
-
-            - name: Install Deps
-              run: "./scripts/layered.sh"
-              env:
-                  JS_SDK_GITHUB_BASE_REF: ${{ inputs.matrix-js-sdk-sha }}
-
-            - name: Jest Cache
-              uses: actions/cache@v4
-              with:
-                  path: /tmp/jest_cache
-                  key: ${{ hashFiles('**/yarn.lock') }}
-
-            - name: Get number of CPU cores
-              id: cpu-cores
-              uses: SimenB/github-actions-cpu-cores@97ba232459a8e02ff6121db9362b09661c875ab8 # v2
-
-            - name: Run tests
-              run: |
-                  yarn test \
-                      --coverage=${{ env.ENABLE_COVERAGE }} \
-                      --ci \
-                      --max-workers ${{ steps.cpu-cores.outputs.count }} \
-                      --shard ${{ matrix.runner }}/${{ strategy.job-total }} \
-                      --cacheDirectory /tmp/jest_cache
-              env:
-                  JEST_SONAR_UNIQUE_OUTPUT_NAME: true
-
-                  # tell jest to use coloured output
-                  FORCE_COLOR: true
-
-            - name: Move coverage files into place
-              if: env.ENABLE_COVERAGE == 'true'
-              run: mv coverage/lcov.info coverage/${{ steps.setupNode.outputs.node-version }}-${{ matrix.runner }}.lcov.info
-
-            - name: Upload Artifact
-              if: env.ENABLE_COVERAGE == 'true'
-              uses: actions/upload-artifact@v4
-              with:
-                  name: coverage-${{ matrix.runner }}
-                  path: |
-                      coverage
-                      !coverage/lcov-report
-
-    complete:
-        name: jest-tests
-        needs: jest
-        if: always()
-        runs-on: ubuntu-22.04
-        steps:
-            - if: needs.jest.result != 'skipped' && needs.jest.result != 'success'
-              run: exit 1
-
-            - name: Skip SonarCloud in merge queue
-              if: github.event_name == 'merge_group' || inputs.disable_coverage == 'true'
-              uses: Sibz/github-status-action@faaa4d96fecf273bd762985e0e7f9f933c774918 # v1
-              with:
-                  authToken: ${{ secrets.GITHUB_TOKEN }}
-                  state: success
-                  description: SonarCloud skipped
-                  context: SonarCloud Code Analysis
-                  sha: ${{ github.sha }}
-                  target_url: https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}

.github/workflows/triage-assigned.yml

@@ -14,5 +14,5 @@ jobs:
         steps:
             - uses: actions/add-to-project@main
               with:
-                  project-url: https://github.com/orgs/element-hq/projects/67
+                  project-url: https://github.com/orgs/vector-im/projects/67
                   github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}

.github/workflows/triage-incoming.yml

@@ -8,7 +8,8 @@ jobs:
     automate-project-columns:
         runs-on: ubuntu-latest
         steps:
-            - uses: actions/add-to-project@main
+            - uses: alex-page/github-project-automation-plus@7ffb872c64bd809d23563a130a0a97d01dfa8f43
               with:
-                  project-url: https://github.com/orgs/element-hq/projects/120
-                  github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
+                  project: Issue triage
+                  column: Incoming
+                  repo-token: ${{ secrets.ELEMENT_BOT_TOKEN }}

.github/workflows/triage-labelled.yml

@@ -14,6 +14,7 @@ jobs:
         runs-on: ubuntu-latest
         if: >
             contains(github.event.issue.labels.*.name, 'A-Maths') ||
+            contains(github.event.issue.labels.*.name, 'A-Message-Pinning') ||
             contains(github.event.issue.labels.*.name, 'A-Location-Sharing') ||
             contains(github.event.issue.labels.*.name, 'Z-IA') ||
             contains(github.event.issue.labels.*.name, 'A-Jump-To-Date ') ||
@@ -23,9 +24,10 @@ jobs:
             contains(github.event.issue.labels.*.name, 'A-Video-Rooms') ||
             contains(github.event.issue.labels.*.name, 'A-Message-Starring') ||
             contains(github.event.issue.labels.*.name, 'A-Rich-Text-Editor') ||
-            contains(github.event.issue.labels.*.name, 'A-Element-Call')
+            contains(github.event.issue.labels.*.name, 'A-Element-Call') ||
+            contains(github.event.issue.labels.*.name, 'A-Element-R')
         steps:
-            - uses: actions/github-script@v7
+            - uses: actions/github-script@v6
               with:
                   script: |
                       github.rest.issues.addLabels({
@@ -42,7 +44,7 @@ jobs:
             contains(github.event.issue.labels.*.name, 'good first issue') ||
             contains(github.event.issue.labels.*.name, 'Hacktoberfest')
         steps:
-            - uses: actions/github-script@v7
+            - uses: actions/github-script@v6
               with:
                   script: |
                       github.rest.issues.addLabels({
@@ -55,48 +57,13 @@ jobs:
     move_needs_info_issues:
         name: X-Needs-Info issues to Need info column on triage board
         runs-on: ubuntu-latest
-        if: >
-            contains(github.event.issue.labels.*.name, 'X-Needs-Info')
         steps:
-            - id: add_to_project
-              uses: actions/add-to-project@v1.0.2
+            - uses: konradpabjan/move-labeled-or-milestoned-issue@190352295fe309fcb113b49193bc81d9aaa9cb01
               with:
-                  project-url: ${{ env.PROJECT_URL }}
-                  github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
-
-            - id: set_fields
-              uses: titoportas/update-project-fields@421a54430b3cdc9eefd8f14f9ce0142ab7678751 # v0.1.0
-              with:
-                  project-url: ${{ env.PROJECT_URL }}
-                  github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
-                  item-id: ${{ steps.add_to_project.outputs.itemId }} # Use the item-id output of the previous step
-                  field-keys: Status
-                  field-values: "Needs info"
-        env:
-            PROJECT_URL: https://github.com/orgs/element-hq/projects/120
-
-    move_flakey_test_issues:
-        name: Z-Flaky-Test issues to Sized for maintainer column on triage board
-        runs-on: ubuntu-latest
-        if: >
-            contains(github.event.issue.labels.*.name, 'Z-Flaky-Test')
-        steps:
-            - id: add_to_project
-              uses: actions/add-to-project@v1.0.2
-              with:
-                  project-url: ${{ env.PROJECT_URL }}
-                  github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
-
-            - id: set_fields
-              uses: titoportas/update-project-fields@421a54430b3cdc9eefd8f14f9ce0142ab7678751 # v0.1.0
-              with:
-                  project-url: ${{ env.PROJECT_URL }}
-                  github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
-                  item-id: ${{ steps.add_to_project.outputs.itemId }} # Use the item-id output of the previous step
-                  field-keys: Status
-                  field-values: "Sized for maintainer"
-        env:
-            PROJECT_URL: https://github.com/orgs/element-hq/projects/120
+                  action-token: "${{ secrets.ELEMENT_BOT_TOKEN }}"
+                  project-url: "https://github.com/vector-im/element-web/projects/27"
+                  column-name: "Need info"
+                  label-name: "X-Needs-Info"
 
     add_priority_design_issues_to_project:
         name: P1 X-Needs-Design to Design project board
@@ -112,7 +79,7 @@ jobs:
         steps:
             - uses: actions/add-to-project@main
               with:
-                  project-url: https://github.com/orgs/element-hq/projects/18
+                  project-url: https://github.com/orgs/vector-im/projects/18
                   github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
 
     add_product_issues:
@@ -123,7 +90,7 @@ jobs:
         steps:
             - uses: actions/add-to-project@main
               with:
-                  project-url: https://github.com/orgs/element-hq/projects/28
+                  project-url: https://github.com/orgs/vector-im/projects/28
                   github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
 
     Search_issues_to_board:
@@ -134,7 +101,7 @@ jobs:
         steps:
             - uses: actions/add-to-project@main
               with:
-                  project-url: https://github.com/orgs/element-hq/projects/48
+                  project-url: https://github.com/orgs/vector-im/projects/48
                   github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
 
     voip:
@@ -145,7 +112,7 @@ jobs:
         steps:
             - uses: actions/add-to-project@main
               with:
-                  project-url: https://github.com/orgs/element-hq/projects/41
+                  project-url: https://github.com/orgs/vector-im/projects/41
                   github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
 
     verticals_feature:
@@ -156,7 +123,7 @@ jobs:
         steps:
             - uses: actions/add-to-project@main
               with:
-                  project-url: https://github.com/orgs/element-hq/projects/57
+                  project-url: https://github.com/orgs/vector-im/projects/57
                   github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
 
     tech_debt:
@@ -172,5 +139,28 @@ jobs:
         steps:
             - uses: actions/add-to-project@main
               with:
-                  project-url: https://github.com/orgs/element-hq/projects/101
+                  project-url: https://github.com/orgs/vector-im/projects/101
                   github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
+
+    element_r:
+        name: Add Element R issues to Crypto Team board
+        runs-on: ubuntu-latest
+        if: >
+            contains(github.event.issue.labels.*.name, 'A-Element-R')
+        steps:
+            - id: add_to_project
+              uses: actions/add-to-project@v0.5.0
+              with:
+                  project-url: ${{ env.PROJECT_URL }}
+                  github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
+
+            - id: set_fields
+              uses: titoportas/update-project-fields@421a54430b3cdc9eefd8f14f9ce0142ab7678751 # v0.1.0
+              with:
+                  project-url: ${{ env.PROJECT_URL }}
+                  github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
+                  item-id: ${{ steps.add_to_project.outputs.itemId }} # Use the item-id output of the previous step
+                  field-keys: Workstream,module
+                  field-values: Element-R,web
+        env:
+            PROJECT_URL: https://github.com/orgs/vector-im/projects/76

.github/workflows/triage-move-review-requests.yml

@@ -14,7 +14,7 @@ jobs:
                   headers: '{"GraphQL-Features": "projects_next_graphql"}'
                   query: |
                       query find_team_members($team: String!) {
-                        organization(login: "element-hq") {
+                        organization(login: "vector-im") {
                           team(slug: $team) {
                             members {
                               nodes {
@@ -81,7 +81,7 @@ jobs:
                   headers: '{"GraphQL-Features": "projects_next_graphql"}'
                   query: |
                       query find_team_members($team: String!) {
-                        organization(login: "element-hq") {
+                        organization(login: "vector-im") {
                           team(slug: $team) {
                             members {
                               nodes {

.github/workflows/triage-stale-flaky-tests.yml

@@ -1,18 +0,0 @@
-name: Close stale flaky issues
-on:
-    schedule:
-        - cron: "30 1 * * *"
-jobs:
-    close:
-        runs-on: ubuntu-latest
-        permissions:
-            actions: write
-            issues: write
-        steps:
-            - uses: actions/stale@v9
-              with:
-                  only-labels: "Z-Flaky-Test"
-                  days-before-stale: 14
-                  days-before-close: 0
-                  close-issue-message: "This flaky test issue has not been updated in 14 days. It is being closed as presumed resolved."
-                  exempt-issue-labels: "Z-Flaky-Test-Disabled"

.github/workflows/triage-unlabelled.yml

@@ -35,7 +35,7 @@ jobs:
                     fi
                   fi
             - name: Move issue
-              uses: alex-page/github-project-automation-plus@303f24a24c67ce7adf565a07e96720faf126fe36
+              uses: alex-page/github-project-automation-plus@7ffb872c64bd809d23563a130a0a97d01dfa8f43
               if: ${{ env.ALREADY_IN_BOARD == 'true' && env.SKIP_ACTION != 'true' }}
               with:
                   project: Issue triage
@@ -60,7 +60,7 @@ jobs:
             contains(github.event.issue.labels.*.name, 'A-Element-Call')) &&
             contains(github.event.issue.labels.*.name, 'Z-Labs')
         steps:
-            - uses: actions/github-script@v7
+            - uses: actions/github-script@v6
               with:
                   script: |
                       github.rest.issues.removeLabel({

.github/workflows/update-jitsi.yml

@@ -1,32 +0,0 @@
-# Re-fetches the Jitsi SDK and opens a PR to update it if it's different from what's in the repository
-name: Update Jitsi
-on:
-    workflow_dispatch: {}
-    schedule:
-        - cron: "0 3 * * 0" # 3am every Sunday
-jobs:
-    update:
-        runs-on: ubuntu-latest
-        steps:
-            - uses: actions/checkout@v4
-
-            - uses: actions/setup-node@v4
-              with:
-                  cache: "yarn"
-                  node-version: "lts/*"
-
-            - name: Install Deps
-              run: "yarn install --frozen-lockfile"
-
-            - name: Fetch Jitsi
-              run: "yarn update:jitsi"
-
-            - name: Create Pull Request
-              uses: peter-evans/create-pull-request@5e914681df9dc83aa4e4905692ca88beb2f9e91f # v7
-              with:
-                  token: ${{ secrets.ELEMENT_BOT_TOKEN }}
-                  branch: actions/jitsi-update
-                  delete-branch: true
-                  title: Jitsi Update
-                  labels: |
-                      T-Task

.github/workflows/update-topics.yaml

@@ -21,7 +21,7 @@ jobs:
         runs-on: ubuntu-latest
         environment: Matrix
         steps:
-            - uses: actions/github-script@v7
+            - uses: actions/github-script@v6
               env:
                   HS_URL: ${{ secrets.BETABOT_HS_URL }}
                   LOBBY_ROOM_ID: ${{ secrets.ROOM_ID }}

.gitignore

@@ -29,5 +29,3 @@ electron/pub
 /build_config.yaml
 /book
 /index.html
-# version file and tarball created by `npm pack` / `yarn pack`
-/git-revision.txt

.husky/pre-commit

@@ -1,4 +0,0 @@
-#!/usr/bin/env sh
-. "$(dirname "$0")/_/husky.sh"
-
-npx lint-staged --concurrent false

.lintstagedrc

@@ -1,7 +0,0 @@
-{
-    "*": "prettier --write",
-    "src/**/*.(ts|tsx)": ["eslint --fix"],
-    "scripts/**/*.(ts|tsx)": ["eslint --fix"],
-    "module_system/**/*.(ts|tsx)": ["eslint --fix --config .eslintrc-module_system.js module_system"],
-    "*.pcss": ["stylelint --fix"]
-}

.modernizr.json

@@ -1,5 +1,5 @@
 {
-    "minify": false,
+    "minify": true,
     "enableClasses": false,
     "feature-detects": [
         "test/css/animations",
@@ -31,7 +31,6 @@
         "test/json",
         "test/network/fetch",
         "test/storage/localstorage",
-        "test/window/resizeobserver",
-        "test/audio/webaudio"
+        "test/window/resizeobserver"
     ]
 }

.node-version

@@ -1 +0,0 @@
-20

.prettierignore

@@ -23,19 +23,6 @@ electron/pub
 src/vector/index.html
 src/vector/modernizr.js
 /docs/lib
-/book
-/debian/tmp
-/.npmrc
-package-lock.json
 
 # This file is owned, parsed, and generated by allchange, which doesn't comply with prettier
 /CHANGELOG.md
-/docs/changelogs
-
-# Legacy skinning file that some people might still have
-/src/component-index.js
-
-# Downloaded and already minified
-res/jitsi_external_api.min.js
-# This file is also machine-generated
-/playwright/e2e/crypto/test_indexeddb_cryptostore_dump/dump.json

.prettierrc.cjs

@@ -1 +0,0 @@
-module.exports = require("eslint-plugin-matrix-org/.prettierrc.js");

.stylelintrc.js

@@ -1,50 +1,4 @@
 module.exports = {
+    ...require("matrix-react-sdk/.stylelintrc.js"),
     extends: ["stylelint-config-standard"],
-    customSyntax: require("postcss-scss"),
-    plugins: ["stylelint-scss"],
-    rules: {
-        "comment-empty-line-before": null,
-        "declaration-empty-line-before": null,
-        "length-zero-no-unit": null,
-        "rule-empty-line-before": null,
-        "color-hex-length": null,
-        "at-rule-no-unknown": null,
-        "no-descending-specificity": null,
-        "scss/at-rule-no-unknown": [
-            true,
-            {
-                // https://github.com/vector-im/element-web/issues/10544
-                ignoreAtRules: ["define-mixin"],
-            },
-        ],
-        // Disable `&_kind`-style selectors while our unused CSS approach is "Find & Replace All"
-        // rather than a CI thing. Shorthand selectors are harder to detect when searching for a
-        // class name. This regex is trying to *allow* anything except `&words`, such as `&::before`,
-        // `&.mx_Class`, etc.
-        "selector-nested-pattern": "^((&[ :.\\[,])|([^&]))",
-        // Disable some defaults
-        "selector-class-pattern": null,
-        "custom-property-pattern": null,
-        "selector-id-pattern": null,
-        "keyframes-name-pattern": null,
-        "alpha-value-notation": null,
-        "color-function-notation": null,
-        "selector-not-notation": null,
-        "import-notation": null,
-        "value-keyword-case": null,
-        "declaration-block-no-redundant-longhand-properties": null,
-        "declaration-block-no-duplicate-properties": [
-            true,
-            // useful for fallbacks
-            { ignore: ["consecutive-duplicates-with-different-values"] },
-        ],
-        "shorthand-property-no-redundant-values": null,
-        "property-no-vendor-prefix": null,
-        "value-no-vendor-prefix": null,
-        "selector-no-vendor-prefix": null,
-        "media-feature-name-no-vendor-prefix": null,
-        "number-max-precision": null,
-        "no-invalid-double-slash-comments": true,
-        "media-feature-range-notation": null,
-    },
 };

CONTRIBUTING.md

@@ -1,6 +1,12 @@
 # Contributing code to Element Web
 
-Everyone is welcome to contribute code to Element Web, provided that they are willing to license their contributions to Element under a [Contributor License Agreement](https://cla-assistant.io/element-hq/element-web) (CLA). This ensures that their contribution will be made available under an OSI-approved open-source license, currently licensed under Affero General Public License v3 (AGPLv3) or General Public License v3 (GPLv3) at your choice.
+Everyone is welcome to contribute code to Element Web, provided that they are
+willing to license their contributions under the same license as the project
+itself. We follow a simple 'inbound=outbound' model for contributions: the act
+of submitting an 'inbound' contribution means that the contributor agrees to
+license the code under the same terms as the project's overall 'outbound'
+license - in this case, Apache Software License v2 (see
+[LICENSE](LICENSE)).
 
 ## How to contribute
 
@@ -79,6 +85,7 @@ element-web notes: Fix a bug where the 'Herd' button only worked on Tuesdays
 
 This example is for Element Web. You can specify:
 
+-   matrix-react-sdk
 -   element-web
 -   element-desktop
 
@@ -112,12 +119,14 @@ checks, so please check back after a few minutes.
 
 Your PR should include tests.
 
-For new user facing features in `matrix-js-sdk` or `element-web`, you must include:
+For new user facing features in `matrix-js-sdk`, `matrix-react-sdk` or `element-web`, you
+must include:
 
 1. Comprehensive unit tests written in Jest. These are located in `/test`.
 2. "happy path" end-to-end tests.
-   These are located in `/playwright/e2e`, and are run using `element-web`.
-   Ideally, you would also include tests for edge and error cases.
+   These are located in `/cypress/e2e` in `matrix-react-sdk`, and
+   are run using `element-web`. Ideally, you would also include tests for edge
+   and error cases.
 
 Unit tests are expected even when the feature is in labs. It's good practice
 to write tests alongside the code as it ensures the code is testable from
@@ -131,7 +140,8 @@ end-to-end test; which is best depends on what sort of test most concisely
 exercises the area.
 
 Changes to must be accompanied by unit tests written in Jest.
-These are located in `/spec/` in `matrix-js-sdk` or `/test/` in `element-web`.
+These are located in `/spec/` in `matrix-js-sdk` or `/test/` in `element-web`
+and `matrix-react-sdk`.
 
 When writing unit tests, please aim for a high level of test coverage
 for new code - 80% or greater. If you cannot achieve that, please document
@@ -261,20 +271,9 @@ on Git 2.17+ you can mass signoff using rebase:
 git rebase --signoff origin/develop
 ```
 
-## Private sign off
-
-If you would like to provide your legal name privately to the Matrix.org
-Foundation (instead of in a public commit or comment), you can do so by emailing
-your legal name and a link to the pull request to dco@matrix.org. It helps to
-include "sign off" or similar in the subject line. You will then be instructed
-further.
-
-Once private sign off is complete, doing so for future contributions will not
-be required.
-
 # Review expectations
 
-See https://github.com/element-hq/element-meta/wiki/Review-process
+See https://github.com/vector-im/element-meta/wiki/Review-process
 
 # Merge Strategy
 

Dockerfile

@@ -1,8 +1,11 @@
 # Builder
 FROM --platform=$BUILDPLATFORM node:20-bullseye as builder
 
-# Support custom branch of the js-sdk. This also helps us build images of element-web develop.
+# Support custom branches of the react-sdk and js-sdk. This also helps us build
+# images of element-web develop.
 ARG USE_CUSTOM_SDKS=false
+ARG REACT_SDK_REPO="https://github.com/matrix-org/matrix-react-sdk.git"
+ARG REACT_SDK_BRANCH="master"
 ARG JS_SDK_REPO="https://github.com/matrix-org/matrix-js-sdk.git"
 ARG JS_SDK_BRANCH="master"
 
@@ -14,7 +17,7 @@ COPY . /src
 RUN dos2unix /src/scripts/docker-link-repos.sh && bash /src/scripts/docker-link-repos.sh
 RUN yarn --network-timeout=200000 install
 
-RUN dos2unix /src/scripts/docker-package.sh /src/scripts/get-version-from-git.sh /src/scripts/normalize-version.sh && bash /src/scripts/docker-package.sh
+RUN dos2unix /src/scripts/docker-package.sh && bash /src/scripts/docker-package.sh
 
 # Copy the config now so that we don't create another layer in the app image
 RUN cp /src/config.sample.json /src/webapp/config.json

LICENSE

@@ -1,8 +1,8 @@
+
                                  Apache License
                            Version 2.0, January 2004
                         http://www.apache.org/licenses/
 
-
    TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
 
    1. Definitions.
@@ -175,45 +175,3 @@
       of your accepting any such warranty or additional liability.
 
    END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.
-   
-   
-
-Note:
-
-This project was originally contributed to the community under the MIT license and with the following notice:
-
-The MIT License (MIT)
-
-Copyright (c) 2013 ESTOS GmbH 
-Copyright (c) 2013 BlueJimp SARL
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

LICENSE-AGPL-3.0

@@ -1,661 +0,0 @@
-                    GNU AFFERO GENERAL PUBLIC LICENSE
-                       Version 3, 19 November 2007
-
-Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-
-                            Preamble
-
-The GNU Affero General Public License is a free, copyleft license for
-software and other kinds of works, specifically designed to ensure
-cooperation with the community in the case of network server software.
-
-The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works. By contrast,
-our General Public Licenses are intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.
-
-When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-Developers that use our General Public Licenses protect your rights
-with two steps: (1) assert copyright on the software, and (2) offer
-you this License which gives you legal permission to copy, distribute
-and/or modify the software.
-
-A secondary benefit of defending all users' freedom is that
-improvements made in alternate versions of the program, if they
-receive widespread use, become available for other developers to
-incorporate. Many developers of free software are heartened and
-encouraged by the resulting cooperation. However, in the case of
-software used on network servers, this result may fail to come about.
-The GNU General Public License permits making a modified version and
-letting the public access it on a server without ever releasing its
-source code to the public.
-
-The GNU Affero General Public License is designed specifically to
-ensure that, in such cases, the modified source code becomes available
-to the community. It requires the operator of a network server to
-provide the source code of the modified version running there to the
-users of that server. Therefore, public use of a modified version, on
-a publicly accessible server, gives the public access to the source
-code of the modified version.
-
-An older license, called the Affero General Public License and
-published by Affero, was designed to accomplish similar goals. This is
-a different license, not a version of the Affero GPL, but Affero has
-released a new version of the Affero GPL which permits relicensing under
-this license.
-
-The precise terms and conditions for copying, distribution and
-modification follow.
-
-                       TERMS AND CONDITIONS
-
-0. Definitions.
-
-"This License" refers to version 3 of the GNU Affero General Public License.
-
-"Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-"The Program" refers to any copyrightable work licensed under this
-License. Each licensee is addressed as "you". "Licensees" and
-"recipients" may be individuals or organizations.
-
-To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy. The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
-
-A "covered work" means either the unmodified Program or a work based
-on the Program.
-
-To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy. Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies. Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-
-An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License. If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-1. Source Code.
-
-The "source code" for a work means the preferred form of the work
-for making modifications to it. "Object code" means any non-source
-form of a work.
-
-A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form. A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities. However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work. For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
-
-The Corresponding Source for a work in source code form is that
-same work.
-
-2. Basic Permissions.
-
-All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met. This License explicitly affirms your unlimited
-permission to run the unmodified Program. The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work. This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force. You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright. Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
-Conveying under any other circumstances is permitted solely under
-the conditions stated below. Sublicensing is not allowed; section 10
-makes it unnecessary.
-
-3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
-4. Conveying Verbatim Copies.
-
-You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-5. Conveying Modified Source Versions.
-
-You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
-    a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
-
-    b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under section
-    7.  This requirement modifies the requirement in section 4 to
-    "keep intact all notices".
-
-    c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy.  This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged.  This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
-
-    d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-
-A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit. Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-6. Conveying Non-Source Forms.
-
-You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
-    a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
-
-    b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the
-    Corresponding Source from a network server at no charge.
-
-    c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source.  This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
-
-    d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge.  You need not require recipients to copy the
-    Corresponding Source along with the object code.  If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source.  Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
-
-    e) Convey the object code using peer-to-peer transmission, provided
-    you inform other peers where the object code and Corresponding
-    Source of the work are being offered to the general public at no
-    charge under subsection 6d.
-
-A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling. In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage. For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product. A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-"Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source. The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
-If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information. But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed. Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
-Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-7. Additional Terms.
-
-"Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law. If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it. (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.) You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
-    a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
-
-    b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
-
-    c) Prohibiting misrepresentation of the origin of that material, or
-    requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
-
-    d) Limiting the use for publicity purposes of names of licensors or
-    authors of the material; or
-
-    e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
-
-    f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions of
-    it) with contractual assumptions of liability to the recipient, for
-    any liability that these contractual assumptions directly impose on
-    those licensors and authors.
-
-All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10. If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term. If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
-8. Termination.
-
-You may not propagate or modify a covered work except as expressly
-provided under this License. Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License. If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-9. Acceptance Not Required for Having Copies.
-
-You are not required to accept this License in order to receive or
-run a copy of the Program. Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance. However,
-nothing other than this License grants you permission to propagate or
-modify any covered work. These actions infringe copyright if you do
-not accept this License. Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-10. Automatic Licensing of Downstream Recipients.
-
-Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License. You are not responsible
-for enforcing compliance by third parties with this License.
-
-An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations. If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License. For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-11. Patents.
-
-A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based. The
-work thus licensed is called the contributor's "contributor version".
-
-A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version. For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement). To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients. "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License. You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
-Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-12. No Surrender of Others' Freedom.
-
-If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all. For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
-13. Remote Network Interaction; Use with the GNU General Public License.
-
-Notwithstanding any other provision of this License, if you modify the
-Program, your modified version must prominently offer all users
-interacting with it remotely through a computer network (if your version
-supports such interaction) an opportunity to receive the Corresponding
-Source of your version by providing access to the Corresponding Source
-from a network server at no charge, through some standard or customary
-means of facilitating copying of software. This Corresponding Source
-shall include the Corresponding Source for any work covered by version 3
-of the GNU General Public License that is incorporated pursuant to the
-following paragraph.
-
-Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU General Public License into a single
-combined work, and to convey the resulting work. The terms of this
-License will continue to apply to the part which is the covered work,
-but the work with which it is combined will remain governed by version
-3 of the GNU General Public License.
-
-14. Revised Versions of this License.
-
-The Free Software Foundation may publish revised and/or new versions of
-the GNU Affero General Public License from time to time. Such new versions
-will be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the
-Program specifies that a certain numbered version of the GNU Affero General
-Public License "or any later version" applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation. If the Program does not specify a version number of the
-GNU Affero General Public License, you may choose any version ever published
-by the Free Software Foundation.
-
-If the Program specifies that a proxy can decide which future
-versions of the GNU Affero General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-
-Later license versions may give you additional or different
-permissions. However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-15. Disclaimer of Warranty.
-
-THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
-IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-16. Limitation of Liability.
-
-IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES.
-
-17. Interpretation of Sections 15 and 16.
-
-If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
-                     END OF TERMS AND CONDITIONS
-
-            How to Apply These Terms to Your New Programs
-
-If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-state the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software: you can redistribute it and/or modify
-    it under the terms of the GNU Affero General Public License as published by
-    the Free Software Foundation, either version 3 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU Affero General Public License for more details.
-
-    You should have received a copy of the GNU Affero General Public License
-    along with this program.  If not, see <https://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If your software can interact with users remotely through a computer
-network, you should also make sure that it provides a way for users to
-get its source. For example, if your program is a web application, its
-interface could display a "Source" link that leads users to an archive
-of the code. There are many ways you could offer source, and different
-solutions will be better for different programs; see section 13 for the
-specific requirements.
-
-You should also get your employer (if you work as a programmer) or school,
-if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU AGPL, see
-<https://www.gnu.org/licenses/>.

LICENSE-GPL-3.0

@@ -1,674 +0,0 @@
-                    GNU GENERAL PUBLIC LICENSE
-                       Version 3, 29 June 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-                            Preamble
-
-  The GNU General Public License is a free, copyleft license for
-software and other kinds of works.
-
-  The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works.  By contrast,
-the GNU General Public License is intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.  We, the Free Software Foundation, use the
-GNU General Public License for most of our software; it applies also to
-any other work released this way by its authors.  You can apply it to
-your programs, too.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-  To protect your rights, we need to prevent others from denying you
-these rights or asking you to surrender the rights.  Therefore, you have
-certain responsibilities if you distribute copies of the software, or if
-you modify it: responsibilities to respect the freedom of others.
-
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must pass on to the recipients the same
-freedoms that you received.  You must make sure that they, too, receive
-or can get the source code.  And you must show them these terms so they
-know their rights.
-
-  Developers that use the GNU GPL protect your rights with two steps:
-(1) assert copyright on the software, and (2) offer you this License
-giving you legal permission to copy, distribute and/or modify it.
-
-  For the developers' and authors' protection, the GPL clearly explains
-that there is no warranty for this free software.  For both users' and
-authors' sake, the GPL requires that modified versions be marked as
-changed, so that their problems will not be attributed erroneously to
-authors of previous versions.
-
-  Some devices are designed to deny users access to install or run
-modified versions of the software inside them, although the manufacturer
-can do so.  This is fundamentally incompatible with the aim of
-protecting users' freedom to change the software.  The systematic
-pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable.  Therefore, we
-have designed this version of the GPL to prohibit the practice for those
-products.  If such problems arise substantially in other domains, we
-stand ready to extend this provision to those domains in future versions
-of the GPL, as needed to protect the freedom of users.
-
-  Finally, every program is threatened constantly by software patents.
-States should not allow patents to restrict development and use of
-software on general-purpose computers, but in those that do, we wish to
-avoid the special danger that patents applied to a free program could
-make it effectively proprietary.  To prevent this, the GPL assures that
-patents cannot be used to render the program non-free.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-                       TERMS AND CONDITIONS
-
-  0. Definitions.
-
-  "This License" refers to version 3 of the GNU General Public License.
-
-  "Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-  "The Program" refers to any copyrightable work licensed under this
-License.  Each licensee is addressed as "you".  "Licensees" and
-"recipients" may be individuals or organizations.
-
-  To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy.  The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
-
-  A "covered work" means either the unmodified Program or a work based
-on the Program.
-
-  To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy.  Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-  To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies.  Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-
-  An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License.  If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-  1. Source Code.
-
-  The "source code" for a work means the preferred form of the work
-for making modifications to it.  "Object code" means any non-source
-form of a work.
-
-  A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-  The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form.  A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-  The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities.  However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work.  For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-  The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
-
-  The Corresponding Source for a work in source code form is that
-same work.
-
-  2. Basic Permissions.
-
-  All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met.  This License explicitly affirms your unlimited
-permission to run the unmodified Program.  The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work.  This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-  You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force.  You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright.  Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
-  Conveying under any other circumstances is permitted solely under
-the conditions stated below.  Sublicensing is not allowed; section 10
-makes it unnecessary.
-
-  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-  No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-  When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
-  4. Conveying Verbatim Copies.
-
-  You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-  You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-  5. Conveying Modified Source Versions.
-
-  You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
-    a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
-
-    b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under section
-    7.  This requirement modifies the requirement in section 4 to
-    "keep intact all notices".
-
-    c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy.  This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged.  This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
-
-    d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-
-  A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit.  Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-  6. Conveying Non-Source Forms.
-
-  You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
-    a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
-
-    b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the
-    Corresponding Source from a network server at no charge.
-
-    c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source.  This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
-
-    d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge.  You need not require recipients to copy the
-    Corresponding Source along with the object code.  If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source.  Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
-
-    e) Convey the object code using peer-to-peer transmission, provided
-    you inform other peers where the object code and Corresponding
-    Source of the work are being offered to the general public at no
-    charge under subsection 6d.
-
-  A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-  A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling.  In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage.  For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product.  A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-  "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source.  The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
-  If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information.  But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-  The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed.  Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
-  Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-  7. Additional Terms.
-
-  "Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law.  If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-  When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it.  (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.)  You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-  Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
-    a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
-
-    b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
-
-    c) Prohibiting misrepresentation of the origin of that material, or
-    requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
-
-    d) Limiting the use for publicity purposes of names of licensors or
-    authors of the material; or
-
-    e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
-
-    f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions of
-    it) with contractual assumptions of liability to the recipient, for
-    any liability that these contractual assumptions directly impose on
-    those licensors and authors.
-
-  All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10.  If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term.  If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-  If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-  Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
-  8. Termination.
-
-  You may not propagate or modify a covered work except as expressly
-provided under this License.  Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-  However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-  Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-  Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License.  If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-  9. Acceptance Not Required for Having Copies.
-
-  You are not required to accept this License in order to receive or
-run a copy of the Program.  Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance.  However,
-nothing other than this License grants you permission to propagate or
-modify any covered work.  These actions infringe copyright if you do
-not accept this License.  Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-  10. Automatic Licensing of Downstream Recipients.
-
-  Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License.  You are not responsible
-for enforcing compliance by third parties with this License.
-
-  An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations.  If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-  You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License.  For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-  11. Patents.
-
-  A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based.  The
-work thus licensed is called the contributor's "contributor version".
-
-  A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version.  For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-  Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-  In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement).  To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-  If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients.  "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-  If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-  A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License.  You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
-  Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-  12. No Surrender of Others' Freedom.
-
-  If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all.  For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
-  13. Use with the GNU Affero General Public License.
-
-  Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU Affero General Public License into a single
-combined work, and to convey the resulting work.  The terms of this
-License will continue to apply to the part which is the covered work,
-but the special requirements of the GNU Affero General Public License,
-section 13, concerning interaction through a network will apply to the
-combination as such.
-
-  14. Revised Versions of this License.
-
-  The Free Software Foundation may publish revised and/or new versions of
-the GNU General Public License from time to time.  Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-  Each version is given a distinguishing version number.  If the
-Program specifies that a certain numbered version of the GNU General
-Public License "or any later version" applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation.  If the Program does not specify a version number of the
-GNU General Public License, you may choose any version ever published
-by the Free Software Foundation.
-
-  If the Program specifies that a proxy can decide which future
-versions of the GNU General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-
-  Later license versions may give you additional or different
-permissions.  However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-  15. Disclaimer of Warranty.
-
-  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
-IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-  16. Limitation of Liability.
-
-  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES.
-
-  17. Interpretation of Sections 15 and 16.
-
-  If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
-                     END OF TERMS AND CONDITIONS
-
-            How to Apply These Terms to Your New Programs
-
-  If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-  To do so, attach the following notices to the program.  It is safest
-to attach them to the start of each source file to most effectively
-state the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software: you can redistribute it and/or modify
-    it under the terms of the GNU General Public License as published by
-    the Free Software Foundation, either version 3 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU General Public License for more details.
-
-    You should have received a copy of the GNU General Public License
-    along with this program.  If not, see <https://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper mail.
-
-  If the program does terminal interaction, make it output a short
-notice like this when it starts in an interactive mode:
-
-    <program>  Copyright (C) <year>  <name of author>
-    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
-    This is free software, and you are welcome to redistribute it
-    under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License.  Of course, your program's commands
-might be different; for a GUI interface, you would use an "about box".
-
-  You should also get your employer (if you work as a programmer) or school,
-if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU GPL, see
-<https://www.gnu.org/licenses/>.
-
-  The GNU General Public License does not permit incorporating your program
-into proprietary programs.  If your program is a subroutine library, you
-may consider it more useful to permit linking proprietary applications with
-the library.  If this is what you want to do, use the GNU Lesser General
-Public License instead of this License.  But first, please read
-<https://www.gnu.org/licenses/why-not-lgpl.html>.

README.md

@@ -1,6 +1,6 @@
 [![Chat](https://img.shields.io/matrix/element-web:matrix.org?logo=matrix)](https://matrix.to/#/#element-web:matrix.org)
-![Tests](https://github.com/element-hq/element-web/actions/workflows/tests.yaml/badge.svg)
-![Static Analysis](https://github.com/element-hq/element-web/actions/workflows/static_analysis.yaml/badge.svg)
+![Tests](https://github.com/vector-im/element-web/actions/workflows/tests.yaml/badge.svg)
+![Static Analysis](https://github.com/vector-im/element-web/actions/workflows/static_analysis.yaml/badge.svg)
 [![Localazy](https://img.shields.io/endpoint?url=https%3A%2F%2Fconnect.localazy.com%2Fstatus%2Felement-web%2Fdata%3Fcontent%3Dall%26title%3Dlocalazy%26logo%3Dtrue)](https://localazy.com/p/element-web)
 [![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=element-web&metric=alert_status)](https://sonarcloud.io/summary/new_code?id=element-web)
 [![Coverage](https://sonarcloud.io/api/project_badges/measure?project=element-web&metric=coverage)](https://sonarcloud.io/summary/new_code?id=element-web)
@@ -10,40 +10,30 @@
 # Element
 
 Element (formerly known as Vector and Riot) is a Matrix web client built using the [Matrix
-JS SDK](https://github.com/matrix-org/matrix-js-sdk).
+React SDK](https://github.com/matrix-org/matrix-react-sdk).
 
 # Supported Environments
 
 Element has several tiers of support for different environments:
 
 -   Supported
-    -   Definition:
-        -   Issues **actively triaged**, regressions **block** the release
+    -   Definition: Issues **actively triaged**, regressions **block** the release
     -   Last 2 major versions of Chrome, Firefox, and Edge on desktop OSes
     -   Last 2 versions of Safari
     -   Latest release of official Element Desktop app on desktop OSes
     -   Desktop OSes means macOS, Windows, and Linux versions for desktop devices
         that are actively supported by the OS vendor and receive security updates
--   Best effort
-    -   Definition:
-        -   Issues **accepted**, regressions **do not block** the release
-        -   The wider Element Products(including Element Call and the Enterprise Server Suite) do still not officially support these browsers.
-        -   The element web project and its contributors should keep the client functioning and gracefully degrade where other sibling features (E.g. Element Call) may not function.
-    -   Last major release of Firefox ESR and Chrome/Edge Extended Stable
--   Community Supported
-    -   Definition:
-        -   Issues **accepted**, regressions **do not block** the release
-        -   Community contributions are welcome to support these issues
+-   Experimental
+    -   Definition: Issues **accepted**, regressions **do not block** the release
+    -   Element as an installed PWA via current stable version of Chrome
     -   Mobile web for current stable version of Chrome, Firefox, and Safari on Android, iOS, and iPadOS
 -   Not supported
     -   Definition: Issues only affecting unsupported environments are **closed**
     -   Everything else
 
-The period of support for these tiers should last until the releases specified above, plus 1 app release cycle(2 weeks). In the case of Firefox ESR this is extended further to allow it land in Debian Stable.
-
 For accessing Element on an Android or iOS device, we currently recommend the
-native apps [element-android](https://github.com/element-hq/element-android)
-and [element-ios](https://github.com/element-hq/element-ios).
+native apps [element-android](https://github.com/vector-im/element-android)
+and [element-ios](https://github.com/vector-im/element-ios).
 
 # Getting Started
 
@@ -51,9 +41,29 @@ The easiest way to test Element is to just use the hosted copy at <https://app.e
 The `develop` branch is continuously deployed to <https://develop.element.io>
 for those who like living dangerously.
 
-To host your own instance of Element see [Installing Element Web](docs/install.md).
+To host your own copy of Element, the quickest bet is to use a pre-built
+released version of Element:
 
-To install Element as a desktop application, see [Running as a desktop app](#running-as-a-desktop-app) below.
+1. Download the latest version from <https://github.com/vector-im/element-web/releases>
+1. Untar the tarball on your web server
+1. Move (or symlink) the `element-x.x.x` directory to an appropriate name
+1. Configure the correct caching headers in your webserver (see below)
+1. Configure the app by copying `config.sample.json` to `config.json` and
+   modifying it. See the [configuration docs](docs/config.md) for details.
+1. Enter the URL into your browser and log into Element!
+
+Releases are signed using gpg and the OpenPGP standard, and can be checked against the public key located
+at <https://packages.riot.im/element-release-key.asc>.
+
+Note that for the security of your chats will need to serve Element
+over HTTPS. Major browsers also do not allow you to use VoIP/video
+chats over HTTP, as WebRTC is only usable over HTTPS.
+There are some exceptions like when using localhost, which is
+considered a [secure context](https://developer.mozilla.org/docs/Web/Security/Secure_Contexts)
+and thus allowed.
+
+To install Element as a desktop application, see [Running as a desktop
+app](#running-as-a-desktop-app) below.
 
 # Important Security Notes
 
@@ -67,7 +77,7 @@ access to Element (or other apps) due to sharing the same domain.
 
 We have put some coarse mitigations into place to try to protect against this
 situation, but it's still not good practice to do it in the first place. See
-<https://github.com/element-hq/element-web/issues/1977> for more details.
+<https://github.com/vector-im/element-web/issues/1977> for more details.
 
 ## Configuration best practices
 
@@ -121,7 +131,7 @@ guide](https://classic.yarnpkg.com/en/docs/install) if you do not have it alread
 
 1. Install or update `node.js` so that your `node` is at least the current recommended LTS.
 1. Install `yarn` if not present already.
-1. Clone the repo: `git clone https://github.com/element-hq/element-web.git`.
+1. Clone the repo: `git clone https://github.com/vector-im/element-web.git`.
 1. Switch to the element-web directory: `cd element-web`.
 1. Install the prerequisites: `yarn install`.
     - If you're using the `develop` branch, then it is recommended to set up a
@@ -147,11 +157,65 @@ Element can also be run as a desktop app, wrapped in Electron. You can download
 pre-built version from <https://element.io/get-started> or, if you prefer,
 build it yourself.
 
-To build it yourself, follow the instructions at <https://github.com/element-hq/element-desktop>.
+To build it yourself, follow the instructions at <https://github.com/vector-im/element-desktop>.
 
 Many thanks to @aviraldg for the initial work on the Electron integration.
 
-The [configuration docs](docs/config.md#desktop-app-configuration) show how to override the desktop app's default settings if desired.
+Other options for running as a desktop app:
+
+-   @asdf:matrix.org points out that you can use nativefier and it just works(tm)
+
+```bash
+yarn global add nativefier
+nativefier https://app.element.io/
+```
+
+The [configuration docs](docs/config.md#desktop-app-configuration) show how to
+override the desktop app's default settings if desired.
+
+# Running from Docker
+
+The Docker image can be used to serve element-web as a web server. The easiest way to use
+it is to use the prebuilt image:
+
+```bash
+docker run -p 80:80 vectorim/element-web
+```
+
+To supply your own custom `config.json`, map a volume to `/app/config.json`. For example,
+if your custom config was located at `/etc/element-web/config.json` then your Docker command
+would be:
+
+```bash
+docker run -p 80:80 -v /etc/element-web/config.json:/app/config.json vectorim/element-web
+```
+
+To build the image yourself:
+
+```bash
+git clone https://github.com/vector-im/element-web.git element-web
+cd element-web
+git checkout master
+docker build .
+```
+
+If you're building a custom branch, or want to use the develop branch, check out the appropriate
+element-web branch and then run:
+
+```bash
+docker build -t \
+    --build-arg USE_CUSTOM_SDKS=true \
+    --build-arg REACT_SDK_REPO="https://github.com/matrix-org/matrix-react-sdk.git" \
+    --build-arg REACT_SDK_BRANCH="develop" \
+    --build-arg JS_SDK_REPO="https://github.com/matrix-org/matrix-js-sdk.git" \
+    --build-arg JS_SDK_BRANCH="develop" \
+    .
+```
+
+# Running in Kubernetes
+
+The provided element-web docker image can also be run from within a Kubernetes cluster.
+See the [Kubernetes example](docs/kubernetes.md) for more details.
 
 # config.json
 
@@ -161,7 +225,7 @@ See the [configuration docs](docs/config.md) for more details.
 # Labs Features
 
 Some features of Element may be enabled by flags in the `Labs` section of the settings.
-Some of these features are described in [labs.md](https://github.com/element-hq/element-web/blob/develop/docs/labs.md).
+Some of these features are described in [labs.md](https://github.com/vector-im/element-web/blob/develop/docs/labs.md).
 
 # Caching requirements
 
@@ -206,11 +270,16 @@ internet. So please don't depend on resources (JS libs, CSS, images, fonts)
 hosted by external CDNs or servers but instead please package all dependencies
 into Element itself.
 
+CSS hot-reload is available as an opt-in development feature. You can enable it
+by defining a `CSS_HOT_RELOAD` environment variable, in a `.env` file in the root
+of the repository. See `.env.example` for documentation and an example.
+
 # Setting up a dev environment
 
-Much of the functionality in Element is actually in the `matrix-js-sdk` module.
-It is possible to set these up in a way that makes it easy to track the `develop` branches
-in git and to make local changes without having to manually rebuild each time.
+Much of the functionality in Element is actually in the `matrix-react-sdk` and
+`matrix-js-sdk` modules. It is possible to set these up in a way that makes it
+easy to track the `develop` branches in git and to make local changes without
+having to manually rebuild each time.
 
 First clone and build `matrix-js-sdk`:
 
@@ -222,10 +291,21 @@ yarn install
 popd
 ```
 
+Then similarly with `matrix-react-sdk`:
+
+```bash
+git clone https://github.com/matrix-org/matrix-react-sdk.git
+pushd matrix-react-sdk
+yarn link
+yarn link matrix-js-sdk
+yarn install
+popd
+```
+
 Clone the repo and switch to the `element-web` directory:
 
 ```bash
-git clone https://github.com/element-hq/element-web.git
+git clone https://github.com/vector-im/element-web.git
 cd element-web
 ```
 
@@ -236,6 +316,7 @@ Finally, build and start Element itself:
 
 ```bash
 yarn link matrix-js-sdk
+yarn link matrix-react-sdk
 yarn install
 yarn start
 ```
@@ -260,8 +341,8 @@ for changes. If the inotify limits are too low your build will fail silently or
 `Error: EMFILE: too many open files`. To avoid these issues, we recommend a watch limit
 of at least `128M` and instance limit around `512`.
 
-You may be interested in issues [#15750](https://github.com/element-hq/element-web/issues/15750) and
-[#15774](https://github.com/element-hq/element-web/issues/15774) for further details.
+You may be interested in issues [#15750](https://github.com/vector-im/element-web/issues/15750) and
+[#15774](https://github.com/vector-im/element-web/issues/15774) for further details.
 
 To set a new inotify watch and instance limit, execute:
 
@@ -281,7 +362,8 @@ sudo sysctl -p
 
 ---
 
-When you make changes to `matrix-js-sdk` they should be automatically picked up by webpack and built.
+When you make changes to `matrix-react-sdk` or `matrix-js-sdk` they should be
+automatically picked up by webpack and built.
 
 If any of these steps error with, `file table overflow`, you are probably on a mac
 which has a very low limit on max open files. Run `ulimit -Sn 1024` and try again.
@@ -308,6 +390,6 @@ For a developer guide, see the [translating dev doc](docs/translating-dev.md).
 
 # Triaging issues
 
-Issues are triaged by community members and the Web App Team, following the [triage process](https://github.com/element-hq/element-meta/wiki/Triage-process).
+Issues are triaged by community members and the Web App Team, following the [triage process](https://github.com/vector-im/element-meta/wiki/Triage-process).
 
-We use [issue labels](https://github.com/element-hq/element-meta/wiki/Issue-labelling) to sort all incoming issues.
+We use [issue labels](https://github.com/vector-im/element-meta/wiki/Issue-labelling) to sort all incoming issues.

__mocks__/FontManager.js

@@ -1,6 +0,0 @@
-// Stub out FontManager for tests as it doesn't validate anything we don't already know given
-// our fixed test environment and it requires the installation of node-canvas.
-
-module.exports = {
-    fixupColorFonts: () => Promise.resolve(),
-};

__mocks__/empty.js

@@ -1,2 +0,0 @@
-// Yes, this is empty.
-module.exports = {};

__mocks__/imageMock.js

@@ -1 +0,0 @@
-module.exports = "image-file-stub";

__mocks__/languages.json

@@ -1,4 +0,0 @@
-{
-    "en": "en_EN.json",
-    "en-us": "en_US.json"
-}

__mocks__/maplibre-gl.js

@@ -1,40 +0,0 @@
-/*
-Copyright 2024 New Vector Ltd.
-Copyright 2022 The Matrix.org Foundation C.I.C.
-
-SPDX-License-Identifier: AGPL-3.0-only OR GPL-3.0-only
-Please see LICENSE files in the repository root for full details.
-*/
-
-const EventEmitter = require("events");
-const { LngLat, NavigationControl, LngLatBounds } = require("maplibre-gl");
-
-class MockMap extends EventEmitter {
-    addControl = jest.fn();
-    removeControl = jest.fn();
-    zoomIn = jest.fn();
-    zoomOut = jest.fn();
-    setCenter = jest.fn();
-    setStyle = jest.fn();
-    fitBounds = jest.fn();
-}
-const MockMapInstance = new MockMap();
-
-class MockAttributionControl {}
-class MockGeolocateControl extends EventEmitter {
-    trigger = jest.fn();
-}
-const MockGeolocateInstance = new MockGeolocateControl();
-const MockMarker = {};
-MockMarker.setLngLat = jest.fn().mockReturnValue(MockMarker);
-MockMarker.addTo = jest.fn().mockReturnValue(MockMarker);
-MockMarker.remove = jest.fn().mockReturnValue(MockMarker);
-module.exports = {
-    Map: jest.fn().mockReturnValue(MockMapInstance),
-    GeolocateControl: jest.fn().mockReturnValue(MockGeolocateInstance),
-    Marker: jest.fn().mockReturnValue(MockMarker),
-    LngLat,
-    LngLatBounds,
-    NavigationControl,
-    AttributionControl: MockAttributionControl,
-};

__mocks__/svg.js

@@ -1,2 +0,0 @@
-export const Icon = "div";
-export default "image-file-stub";

__mocks__/workerFactoryMock.js

@@ -1,11 +0,0 @@
-/*
-Copyright 2024 New Vector Ltd.
-Copyright 2023 The Matrix.org Foundation C.I.C.
-
-SPDX-License-Identifier: AGPL-3.0-only OR GPL-3.0-only
-Please see LICENSE files in the repository root for full details.
-*/
-
-export default function workerFactory(options) {
-    return jest.fn;
-}

babel.config.js

@@ -10,24 +10,24 @@ module.exports = {
                     "last 2 Safari versions",
                     "last 2 Edge versions",
                 ],
-                include: ["@babel/plugin-transform-class-properties"],
             },
         ],
-        ["@babel/preset-typescript", { allowDeclareFields: true }],
+        "@babel/preset-typescript",
         "@babel/preset-react",
     ],
     plugins: [
         "@babel/plugin-proposal-export-default-from",
-        "@babel/plugin-transform-numeric-separator",
-        "@babel/plugin-transform-object-rest-spread",
-        "@babel/plugin-transform-optional-chaining",
-        "@babel/plugin-transform-nullish-coalescing-operator",
+        "@babel/plugin-proposal-numeric-separator",
+        "@babel/plugin-proposal-class-properties",
+        "@babel/plugin-proposal-object-rest-spread",
+        "@babel/plugin-proposal-optional-chaining",
+        "@babel/plugin-proposal-nullish-coalescing-operator",
 
         // transform logical assignment (??=, ||=, &&=). preset-env doesn't
         // normally bother with these (presumably because all the target
         // browsers support it natively), but they make our webpack version (or
         // something downstream of babel, at least) fall over.
-        "@babel/plugin-transform-logical-assignment-operators",
+        "@babel/plugin-proposal-logical-assignment-operators",
 
         "@babel/plugin-syntax-dynamic-import",
         "@babel/plugin-transform-runtime",

book.toml

@@ -18,10 +18,9 @@ create-missing = false
 # Remove the numbers that appear before each item in the sidebar, as they can
 # get quite messy as we nest deeper
 no-section-label = true
-additional-css = ["docs/lib/custom.css"]
 
 # The source code URL of the repository
-git-repository-url = "https://github.com/element-hq/element-web"
+git-repository-url = "https://github.com/vector-im/element-web"
 
 # The path that the docs are hosted on
 site-url = "/element-web/"

build_config.sample.yaml

@@ -21,5 +21,5 @@ modules:
     # An example of pulling a module from NPM
     - "@vector-im/element-web-ilag-module@^0.0.1"
 
-    # An example of pulling a module from local filesystem during development
-    - "file:/home/user/development/element-web-ilag-module"
+    # An example of pulling a module from github
+    - "github:vector-im/element-web-ilag-module#main"

code_style.md

@@ -5,6 +5,7 @@ adjacent to. As of writing, these are:
 
 -   element-desktop
 -   element-web
+-   matrix-react-sdk
 -   matrix-js-sdk
 
 Other projects might extend this code style for increased strictness. For example, matrix-events-sdk
@@ -224,12 +225,6 @@ Unless otherwise specified, the following applies to all code:
     }
     ```
 
-37. Avoid functions whose fundamental behaviour varies with different parameter types.
-    Multiple return types are fine, but if the function's behaviour is going to change significantly,
-    have two separate functions. For example, `SDKConfig.get()` with a string param which returns the
-    type according to the param given is ok, but `SDKConfig.get()` with no args returning the whole
-    config object would not be: this should just be a separate function.
-
 ## React
 
 Inheriting all the rules of TypeScript, the following additionally apply:

config.sample.json

@@ -12,7 +12,6 @@
     "disable_guests": false,
     "disable_login_language_selector": false,
     "disable_3pid_login": false,
-    "force_verification": false,
     "brand": "Element",
     "integrations_ui_url": "https://scalar.vector.im/",
     "integrations_rest_url": "https://scalar.vector.im/api",
@@ -23,7 +22,6 @@
         "https://scalar-staging.vector.im/api",
         "https://scalar-staging.riot.im/scalar/api"
     ],
-    "default_widget_container_height": 280,
     "default_country_code": "GB",
     "show_labs_settings": false,
     "features": {},

contribute.json

@@ -2,12 +2,12 @@
     "name": "Element",
     "description": "A glossy Matrix collaboration client for the web.",
     "repository": {
-        "url": "https://github.com/element-hq/element-web",
-        "license": "AGPL-3.0-only OR GPL-3.0-only"
+        "url": "https://github.com/vector-im/element-web",
+        "license": "Apache License 2.0"
     },
     "bugs": {
-        "list": "https://github.com/element-hq/element-web/issues",
-        "report": "https://github.com/element-hq/element-web/issues/new/choose"
+        "list": "https://github.com/vector-im/element-web/issues",
+        "report": "https://github.com/vector-im/element-web/issues/new/choose"
     },
     "keywords": ["chat", "riot", "matrix"]
 }

debian/conffiles

@@ -1 +1 @@
-/etc/element-web/config.json
+/usr/share/element-web/config.json

docs/SUMMARY.md

@@ -9,7 +9,6 @@
 
 # Setup
 
--   [Install](install.md)
 -   [Config](config.md)
 -   [Custom home page](custom-home.md)
 -   [Kubernetes](kubernetes.md)
@@ -34,22 +33,7 @@
 -   [App load order](app-load.md)
 -   [Translation](translating-dev.md)
 -   [Theming](theming.md)
--   [Playwright end to end tests](playwright.md)
 -   [Memory profiling](memory-profiles-and-leaks.md)
 -   [Jitsi](jitsi-dev.md)
 -   [Feature flags](feature-flags.md)
 -   [OIDC and delegated authentication](oidc.md)
--   [Release Process](release.md)
-
-# Deep dive
-
--   [Skinning](skinning.md)
--   [Cider editor](ciderEditor.md)
--   [Iconography](icons.md)
--   [Jitsi](jitsi.md)
--   [Local echo](local-echo-dev.md)
--   [Media](media-handling.md)
--   [Room List Store](room-list-store.md)
--   [Scrolling](scrolling.md)
--   [Usercontent](usercontent.md)
--   [Widget layouts](widget-layouts.md)

docs/betas.md

@@ -4,7 +4,7 @@ Beta features are features that are not ready for production yet but the team
 wants more people to try the features and give feedback on them.
 
 Before a feature gets into its beta phase, it is often a labs feature (see
-[Labs](https://github.com/element-hq/element-web/blob/develop/docs/labs.md)).
+[Labs](https://github.com/vector-im/element-web/blob/develop/docs/labs.md)).
 
 **Be warned! Beta features may not be completely finalised or stable!**
 

docs/choosing-an-issue.md

@@ -18,11 +18,12 @@ If you're looking for inspiration on where to start, keep reading!
 ## Finding a good first issue
 
 All the issues for Element Web live in the
-[element-web](https://github.com/element-hq/element-web) repository, including
-issues that actually need fixing in one of the related repos.
+[element-web](https://github.com/vector-im/element-web) repository, including
+issues that actually need fixing in `matrix-react-sdk` or one of the related
+repos.
 
 The first place to look is for
-[issues tagged with "good first issue"](https://github.com/element-hq/element-web/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22).
+[issues tagged with "good first issue"](https://github.com/vector-im/element-web/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22).
 
 Look through that list and find something that catches your interest. If there
 is nothing, there, try gently asking in
@@ -37,8 +38,8 @@ issue a **GOOD** choice:
 -   You think you can understand what's needed.
 -   It already has approval from Element Web's designers (look for comments from
     members of the
-    [Product](https://github.com/orgs/element-hq/teams/product/members) or
-    [Design](https://github.com/orgs/element-hq/teams/design/members) teams).
+    [Product](https://github.com/orgs/vector-im/teams/product/members) or
+    [Design](https://github.com/orgs/vector-im/teams/design/members) teams).
 
 Here are some things that might make it a **BAD** choice:
 
@@ -56,7 +57,7 @@ way the product works, or how it looks in a specific area.
 Once you've fixed a few small things, you can consider taking on something a
 little larger. This should mostly be driven by what you find interesting, but
 you may also find the
-[Help Wanted](https://github.com/element-hq/element-web/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22Help+Wanted%22)
+[Help Wanted](https://github.com/vector-im/element-web/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22Help+Wanted%22)
 label useful.
 
 Note that the same comment applies as in the previous section: if you want to

docs/ciderEditor.md

@@ -1,71 +0,0 @@
-# The CIDER (Contenteditable-Input-Diff-Error-Reconcile) editor
-
-The CIDER editor is a custom editor written for Element.
-Most of the code can be found in the `/editor/` directory.
-It is used to power the composer main composer (both to send and edit messages), and might be used for other usecases where autocomplete is desired (invite box, ...).
-
-## High-level overview.
-
-The editor is backed by a model that contains parts.
-A part has some text and a type (plain text, pill, ...). When typing in the editor,
-the model validates the input and updates the parts.
-The parts are then reconciled with the DOM.
-
-## Inner workings
-
-When typing in the `contenteditable` element, the `input` event fires and
-the DOM of the editor is turned into a string. The way this is done has
-some logic to it to deal with adding newlines for block elements, to make sure
-the caret offset is calculated in the same way as the content string, and to ignore
-caret nodes (more on that later).
-For these reasons it doesn't use `innerText`, `textContent` or anything similar.
-The model addresses any content in the editor within as an offset within this string.
-The caret position is thus also converted from a position in the DOM tree
-to an offset in the content string. This happens in `getCaretOffsetAndText` in `dom.ts`.
-
-Once the content string and caret offset is calculated, it is passed to the `update()`
-method of the model. The model first calculates the same content string of its current parts,
-basically just concatenating their text. It then looks for differences between
-the current and the new content string. The diffing algorithm is very basic,
-and assumes there is only one change around the caret offset,
-so this should be very inexpensive. See `diff.ts` for details.
-
-The result of the diffing is the strings that were added and/or removed from
-the current content. These differences are then applied to the parts,
-where parts can apply validation logic to these changes.
-
-For example, if you type an @ in some plain text, the plain text part rejects
-that character, and this character is then presented to the part creator,
-which will turn it into a pill candidate part.
-Pill candidate parts are what opens the auto completion, and upon picking a completion,
-replace themselves with an actual pill which can't be edited anymore.
-
-The diffing is needed to preserve state in the parts apart from their text
-(which is the only thing the model receives from the DOM), e.g. to build
-the model incrementally. Any text that didn't change is assumed
-to leave the parts it intersects alone.
-
-The benefit of this is that we can use the `input` event, which is broadly supported,
-to find changes in the editor. We don't have to rely on keyboard events,
-which relate poorly to text input or changes, and don't need the `beforeinput` event,
-which isn't broadly supported yet.
-
-Once the parts of the model are updated, the DOM of the editor is then reconciled
-with the new model state, see `renderModel` in `render.ts` for this.
-If the model didn't reject the input and didn't make any additional changes,
-this won't make any changes to the DOM at all, and should thus be fairly efficient.
-
-For the browser to allow the user to place the caret between two pills,
-or between a pill and the start and end of the line, we need some extra DOM nodes.
-These DOM nodes are called caret nodes, and contain an invisble character, so
-the caret can be placed into them. The model is unaware of caret nodes, and they
-are only added to the DOM during the render phase. Likewise, when calculating
-the content string, caret nodes need to be ignored, as they would confuse the model.
-
-As part of the reconciliation, the caret position is also adjusted to any changes
-the model made to the input. The caret is passed around in two formats.
-The model receives the caret _offset_ within the content string (which includes
-an atNodeEnd flag to make it unambiguous if it is at a part and or the next part start).
-The model converts this to a caret _position_ internally, which has a partIndex
-and an offset within the part text, which is more natural to work with.
-From there on, the caret _position_ is used, also during reconciliation.

docs/config.md

@@ -109,7 +109,7 @@ instance. As of writing those settings are not fully documented, however a few a
     }
     ```
     These values will take priority over the hardcoded defaults for the settings. For a list of available settings, see
-    [Settings.tsx](https://github.com/element-hq/element-web/blob/develop/src/settings/Settings.tsx).
+    [Settings.tsx](https://github.com/matrix-org/matrix-react-sdk/blob/develop/src/settings/Settings.tsx).
 
 ## Customisation & branding
 
@@ -137,7 +137,7 @@ complete re-branding/private labeling, a more personalised experience can be ach
    This setting is ignored if your homeserver provides `/.well-known/matrix/client` in its well-known location, and the JSON file
    at that location has a key `m.tile_server` (or the unstable version `org.matrix.msc3488.tile_server`). In this case, the
    configuration found in the well-known location is used instead.
-10. `welcome_user_id`: **DEPRECATED** An optional user ID to start a DM with after creating an account. Defaults to nothing (no DM created).
+10. `welcome_user_id`: An optional user ID to start a DM with after creating an account. Defaults to nothing (no DM created).
 11. `custom_translations_url`: An optional URL to allow overriding of translatable strings. The JSON file must be in a format of
     `{"affected|translation|key": {"languageCode": "new string"}}`. See https://github.com/matrix-org/matrix-react-sdk/pull/7886 for details.
 12. `branding`: Options for configuring various assets used within the app. Described in more detail down below.
@@ -154,8 +154,7 @@ complete re-branding/private labeling, a more personalised experience can be ach
     2. `description`: Required. The description to use for the notice.
     3. `show_once`: Optional. If true then the notice will only be shown once per device.
 18. `help_url`: The URL to point users to for help with the app, defaults to `https://element.io/help`.
-19. `help_encryption_url`: The URL to point users to for help with encryption, defaults to `https://element.io/help#encryption`.
-20. `force_verification`: If true, users must verify new logins (eg. with another device / their security key)
+19. `help_encrption_url`: The URL to point users to for help with encryption, defaults to `https://element.io/help#encryption`.
 
 ### `desktop_builds` and `mobile_builds`
 
@@ -168,10 +167,6 @@ Starting with `desktop_builds`, the following subproperties are available:
 1. `available`: Required. When `true`, the desktop app can be downloaded from somewhere.
 2. `logo`: Required. A URL to a logo (SVG), intended to be shown at 24x24 pixels.
 3. `url`: Required. The download URL for the app. This is used as a hyperlink.
-4. `url_macos`: Optional. Direct link to download macOS desktop app.
-5. `url_win32`: Optional. Direct link to download Windows 32-bit desktop app.
-6. `url_win64`: Optional. Direct link to download Windows 64-bit desktop app.
-7. `url_linux`: Optional. Direct link to download Linux desktop app.
 
 When `desktop_builds` is not specified at all, the app will assume desktop downloads are available from https://element.io
 
@@ -255,60 +250,17 @@ When Element is deployed alongside a homeserver with SSO-only login, some option
    user can be sent to in order to log them out of that system too, making logout symmetric between Element and the SSO system.
 2. `sso_redirect_options`: Options to define how to handle unauthenticated users. If the object contains `"immediate": true`, then
    all unauthenticated users will be automatically redirected to the SSO system to start their login. If instead you'd only like to
-   have users which land on the welcome page to be redirected, use `"on_welcome_page": true`. Additionally, there is an option to
-   redirect anyone landing on the login page, by using `"on_login_page": true`. As an example:
+   have users which land on the welcome page to be redirected, use `"on_welcome_page": true`. As an example:
     ```json
     {
         "sso_redirect_options": {
             "immediate": false,
-            "on_welcome_page": true,
-            "on_login_page": true
+            "on_welcome_page": true
         }
     }
     ```
     It is most common to use the `immediate` flag instead of `on_welcome_page`.
 
-## Native OIDC
-
-Native OIDC support is currently in labs and is subject to change.
-
-Static OIDC Client IDs are preferred and can be specified under `oidc_static_clients` as a mapping from `issuer` to configuration object containing `client_id`.
-Issuer must have a trailing forward slash. As an example:
-
-```json
-{
-    "oidc_static_clients": {
-        "https://auth.example.com/": {
-            "client_id": "example-client-id"
-        }
-    }
-}
-```
-
-If a matching static client is not found, the app will attempt to dynamically register a client using metadata specified under `oidc_metadata`.
-The app has sane defaults for the metadata properties below but on stricter policy identity providers they may not pass muster, e.g. `contacts` may be required.
-The following subproperties are available:
-
-1. `client_uri`: This is the base URI for the OIDC client registration, typically `logo_uri`, `tos_uri`, and `policy_uri` must be either on the same domain or a subdomain of this URI.
-2. `logo_uri`: Optional URI for the client logo.
-3. `tos_uri`: Optional URI for the client's terms of service.
-4. `policy_uri`: Optional URI for the client's privacy policy.
-5. `contacts`: Optional list of contact emails for the client.
-
-As an example:
-
-```json
-{
-    "oidc_metadata": {
-        "client_uri": "https://example.com",
-        "logo_uri": "https://example.com/logo.png",
-        "tos_uri": "https://example.com/tos",
-        "policy_uri": "https://example.com/policy",
-        "contacts": ["support@example.com"]
-    }
-}
-```
-
 ## VoIP / Jitsi calls
 
 Currently, Element uses Jitsi to offer conference calls in rooms, with an experimental Element Call implementation in the works.
@@ -379,8 +331,8 @@ The VoIP and Jitsi options are:
     }
     ```
     The `widget` is the `content` of a normal widget state event. The `layout` is the layout specifier for the widget being created,
-    as defined by the `io.element.widgets.layout` state event. By default this applies to all rooms, but the behaviour can be skipped for
-    2-person rooms, causing Element to fall back to 1:1 VoIP, by setting the option `widget_build_url_ignore_dm` to `true`.
+    as defined by the `io.element.widgets.layout` state event. By default this applies to all rooms, but the behaviour can be skipped for DMs
+    by setting the option `widget_build_url_ignore_dm` to `true`.
 5. `audio_stream_url`: Optional URL to pass to Jitsi to enable live streaming. This option is considered experimental and may be removed
    at any time without notice.
 6. `element_call`: Optional configuration for native group calls using Element Call, with the following subkeys:
@@ -392,12 +344,6 @@ The VoIP and Jitsi options are:
       this number is exceeded, the user will not be able to join a given call.
     - `brand`: Optional name for the app. Defaults to `Element Call`. This is
       used throughout the application in various strings/locations.
-    - `guest_spa_url`: Optional URL for an Element Call single-page app (SPA),
-      for guest links. If this is set, Element Web will expose a "join" link
-      for public video rooms, which can then be shared to non-matrix users.
-      The target Element Call SPA is typically set up to use a homeserver that
-      allows users to register without email ("passwordless guest users") and to
-      federate.
 
 ## Bug reporting
 
@@ -453,12 +399,6 @@ If you would like to use Scalar, the integration manager maintained by Element,
 }
 ```
 
-For widgets in general (from an integration manager or not) there is also:
-
--   `default_widget_container_height`
-
-This controls the height that the top widget panel initially appears as and is the height in pixels, default 280.
-
 ## Administrative options
 
 If you would like to include a custom message when someone is reporting an event, set the following Markdown-capable field:
@@ -540,7 +480,7 @@ decentralised.
 
 ## Desktop app configuration
 
-See https://github.com/element-hq/element-desktop#user-specified-configjson
+See https://github.com/vector-im/element-desktop#user-specified-configjson
 
 ## UI Features
 

docs/customisations.md

@@ -2,7 +2,7 @@
 
 ### 🦖 DEPRECATED
 
-Customisations have been deprecated in favour of the [Module API](https://github.com/element-hq/element-web/blob/develop/docs/modules.md).
+Customisations have been deprecated in favour of the [Module API](https://github.com/vector-im/element-web/blob/develop/docs/modules.md).
 If you have use cases from customisations which are not yet available via the Module API please open an issue.
 Customisations will be removed from the codebase in a future release.
 
@@ -12,7 +12,7 @@ Element Web and the React SDK support "customisation points" that can be used to
 easily add custom logic specific to a particular deployment of Element Web.
 
 An example of this is the [security customisations
-module](https://github.com/element-hq/element-web/blob/develop/src/customisations/Security.ts).
+module](https://github.com/matrix-org/matrix-react-sdk/blob/develop/src/customisations/Security.ts).
 This module in the React SDK only defines some empty functions and their types:
 it does not do anything by default.
 
@@ -54,7 +54,7 @@ UI for some actions can be hidden via the ComponentVisibility customisation:
 -   creating rooms,
 -   creating spaces,
 
-To customise visibility create a customisation module from [ComponentVisibility](https://github.com/element-hq/element-web/blob/master/src/customisations/ComponentVisibility.ts) following the instructions above.
+To customise visibility create a customisation module from [ComponentVisibility](https://github.com/matrix-org/matrix-react-sdk/blob/master/src/customisations/ComponentVisibility.ts) following the instructions above.
 
 `shouldShowComponent` determines whether the active MatrixClient user should be able to use
 the given UI component. When `shouldShowComponent` returns falsy all UI components for that feature will be hidden.

docs/feature-flags.md

@@ -35,7 +35,7 @@ clients commit to doing the associated clean up work once a feature stabilises.
 When starting work on a feature, we should create a matching feature flag:
 
 1. Add a new
-   [setting](https://github.com/element-hq/element-web/blob/develop/src/settings/Settings.tsx)
+   [setting](https://github.com/matrix-org/matrix-react-sdk/blob/develop/src/settings/Settings.tsx)
    of the form:
 
 ```js
@@ -53,7 +53,7 @@ When starting work on a feature, we should create a matching feature flag:
 SettingsStore.getValue("feature_cats");
 ```
 
-3. Document the feature in the [labs documentation](https://github.com/element-hq/element-web/blob/develop/docs/labs.md)
+3. Document the feature in the [labs documentation](https://github.com/vector-im/element-web/blob/develop/docs/labs.md)
 
 With these steps completed, the feature is disabled by default, but can be
 enabled on develop and nightly by interested users for testing.
@@ -64,9 +64,9 @@ The following lists a few common options.
 ## Enabling by default on develop and nightly
 
 Set the feature to `true` in the
-[develop](https://github.com/element-hq/element-web/blob/develop/element.io/develop/config.json)
+[develop](https://github.com/vector-im/element-web/blob/develop/element.io/develop/config.json)
 and
-[nightly](https://github.com/element-hq/element-desktop/blob/develop/element.io/nightly/config.json)
+[nightly](https://github.com/vector-im/element-desktop/blob/develop/element.io/nightly/config.json)
 configs:
 
 ```json
@@ -78,9 +78,9 @@ configs:
 ## Enabling by default on staging, app, and release
 
 Set the feature to `true` in the
-[staging / app](https://github.com/element-hq/element-web/blob/develop/element.io/app/config.json)
+[staging / app](https://github.com/vector-im/element-web/blob/develop/element.io/app/config.json)
 and
-[release](https://github.com/element-hq/element-desktop/blob/develop/element.io/release/config.json)
+[release](https://github.com/vector-im/element-desktop/blob/develop/element.io/release/config.json)
 configs.
 
 **Note:** The above will only enable the feature for https://app.element.io and official Element
@@ -93,21 +93,21 @@ Once we're confident that a feature is working well, we should remove or convert
 
 If the feature is meant to be turned off/on by the user:
 
-1. Remove `isFeature` from the [setting](https://github.com/element-hq/element-web/blob/develop/src/settings/Settings.ts)
+1. Remove `isFeature` from the [setting](https://github.com/matrix-org/matrix-react-sdk/blob/develop/src/settings/Settings.ts)
 2. Change the `default` to `true` (if desired).
-3. Remove the feature from the [labs documentation](https://github.com/element-hq/element-web/blob/develop/docs/labs.md)
+3. Remove the feature from the [labs documentation](https://github.com/vector-im/element-web/blob/develop/docs/labs.md)
 4. Celebrate! 🥳
 
 If the feature is meant to be forced on (non-configurable):
 
-1. Remove the [setting](https://github.com/element-hq/element-web/blob/develop/src/settings/Settings.ts)
+1. Remove the [setting](https://github.com/matrix-org/matrix-react-sdk/blob/develop/src/settings/Settings.ts)
 2. Remove all `getValue` lines that test for the feature.
-3. Remove the feature from the [labs documentation](https://github.com/element-hq/element-web/blob/develop/docs/labs.md)
+3. Remove the feature from the [labs documentation](https://github.com/vector-im/element-web/blob/develop/docs/labs.md)
 4. If applicable, remove the feature state from
-   [develop](https://github.com/element-hq/element-web/blob/develop/element.io/develop/config.json),
-   [nightly](https://github.com/element-hq/element-desktop/blob/develop/element.io/nightly/config.json),
-   [staging / app](https://github.com/element-hq/element-web/blob/develop/element.io/app/config.json),
+   [develop](https://github.com/vector-im/element-web/blob/develop/element.io/develop/config.json),
+   [nightly](https://github.com/vector-im/element-desktop/blob/develop/element.io/nightly/config.json),
+   [staging / app](https://github.com/vector-im/element-web/blob/develop/element.io/app/config.json),
    and
-   [release](https://github.com/element-hq/element-desktop/blob/develop/element.io/release/config.json)
+   [release](https://github.com/vector-im/element-desktop/blob/develop/element.io/release/config.json)
    configs
 5. Celebrate! 🥳

docs/features/README.md

@@ -1,6 +0,0 @@
-# Feature documention
-
-The idea of this folder is to document the features we support in different parts of the app.
-In case anyone needs to work on a given part, and isn't aware of all the features in the area,
-they will hopefully get an idea for all the supported functionality to know what to take into account
-when making changes.

docs/features/composer.md

@@ -1,38 +0,0 @@
-# Composer Features
-
-## Auto Complete
-
--   Hitting tab tries to auto-complete the word before the caret as a room member
-    -   If no matching name is found, a visual bell is shown
--   @ + a letter opens auto complete for members starting with the given letter
-    -   When inserting a user pill at the start in the composer, a colon and space is appended to the pill
-    -   When inserting a user pill anywhere else in composer, only a space is appended to the pill
--   # + a letter opens auto complete for rooms starting with the given letter
--   : open auto complete for emoji
--   Pressing arrow-up/arrow-down while the autocomplete is open navigates between auto complete options
--   Pressing tab while the autocomplete is open goes to the next autocomplete option,
-    wrapping around at the end after reverting to the typed text first.
-
-## Formatting
-
--   When selecting text, a formatting bar appears above the selection.
--   The formatting bar allows to format the selected test as:
-    bold, italic, strikethrough, a block quote, and a code block (inline if no linebreak is selected).
--   Formatting is applied as markdown syntax.
--   Hitting ctrl/cmd+B also marks the selected text as bold
--   Hitting ctrl/cmd+I also marks the selected text as italic
--   Hitting ctrl/cmd+> also marks the selected text as a blockquote
-
-## Misc
-
--   When hitting the arrow-up button while having the caret at the start in the composer,
-    the last message sent by the syncing user is edited.
--   Clicking a display name on an event in the timeline inserts a user pill into the composer
--   Emoticons (like :-), >:-), :-/, ...) are replaced by emojis while typing if the relevant setting is enabled
--   Typing in the composer sends typing notifications in the room
--   Pressing ctrl/mod+z and ctrl/mod+y undoes/redoes modifications
--   Pressing shift+enter inserts a line break
--   Pressing enter sends the message.
--   Choosing "Quote" in the context menu of an event inserts a quote of the event body in the composer.
--   Choosing "Reply" in the context menu of an event shows a preview above the composer to reply to.
--   Pressing alt+arrow up/arrow down navigates in previously sent messages, putting them in the composer.

docs/features/keyboardShortcuts.md

@@ -1,59 +0,0 @@
-# Keyboard shortcuts
-
-## Using the `KeyBindingManager`
-
-The `KeyBindingManager` (accessible using `getKeyBindingManager()`) is a class
-with several methods that allow you to get a `KeyBindingAction` based on a
-`KeyboardEvent | React.KeyboardEvent`.
-
-The event passed to the `KeyBindingManager` gets compared to the list of
-shortcuts that are retrieved from the `IKeyBindingsProvider`s. The
-`IKeyBindingsProvider` is in `KeyBindingDefaults`.
-
-### Examples
-
-Let's say we want to close a menu when the correct keys were pressed:
-
-```ts
-const onKeyDown = (ev: KeyboardEvent): void => {
-    let handled = true;
-    const action = getKeyBindingManager().getAccessibilityAction(ev);
-    switch (action) {
-        case KeyBindingAction.Escape:
-            closeMenu();
-            break;
-        default:
-            handled = false;
-            break;
-    }
-
-    if (handled) {
-        ev.preventDefault();
-        ev.stopPropagation();
-    }
-};
-```
-
-## Managing keyboard shortcuts
-
-There are a few things at play when it comes to keyboard shortcuts. The
-`KeyBindingManager` gets `IKeyBindingsProvider`s one of which is
-`defaultBindingsProvider` defined in `KeyBindingDefaults`. In
-`KeyBindingDefaults` a `getBindingsByCategory()` method is used to create
-`KeyBinding`s based on `KeyboardShortcutSetting`s defined in
-`KeyboardShortcuts`.
-
-### Adding keyboard shortcuts
-
-To add a keyboard shortcut there are two files we have to look at:
-`KeyboardShortcuts.ts` and `KeyBindingDefaults.ts`. In most cases we only need
-to edit `KeyboardShortcuts.ts`: add a `KeyBindingAction` and add the
-`KeyBindingAction` to the `KEYBOARD_SHORTCUTS` object.
-
-Though, to make matters worse, sometimes we want to add a shortcut that has
-multiple keybindings associated with. This keyboard shortcut won't be
-customizable as it would be rather difficult to manage both from the point of
-the settings and the UI. To do this, we have to add a `KeyBindingAction` and add
-the UI representation of that keyboard shortcut to the `getUIOnlyShortcuts()`
-method. Then, we also need to add the keybinding to the correct method in
-`KeyBindingDefaults`.

docs/icons.md

@@ -1,56 +0,0 @@
-# Icons
-
-Icons are loaded using [@svgr/webpack](https://www.npmjs.com/package/@svgr/webpack).
-This is configured in [element-web](https://github.com/vector-im/element-web/blob/develop/webpack.config.js#L458).
-
-Each `.svg` exports a `ReactComponent` at the named export `Icon`.
-Icons have `role="presentation"` and `aria-hidden` automatically applied. These can be overriden by passing props to the icon component.
-
-SVG file recommendations:
-
--   Colours should not be defined absolutely. Use `currentColor` instead.
--   SVG files should be taken from the design compound as they are. Some icons contain special padding.
-    This means that there should be icons for each size, e.g. warning-16px and warning-32px.
-
-Example usage:
-
-```
-import { Icon as FavoriteIcon } from 'res/img/element-icons/favorite.svg';
-
-const MyComponent = () => {
-    return <>
-        <FavoriteIcon className="mx_Icon mx_Icon_16">
-    </>;
-}
-```
-
-If possible, use the icon classes from [here](../res/css/compound/_Icon.pcss).
-
-## Custom styling
-
-Icon components are svg elements and may be custom styled as usual.
-
-`_MyComponents.pcss`:
-
-```css
-.mx_MyComponent-icon {
-    height: 20px;
-    width: 20px;
-
-    * {
-        fill: $accent;
-    }
-}
-```
-
-`MyComponent.tsx`:
-
-```typescript
-import { Icon as FavoriteIcon } from 'res/img/element-icons/favorite.svg';
-
-const MyComponent = () => {
-    return <>
-        <FavoriteIcon className="mx_MyComponent-icon" role="img" aria-hidden="false">
-    </>;
-}
-```

docs/install.md

@@ -1,78 +0,0 @@
-# Installing Element Web
-
-**Familiarise yourself with the [Important Security Notes](../README.md#important-security-notes) before starting, they apply to all installation methods.**
-
-_Note: that for the security of your chats will need to serve Element over HTTPS.
-Major browsers also do not allow you to use VoIP/video chats over HTTP, as WebRTC is only usable over HTTPS.
-There are some exceptions like when using localhost, which is considered a [secure context](https://developer.mozilla.org/docs/Web/Security/Secure_Contexts) and thus allowed._
-
-## Release tarball
-
-1. Download the latest version from <https://github.com/element-hq/element-web/releases>
-1. Untar the tarball on your web server
-1. Move (or symlink) the `element-x.x.x` directory to an appropriate name
-1. Configure the correct caching headers in your webserver (see below)
-1. Configure the app by copying `config.sample.json` to `config.json` and
-   modifying it. See the [configuration docs](config.md) for details.
-1. Enter the URL into your browser and log into Element!
-
-Releases are signed using gpg and the OpenPGP standard,
-and can be checked against the public key located at <https://packages.element.io/element-release-key.asc>.
-
-## Debian package
-
-Element Web is now also available as a Debian package for Debian and Ubuntu based systems.
-
-```shell
-sudo apt install -y wget apt-transport-https
-sudo wget -O /usr/share/keyrings/element-io-archive-keyring.gpg https://packages.element.io/debian/element-io-archive-keyring.gpg
-echo "deb [signed-by=/usr/share/keyrings/element-io-archive-keyring.gpg] https://packages.element.io/debian/ default main" | sudo tee /etc/apt/sources.list.d/element-io.list
-sudo apt update
-sudo apt install element-web
-```
-
-Configure the app by modifying `/etc/element-web/config.json`. See the [configuration docs](config.md) for details.
-
-Then point your chosen web server (e.g. Caddy, Nginx, Apache, etc) at the `/usr/share/element-web` webroot.
-
-## Docker
-
-The Docker image can be used to serve element-web as a web server. The easiest way to use
-it is to use the prebuilt image:
-
-```bash
-docker run -p 80:80 vectorim/element-web
-```
-
-To supply your own custom `config.json`, map a volume to `/app/config.json`. For example,
-if your custom config was located at `/etc/element-web/config.json` then your Docker command
-would be:
-
-```bash
-docker run -p 80:80 -v /etc/element-web/config.json:/app/config.json vectorim/element-web
-```
-
-To build the image yourself:
-
-```bash
-git clone https://github.com/element-hq/element-web.git element-web
-cd element-web
-git checkout master
-docker build .
-```
-
-If you're building a custom branch, or want to use the develop branch, check out the appropriate
-element-web branch and then run:
-
-```bash
-docker build -t \
-    --build-arg USE_CUSTOM_SDKS=true \
-    --build-arg JS_SDK_REPO="https://github.com/matrix-org/matrix-js-sdk.git" \
-    --build-arg JS_SDK_BRANCH="develop" \
-    .
-```
-
-## Kubernetes
-
-The provided element-web docker image can also be run from within a Kubernetes cluster.
-See the [Kubernetes example](kubernetes.md) for more details.

docs/jitsi.md

@@ -64,47 +64,9 @@ Element Android (1.0.5+) supports custom Jitsi domains, similar to Element Web a
 calls work directly between clients or via TURN servers configured on the respective
 homeservers.
 
-For rooms with more than 2 joined members, when creating a Jitsi conference via call/video buttons of the toolbar (not via integration manager), Element Android will create a widget using the [wrapper](https://github.com/element-hq/element-web/blob/develop/docs/jitsi-dev.md) hosted on `app.element.io`.
+For rooms with more than 2 joined members, when creating a Jitsi conference via call/video buttons of the toolbar (not via integration manager), Element Android will create a widget using the [wrapper](https://github.com/vector-im/element-web/blob/develop/docs/jitsi-dev.md) hosted on `app.element.io`.
 The domain used is the one specified by the `/.well-known/matrix/client` endpoint, and if not present it uses the fallback defined in `config.json` (meet.element.io)
 
 For active Jitsi widgets in the room, a native Jitsi widget UI is created and points to the instance specified in the `domain` key of the widget content data.
 
 Element Android manages allowed native widgets permissions a bit differently than web widgets (as the data shared are different and never shared with the widget URL). For Jitsi widgets, permissions are requested only once per domain (consent saved in account data).
-
-# Jitsi Wrapper
-
-**Note**: These are developer docs. Please consult your client's documentation for
-instructions on setting up Jitsi.
-
-The react-sdk wraps all Jitsi call widgets in a local wrapper called `jitsi.html`
-which takes several parameters:
-
-_Query string_:
-
--   `widgetId`: The ID of the widget. This is needed for communication back to the
-    react-sdk.
--   `parentUrl`: The URL of the parent window. This is also needed for
-    communication back to the react-sdk.
-
-_Hash/fragment (formatted as a query string)_:
-
--   `conferenceDomain`: The domain to connect Jitsi Meet to.
--   `conferenceId`: The room or conference ID to connect Jitsi Meet to.
--   `isAudioOnly`: Boolean for whether this is a voice-only conference. May not
-    be present, should default to `false`.
--   `startWithAudioMuted`: Boolean for whether the calls start with audio
-    muted. May not be present.
--   `startWithVideoMuted`: Boolean for whether the calls start with video
-    muted. May not be present.
--   `displayName`: The display name of the user viewing the widget. May not
-    be present or could be null.
--   `avatarUrl`: The HTTP(S) URL for the avatar of the user viewing the widget. May
-    not be present or could be null.
--   `userId`: The MXID of the user viewing the widget. May not be present or could
-    be null.
-
-The react-sdk will assume that `jitsi.html` is at the path of wherever it is currently
-being served. For example, `https://develop.element.io/jitsi.html` or `vector://webapp/jitsi.html`.
-
-The `jitsi.html` wrapper can use the react-sdk's `WidgetApi` to communicate, making
-it easier to actually implement the feature.

docs/labs.md

@@ -5,7 +5,7 @@ to `Settings->Labs`. This list is non-exhaustive and subject to change, chat in
 [#element-web:matrix.org](https://matrix.to/#/#element-web:matrix.org) for more information.
 
 If a labs features gets more stable, it _may_ be promoted to a beta feature
-(see [Betas](https://github.com/element-hq/element-web/blob/develop/docs/betas.md)).
+(see [Betas](https://github.com/vector-im/element-web/blob/develop/docs/betas.md)).
 
 **Be warned! Labs features are not finalised, they may be fragile, they may change, they may be
 dropped. Ask in the room if you are unclear about any details here.**
@@ -37,6 +37,29 @@ date from the calendar.
 
 Also adds the `/jumptodate 2022-01-31` slash command.
 
+## Render simple counters in room header (`feature_state_counters`)
+
+Allows rendering of labelled counters above the message list.
+
+Once enabled, send a custom state event to a room to set values:
+
+1. In a room, type `/devtools` to bring up the devtools interface
+2. Click "Send Custom Event"
+3. Toggle from "Event" to "State Event"
+4. Set the event type to: `re.jki.counter` and give it a unique key
+5. Specify the content in the following format:
+
+```
+{
+    "link": "",
+    "severity": "normal",
+    "title": "my counter",
+    "value": 0
+}
+```
+
+That's it. Now should see your new counter under the header.
+
 ## New ways to ignore people (`feature_mjolnir`)
 
 When enabled, a new settings tab appears for users to be able to manage their ban lists.
@@ -72,13 +95,18 @@ theme definition.
 
 For some sample themes, check out [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes).
 
+## Dehydrated devices (`feature_dehydration`)
+
+Allows users to receive encrypted messages by creating a device that is stored
+encrypted on the server, as described in [MSC2697](https://github.com/matrix-org/matrix-doc/pull/2697).
+
 ## Live location sharing (`feature_location_share_live`) [In Development]
 
 Enables sharing your current location to the timeline, with live updates.
 
 ## Video rooms (`feature_video_rooms`)
 
-Enables support for creating video rooms, which are persistent video chats that users can jump in and out of.
+Enables support for creating and joining video rooms, which are persistent video chats that users can jump in and out of.
 
 ## Element Call video rooms (`feature_element_call_video_rooms`) [In Development]
 
@@ -88,23 +116,24 @@ This flag will not have any effect unless `feature_video_rooms` is also enabled.
 
 ## New group call experience (`feature_group_calls`) [In Development]
 
-This feature allows users to place native [MSC3401](https://github.com/matrix-org/matrix-spec-proposals/pull/3401) group calls in compatible rooms, using Element Call.
+This feature allows users to place and join native [MSC3401](https://github.com/matrix-org/matrix-spec-proposals/pull/3401) group calls in compatible rooms, using Element Call.
 
 If you're enabling this at the deployment level, you may also want to reference the docs for the `element_call` config section.
 
-## Disable per-sender encryption for Element Call (`feature_disable_call_per_sender_encryption`)
-
-The default for embedded Element Call in Element Web is per-participant encryption.
-This labs flag disables encryption for embedded Element Call in encrypted rooms.
-
-Under the hood this stops Element Web from adding the `perParticipantE2EE` flag for the Element Call widget url.
-
-This is useful while we experiment with encryption and to make calling compatible with platforms that don't use encryption yet.
-
 ## Rich text in room topics (`feature_html_topic`) [In Development]
 
 Enables rendering of MD / HTML in room topics.
 
+## Use the Rust cryptography implementation (`feature_rust_crypto`) [In Development]
+
+Configures Element to use a new cryptography implementation based on the [matrix-rust-sdk](https://github.com/matrix-org/matrix-rust-sdk).
+
+This setting is (currently) _sticky_ to a user's session: it only takes effect when the user logs in to a new session. Likewise, even after disabling the setting in `config.json`, the Rust implementation will remain in use until users log out.
+
+## New room header & details (`feature_new_room_decoration_ui`) [In Development]
+
+Refactors visually the room header and room sidebar
+
 ## Enable the notifications panel in the room header (`feature_notifications`)
 
 Unreliable in encrypted rooms.

docs/lib/custom.css

@@ -1,14 +0,0 @@
-/* Prevent collapsible headings from wrapping onto two lines eagerly */
-summary > h1,
-summary > h2,
-summary > h3,
-summary > h4,
-summary > h5,
-summary > h6 {
-    display: inline-block;
-}
-
-/* Prevent longer checkbox lists from wrapping eagerly */
-input + p {
-    display: inline;
-}

docs/local-echo-dev.md

@@ -1,38 +0,0 @@
-# Local echo (developer docs)
-
-The React SDK provides some local echo functionality to allow for components to do something
-quickly and fall back when it fails. This is all available in the `local-echo` directory within
-`stores`.
-
-Echo is handled in EchoChambers, with `GenericEchoChamber` being the base implementation for all
-chambers. The `EchoChamber` class is provided as semantic access to a `GenericEchoChamber`
-implementation, such as the `RoomEchoChamber` (which handles echoable details of a room).
-
-Anything that can be locally echoed will be provided by the `GenericEchoChamber` implementation.
-The echo chamber will also need to deal with external changes, and has full control over whether
-or not something has successfully been echoed.
-
-An `EchoContext` is provided to echo chambers (usually with a matching type: `RoomEchoContext`
-gets provided to a `RoomEchoChamber` for example) with details about their intended area of
-effect, as well as manage `EchoTransaction`s. An `EchoTransaction` is simply a unit of work that
-needs to be locally echoed.
-
-The `EchoStore` manages echo chamber instances, builds contexts, and is generally less semantically
-accessible than the `EchoChamber` class. For separation of concerns, and to try and keep things
-tidy, this is an intentional design decision.
-
-**Note**: The local echo stack uses a "whenable" pattern, which is similar to thenables and
-`EventEmitter`. Whenables are ways of actioning a changing condition without having to deal
-with listeners being torn down. Once the reference count of the Whenable causes garbage collection,
-the Whenable's listeners will also be torn down. This is accelerated by the `IDestroyable` interface
-usage.
-
-## Audit functionality
-
-The UI supports a "Server isn't responding" dialog which includes a partial audit log-like
-structure to it. This is partially the reason for added complexity of `EchoTransaction`s
-and `EchoContext`s - this information feeds the UI states which then provide direct retry
-mechanisms.
-
-The `EchoStore` is responsible for ensuring that the appropriate non-urgent toast (lower left)
-is set up, where the dialog then drives through the contexts and transactions.

docs/media-handling.md

@@ -1,19 +0,0 @@
-# Media handling
-
-Surely media should be as easy as just putting a URL into an `img` and calling it good, right?
-Not quite. Matrix uses something called a Matrix Content URI (better known as MXC URI) to identify
-content, which is then converted to a regular HTTPS URL on the homeserver. However, sometimes that
-URL can change depending on deployment considerations.
-
-The react-sdk features a [customisation endpoint](https://github.com/vector-im/element-web/blob/develop/docs/customisations.md)
-for media handling where all conversions from MXC URI to HTTPS URL happen. This is to ensure that
-those obscure deployments can route all their media to the right place.
-
-For development, there are currently two functions available: `mediaFromMxc` and `mediaFromContent`.
-The `mediaFromMxc` function should be self-explanatory. `mediaFromContent` takes an event content as
-a parameter and will automatically parse out the source media and thumbnail. Both functions return
-a `Media` object with a number of options on it, such as getting various common HTTPS URLs for the
-media.
-
-**It is extremely important that all media calls are put through this customisation endpoint.** So
-much so it's a lint rule to avoid accidental use of the wrong functions.

docs/modules.md

@@ -6,7 +6,7 @@ at runtime.
 
 ## Installing modules
 
-If you already have a module you want to install, such as our [ILAG Module](https://github.com/element-hq/element-web-ilag-module),
+If you already have a module you want to install, such as our [ILAG Module](https://github.com/vector-im/element-web-ilag-module),
 then copy `build_config.sample.yaml` to `build_config.yaml` in the same directory. In your new `build_config.yaml` simply
 add the reference to the module as described by the sample file, using the same syntax you would for `yarn add`:
 
@@ -23,14 +23,14 @@ the current directory as the build context (the `.` in `docker build -t my-eleme
 ## Writing modules
 
 While writing modules is meant to be easy, not everything is possible yet. For modules which want to do something we haven't
-exposed in the module API, the module API will need to be updated. This means a PR to both this repo
-and [`matrix-react-sdk-module-api`](https://github.com/matrix-org/matrix-react-sdk-module-api).
+exposed in the module API, the module API will need to be updated. This means a PR to both the
+[`matrix-react-sdk`](https://github.com/matrix-org/matrix-react-sdk) and [`matrix-react-sdk-module-api`](https://github.com/matrix-org/matrix-react-sdk-module-api).
 
 Once your change to the module API is accepted, the `@matrix-org/react-sdk-module-api` dependency gets updated at the
-`element-web` layer (usually by us, the maintainers) to ensure your module can operate.
+`matrix-react-sdk` and `element-web` layers (usually by us, the maintainers) to ensure your module can operate.
 
 If you're not adding anything to the module API, or your change was accepted per above, then start off with a clone of
-our [ILAG module](https://github.com/element-hq/element-web-ilag-module) which will give you a general idea for what the
+our [ILAG module](https://github.com/vector-im/element-web-ilag-module) which will give you a general idea for what the
 structure of a module is and how it works.
 
 The following requirements are key for any module:
@@ -40,8 +40,6 @@ The following requirements are key for any module:
    which takes a single parameter: a `ModuleApi` instance. This instance is passed to `super()`.
 3. The module must be deployed in a way where `yarn add` can access it, as that is how the build system will try to
    install it. Note that while this is often NPM, it can also be a GitHub/GitLab repo or private NPM registry.
-   Be careful when using git dependencies in yarn classic, many lifecycle scripts will not be executed which may mean
-   that your module is not built and thus may fail to be imported.
 
 ... and that's pretty much it. As with any code, please be responsible and call things in line with the documentation.
 Both `RuntimeModule` and `ModuleApi` have extensive documentation to describe what is proper usage and how to set things

docs/native-node-modules.md

@@ -1,3 +1,3 @@
 # Native Node Modules
 
-This documentation moved to the [`element-desktop`](https://github.com/element-hq/element-desktop/blob/develop/docs/native-node-modules.md) repository.
+This documentation moved to the [`element-desktop`](https://github.com/vector-im/element-desktop/blob/develop/docs/native-node-modules.md) repository.

docs/playwright.md

@@ -1,219 +0,0 @@
-# Playwright in Element Web
-
-## Contents
-
--   How to run the tests
--   How the tests work
--   How to write great Playwright tests
--   Visual testing
-
-## Running the Tests
-
-Our Playwright tests run automatically as part of our CI along with our other tests,
-on every pull request and on every merge to develop & master.
-
-You may need to follow instructions to set up your development environment for running
-Playwright by following <https://playwright.dev/docs/browsers#install-browsers> and
-<https://playwright.dev/docs/browsers#install-system-dependencies>.
-
-However the Playwright tests are run, an element-web instance must be running on
-http://localhost:8080 (this is configured in `playwright.config.ts`) - this is what will
-be tested. When running Playwright tests yourself, the standard `yarn start` from the
-element-web project is fine: leave it running it a different terminal as you would
-when developing. Alternatively if you followed the development set up from element-web then
-Playwright will be capable of running the webserver on its own if it isn't already running.
-
-The tests use Docker to launch Homeserver (Synapse or Dendrite) instances to test against, so you'll also
-need to have Docker installed and working in order to run the Playwright tests.
-
-There are a few different ways to run the tests yourself. The simplest is to run:
-
-```shell
-docker pull ghcr.io/element-hq/synapse:develop
-yarn run test:playwright
-```
-
-This will run the Playwright tests once, non-interactively.
-
-Note: you don't need to run the `docker pull` command every time, but you should
-do it regularly to ensure you are running against an up-to-date Synapse.
-
-You can also run individual tests this way too, as you'd expect:
-
-```shell
-yarn run test:playwright --spec playwright/e2e/register/register.spec.ts
-```
-
-Playwright also has its own UI that you can use to run and debug the tests.
-To launch it:
-
-```shell
-yarn run test:playwright:open --headed --debug
-```
-
-See more command line options at <https://playwright.dev/docs/test-cli>.
-
-### Running with Rust cryptography
-
-`matrix-js-sdk` is currently in the
-[process](https://github.com/vector-im/element-web/issues/21972) of being
-updated to replace its end-to-end encryption implementation to use the [Matrix
-Rust SDK](https://github.com/matrix-org/matrix-rust-sdk). This is not currently
-enabled by default, but it is possible to have Playwright configure Element to use
-the Rust crypto implementation by passing `--project="Rust Crypto"` or using
-the top left options in open mode.
-
-## How the Tests Work
-
-Everything Playwright-related lives in the `playwright/` subdirectory of react-sdk
-as is typical for Playwright tests. Likewise, tests live in `playwright/e2e`.
-
-`playwright/plugins/homeservers` contains Playwright plugins that starts instances
-of Synapse/Dendrite in Docker containers. These servers are what Element-web runs
-against in the tests.
-
-Synapse can be launched with different configurations in order to test element
-in different configurations. `playwright/plugins/homeserver/synapse/templates`
-contains template configuration files for each different configuration.
-
-Each test suite can then launch whatever Synapse instances it needs in whatever
-configurations.
-
-Note that although tests should stop the Homeserver instances after running and the
-plugin also stop any remaining instances after all tests have run, it is possible
-to be left with some stray containers if, for example, you terminate a test such
-that the `after()` does not run and also exit Playwright uncleanly. All the containers
-it starts are prefixed, so they are easy to recognise. They can be removed safely.
-
-After each test run, logs from the Synapse instances are saved in `playwright/logs/synapse`
-with each instance in a separate directory named after its ID. These logs are removed
-at the start of each test run.
-
-## Writing Tests
-
-Mostly this is the same advice as for writing any other Playwright test: the Playwright
-docs are well worth a read if you're not already familiar with Playwright testing, eg.
-https://playwright.dev/docs/best-practices. To avoid your tests being flaky it is also
-recommended to use [auto-retrying assertions](https://playwright.dev/docs/test-assertions#auto-retrying-assertions).
-
-### Getting a Synapse
-
-We heavily leverage the magic of [Playwright fixtures](https://playwright.dev/docs/test-fixtures).
-To acquire a homeserver within a test just add the `homeserver` fixture to the test:
-
-```typescript
-test("should do something", async ({ homeserver }) => {
-    // homeserver is a Synapse/Dendrite instance
-});
-```
-
-This returns an object with information about the Homeserver instance, including what port
-it was started on and the ID that needs to be passed to shut it down again. It also
-returns the registration shared secret (`registrationSecret`) that can be used to
-register users via the REST API. The Homeserver has been ensured ready to go by awaiting
-its internal health-check.
-
-Homeserver instances should be reasonably cheap to start (you may see the first one take a
-while as it pulls the Docker image).
-You do not need to explicitly clean up the instance as it will be cleaned up by the fixture.
-
-### Synapse Config Templates
-
-When a Synapse instance is started, it's given a config generated from one of the config
-templates in `playwright/plugins/homeserver/synapse/templates`. There are a couple of special files
-in these templates:
-
--   `homeserver.yaml`:
-    Template substitution happens in this file. Template variables are:
-    -   `REGISTRATION_SECRET`: The secret used to register users via the REST API.
-    -   `MACAROON_SECRET_KEY`: Generated each time for security
-    -   `FORM_SECRET`: Generated each time for security
-    -   `PUBLIC_BASEURL`: The localhost url + port combination the synapse is accessible at
--   `localhost.signing.key`: A signing key is auto-generated and saved to this file.
-    Config templates should not contain a signing key and instead assume that one will exist
-    in this file.
-
-All other files in the template are copied recursively to `/data/`, so the file `foo.html`
-in a template can be referenced in the config as `/data/foo.html`.
-
-### Logging In
-
-We again heavily leverage the magic of [Playwright fixtures](https://playwright.dev/docs/test-fixtures).
-To acquire a logged-in user within a test just add the `user` fixture to the test:
-
-```typescript
-test("should do something", async ({ user }) => {
-    // user is a logged in user
-});
-```
-
-You can specify a display name for the user via `test.use` `displayName`,
-otherwise a random one will be generated.
-This will register a random userId using the registrationSecret with a random password
-and the given display name. The user fixture will contain details about the credentials for if
-they are needed for User-Interactive Auth or similar but localStorage will already be seeded with them
-and the app loaded (path `/`).
-
-### Joining a Room
-
-Many tests will also want to start with the client in a room, ready to send & receive messages. Best
-way to do this may be to get an access token for the user and use this to create a room with the REST
-API before logging the user in.
-You can make use of the bot fixture and the `client` field on the app fixture to do this.
-
-### Try to write tests from the users' perspective
-
-Like for instance a user will not look for a button by querying a CSS selector.
-Instead, you should work with roles / labels etc, see https://playwright.dev/docs/locators.
-
-### Using matrix-js-sdk
-
-Due to the way we run the Playwright tests in CI, at this time you can only use the matrix-js-sdk module
-exposed on `window.matrixcs`. This has the limitation that it is only accessible with the app loaded.
-This may be revisited in the future.
-
-## Good Test Hygiene
-
-This section mostly summarises general good Playwright testing practice, and should not be news to anyone
-already familiar with Playwright.
-
-1. Test a well-isolated unit of functionality. The more specific, the easier it will be to tell what's
-   wrong when they fail.
-1. Don't depend on state from other tests: any given test should be able to run in isolation.
-1. Try to avoid driving the UI for anything other than the UI you're trying to test. e.g. if you're
-   testing that the user can send a reaction to a message, it's best to send a message using a REST
-   API, then react to it using the UI, rather than using the element-web UI to send the message.
-1. Avoid explicit waits. Playwright locators & assertions will implicitly wait for the specified
-   element to appear and all assertions are retried until they either pass or time out, so you should
-   never need to manually wait for an element.
-    - For example, for asserting about editing an already-edited message, you can't wait for the
-      'edited' element to appear as there was already one there, but you can assert that the body
-      of the message is what is should be after the second edit and this assertion will pass once
-      it becomes true. You can then assert that the 'edited' element is still in the DOM.
-    - You can also wait for other things like network requests in the
-      browser to complete (https://playwright.dev/docs/api/class-page#page-wait-for-response).
-      Needing to wait for things can also be because of race conditions in the app itself, which ideally
-      shouldn't be there!
-
-This is a small selection - the Playwright best practices guide, linked above, has more good advice, and we
-should generally try to adhere to them.
-
-## Screenshot testing
-
-When we previously used Cypress we also dabbled with Percy, and whilst powerful it did not
-lend itself well to being executed on all PRs without needing to budget it substantially.
-
-Playwright has built-in support for [visual comparison testing](https://playwright.dev/docs/test-snapshots).
-Screenshots are saved in `playwright/snapshots` and are rendered in a Linux Docker environment for stability.
-
-One must be careful to exclude any dynamic content from the screenshot, such as timestamps, avatars, etc,
-via the `mask` option. See the [Playwright docs](https://playwright.dev/docs/test-snapshots#masking).
-
-Some UI elements render differently between test runs, such as BaseAvatar when
-there is no avatar set, choosing a colour from the theme palette based on the
-hash of the user/room's Matrix ID. To avoid this creating flaky tests we inject
-some custom CSS, for this to happen we use the custom assertion `toMatchScreenshot`
-instead of the native `toHaveScreenshot`.
-
-If you are running Linux and are unfortunate that the screenshots are not rendering identically,
-you may wish to specify `--ignore-snapshots` and rely on Docker to render them for you.

docs/release.md

@@ -1,260 +0,0 @@
-> Tip: Paste this into the browser console to make the checkboxes on this page tickable. (Bear in mind that your ticks will be lost if you reload though.)
->
-> ```
-> document.querySelectorAll("input[type='checkbox']").forEach(i => {i.disabled = false;})
-> ```
-
-<details><summary><h1>Branches</h1></summary><blockquote>
-
-#### develop
-
-The develop branch holds the very latest and greatest code we have to offer, as such it may be less stable. It corresponds to the develop.element.io CD platform.
-
-#### staging
-
-The staging branch corresponds to the very latest release regardless of whether it is an RC or not. Deployed to staging.element.io manually.
-
-#### master
-
-The master branch is the most stable as it is the very latest non-RC release. Deployed to app.element.io manually.
-
-</blockquote></details>
-
-<details><summary><h1>Versions</h1></summary><blockquote>
-
-The matrix-js-sdk follows semver, most releases will bump the minor version number.
-Breaking changes will bump the major version number.
-Element Web & Element Desktop do not follow semver and always have matching version numbers. The patch version number is normally incremented for every release.
-
-</blockquote></details>
-
-<details><summary><h1>Release Types</h1></summary><blockquote>
-
-#### Release candidate
-
-A normal release begins with a Release Candidate on the Tick phase of the release cycle,
-and may contain as many further RCs as are needed before the Tock phase of cycle.
-Each subsequent RC may add additional commits via any of the means of preparation.
-
-A normal release is the most typical run-of-the-mill release,
-with at least one RC (Release Candidate) followed by a FINAL release.
-The typical cadence for these is every 2 weeks we'll do a new initial RC,
-then the following week we'll do that release cycle's FINAL release with sometimes more RCs in between, as needed.
-
-#### Final
-
-A normal release culminates with a Final release on the Tock phase of the cycle.
-This may be merely shipping the very latest RC with an adjusted version number,
-but can also include (hopefully small) additional changes present on `staging` if they are deemed safe to skip an RC.
-
-### Hotfix / Security
-
-This is an accelerated type of release which sits somewhere between RC and Final.
-They tend to contain few patches delta from the previous release but also skip any form of RC
-and in the case of Security the patch lands on GitHub only moments prior.
-For all intents and purposes they are the same as a Final release but with a different purpose.
-
-</blockquote></details>
-
-<details><summary><h1>Release Blockers</h1></summary><blockquote>
-
-You should become release rabbit on the day after the last full release.
-For that week, it's your job to keep an eye on the Releases room and see whether any issues marked `X-Release-Blocker` are opened,
-or were already open. You should chase people to fix them, so that on RC day you can make the release.
-
-If release-blocking issues are still open, you need to delay the release until they are fixed or reclassified.
-
-There are two labels for tracking release blockers.
-
-#### X-Release-Blocker
-
-This label applied to an issue means we cannot ship a release affected by the specific issue.
-This means we cannot cut branches for an RC but security & hotfix releases may still be fine.
-
-#### X-Upcoming-Release-Blocker
-
-This label applied to an issue means that the next (read: not current) release cycle will be affected by the specific issue.
-This label will automagically convert to `X-Release-Blocker` at the conclusion of a full release.
-
-</blockquote></details>
-
-<details><summary><h1>Repositories</h1></summary><blockquote>
-
-This release process revolves around our main repositories:
-
--   [Element Desktop](https://github.com/element-hq/element-desktop/)
--   [Element Web](https://github.com/element-hq/element-web/)
--   [Matrix JS SDK](https://github.com/matrix-org/matrix-js-sdk/)
-
-We own other repositories, but they have more ad-hoc releases and are not part of the bi-weekly cycle:
-
--   https://github.com/matrix-org/matrix-web-i18n/
--   https://github.com/matrix-org/matrix-react-sdk-module-api
-
-</blockquote></details>
-
-<details><summary><h1>Prerequisites</h1></summary><blockquote>
-
--   You must be part of the 2 Releasers GitHub groups:
-    -   <https://github.com/orgs/element-hq/teams/element-web-releasers>
-    -   <https://github.com/orgs/matrix-org/teams/element-web-releasers>
--   You will need access to the **VPN** ([docs](https://gitlab.matrix.org/new-vector/internal/-/wikis/SRE/Tailscale)) to be able to follow the instructions under Deploy below.
--   You will need the ability to **SSH** in to the production machines to be able to follow the instructions under Deploy below. Ensure that your SSH key has a non-empty passphrase, and you registered your SSH key with Ops. Log a ticket at https://github.com/matrix-org/matrix-ansible-private and ask for:
-    -   Two-factor authentication to be set up on your SSH key. (This is needed to get access to production).
-    -   SSH access to `horme` (staging.element.io and app.element.io)
-    -   Permission to sudo on horme as the user `element`
--   You need "**jumphost**" configuration in your local `~/.ssh/config`. This should have been set up as part of your onboarding.
-
-</blockquote></details>
-
-<details><summary><h1>Overview</h1></summary><blockquote>
-
-```mermaid
-flowchart TD
-    P[[Prepare staging branches]]
-    P --> R1
-
-    subgraph Releasing
-        R1[[Releasing matrix-js-sdk]]
-        R2[[Releasing element-web]]
-        R3[[Releasing element-desktop]]
-
-        R1 --> R2 --> R3
-    end
-
-    R3 --> D1
-
-    subgraph Deploying
-        D1[\Deploy staging.element.io/]
-        D2[\Check dockerhub/]
-        D3[\Deploy app.element.io/]
-        D4[\Check desktop package/]
-
-        D1 --> D2 --> D
-        D{FINAL?}
-        D -->|Yes| D3 --> D4
-    end
-
-    D -->|No| H1
-    D4 --> H1
-
-    subgraph Housekeeping
-        H1[\Update topics/]
-        H2[\Announce/]
-        H3[\Archive done column/]
-        H4[\Add diary entry/]
-        H5[\Renovate/]
-
-        H1 --> H2 --> H
-
-        H{FINAL?}
-        H -->|Yes| H3 --> H4 --> DONE
-        H -->|No| H5
-    end
-
-    DONE([You are done!])
-    H5 --> DONE
-```
-
-</blockquote></details>
-
----
-
-# Preparation
-
-The goal of this stage is to get the code you want to ship onto the `staging` branch.
-There are multiple ways to accomplish this depending on the type of release you need to perform.
-
-For the first RC in a given release cycle the easiest way to prepare branches is using the
-[Cut branches automation](https://github.com/element-hq/element-web/actions/workflows/release_prepare.yml) -
-this will take `develop` and merge it into the `staging` on the chosen repositories.
-
-For subsequent RCs, if you need to include a change you may PR it directly to the `staging` branch or rely on the
-backport automation via labelling a PR to `develop` with `backport staging` which will cause a new PR to be opened
-which backports the requested change to the `staging` branch.
-
-For security, you may wish to merge the security advisory private fork or apply the patches manually and then push them directly to `staging`.
-It is worth noting that at the end of the Final/Hotfix/Security release `staging` is merged to `master` which is merged back into `develop` -
-this means that any commit which goes to `staging` will eventually make its way back to the default branch.
-
--   [ ] The staging branch is prepared
-
-# Releasing
-
-Shortly after concluding the preparation stage (or pushing any changes to `staging` in general);
-a draft release will be automatically made on the 4 project repositories with suggested changelogs and version numbers.
-
-_Note: we should add a step here to write summaries atop the changelogs manually, or via AI_
-
-Publishing the SDKs to npm also commits a dependency upgrade to the relevant downstream projects,
-if you skip a layer of this release (e.g. for a hotfix) then the dependency will remain on `#develop` which will be
-switched back to the version of the dependency from the master branch to not leak develop code into a release.
-
-### Matrix JS SDK
-
--   [ ] Check the draft release which has been generated by [the automation](https://github.com/matrix-org/matrix-js-sdk/actions/workflows/release-drafter.yml)
--   [ ] Make any changes to the release notes in the draft release as are necessary - **Do not click publish, only save draft**
--   [ ] Kick off a release using [the automation](https://github.com/matrix-org/matrix-js-sdk/actions/workflows/release.yml) - making sure to select the right type of release. For anything other than an RC: choose final. You should not need to ever switch off either of the Publishing options.
-
-### Element Web
-
--   [ ] Check the draft release which has been generated by [the automation](https://github.com/element-hq/element-web/actions/workflows/release-drafter.yml)
--   [ ] Make any changes to the release notes in the draft release as are necessary - **Do not click publish, only save draft**
--   [ ] Kick off a release using [the automation](https://github.com/element-hq/element-web/actions/workflows/release.yml) - making sure to select the right type of release. For anything other than an RC: choose final. You should not need to ever switch off either of the Publishing options.
-
-### Element Desktop
-
--   [ ] Check the draft release which has been generated by [the automation](https://github.com/element-hq/element-desktop/actions/workflows/release-drafter.yml)
--   [ ] Make any changes to the release notes in the draft release as are necessary - **Do not click publish, only save draft**
--   [ ] Kick off a release using [the automation](https://github.com/element-hq/element-desktop/actions/workflows/release.yml) - making sure to select the right type of release. For anything other than an RC: choose final. You should not need to ever switch off either of the Publishing options.
-
-# Deploying
-
-We ship the SDKs to npm, this happens as part of the release process.
-We ship Element Web to dockerhub, `*.element.io`, and packages.element.io.
-We ship Element Desktop to packages.element.io.
-
--   [ ] Check that element-web has shipped to dockerhub
--   [ ] Deploy staging.element.io. [See docs.](https://handbook.element.io/books/element-web-team/page/deploying-appstagingelementio)
--   [ ] Test staging.element.io
-
-For final releases additionally do these steps:
-
--   [ ] Deploy app.element.io. [See docs.](https://handbook.element.io/books/element-web-team/page/deploying-appstagingelementio)
--   [ ] Test app.element.io
--   [ ] Ensure Element Web package has shipped to packages.element.io
--   [ ] Ensure Element Desktop packages have shipped to packages.element.io
-
-# Housekeeping
-
-We have some manual housekeeping to do in order to prepare for the next release.
-
--   [ ] Update topics using [the automation](https://github.com/element-hq/element-web/actions/workflows/update-topics.yaml). It will autodetect the current latest version. Don't forget the date you supply should be e.g. September 5th (including the "th") for the script to work.
--   [ ] Announce the release in [#element-web-announcements:matrix.org](https://matrix.to/#/#element-web-announcements:matrix.org)
-
-<details><summary>(show)</summary>
-
-With wording like:
-
-> Element Web v1.11.24 is here!
->
-> This version adds ... and fixes bugs ...
->
-> Check it out at app.element.io, in Element Desktop, or from Docker Hub. Changelog and more details at https://github.com/element-hq/element-web/releases/tag/v1.11.24
-
-</details>
-
-For the first RC of a given release cycle do these steps:
-
--   [ ] Go to the [matrix-js-sdk Renovate dashboard](https://github.com/matrix-org/matrix-js-sdk/issues/2406) and click the checkbox to create/update its PRs.
-
--   [ ] Go to the [element-web Renovate dashboard](https://github.com/element-hq/element-web/issues/22941) and click the checkbox to create/update its PRs.
-
--   [ ] Go to the [element-desktop Renovate dashboard](https://github.com/element-hq/element-desktop/issues/465) and click the checkbox to create/update its PRs.
-
--   [ ] Later, check back and merge the PRs that succeeded to build. The ones that failed will get picked up by the [maintainer](https://docs.google.com/document/d/1V5VINWXATMpz9UBw4IKmVVB8aw3CxM0Jt7igtHnDfSk/edit#).
-
-For final releases additionally do these steps:
-
--   [ ] Archive done column on the [team board](https://github.com/orgs/element-hq/projects/67/views/34) _Note: this should be automated_
--   [ ] Add entry to the [milestones diary](https://docs.google.com/document/d/1cpRFJdfNCo2Ps6jqzQmatzbYEToSrQpyBug0aP_iwZE/edit#heading=h.6y55fw4t283z). The document says only to add significant releases, but we add all of them just in case.

docs/room-list-store.md

@@ -1,165 +0,0 @@
-# Room list sorting
-
-It's so complicated it needs its own README.
-
-![](img/RoomListStore2.png)
-
-Legend:
-
--   Orange = External event.
--   Purple = Deterministic flow.
--   Green = Algorithm definition.
--   Red = Exit condition/point.
--   Blue = Process definition.
-
-## Algorithms involved
-
-There's two main kinds of algorithms involved in the room list store: list ordering and tag sorting.
-Throughout the code an intentional decision has been made to call them the List Algorithm and Sorting
-Algorithm respectively. The list algorithm determines the primary ordering of a given tag whereas the
-tag sorting defines how rooms within that tag get sorted, at the discretion of the list ordering.
-
-Behaviour of the overall room list (sticky rooms, etc) are determined by the generically-named Algorithm
-class. Here is where much of the coordination from the room list store is done to figure out which list
-algorithm to call, instead of having all the logic in the room list store itself.
-
-Tag sorting is effectively the comparator supplied to the list algorithm. This gives the list algorithm
-the power to decide when and how to apply the tag sorting, if at all. For example, the importance algorithm,
-later described in this document, heavily uses the list ordering behaviour to break the tag into categories.
-Each category then gets sorted by the appropriate tag sorting algorithm.
-
-### Tag sorting algorithm: Alphabetical
-
-When used, rooms in a given tag will be sorted alphabetically, where the alphabet's order is a problem
-for the browser. All we do is a simple string comparison and expect the browser to return something
-useful.
-
-### Tag sorting algorithm: Manual
-
-Manual sorting makes use of the `order` property present on all tags for a room, per the
-[Matrix specification](https://matrix.org/docs/spec/client_server/r0.6.0#room-tagging). Smaller values
-of `order` cause rooms to appear closer to the top of the list.
-
-### Tag sorting algorithm: Recent
-
-Rooms get ordered by the timestamp of the most recent useful message. Usefulness is yet another algorithm
-in the room list system which determines whether an event type is capable of bubbling up in the room list.
-Normally events like room messages, stickers, and room security changes will be considered useful enough
-to cause a shift in time.
-
-Note that this is reliant on the event timestamps of the most recent message. Because Matrix is eventually
-consistent this means that from time to time a room might plummet or skyrocket across the tag due to the
-timestamp contained within the event (generated server-side by the sender's server).
-
-### List ordering algorithm: Natural
-
-This is the easiest of the algorithms to understand because it does essentially nothing. It imposes no
-behavioural changes over the tag sorting algorithm and is by far the simplest way to order a room list.
-Historically, it's been the only option in Element and extremely common in most chat applications due to
-its relative deterministic behaviour.
-
-### List ordering algorithm: Importance
-
-On the other end of the spectrum, this is the most complicated algorithm which exists. There's major
-behavioural changes, and the tag sorting algorithm gets selectively applied depending on circumstances.
-
-Each tag which is not manually ordered gets split into 4 sections or "categories". Manually ordered tags
-simply get the manual sorting algorithm applied to them with no further involvement from the importance
-algorithm. There are 4 categories: Red, Grey, Bold, and Idle. Each has their own definition based off
-relative (perceived) importance to the user:
-
--   **Red**: The room has unread mentions waiting for the user.
--   **Grey**: The room has unread notifications waiting for the user. Notifications are simply unread
-    messages which cause a push notification or badge count. Typically, this is the default as rooms get
-    set to 'All Messages'.
--   **Bold**: The room has unread messages waiting for the user. Essentially this is a grey room without
-    a badge/notification count (or 'Mentions Only'/'Muted').
--   **Idle**: No useful (see definition of useful above) activity has occurred in the room since the user
-    last read it.
-
-Conveniently, each tag gets ordered by those categories as presented: red rooms appear above grey, grey
-above bold, etc.
-
-Once the algorithm has determined which rooms belong in which categories, the tag sorting algorithm
-gets applied to each category in a sub-list fashion. This should result in the red rooms (for example)
-being sorted alphabetically amongst each other as well as the grey rooms sorted amongst each other, but
-collectively the tag will be sorted into categories with red being at the top.
-
-## Sticky rooms
-
-When the user visits a room, that room becomes 'sticky' in the list, regardless of ordering algorithm.
-From a code perspective, the underlying algorithm is not aware of a sticky room and instead the base class
-manages which room is sticky. This is to ensure that all algorithms handle it the same.
-
-The sticky flag is simply to say it will not move higher or lower down the list while it is active. For
-example, if using the importance algorithm, the room would naturally become idle once viewed and thus
-would normally fly down the list out of sight. The sticky room concept instead holds it in place, never
-letting it fly down until the user moves to another room.
-
-Only one room can be sticky at a time. Room updates around the sticky room will still hold the sticky
-room in place. The best example of this is the importance algorithm: if the user has 3 red rooms and
-selects the middle room, they will see exactly one room above their selection at all times. If they
-receive another notification which causes the room to move into the topmost position, the room that was
-above the sticky room will move underneath to allow for the new room to take the top slot, maintaining
-the sticky room's position.
-
-Though only applicable to the importance algorithm, the sticky room is not aware of category boundaries
-and thus the user can see a shift in what kinds of rooms move around their selection. An example would
-be the user having 4 red rooms, the user selecting the third room (leaving 2 above it), and then having
-the rooms above it read on another device. This would result in 1 red room and 1 other kind of room
-above the sticky room as it will try to maintain 2 rooms above the sticky room.
-
-An exception for the sticky room placement is when there's suddenly not enough rooms to maintain the placement
-exactly. This typically happens if the user selects a room and leaves enough rooms where it cannot maintain
-the N required rooms above the sticky room. In this case, the sticky room will simply decrease N as needed.
-The N value will never increase while selection remains unchanged: adding a bunch of rooms after having
-put the sticky room in a position where it's had to decrease N will not increase N.
-
-## Responsibilities of the store
-
-The store is responsible for the ordering, upkeep, and tracking of all rooms. The room list component simply gets
-an object containing the tags it needs to worry about and the rooms within. The room list component will
-decide which tags need rendering (as it commonly filters out empty tags in most cases), and will deal with
-all kinds of filtering.
-
-## Filtering
-
-Filters are provided to the store as condition classes and have two major kinds: Prefilters and Runtime.
-
-Prefilters flush out rooms which shouldn't appear to the algorithm implementations. Typically this is
-due to some higher order room list filtering (such as spaces or tags) deliberately exposing a subset of
-rooms to the user. The algorithm implementations will not see a room being prefiltered out.
-
-Runtime filters are used for more dynamic filtering, such as the user filtering by room name. These
-filters are passed along to the algorithm implementations where those implementations decide how and
-when to apply the filter. In practice, the base `Algorithm` class ends up doing the heavy lifting for
-optimization reasons.
-
-The results of runtime filters get cached to avoid needlessly iterating over potentially thousands of
-rooms, as the old room list store does. When a filter condition changes, it emits an update which (in this
-case) the `Algorithm` class will pick up and act accordingly. Typically, this also means filtering a
-minor subset where possible to avoid over-iterating rooms.
-
-All filter conditions are considered "stable" by the consumers, meaning that the consumer does not
-expect a change in the condition unless the condition says it has changed. This is intentional to
-maintain the caching behaviour described above.
-
-One might ask why we don't just use prefilter conditions for everything, and the answer is one of slight
-subtlety: in the cases of prefilters we are knowingly exposing the user to a workspace-style UX where
-room notifications are self-contained within that workspace. Runtime filters tend to not want to affect
-visible notification counts (as it doesn't want the room header to suddenly be confusing to the user as
-they type), and occasionally UX like "found 2/12 rooms" is desirable. If prefiltering were used instead,
-the notification counts would vary while the user was typing and "found 2/12" UX would not be possible.
-
-## Class breakdowns
-
-The `RoomListStore` is the major coordinator of various algorithm implementations, which take care
-of the various `ListAlgorithm` and `SortingAlgorithm` options. The `Algorithm` class is responsible
-for figuring out which tags get which rooms, as Matrix specifies them as a reverse map: tags get
-defined on rooms and are not defined as a collection of rooms (unlike how they are presented to the
-user). Various list-specific utilities are also included, though they are expected to move somewhere
-more general when needed. For example, the `membership` utilities could easily be moved elsewhere
-as needed.
-
-The various bits throughout the room list store should also have jsdoc of some kind to help describe
-what they do and how they work.

docs/scrolling.md

@@ -1,27 +0,0 @@
-# ScrollPanel
-
-## Updates
-
-During an onscroll event, we check whether we're getting close to the top or bottom edge of the loaded content. If close enough, we fire a request to load more through the callback passed in the `onFillRequest` prop. This returns a promise is passed down from `TimelinePanel`, where it will call paginate on the `TimelineWindow` and once the events are received back, update its state with the new events. This update trickles down to the `MessagePanel`, which rerenders all tiles and passed that to `ScrollPanel`. ScrollPanels `componentDidUpdate` method gets called, and we do the scroll housekeeping there (read below). Once the rerender has completed, the `setState` callback is called and we resolve the promise returned by `onFillRequest`. Now we check the DOM to see if we need more fill requests.
-
-## Prevent Shrinking
-
-ScrollPanel supports a mode to prevent it shrinking. This is used to prevent a jump when at the bottom of the timeline and people start and stop typing. It gets cleared automatically when 200px above the bottom of the timeline.
-
-## BACAT (Bottom-Aligned, Clipped-At-Top) scrolling
-
-BACAT scrolling implements a different way of restoring the scroll position in the timeline while tiles out of view are changing height or tiles are being added or removed. It was added in https://github.com/matrix-org/matrix-react-sdk/pull/2842.
-
-The motivation for the changes is having noticed that setting scrollTop while scrolling tends to not work well, with it interrupting ongoing scrolling and also querying scrollTop reporting outdated values and consecutive scroll adjustments cancelling each out previous ones. This seems to be worse on macOS than other platforms, presumably because of a higher resolution in scroll events there. Also see https://github.com/vector-im/element-web/issues/528. The BACAT approach allows to only have to change the scroll offset when adding or removing tiles.
-
-The approach taken instead is to vertically align the timeline tiles to the bottom of the scroll container (using flexbox) and give the timeline inside the scroll container an explicit height, initially set to a multiple of the PAGE_SIZE (400px at time of writing) as needed by the content. When scrolled up, we can compensate for anything that grew below the viewport by changing the height of the timeline to maintain what's currently visible in the viewport without adjusting the scrollTop and hence without jumping.
-
-For anything above the viewport growing or shrinking, we don't need to do anything as the timeline is bottom-aligned. We do need to update the height manually to keep all content visible as more is loaded. To maintain scroll position after the portion above the viewport changes height, we need to set the scrollTop, as we cannot balance it out with more height changes. We do this 100ms after the user has stopped scrolling, so setting scrollTop has not nasty side-effects.
-
-As of https://github.com/matrix-org/matrix-react-sdk/pull/4166, we are scrolling to compensate for height changes by calling `scrollBy(0, x)` rather than reading and than setting `scrollTop`, as reading `scrollTop` can (again, especially on macOS) easily return values that are out of sync with what is on the screen, probably because scrolling can be done [off the main thread](https://wiki.mozilla.org/Platform/GFX/APZ) in some circumstances. This seems to further prevent jumps.
-
-### How does it work?
-
-`componentDidUpdate` is called when a tile in the timeline is updated (as we rerender the whole timeline) or tiles are added or removed (see Updates section before). From here, `checkScroll` is called, which calls `restoreSavedScrollState`. Now, we increase the timeline height if something below the viewport grew by adjusting `this.bottomGrowth`. `bottomGrowth` is the height added to the timeline (on top of the height from the number of pages calculated at the last `updateHeight` run) to compensate for growth below the viewport. This is cleared during the next run of `updateHeight`. Remember that the tiles in the timeline are aligned to the bottom.
-
-From `restoreSavedScrollState` we also call `updateHeight` which waits until the user stops scrolling for 100ms and then recalculates the amount of pages of 400px the timeline should be sized to, to be able to show all of its (newly added) content. We have to adjust the scroll offset (which is why we wait until scrolling has stopped) now because the space above the viewport has likely changed.

docs/settings.md

@@ -1,236 +0,0 @@
-# Settings Reference
-
-This document serves as developer documentation for using "Granular Settings". Granular Settings allow users to specify
-different values for a setting at particular levels of interest. For example, a user may say that in a particular room
-they want URL previews off, but in all other rooms they want them enabled. The `SettingsStore` helps mask the complexity
-of dealing with the different levels and exposes easy to use getters and setters.
-
-## Levels
-
-Granular Settings rely on a series of known levels in order to use the correct value for the scenario. These levels, in
-order of priority, are:
-
--   `device` - The current user's device
--   `room-device` - The current user's device, but only when in a specific room
--   `room-account` - The current user's account, but only when in a specific room
--   `account` - The current user's account
--   `room` - A specific room (setting for all members of the room)
--   `config` - Values are defined by the `setting_defaults` key (usually) in `config.json`
--   `default` - The hardcoded default for the settings
-
-Individual settings may control which levels are appropriate for them as part of the defaults. This is often to ensure
-that room administrators cannot force account-only settings upon participants.
-
-## Settings
-
-Settings are the different options a user may set or experience in the application. These are pre-defined in
-`src/settings/Settings.tsx` under the `SETTINGS` constant, and match the `ISetting` interface as defined there.
-
-Settings that support the config level can be set in the config file under the `setting_defaults` key (note that some
-settings, like the "theme" setting, are special cased in the config file):
-
-```json5
-{
-  ...
-  "setting_defaults": {
-    "settingName": true
-  },
-  ...
-}
-```
-
-### Getting values for a setting
-
-After importing `SettingsStore`, simply make a call to `SettingsStore.getValue`. The `roomId` parameter should always
-be supplied where possible, even if the setting does not have a per-room level value. This is to ensure that the value
-returned is best represented in the room, particularly if the setting ever gets a per-room level in the future.
-
-In settings pages it is often desired to have the value at a particular level instead of getting the calculated value.
-Call `SettingsStore.getValueAt` to get the value of a setting at a particular level, and optionally make it explicitly
-at that level. By default `getValueAt` will traverse the tree starting at the provided level; making it explicit means
-it will not go beyond the provided level. When using `getValueAt`, please be sure to use `SettingLevel` to represent the
-target level.
-
-### Setting values for a setting
-
-Values are defined at particular levels and should be done in a safe manner. There are two checks to perform to ensure a
-clean save: is the level supported and can the user actually set the value. In most cases, neither should be an issue
-although there are circumstances where this changes. An example of a safe call is:
-
-```javascript
-const isSupported = SettingsStore.isLevelSupported(SettingLevel.ROOM);
-if (isSupported) {
-    const canSetValue = SettingsStore.canSetValue("mySetting", "!curbf:matrix.org", SettingLevel.ROOM);
-    if (canSetValue) {
-        SettingsStore.setValue("mySetting", "!curbf:matrix.org", SettingLevel.ROOM, newValue);
-    }
-}
-```
-
-These checks may also be performed in different areas of the application to avoid the verbose example above. For
-instance, the component which allows changing the setting may be hidden conditionally on the above conditions.
-
-##### `SettingsFlag` component
-
-Where possible, the `SettingsFlag` component should be used to set simple "flip-a-bit" (true/false) settings. The
-`SettingsFlag` also supports simple radio button options, such as the theme the user would like to use.
-
-```TSX
-<SettingsFlag name="theSettingId" level={SettingsLevel.ROOM} roomId="!curbf:matrix.org"
-    label={_td("Your label here")} // optional, if falsey then the `SettingsStore` will be used
-    onChange={function(newValue) { }} // optional, called after saving
-    isExplicit={false} // this is passed along to `SettingsStore.getValueAt`, defaulting to false
-    manualSave={false} // if true, saving is delayed. You will need to call .save() on this component
-
-    // Options for radio buttons
-    group="your-radio-group" // this enables radio button support
-    value="yourValueHere" // the value for this particular option
-/>
-```
-
-### Getting the display name for a setting
-
-Simply call `SettingsStore.getDisplayName`. The appropriate display name will be returned and automatically translated
-for you. If a display name cannot be found, it will return `null`.
-
-## Features
-
-Feature flags are just like regular settings with some underlying semantics for how they are meant to be used. Usually
-a feature flag is used when a portion of the application is under development or not ready for full release yet, such
-as new functionality or experimental ideas. In these cases, the feature name _should_ be named with the `feature_*`
-convention and must be tagged with `isFeature: true` in the setting definition. By doing so, the feature will automatically
-appear in the "labs" section of the user's settings.
-
-Features can be controlled at the config level using the following structure:
-
-```json
-"features": {
-  "feature_lazyloading": true
-}
-```
-
-When `true`, the user will see the feature as enabled. Similarly, when `false` the user will see the feature as disabled.
-The user will only be able to change/see these states if `show_labs_settings: true` is in the config.
-
-### Determining if a feature is enabled
-
-Call `SettingsStore.getValue()` as you would for any other setting.
-
-### Enabling a feature
-
-Call `SettingsStore.setValue("feature_name", null, SettingLevel.DEVICE, true)`.
-
-### A note on UI features
-
-UI features are a different concept to plain features. Instead of being representative of unstable or
-unpredicatable behaviour, they are logical chunks of UI which can be disabled by deployments for ease
-of understanding with users. They are simply represented as boring settings with a convention of being
-named as `UIFeature.$location` where `$location` is a rough descriptor of what is toggled, such as
-`URLPreviews` or `Communities`.
-
-UI features also tend to have their own setting controller (see below) to manipulate settings which might
-be affected by the UI feature being disabled. For example, if URL previews are disabled as a UI feature
-then the URL preview options will use the `UIFeatureController` to ensure they remain disabled while the
-UI feature is disabled.
-
-## Setting controllers
-
-Settings may have environmental factors that affect their value or need additional code to be called when they are
-modified. A setting controller is able to override the calculated value for a setting and react to changes in that
-setting. Controllers are not a replacement for the level handlers and should only be used to ensure the environment is
-kept up to date with the setting where it is otherwise not possible. An example of this is the notification settings:
-they can only be considered enabled if the platform supports notifications, and enabling notifications requires
-additional steps to actually enable notifications.
-
-For more information, see `src/settings/controllers/SettingController.ts`.
-
-## Local echo
-
-`SettingsStore` will perform local echo on all settings to ensure that immediately getting values does not cause a
-split-brain scenario. As mentioned in the "Setting values for a setting" section, the appropriate checks should be done
-to ensure that the user is allowed to set the value. The local echo system assumes that the user has permission and that
-the request will go through successfully. The local echo only takes effect until the request to save a setting has
-completed (either successfully or otherwise).
-
-```javascript
-SettingsStore.setValue(...).then(() => {
-  // The value has actually been stored at this point.
-});
-SettingsStore.getValue(...); // this will return the value set in `setValue` above.
-```
-
-## Watching for changes
-
-Most use cases do not need to set up a watcher because they are able to react to changes as they are made, or the
-changes which are made are not significant enough for it to matter. Watchers are intended to be used in scenarios where
-it is important to react to changes made by other logged in devices. Typically, this would be done within the component
-itself, however the component should not be aware of the intricacies of setting inversion or remapping to particular
-data structures. Instead, a generic watcher interface is provided on `SettingsStore` to watch (and subsequently unwatch)
-for changes in a setting.
-
-An example of a watcher in action would be:
-
-```javascript
-class MyComponent extends React.Component {
-    settingWatcherRef = null;
-
-    componentDidMount() {
-        const callback = (settingName, roomId, level, newValAtLevel, newVal) => {
-            this.setState({ color: newVal });
-        };
-        this.settingWatcherRef = SettingsStore.watchSetting("roomColor", "!example:matrix.org", callback);
-    }
-
-    componentWillUnmount() {
-        SettingsStore.unwatchSetting(this.settingWatcherRef);
-    }
-}
-```
-
-# Maintainers Reference
-
-The granular settings system has a few complex parts to power it. This section is to document how the `SettingsStore` is
-supposed to work.
-
-### General information
-
-The `SettingsStore` uses the hardcoded `LEVEL_ORDER` constant to ensure that it is using the correct override procedure.
-The array is checked from left to right, simulating the behaviour of overriding values from the higher levels. Each
-level should be defined in this array, including `default`.
-
-Handlers (`src/settings/handlers/SettingsHandler.ts`) represent a single level and are responsible for getting and
-setting values at that level. Handlers also provide additional information to the `SettingsStore` such as if the level
-is supported or if the current user may set values at the level. The `SettingsStore` will use the handler to enforce
-checks and manipulate settings. Handlers are also responsible for dealing with migration patterns or legacy settings for
-their level (for example, a setting being renamed or using a different key from other settings in the underlying store).
-Handlers are provided to the `SettingsStore` via the `LEVEL_HANDLERS` constant. `SettingsStore` will optimize lookups by
-only considering handlers that are supported on the platform.
-
-Local echo is achieved through `src/settings/handlers/LocalEchoWrapper.ts` which acts as a wrapper around a given
-handler. This is automatically applied to all defined `LEVEL_HANDLERS` and proxies the calls to the wrapped handler
-where possible. The echo is achieved by a simple object cache stored within the class itself. The cache is invalidated
-immediately upon the proxied save call succeeding or failing.
-
-Controllers are notified of changes by the `SettingsStore`, and are given the opportunity to override values after the
-`SettingsStore` has deemed the value calculated. Controllers are invoked as the last possible step in the code.
-
-### Features
-
-See above for feature reference.
-
-### Watchers
-
-Watchers can appear complicated under the hood: there is a central `WatchManager` which handles the actual invocation
-of callbacks, and callbacks are managed by the SettingsStore by redirecting the caller's callback to a dedicated
-callback. This is done so that the caller can reuse the same function as their callback without worrying about whether
-or not it'll unsubscribe all watchers.
-
-Setting changes are emitted into the default `WatchManager`, which calculates the new value for the setting. Ideally,
-we'd also try and suppress updates which don't have a consequence on this value, however there's not an easy way to do
-this. Instead, we just dispatch an update for all changes and leave it up to the consumer to deduplicate.
-
-In practice, handlers which rely on remote changes (account data, room events, etc) will always attach a listener to the
-`MatrixClient`. They then watch for changes to events they care about and send off appropriate updates to the
-generalized `WatchManager` - a class specifically designed to deduplicate the logic of managing watchers. The handlers
-which are localized to the local client (device) generally just trigger the `WatchManager` when they manipulate the
-setting themselves as there's nothing to really 'watch'.