Aquest lloc web fa servir cookies pròpies i de tercers per millorar l’experiència de navegació, i oferir continguts i serveis d’interès. En continuar la navegació entenem que s’accepta la nostra política de cookies. Per a més informació consulta aquí.
LAB de Planificació estratègica i pressupostos participatius: Apunta't al Lab en un PIM PAM! - -
Carol Romero
@carol
Participant verificat/da
Membre de
Eix PRO (Processos) Eix PX (experiència de participant)
Seguidors

40
Segueix

91
Distintius
  • 14 de Gen 14:24
  • Nova proposta a Notifica una Bug (Errors o Incidències)
    Participatory texts - workflow document upload
    1. What went wrong? When you upload a new document as a participatory text, you have a preview to check that everything is in order, but if it's not, if there is an error, you don't have the option to go back and reload it again. This means that in order to repeat the operation you have to create a new component of proposals, not being able to delete the first one. And you can end up having 'n' proposal components depending on the errors you make when uploading the file. Also: you can't edit the document title once is published, and this can be also a problem. 2. What did you expect to happen? I expected to have an option to reset and reload the file as long as it hasn't been published yet.
  • 14 de Gen 12:06
  • Nova proposta a Notifica una Bug (Errors o Incidències)
    Sorting filter in frontend doesn't work properly
    I've noticed that sorting by the most recent doesn't work well. Also, when you select a filter there is no indicator that it is being processed and this causes confusion. To reproduce: 1. Go to "https://meta.decidim.org/processes/bug-report/f/210/" 2. Select "Order proposals by most recent". 3. Scroll down and you will see a proposal created today among older ones. Take a look at the attached gif.
  • 19 de Des 21:50
  • Nova proposta a Proposa noves funcionalitats
    Autocomplete for @username mentions
    Being able to mention someone is great for encouraging conversation, but right now it's a little cumbersome to do so. Either you copy the username, which is not easy because it is a link and you can accidentally click on it, taking you to the profile page, or you write the username manually and you can mistype it. It would be great to have autocomplete for @usernames mentions. ps. Does anyone have a special trick to mention other people?
  • 19 de Des 13:04
  • Nova proposta a Decidim.GOV: Governança democràtica per a una comunitat oberta
    [ES] Sistema para valorar el impacto de nuevas funcionalidades / [EN] System to assess the impact of...
    [ES] Establecer un sistema para valorar el impacto de nuevas funcionalidades o cambios en el código. Poder clasificar las mejoras utilizando por ejemplo las mismas categorías del método Semver (major, minor y patch). *MAJOR: cuando se hacen cambios incompatibles con la API *MINOR: cuando se agrega funcionalidad de manera compatible con la versión anterior *PATCH: al hacer correcciones de errores compatibles con versiones anteriores. [EN] Establish a system to assess the impact of new features or changes in the code. To be able to classify the improvements using for example the same categories of the Semver method (major, minor and patch). *MAJOR: when you make incompatible API changes *MINOR: when you add functionality in a backwards-compatible manner *PATCH: when you make backwards-compatible bug fixes.
  • 19 de Des 12:55
  • Nova proposta a Decidim.GOV: Governança democràtica per a una comunitat oberta
    [ES] Proceso para aceptar contribuciones a la rama master / [EN] Process for accepting contributions...
    [ES] El proceso actual de contribución al código no garantiza que, una vez abierto un PR (Pull request), éste termine mergeado en Master (el repositorio principal de código). Uno de los motivos es que cualquier funcionalidad (habiendo sido validada previamente por la comunidad) puede resolverse técnicamente de maneras diferentes, y por tanto la valoración técnica es subjetiva. Publicar las condiciones claras para que un PR sea aceptado y abrir más la comunicación una vez que se abre el PR en github para negociar si es necesario y asegurar que se puede llegar a mergear. [EN] The current process of contribution to the code does not guarantee that, once a PR (Pull request) is opened, it ends up merged in Master (the main code repository). One of the reasons is that any functionality (having been previously validated by the community) can be solved technically in different ways, and therefore technical validation is subjective. Publish clear conditions for a PR to be accepted and open more communication once the PR is opened in github to negotiate if necessary and ensure that it can be merged.
Creative Commons License Web feta amb programari lliure.

Si us plau, inicia sessió

Has oblidat la teva contrasenya?

O