decidim 0.30.1 → 0.31.0.rc1

data/docs/modules/develop/pages/maintainers/releases.adoc

@@ -2,187 +2,6 @@
 
 In order to release new version you need to be owner of all the gems at RubyGems, ask one of the owners to add you before releasing. Try `gem owner decidim` to find out the owners of the gem. It is worth making sure you are owner of all gems.
 
-Remember to follow the Gitflow branching workflow.
-
-== Create the stable branch for the release
-
-. Merge all the https://github.com/decidim/decidim/pulls?q=is%3Apr+is%3Aopen+author%3Adecidim-bot+sort%3Aupdated-desc+base%3Adevelop[Crowdin pull requests created by the user `decidim-bot`], specially the one that is going to be marged against `develop` that should be returned by the provided example search.
-. Go to develop with `git checkout develop`
-. Create the release branch `git checkout -b release/x.y-stable && git push origin release/x.y-stable`.
-. Add the release branch to Crowdin so that any pending translations will generate a PR to this branch. This needs to be done with the generic user `decidim` in the GitHub's Crowdin integration, as this is the user that initially configured the installation and other admins in the Crowdin organization cannot change it. See instructions for this on the "Create the stable branch in Crowdin". Note that after the branch is configured at Crowdin, it takes some time for the synchronization to happen, so be prepared to wait a couple of hours.
-
-Mark `develop` as the reference to the next release:
-
-. Go back to develop with `git checkout develop`
-. Turn develop into the `dev` branch for the next release:
- .. Update `.decidim-version` to the new `dev` development version: `x.y.z.dev`, where `x.y.z` is the new semver number for the next version
- .. Run `bin/rake update_versions`, this will update all references to the new version.
- .. Run `bin/rake patch_generators`, this will update the Gemfile for the generators to the new version.
- .. Run `bin/rake bundle`, this will update all the `Gemfile.lock` files
- .. Run `bin/rake webpack`, this will update the JavaScript bundle.
-. Update `SECURITY.md` and change the supported version to the new version.
-. Update the `CHANGELOG.md`.
-At the top you should have an `Unreleased` header and under that the content `Nothing.`. The CHANGELOG is automatically generated for the release branches so do not worry about its actual contents at the `develop` branch.
-After that, the header with the current version and link with the same beforementioned sections and a `Previous versions` header at the bottom that links to the previous minor release stable branch.
-
-[source,markdown]
-----
-# Changelog
-
-## [Unreleased](https://github.com/decidim/decidim/tree/HEAD)
-
-Nothing.
-
-...
-
-## Previous versions
-
-Please check [0.XX-stable](https://github.com/decidim/decidim/blob/release/0.XX-stable/CHANGELOG.md) for previous changes.
-----
-
-. Update the `RELEASE_NOTES.md`
-You can use the following template for the new `RELEASE_NOTES.md`:
-
-[source,markdown]
-----
-# Release Notes
-
-## 1. Upgrade notes
-
-As usual, we recommend that you have a full backup, of the database, application code and static files.
-
-To update, follow these steps:
-
-### 1.1. Update your Gemfile
-
-```ruby
-gem "decidim", github: "decidim/decidim"
-gem "decidim-dev", github: "decidim/decidim"
-```
-
-### 1.2. Run these commands
-
-```console
-bundle update decidim
-bin/rails decidim:upgrade
-bin/rails db:migrate
-```
-
-### 1.3. Follow the steps and commands detailed in these notes
-
-## 2. General notes
-
-## 3. One time actions
-
-These are one time actions that need to be done after the code is updated in the production database.
-
-### 3.1. [[TITLE OF THE ACTION]]
-
-You can read more about this change on PR [\#XXXX](https://github.com/decidim/decidim/pull/XXXX).
-
-## 4. Scheduled tasks
-
-Implementers need to configure these changes it in your scheduler task system in the production server. We give the examples
- with `crontab`, although alternatively you could use `whenever` gem or the scheduled jobs of your hosting provider.
-
-### 4.1. [[TITLE OF THE TASK]]
-
-```bash
-4 0 * * * cd /home/user/decidim_application && RAILS_ENV=production bundle exec rails decidim:TASK
-```
-
-You can read more about this change on PR [\#XXXX](https://github.com/decidim/decidim/pull/XXXX).
-
-## 5. Changes in APIs
-
-### 5.1. [[TITLE OF THE CHANGE]]
-
-In order to [[REASONING (e.g. improve the maintenance of the code base)]] we have changed...
-
-If you have used code as such:
-
-```ruby
-# Explain the usage of the API as it was in the previous version
-result = 1 + 1 if before
-```
-
-You need to change it to:
-
-```ruby
-# Explain the usage of the API as it is in the new version
-result = 1 + 1 if after
-```
-----
-
-. Push the changes `git add . && git commit -m "Bump develop to next release version" && git push origin develop`
-
-== Create the stable branch in Crowdin
-
-. You will need to first create the version branch in Crowdin
- .. Sign in as manager in Crowdin.
- .. Go to the https://translate.decidim.org/project/decidim/content/files[Content tab in the Decidim project]
- .. Click on the dropdown of the "New folder" button (top right) and select "New Version Branch"
- .. On the modal, add the name of the branch. As it does not allow the slash character in the name ("/") you will need to change it to a dot ("."). So, for instance, "release/0.20-stable" would become "release.0.20-stable". See other releases if in doubt, it should be consistent.
- .. After creating the version branch, edit it and change the "Title as it appears to translators" to the name with the slash ("release/0.20-stable")
-. Then you will be able to setup the GitHub integration in Crowdin
- .. Sign in as user "Decidim" in Crowdin. NOTE: this user is the only one that can do this.
- .. Go to the https://translate.decidim.org/project/decidim/apps[Integrations tab in the Decidim project]
- .. Click on GitHub
- .. Click on the "Edit" button
- .. In the "Select Branches for Translation", search the branch. Click on it.
- .. Change the "Service Branch Name" to be consistent with the other branches. So, for instance, "release/0.20-stable" would become "chore/l10n/release/0.20-stable".
- .. Click on "Save"
- .. After a couple of hours, if there are any changes in Crowdin that would involve this branch, you will see the correspondent "Decidim bot" Pull Request in GitHub.
-
-== Producing the CHANGELOG.md
-
-Look for the "Bump develop to next release version" commit sha1.
-You can do it either visually with `gitk .decidim-version` or by blaming `git blame .decidim-version`.
-
-Here you have different options to see what happened from one revision to another:
-
-[source,bash]
-----
-git log v0.20.0..v0.20.1 --grep " (#[0-9]\+)" --oneline
-git log <SHA>..HEAD --grep " (#[0-9]\+)" --oneline
-----
-
-Once you have checked the list of changes, it is time to actually generating the changelog.
-
-[source,bash]
-----
-bin/changelog_generator
-----
-
-In order to generate the changelog, you need to know the SHA hash of the first commit that was not part of the previous release. You can check the commit hash by inspecting the commit log of the `.decidim-version` file as follows when in the correct release branch:
-
-[source,bash]
-----
-git log -1 --format=oneline .decidim-version
-----
-
-Alternatively, you can find the first commit after the point of time that the two release branches have separated from each other as follows:
-
-[source,bash]
-----
-git log --reverse --pretty=format:"%H" $(git merge-base release/0.XX-stable release/0.YY-stable)..release/0.YY-stable | head -1
-----
-
-In the above command, replace `0.XX` with the previous release and `0.YY` with the current release you are generating the change log for. This command works only for major releases, not for patch or bugfix releases.
-
-Running it as is, or passing it the `--help` flag, will render the help section for the script. In order to actually run the script, follow the instructions:
-
-[source,bash]
-----
-bin/changelog_generator <GITHUB_TOKEN> <SHA>
-----
-
-This command will create a `temporary_changelog.md` in the root of the project, so you can inspect this file and generated changelog.
-
-If you have some elements in the `Unsorted` section of the output, you can review the PRs individually, fix the title and the tags and rerun the script. Those PRs with the tags fixed will be automatically sorted. Labelling the PRs as they are opened or merged is encouraged to save some time when producing the changelog.
-
-You can copy-paste the contents of the temporary changelog file to the relevant sections of the Changelog file.
-
 == Release Candidates
 
 Release Candidates are the same as beta versions.
@@ -191,17 +10,19 @@ They should be ready to go to production, but publicly released just before in o
 If this is a *Release Candidate version* release, the steps to follow are:
 
 . Merge all the https://github.com/decidim/decidim/pulls?q=is%3Apr+is%3Aopen+author%3Adecidim-bot+sort%3Aupdated-desc[Crowdin pull requests created by the user `decidim-bot`], specially the one that is going to be marged against the release branch `release/x.y-stable` that should be returned by the provided example search (pick the correct pull request for the release from the results).
-. Checkout the release stable branch `git checkout release/x.y-stable`.
-. Update `.decidim-version` to the new version `x.y.z.rc1`
-. Run `bin/rake update_versions`, this will update all references to the new version.
-. Run `bin/rake patch_generators`, this will update the Gemfile for the generators to the new version.
-. Run `bin/rake bundle`, this will update all the `Gemfile.lock` files
-. Run `bin/rake webpack`, this will update the JavaScript bundle.
-. Run `bin/rspec`, this will check things like if all the officially supported languages translations are OK.
-. Commit all the changes: `git add . && git commit -m "Bump to rcXX version" && git push origin release/x.y-stable`.
-. Wait for the tests to finish and check that everything is passing before releasing the version.
-NOTE: When you bump the version, the generator tests will fail because the gems and NPM packages have not been actually published yet (as in sent to rubygems/npm). You may see errors such as `No matching version found for @decidim/browserslist-config@~0.xx.y` in the CI logs. This should be fine as long as you have ensured that the generators tests passed in the previous commit.
-. Run `git pull && bin/rake release_all`, this will create all the tags, push the commits and tags and release the gems to RubyGems.
+. Go to develop with `git checkout develop`
+. Install the last version of the `decidim-maintainers_toolbox` gem, and run the releaser command. Mind that for this to work you need locally the gh CLI from GitHub.
+[source,bash]
+----
+gem install decidim-maintainers_toolbox
+decidim-releaser --github-token=(gh auth token) --version-type=rc
+----
+. This will create the stable branch and also create two Pull Requests:
+.. One for changing the development version on the `develop` branch (with title "Bump develop to next release version (x.y.z)")
+.. Another for creating the  the new release in the stable branch with title `Bump to vx.y.z version`. Wait for the tests to finish and check that everything is passing before releasing the version.
+During this process you will have the instructions on how to follow with the process in the command line. One of the tasks is updating Crowdin, you can read more about this in the "Create the stable branch in Crowdin" section of this page.
+. Review, accept and merge the Pull Request.
+. Run `git pull && bin/rake release_all`, this will create all the tags, push the commits and tags and release the gems to RubyGems. Be ready for the One Time Password fill for each of the gems.
 
 Usually, at this point, the release branch is deployed to Metadecidim during, at least, one week to validate the stability of the version.
 
@@ -278,17 +99,16 @@ The process is very similar from releasing a new Decidim version:
 . Merge all the https://github.com/decidim/decidim/pulls?q=is%3Apr+is%3Aopen+author%3Adecidim-bot+sort%3Aupdated-desc[Crowdin pull requests created by the user `decidim-bot`], specially the one that is going to be marged against the release branch `release/x.y-stable` that should be returned by the provided example search (pick the correct pull request for the release from the results).
 . Make sure that there are no more PRs to backport. Learn more about xref:develop:backports.adoc[Backports].
 . Checkout the branch you want to release: `git checkout -b release/x.y-stable`
-. Update `.decidim-version` to the new version number.
-. Run `bin/rake update_versions`, this will update all references to the new version.
-. Run `bin/rake patch_generators`, this will update the Gemfile for the generators to the new version.
-. Run `bin/rake bundle`, this will update all the `Gemfile.lock` files
-. Run `bin/rake webpack`, this will update the JavaScript bundle.
-. Update the `CHANGELOG.md`.
-Add the header with the current version and link like `+## [0.20.0](https://github.com/decidim/decidim/tree/v0.20.0)+` and the headers generated by the changelog generator.
-. Commit all the changes: `git add . && git commit -m "Prepare VERSION release"`
-. Wait for the tests to finish and check that everything is passing before releasing the version.
+. Install the last version of the `decidim-maintainers_toolbox` gem, and run the releaser command. Mind that for this to work you need locally the gh CLI from GitHub.
+[source,bash]
+----
+gem install decidim-maintainers_toolbox
+decidim-releaser --github-token=(gh auth token) --version-type=patch
+----
+. This will create a Pull Request for the new release with title `Bump to vx.y.z version`. Wait for the tests to finish and check that everything is passing before releasing the version.
 NOTE: When you bump the version, the generator tests will fail because the gems and NPM packages have not been actually published yet (as in sent to rubygems/npm). You may see errors such as `No matching version found for @decidim/browserslist-config@~0.xx.y` in the CI logs. This should be fine as long as you have ensured that the generators tests passed in the previous commit.
-. Run `git pull && bin/rake release_all`, this will create all the tags, push the commits and tags and release the gems to RubyGems.
+. Review, accept and merge the Pull Request.
+. Run `git pull && bin/rake release_all`, this will create all the tags, push the commits and tags and release the gems to RubyGems. Be ready for the One Time Password fill for each of the gems.
 . Once all the gems are published:
  .. Re-run the failed generators tests at the release branch.
  .. Create a new release at this repository, just go to the https://github.com/decidim/decidim/releases[releases page] and create a new one.
@@ -297,3 +117,21 @@ NOTE: When you bump the version, the generator tests will fail because the gems
 == Docker images for each release
 
 Each release triggers a https://github.com/decidim/decidim/blob/develop/.github/workflows/on_release.yml[GitHub workflow] that rebuilds and publishes the https://github.com/decidim/docker[decidim/docker images] to https://github.com/orgs/decidim/packages[GitHub Container Registry] and https://hub.docker.com/repository/docker/decidim/decidim[Docker Hub].
+
+== Create the stable branch in Crowdin
+
+. You will need to first create the version branch in Crowdin
+ .. Sign in as manager in Crowdin.
+ .. Go to the https://translate.decidim.org/project/decidim/content/files[Content tab in the Decidim project]
+ .. Click on the dropdown of the "New folder" button (top right) and select "New Version Branch"
+ .. On the modal, add the name of the branch. As it does not allow the slash character in the name ("/") you will need to change it to a dot ("."). So, for instance, "release/0.20-stable" would become "release.0.20-stable". See other releases if in doubt, it should be consistent.
+ .. After creating the version branch, edit it and change the "Title as it appears to translators" to the name with the slash ("release/0.20-stable")
+. Then you will be able to setup the GitHub integration in Crowdin
+ .. Sign in as user "Decidim" in Crowdin. NOTE: this user is the only one that can do this.
+ .. Go to the https://translate.decidim.org/project/decidim/apps[Integrations tab in the Decidim project]
+ .. Click on GitHub
+ .. Click on the "Edit" button
+ .. In the "Select Branches for Translation", search the branch. Click on it.
+ .. Change the "Service Branch Name" to be consistent with the other branches. So, for instance, "release/0.20-stable" would become "chore/l10n/release/0.20-stable".
+ .. Click on "Save"
+ .. After a couple of hours, if there are any changes in Crowdin that would involve this branch, you will see the correspondent "Decidim bot" Pull Request in GitHub.

data/docs/modules/develop/pages/maps.adoc

@@ -95,7 +95,7 @@ In order to provide configuration options for the Geocoder gem's lookup, you can
 ----
 config.maps = {
   provider: :your_provider,
-  api_key: Rails.application.secrets.maps[:api_key],
+  api_key: ENV["MAPS_API_KEY"],
   geocoding: { extra_option: "value", another_option: "value" }
 }
 ----
@@ -106,7 +106,7 @@ This would equal to configuring the Geocoder gem with the following code:
 ----
 Geocoder.configure(
   your_provider: {
-    api_key: Rails.application.secrets.maps[:api_key],
+    api_key: ENV["MAPS_API_KEY"],
     extra_option: "value",
     another_option: "value"
   }
@@ -152,8 +152,8 @@ In order to provide configuration options for the geocoding autocompletion, you
 [source,ruby]
 ----
 config.maps = {
-  provider: :your_provider,
-  api_key: Rails.application.secrets.maps[:api_key],
+  provider: ENV["MAPS_PROVIDER"],
+  api_key: ENV["MAPS_API_KEY"],
   autocomplete: {
     url: "https://photon.example.org/api/"
   }
@@ -353,7 +353,7 @@ In order to provide configuration options for the dynamic maps, you can pass the
 ----
 config.maps = {
   provider: :your_provider,
-  api_key: Rails.application.secrets.maps[:api_key],
+  api_key: ENV["MAPS_API_KEY"],
   dynamic: {
     tile_layer: {
       url: "https://tiles.example.org/{z}/{x}/{y}.png?key={apiKey}&{foo}&style={style}",
@@ -376,7 +376,7 @@ This will cause the following options to be available for the builder instance b
   tile_layer: {
     url: "https://tiles.example.org/{z}/{x}/{y}.png?key={apiKey}&{foo}&style={style}",
     configuration: {
-      api_key: Rails.application.secrets.maps[:api_key],
+      api_key: ENV["MAPS_API_KEY"],
       foo: "bar=baz",
       style: "bright",
       attribution: %{
@@ -450,7 +450,7 @@ In order to provide configuration options for the static maps, you can pass them
 ----
 config.maps = {
   provider: :your_provider,
-  api_key: Rails.application.secrets.maps[:api_key],
+  api_key: ENV["MAPS_API_KEY"],
   static: {
     url: "https://staticmap.example.org/",
     foo: "bar",
@@ -485,7 +485,7 @@ If you want to use the dynamic map replacements for the static map images, do no
 ----
 config.maps = {
   provider: :your_provider,
-  api_key: Rails.application.secrets.maps[:api_key]
+  api_key: ENV["MAPS_API_KEY"]
   # static: { ... } # LEAVE THIS OUT
 }
 ----

data/docs/modules/develop/pages/modules.adoc

@@ -102,7 +102,7 @@ the https://github.com/decidim/decidim/network/dependents[dependency graph]. See
   . Generate logs on Admin panel if admins can operate on it
   . GraphQL API
   . Download your data
-  . Endorsable
+  . Likeable
   . Followable
   . Embeddable
   . Notifications

data/docs/modules/develop/pages/notifications.adoc

@@ -114,43 +114,43 @@ It is possible to render actions into the notifications area. These actions are
 
 In order to add actions to your notification, you need to implement the methods `action_cell`, `action_data` in your event class. The `action_cell` method should return the name of the cell that will be rendered in the notification area. The `action_data` method should return the data that will be passed to the cell.
 
-Currently, there is only one action cell available, `Decidim::Notifications::Actions::ButtonCell`. This cell renders a list of buttons with the text and URL provided in the `action_data`. See the code for the `Decidim::InvitedToGroupEvent` to render actions that allow users to accept or reject a membership invitation to a group:
+Currently, there is only one action cell available, `Decidim::Notifications::Actions::ButtonCell`. This cell renders a list of buttons with the text and URL provided in the `action_data`. See the code for the `Decidim::Proposals::CoauthorInvitedEvent` to render actions that allow users to accept or reject a proposal coauthorship invitation:
 
 [source,ruby]
 ----
-# decidim-core/app/events/decidim/invited_to_group_event.rb
+# decidim-proposals/app/events/decidim/proposals/coauthor_invited_event.rb
 
-def membership_id
-  extra["membership_id"]
+def user_is_coauthor?
+  resource.authors.include?(user)
 end
 
-def invitation
-  @invitation ||= UserGroupMembership.find_by(user:, id: membership_id, role: "invited")
+def invite_path
+  @invite_path ||= EngineRouter.main_proxy(component).proposal_invite_coauthor_path(proposal_id: resource, id: user.id)
 end
 
 def action_cell
-  "decidim/notification_actions/buttons" if invitation
+  "decidim/notification_actions/buttons" unless user_is_coauthor?
 end
 
 def action_data
   [
     {
-      url: url_helpers.group_invite_path(user_group_nickname, membership_id, format: :json),
+      i18n_label: "decidim.events.proposals.coauthor_invited.actions.accept",
+      url: invite_path,
       icon: "check-line",
-      method: "patch",
-      i18n_label: "decidim.group_invites.accept_invitation"
+      method: "patch"
     },
     {
-      url: url_helpers.group_invite_path(user_group_nickname, membership_id, format: :json),
+      i18n_label: "decidim.events.proposals.coauthor_invited.actions.decline",
+      url: invite_path,
       icon: "close-circle-line",
-      method: "delete",
-      i18n_label: "decidim.group_invites.reject_invitation"
+      method: "delete"
     }
   ]
 end
 ----
 
-The previous code will render a couple of buttons to accept/reject the invitation but only if the UserGroupMembership is not accepted yet.
+The previous code will render a couple of buttons to accept/reject the invitation but only if the user is not coauthor yet.
 
 Note that the cell returned is "decidim/notification_actions/buttons", if you want to use a custom cell, you should create it in your application and return it accordingly.
 
@@ -165,67 +165,38 @@ So, it is advisable for the controller handling the request to respond with a JS
 }
 ----
 
-Use standard HTTP status codes to indicate the result of the operation. For an example, see the implementation of the `Decidim::GroupInvitesController` that responds with a JSON object only when requests are made with the `:json` format:
+Use standard HTTP status codes to indicate the result of the operation. For an example, see the implementation of the `Decidim::Proposals::InviteCoauthorsController` that responds with a JSON object only when requests are made with the `:json` format:
 
 [source,ruby]
 ----
-# decidim-core/app/controllers/decidim/group_invites_controller.rb
+# decidim-proposals/app/controllers/decidim/proposals/invite_coauthors_controller.rb
 
+# coauthor accepts invitation
 def update
-  enforce_permission_to :accept, :user_group_invitations
-  AcceptGroupInvitation.call(inviting_user_group, current_user) do
+  enforce_permission_to :accept, :proposal_coauthor_invites, { proposal:, coauthor: }
+
+  AcceptCoauthorship.call(proposal, current_user) do
     on(:ok) do
-      respond_to do |format|
-        format.json do
-          render json: { message: t("group_invites.accept.success", scope: "decidim") }
-        end
-        format.all do
-          flash[:notice] = t("group_invites.accept.success", scope: "decidim")
-          redirect_to profile_groups_path(current_user.nickname)
-        end
-      end
+      render json: { message: I18n.t("update.success", scope: "decidim.proposals.invite_coauthors") }
     end
 
     on(:invalid) do
-      respond_to do |format|
-        format.json do
-          render json: { message: t("group_invites.accept.error", scope: "decidim") }, status: :unprocessable_entity
-        end
-        format.all do
-          flash[:alert] = t("group_invites.accept.error", scope: "decidim")
-          redirect_to profile_groups_path(current_user.nickname)
-        end
-      end
+      render json: { message: I18n.t("update.error", scope: "decidim.proposals.invite_coauthors") }, status: :unprocessable_entity
     end
   end
 end
 
+# coauthor declines invitation
 def destroy
-  enforce_permission_to :reject, :user_group_invitations
+  enforce_permission_to :decline, :proposal_coauthor_invites, { proposal:, coauthor: }
 
-  RejectGroupInvitation.call(inviting_user_group, current_user) do
+  RejectCoauthorship.call(proposal, current_user) do
     on(:ok) do
-      respond_to do |format|
-        format.json do
-          render json: { message: t("group_invites.reject.success", scope: "decidim") }
-        end
-        format.all do
-          flash[:notice] = t("group_invites.reject.success", scope: "decidim")
-          redirect_to profile_groups_path(current_user.nickname)
-        end
-      end
+      render json: { message: I18n.t("destroy.success", scope: "decidim.proposals.invite_coauthors") }
     end
 
     on(:invalid) do
-      respond_to do |format|
-        format.json do
-          render json: { message: t("group_invites.reject.error", scope: "decidim") }, status: :unprocessable_entity
-        end
-        format.all do
-          flash[:alert] = t("group_invites.reject.error", scope: "decidim")
-          redirect_to profile_groups_path(current_user.nickname)
-        end
-      end
+      render json: { message: I18n.t("destroy.error", scope: "decidim.proposals.invite_coauthors") }, status: :unprocessable_entity
     end
   end
 end

data/docs/modules/develop/pages/permissions.adoc

@@ -26,62 +26,62 @@ Permission actions have a scope. It is usually either `:public` or `:admin`, and
 
 === Proposals example
 
-We are going to reproduce the steps to add an action (endorse) for a proposal step by step.
+We are going to reproduce the steps to add an action (like) for a proposal step by step.
 
-==== Configuring a new 'endorse' action
+==== Configuring a new 'like' action
 
 . Edit decidim-proposals/lib/decidim/proposals/component.rb
-. Add the new 'endorse' action into the `component.actions` array and save the file:
+. Add the new 'like' action into the `component.actions` array and save the file:
 
 [source,ruby]
 ----
-component.actions = %w(endorse vote create)
+component.actions = %w(like vote create)
 ----
 
-. Translate the action for the corresponding key: `en.decidim.components.proposals.actions.endorse = Endorse`
+. Translate the action for the corresponding key: `en.decidim.components.proposals.actions.like = Like`
 . Edit `app/permissions/decidim/proposals/permissions.rb` and add the corresponding permission, using `authorized?` method to run the `authorization handler` logic.
-. In the endorse proposals controller, enforce that the user has permissions to perform the `endorse` action before actually doing it, using the `enforce_permission_to` method:
+. In the like proposals controller, enforce that the user has permissions to perform the `like` action before actually doing it, using the `enforce_permission_to` method:
 
 [source,ruby]
 ----
-enforce_permission_to :endorse, :proposal, proposal: proposal
+enforce_permission_to :like, :proposal, proposal: proposal
 ----
 
-. In the proposals templates, change regular links and buttons to endorse a proposal with calls to `action_authorized_link_to` and `action_authorized_button_to` helpers.
+. In the proposals templates, change regular links and buttons to like a proposal with calls to `action_authorized_link_to` and `action_authorized_button_to` helpers.
 . Restart the server to pick up the changes.
 
-==== Using the new 'endorse' action
+==== Using the new 'like' action
 
-. Now an admin user should be able to go to a participatory space with a `proposals` component panel and click on its `Permissions` link (the icon with a key). There, an `authorization handler` can be set for the `endorse` action.
+. Now an admin user should be able to go to a participatory space with a `proposals` component panel and click on its `Permissions` link (the icon with a key). There, an `authorization handler` can be set for the `like` action.
 . Go to a Proposal detail in the front-end
-. Try to endorse the current proposal
- ** If the user has not granted the selected permission, the 'endorse' button should block the action and allow the user to grant the permission with the selected `authorization handler` logic.
- ** If the logger user has already granted the selected permission, the user should be able to perform the endorsement.
+. Try to like the current proposal
+ ** If the user has not granted the selected permission, the 'like' button should block the action and allow the user to grant the permission with the selected `authorization handler` logic.
+ ** If the logger user has already granted the selected permission, the user should be able to perform the like.
 
 ==== Allow to configure the related permissions at resource level
 
 Permissions settings could also be set for an specific resources apart from the full component. Actions should also be related to the resource.
 
 . Edit decidim-proposals/lib/decidim/proposals/component.rb
-. Add the 'endorse' action into the `resource.actions` array for the `proposal` resource definition and save the file:
+. Add the 'like' action into the `resource.actions` array for the `proposal` resource definition and save the file:
 
 [source,ruby]
 ----
-resource.actions = %w(endorse vote)
+resource.actions = %w(like vote)
 ----
 
-. Only if this is the first resource action added, edit the proposals admin templates and use the `resource_permissions_link` helper to link the resource permissions page from each resource in the listing.
+. Only if this is the first resource action added, edit the proposals admin templates and use the `dropdown_resource_permissions_link` helper to link the resource permissions page from each resource in the listing.
 
 [source,erb]
 ----
-<%= resource_permissions_link(proposal) %>
+<%= dropdown_resource_permissions_link(proposal) %>
 ----
 
 . In the proposals permission class, pass an extra `resource` named parameter to the calls to the `authorized?` method.
 
 [source,ruby]
 ----
-authorized?(:endorse, resource: proposal)
+authorized?(:like, resource: proposal)
 ----
 
 . In the proposals templates, also add the extra `resource` parameter to the `action_authorized_link_to` and `action_authorized_button_to` helpers.
@@ -89,4 +89,4 @@ authorized?(:endorse, resource: proposal)
 
 ==== Using permissions at resource level
 
-. Now an admin user should be able to go to a participatory space with a `proposals` component panel and click on its `Permissions` link (the icon with a key). There, an `authorization handler` can be set for the `endorse` action.
+. Now an admin user should be able to go to a participatory space with a `proposals` component panel and click on its `Permissions` link (the icon with a key). There, an `authorization handler` can be set for the `like` action.

data/docs/modules/develop/pages/share_tokens.adoc

@@ -96,7 +96,7 @@ Decidim.menu :admin_assembly_menu do |menu|
                 decidim_admin_assemblies.assembly_share_tokens_path(current_participatory_space),
                 active: is_active_link?(decidim_admin_assemblies.assembly_share_tokens_path(current_participatory_space)),
                 icon_name: "share-line",
-                if: allowed_to?(:read, :share_tokens, current_participatory_space:)
+                if: allowed_to?(:read, :share_token, current_participatory_space:)
   ...
 end
 ----
@@ -128,7 +128,7 @@ For admin controllers:
 
 [source,ruby]
 ----
-allow! if permission_action.subject == :share_tokens
+allow! if permission_action.subject == :share_token
 ----
 
 For frontend controllers:

data/docs/modules/develop/pages/taxonomies.adoc

@@ -231,20 +231,6 @@ bin/rails decidim:taxonomies:import_all_plans
 
 This command will look for all the plan files in the `tmp/taxonomies` directory
 
-==== Updating metrics
-
-Internal metrics can be assigned to a category. However as this table can be very large, it is not included in the import process.
-To update the metrics, you can use the `decidim:taxonomies:update_metrics[tmp/taxonomies/example.com_result.json]` rake task. This task will convert the old categorization metrics to the new taxonomy metrics.
-
-You can also update all the metrics for all organizations at once by running the following command:
-
-[source,bash]
-----
-bin/rails decidim:taxonomies:update_all_metrics
-----
-
-This command will look for all the result files in the `tmp/taxonomies` directory.
-
 [NOTE]
 ----
 **IMPORTANT NOTES**
@@ -473,4 +459,4 @@ For instance, the `decidim_participatory_process_types` section could look like
     ]
   }
 }
-----
+----

data/docs/modules/install/pages/checklist.adoc

@@ -21,7 +21,8 @@ As a technopolitical project, Decidim needs several things to work. This is a no
 . Setup *backup* on your server. The most important things to save are the `public/uploads` and the database.
 . Decide and implement which kind of *xref:customize:authorizations.adoc[Authorization]* you are going to use.
 . Comply with our License (Affero GPL 3) and *publish your code* to http://github.com[GitHub] or wherever you want.
-. Review your *decidim initializer* on your application (config/initializers/decidim.rb).
+. Review your environment variables on the deployment server.
+. Review your *decidim initializer* contents (config/initializers/decidim.rb) - If the file exists.
 . Configure your xref:services:activejob.adoc[*ActiveJob*] background queue.
 . Configure your xref:services:activestorage.adoc[*ActiveStorage*] dynamic uploads.
 . If you want, configure your xref:services:social_providers.adoc[*social providers*] to enable login using external applications.