Propose new functionalities for Decidim software

Fingerprint

The piece of text below is a shortened, hashed representation of this content. It's useful to ensure the content hasn't been tampered with, as a single modification would result in a totally different value.

Value: 84a9a81706a6cadeaeb6a43650851be4a0df81d5e9d0f722fda009194dbcba1b

Source: {"body":{"en":"<p>Ref. PWA01</p><p>NOTE: this feature is from a big development. See <a href=\"https://github.com/decidim/decidim/discussions/8334\" target=\"_blank\">PWA discussion at GitHub</a>.</p><p><strong>Is your feature request related to a problem? Please describe.</strong></p><p>By making changes in performance with servers or local machines we’re at risk that things change in the future and that we can’t know for sure when/what/why have changed.</p><p><strong>Describe the solution you’d like</strong></p><p>To have performance tests, and to control the environment where these tests are executed so it’s always the same (the CI).</p><p>For PWA, Lighthouse is the de-facto official tool to check most of the metrics. There are some GH Actions that already do these checks, although if we have other options we’re open to change this for a better solution, for instance, something integrated with RSpec.</p><p><a href=\"https://github.com/marketplace/actions/lighthouse-ci-action\" target=\"_blank\">https://github.com/marketplace/actions/lighthouse-ci-action</a><strong><br></strong><a href=\"https://github.com/marketplace/actions/lighthouse-check\" target=\"_blank\">https://github.com/marketplace/actions/lighthouse-check</a></p><p><strong>Additional context</strong></p><p>As mentioned in the EPIC:</p><p><strong><img src=\"https://i.imgur.com/c1EHGLN.png\"><br></strong> <em>Lighthouse relevant section</em></p><p><strong><img src=\"https://i.imgur.com/qegt9xM.png\"><br></strong> <em>Lighthouse relevant section</em></p><p>As some of these changes could be particular for a given provider (ie it’s not the same Heroku/AWS/OVH/Digital Ocean), at the beginning of these developments there should be done Performance and reproducible testing, and it should also be on someway integrated on the Continuous Integration platform being used at the moment of development so we have a comparison point (an initial picture) and also detect regressions. For instance: <a href=\"https://github.com/marketplace/actions/lighthouse-check\" target=\"_blank\">https://github.com/marketplace/actions/lighthouse-check</a></p><p><strong>Does this issue could impact on users private data?<br></strong> No, it’s about performance.</p><p><strong>Acceptance criteria</strong></p><ul><li>Given that I’m a Decidim developer<strong><br></strong> When I go to the GitHub Actions tab in GH,<strong><br></strong> Then I have Lighthouse Workflow sections<strong><br></strong> And<strong><br></strong> I have the history of this data (at least 90 days).</li><li>Regarding the data I have access to in this Workflow, I can see …</li><li>… First Contentful Paint of the homepage</li><li>… First Contentful Paint of a participatory process</li><li>… First Contentful Paint of a proposal</li><li>… First Contentful Paint of a meeting</li><li>… Speed Index of the homepage</li><li>… Speed Index of a participatory process</li><li>… Speed Index of a proposal</li><li>… Speed Index of a meeting</li><li>… Time to Interactive of the homepage</li><li>… Time to Interactive of a participatory process</li><li>… Time to Interactive of a proposal</li><li>… Time to Interactive of a meeting</li><li>… Largest Contentful Paint of the homepage</li><li>… Largest Contentful Paint of a participatory process</li><li>… Largest Contentful Paint of a proposal</li><li>… Largest Contentful Paint of a meeting</li></ul><p><br></p>"},"title":{"en":"Configure performance monitoring metrics at CI"}}

This fingerprint is calculated using a SHA256 hashing algorithm. In order to replicate it yourself, you can use an MD5 calculator online and copy-paste the source data. ×