When I report a content (for instance a proposition or a comment) and if I go to the admin backoffice to moderate it and hide it, in the process menu > moderation, I get this error :

ArgumentError (wrong number of arguments (given 1, expected 2)):
/Users/juliesimon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/bundler/gems/decidim-fb24acdc05e5/decidim-admin/app/commands/decidim/admin/hide_resource.rb:11:in `initialize'

I was on decidim#0.10-stable with osp-app#0.10-stable

When we seed a decidim organization, as a user, we can use an authorization handler to fill in our birthday, postal code and document number.

1/ How can we configure the type of fields of this authorization handler?

2/ How do we activate it so that its available to the users?

3/ In the admin dashboard, for each component, we can configure who can have access to it. What I don't understand is what sorts of data do you expect in the "options" field ? We can see that it expects a JSON, but what does decidim expect in this JSON ? For instance if you want to pass some postal codes that are authorized ? Or if you want to only let people over 18 to participate?

I can't find any documentation on the subject.
Thanks !

I don't know if it is in this repo or in osp-app but for instance, when you receive an email from https://osp-dcd-dev.herokuapp.com/ you get "LOL" in the email description

Decidim sort une nouvelle version tous les 2 mois.

Vous pouvez consulter les releases log ici.
Les instances suivantes sont mises à jour :

• staging.decidim.codegram.com vous pouvez vous connecter avec les id [email protected] et decidim123456
• meta.decidim.barcelona qui est l'instance qu'ils utilisent pour la communauté et où ils font du bug hunting

Pour l'instant nous avons surtout travaillé avec la 0.7 stable. Je pense qu'on a intérêt à passer à la 0.8 et à migrer la modération à priori faite par Ludivine. Faudrait vérifier que les engines Conversation Pol.is et user-export fonctionne bien avec cette nouvelle version.

by @virgile-dev

Les règles de validation se trouvent dans le dans le fichier decidim-core/app/validators/etiquette_validator.rb.

Voici une explication des différents règles. Il faut qu'on décide desquelles on garde car certaines d'entre elle nous ont causé des problèmes.
Notamment ces deux là

• validate caps : est problématique avec l'utilisation des acronymes (ex SNCF) - voir issue
• Le champ description est limité à 500 caractères - issue
• validate marks nous a aussi causé des souci à plusieurs reprises.

@valentinchaput qu'en penses-tu ?

Decidim form validators

Ce bout de code sert à vérifier si il y a des majuscules qui se suivent :

def validate_caps(record, attribute, value)
    return if value.scan(/[A-Z]/).length < value.length / 4
    record.errors.add(attribute, options[:message] || :too_much_caps)
  end

Celui la sert à vérifier qu'il n'y a pas de signe de ponctuation qui se suivent :

def validate_marks(record, attribute, value)
     return if value.scan(/[!?¡¿]{2,}/).empty?
     record.errors.add(attribute, options[:message] || :too_many_marks)             
   end

Celui ci sert à ne pas avoir de mot de plus de 35 lettres :

def validate_long_words(record, attribute, value)
    return if value.scan(/[A-z]{35,}/).empty?
    record.errors.add(attribute, options[:message] || :long_words)
  end

Ce bout la permet de faire commencer la phrase par une majuscule :

def validate_caps_first(record, attribute, value)
    return if value.scan(/^[a-z]{1}/).empty?
    record.errors.add(attribute, options[:message] || :must_start_with_caps)
  end

Et celui la permet d'avoir des titres d'au moins 15 caractères :

def validate_length(record, attribute, value)
    return if value.length > 15
    record.errors.add(attribute, options[:message] || :too_short)
  end

by @virgile-dev

This is a Feature Proposal

🎩 Description

This issue originates from the decidim main repository.

Regarding that, I was made aware that pre-moderation (or priori moderation) has been implemented in this Decidim repository due to convincing some organizations into using Decidim. Further details regarding the feature proposal and also about the implementation details can be found from the linked Decidim main repository issue. The implemented code is available in the f-moderation branch of this repository.

What I am suggesting is that we should extract this feature into its own gem so that this feature would be more widely available to the decidim users. There is the ideological debate also concerning this issue whether it is good for the Decidim community to make this feature mode widely available. However, I personally believe this may lead into more Decidim users as already proven by the original need of developing this feature.

Action points:

• 👍 Yes, let's do it! - Leave a thumbs up to this thread if you feel this feature should be available for all Decidim users.
• 👎 No, this should not be done! - Leave a thumbs down to this thread if you feel this feature should NOT be available for all Decidim users.

The repository maintainer can decide the threshold on when this would be accepted/rejected.

In case this is accepted, we would need to scratch out a plan on the implementation details and how it would be possible to extract this feature into its own gem.

📌 Related issues

• decidim#2503

📋 Additional Data

• Decidim deployment where you found the issue:
• Browser & version:
• Screenshot:
• Error messages:
• URL to reproduce the error:

Screens about the implementation:
https://www.figma.com/file/MX4BYbJ5VKUO1xSraC8DQefk/user-flow-moderation-a-priori

Logical workflow:

On the MEL's platform, you hide "Processus participatifs" + "Plus d'information" on the secondary navbar in order to place custom links :

Angers also uses a custom link to "Budget participatif 2018" but cannot display it before "Participations en cours" + "Plus d'information" as they are not hidden :

Could you make the same change in order to have "Accueil / Budget participatif 2018 / Participations en cours / Plus d'information" (they may have to recreate the last two manually)? And document the issue so Julie will know how to do it next time ;)

On https://participons.debatpublic.fr/ : logo is on the left (ok) but links are not centered (not ok)

On https://cerise.osp.cat/ : logo is in the middle kind of (not ok) but links are centered (ok)

On https://ecrivons.angers.fr/ : logo on the left (ok) and links centered (ok)

As a user I can't leave a comment on the features that have been added by the Decidim team since OSP developed upstream moderation.
Here is the error message I get when I try to leave a comment :

Completed 500 Internal Server Error in 104ms (ActiveRecord: 8.0ms)
NoMethodError (undefined method `comments_upstream_moderation_enabled' for #<#<Class:0x00007fe94d87a620>:0x00007fe94da5c470>)

Maybe it's because upstream moderation has to be set for the new features "debates" and "blogs"

Retirer le champ "Numéro d'identification de l'organisation" lors de l'inscription en tant qu'organisation / collectif

by @virgile-dev

See : OpenSourcePolitics/decidim-user-export#1

1. Faire les modifications sur decidim/0.9-separate_proposal
2. Merger dans OSP/0.9-separate_proposal
3. Et enfin fait une PR de OSP/0.9-separate_proposal dans 0.9-nouvelle_aquitaine (Fais moi signe à ce moment là afin que je la merge rapidement)

• Affichage des icones

• Quand on passe en mode mobile, les propositions ne s'affichent plus. L'un des containers doit avoir un média querie lui disant de disparaitre en mobile.

• La partie grise (lorsque l'affichage est en ligne) n'est pas tout à fait responsive

• Mettre de l’espace entre “X propositions” et les propositions

• Le bouton "voir toutes les propositions"

• Now using the dummy authorisation handler, with field "document number" that has to end with an X --> should create a specific AH for each client/need ?

• No error message appears when trying to managed a user with a name that is already taken

• Two buttons "Create" and "Send" that do the same action : what is the need for these two buttons ?

Seen on https://monopinion.belgium.be for instance

When it works on https://deploy-decidim.herokuapp.com (osp-app#0.10 stable sur branche decidim#0.10-stable)

En tant qu'admin, je peux configurer la fonctionnalité "participation"

• Changer "Assemblées" (car confusion avec l'Assemblée nationale) en "Initiatives" (même mot qu'en catalan ?) @valentinchaput vu que ya déjà un espace de participation qui s'appelle "Initiative" faut qu'on lui trouve un autre nom. Des idées ?
• Dans la section "Auteurs" des filtres des proposition, remplacer "Elu-e-s" par "Propositions officielles" et "Citoyens" par "Propositions citoyennes"
• Dans le formulaire de signalement des propositions/commentaires, rajouter "homophobes" après sexistes (Traduction actuelle: "Contient des propos racistes, sexistes, des insultes, des attaques personnelles, des menaces de mort, des incitations au suicide ou toute forme de discours de haine."

Objectif : rendre la secondary navbar éditable pour pouvoir

• intégrer un lien direct vers une page du site (ex : budget Angers)
• intégrer un lien direct vers un site externe

by @valentinchaput

So far, nothing about the user appears in the export of a proposal (and for all exports)

Angers needs it since the administrators of the platform sends the xls to the service which in fine contacts the users regarding their proposals.

Should we include user data, in terms of privacy ?
If so, what could we include ? Name, username, email ?

Actuellement, les administrateurs peuvent "répondre" à une proposition en lui accordant un statut "retenue/refusée/en cours d'évaluation". Il faudrait pouvoir ajouter un ou plusieurs statuts supplémentaires (ex d'Angers : recevable, non recevable, en cours d'évaluation, réalisable, non réalisable, soumis au vote...).

by @valentinchaput

Standardisation FR

Traduction

• couverture à 99.9% (cf. decidim:check_locales ou crowdin.com)
• exemple(s) de surcharge de clé standard pour projets custo
• français par défaut au déploiement (bien vérifier que la partie /system et db:seed soient pris en compte)

Authorization Handler

• ajouter un AuthorizationHandler dédié aux formats FR (N° Sécu, Carte Identité, Passeport etc...)
• Tests des fonctionnalités pour comptes validés / non validés ( Certification ✅ )

France Connect

• ajout d'un connecteur OmniAuth / France Connect
• gestion Authorization Handler (auto validation)
• documenter la procédure d'ouverture de service

Documentation
Exemple de connecteur

Geocoding BAN data.gouv.fr

• Carte : intégration de leaflet-rails
• Géocodage : intégration de OpenStreetMap(Nominatim) et Google Map API
• Géocodage : intégration de la base adresse.data.gouv.fr
• ajout des options et clé de configuration ad-hoc

Module Geocoder
(et le mode data.gouv)
Gem leaflet-rails

1 / Les exports des commentaires de Decidim ne mentionnent pas la catégorie de la proposition à laquelle ils sont reliés. Ceci pose problème dans l'analyse du corpus car sans ces catégories les commentaires ne peuvent pas être traités de façon pertinente.

2 / Il faudrait donc que dans les exports des commentaires, il y ait une colone "Category" comme dans les exports des propositions, qui mentionne le nom de la catégorie.

As an admin I can invite another person to be an admin when I create the organisation

This is a Bug Report

Bug sending invitation for admin when creating an organisation
by @virgile-dev

🎩 Description

📌 Related issues

📋 Additional Data

On pompano.osp.cat, when there is a new comment, the mail that is sent to the administrator is not using the french translation for the email_intro variable :

But we can see in the locale file decidim/decidim_comments/config/locales/fr.yml that email_intro is translated in french

    events:
      comments:
        comment_created:
          comment:
            email_intro: '"%{resource_title}" a été commenté. Vous pouvez lire le commentaire sur cette page:'
            email_outro: Vous avez reçu cette notification parce que vous suivez "%{resource_title}" ou son auteur. Vous pouvez annuler ces notifications à partir du lien précédent.
            email_subject: Un nouveau commentaire a été publié par %{author_name} dans %{resource_title}
            notification_title: Un nouveau commentaire a été publié par <a href="%{author_path}">%{author_name} %{author_nickname}</a> dans <a href="%{resource_path}">%{resource_title}</a>

@ludivine cette issue faisait partie de la liste que tu m'avais confiée mais je n'ai pas eu le temps (à me battre avec le déploiement), penses tu pouvoir t'en occuper pendant tes journées decidim ?

• Lorsque les catégories "proposals" des cartes en liste sont très longues, les boutons de vote vont à la ligne et l'affichage est étrange, que ce soit sur un petit, moyen ou grand écran. Il y a également un problème d'affichage en liste des propositions refusées, qui n'ont donc pas de vote possible :
  1/ LARGE
  
  2/ MEDIUM
  
  3/ SMALL
  

Il faudrait que l'affichage des cards-lists suive les comportements suivants :

• en écran large, les boutons de vote reste à droite. Les catégories vont à la ligne dans leur container, comme sur les cards classiques :

• Dans le cas d'une proposition refusée, il faut que le footer gris de la card prenne toute la largeur, comme lors de l'affichage classique :

Voir : OpenSourcePolitics/decidim-osp#4

Navbar links first version was done based on this #3 for spec

Is left to do :

• Application should check that the url entered by the user is valid (check existing regex url check ex : https://stackoverflow.com/questions/7167895/rails-whats-a-good-way-to-validate-links-urls)
• Set title field as obligatory (should add a star next to field label)
• Labels for Title and Link fields display in English, make translations in French
  
• Be able to choose the order of display for links. Check what is being done for activated features on a participatory process. updated mockups @bastienrobert
  
  

This is a (Bug Report / Feature Proposal)

🎩 Description

In the past few days we've had several problems related to the decidim-angers repo that is deployed in angers.opensourcepolitics.eu.

Bugs were related to user sign ups :

• At first, when trying to sign up, once form filled and clicking on the sign up button, the app would return a "the server couldn't locate your page".
• Then after @moustachu spent some time on it, but it seem we haven't solved all problems. The behaviour right now is that when signing up you are able to fill the form but you never receive the confirmation email. I've been doing some testing on my side using the regular osp-app and i replicated this bug. So it's not just related to osp-angers.

• Filtres + étiquette de la card + show => changer "retenue" par "réponse publiée"

This is a Feature Proposal

🎩 Description

Context :
Ludivine has been working on moderations adding the possibility to moderate content a priori for proposals and comments (on all comment objects on the app : meetings, results, etc.). On the Decidim core it is only possible to moderate a posteriori, meaning after a comment / proposal was published and signaled. A priori moderation means that moderators and admins can review what's being published before hand and decide to publish it or not. Here is the spec that was given to Ludivine

Admin and moderator can see content that is not visible to normal users so they can checkout what they moderate.

The problem we had is that when moderating comments, it's not easy for admins and moderators to see the effect of their moderation work as everything was displayed (included content that were moderated and don't display for normal users). So to see the effect you had to log off and load the page as a normal user.

For proposals we just filtered the list of proposals to only show those which where tagged as OK to display.

For comments @ludivinecp told me it might be complicated to filter them to only show those which were tagged as OK to display.

Maybe if you could quickly explain why

We came up with this solution of displaying tags next to comments to specify the status of the comment to help admin and moderators distinguish them. Here is a little mockup we did.

Ludivine suggested that @netbe could try to work on this as the comment system on decidim uses react and he is familiar with that technology.

A strange behaviour occurs with the date configuration in a participatory process.

1/ Months are written in French, but dates are in English (MM/DD/YYYY) -- which we might change eventually for our French-speaking clients.

2/ The main problem: when you add dates on the information page of your participatory process, they change with no reason when you save the page. The dates are good on the front page but the ones in the admin panel are wrong. Even when you try to restore them, they change again when you save your page.

Pictures from a same participatory process:

Currently :

There should be more data (at least name, better if the date also) instead of "tableau 1"

• Trouver un moyen de rendre obligatoire le state lorsque le modérateur valide ou non une question. La compléxité est de rendre l'attribut obligatoire en fonction de s'il s'agit d'un MOA ou d'un modérateur car la vue est commune (/decidim/participations/admin/participation_answers/edit.html.erb)

We have a weird behaviour since we upgraded to 0.9 the /admin/officializations is showing all the users accross all the organizations. For example if signup on org A, the user will also be listed on org B in /admin/officializations. Is the same happening for you ? Thanks in advance.

The decidim core team submitted a patch :
decidim#2912

It'd be great to apply it to our repo.

• add date of inscription
• change ordering

La question va se poser pour nous de savoir si par défaut on propose :

• les assemblées
• les initiatives
• la modération à priori
• le téléchargement des listes utilisateurs

by @virgile-dev

This is a Feature Proposal

🎩 Description

Quand la modération à priori est activée et qu'un nouveau contenu est envoyé par un utilisateur, les modérateurs et les admin reçoivent un mail comme celui-ci.

On a du mal a distinguer le contenu à modérer. Je propose de changer un peu le layout de l'email pour qu'il ressorte plus. Comme ceci :

Proposal index : the proposals counter is not correct when the language is set to french. It display "1" even if there is no proposal. The counter has the correct value in English.

This is a Feature Proposal

🎩 Description

When sharing a process/page/proposal on facebook, we get the content of the proposal + the box with a link. On decidim.barcelona, they also manage to show an image which makes the content more attractive. How could we achieve the same result?

Going further, would it be possible to choose/edit those text & image?

On club.decidim.opensourcepolitics.eu, there is a typo in the activity statistics at the bottom of the page :

It should print "1 PROPOSITION" and "1 REUNION".

https://test-nouvelle-aquitaine.herokuapp.com/processes/corrupti-saepe/f/10/

On this page, if you select the filter "AUTEURS" > "Propositions officielles" and then click on "Affichage: Liste", the filter is reinitialized to "AUTEURS" > "Toutes"

This is a Bug Report

🎩 Description

Modération a priori des propositions ne fonctionnent pas sur https://concertations-preprod.nouvelle-aquitaine.fr/processes/second/f/44/
Osp-app : deploy-NA
Decidim : 0.9-Nouvelle-Aquitaine

Il est très probable que de la même manière, la modération a priori des commentaires ne fonctionne pas non plus (à tester)

A titre de comparaison, la modération a priori semble fonctionner sur https://cndp.test.opensourcepolitics.eu/processes/test/f/52/
Osp-app : alt/cndp
Decidim : 0.9-stable

• Decidim deployment where you found the issue:
• Browser & version:
• Screenshot:
• Error messages:
• URL to reproduce the error:

En tant qu'utilisateur, je peux accéder à la vue de chaque participation

When French is activated, on club.decidim.opensourcepolitics.eu, there is an counting error : when there is no submitted proposition, it still reads "1 PROPOSITION".

Il faudrait merger la branche f-moderation. Elle a été mise à jour par rapport aux dernières MAJ des barcelonnais.
Il faut juste vérifier que tout marche correctement avant de la merger.

As we decide how to order proposals, it should be "les plus récentes"

Context for the moderation à priori feature

Ludivine has been working on moderations adding the possibility to moderate content a priori for proposals and comments (on all comment objects on the app : meetings, results, etc.). On the Decidim original gem it is only possible to moderate a posteriori, meaning after a comment / proposal was published and signaled. A priori moderation means that moderators and admins can review what's being published before hand and decide to publish it or not. Here is the spec that was given to Ludivine

Mockups can be checked here : https://www.figma.com/file/MX4BYbJ5VKUO1xSraC8DQefk/user-flow-moderation-a-priori?node-id=0%3A1

Ludivine just merged the branch f-moderation with develop which was upgraded to the last version of decidim 0.9.pre.

The task here is to check if the upgrade went ok:

• create a branch test-develop-maj on osp-app
• in the gemfile point to https://github.com/opensourcepolitics/decidim/tree/develop for the decidim gem
• make migrations (see bellow) and commit
• deploy to heroku and send us the link
• begin testing, could be interesting that @juliesimon be involved in testing so she gets to understand how the feature works.

Migrations to run before deploying new version

rails decidim:install:migrations
rails  decidim_admin:install:migrations
rails      decidim_system:install:migrations
rails      decidim_accountability:install:migrations
rails      decidim_participatory_processes:install:migrations
rails       decidim:install:migrations
rails     decidim_budgets:install:migrations
rails       decidim_pages:install:migrations
rails     decidim_meetings:install:migrations
rails     decidim_comments:install:migrations
rails    decidim_surveys:install:migrations
rails decidim_proposals:install:migrations
rails decidim_assemblies:install:migrations

As an admin I can invite a moderator

Now it's not possible to do this
Issue is more defined in decidim/issues/decidim#2398
by @virgile-dev

This is a Bug Report

🎩 Description

@Olivier-B-Paris has been trying hard to create an agora with proposals that features philosophy text about democracy. He has stumbled upon a bug which can be described this way:

• As a user I cannot create a proposal on an assembly

After some time trying to understand where it was coming from it seems that this bug is occuring only on this organization: https://demo.decidim.opensourcepolitics.eu

I think that it might be related with some old data or migration that didn't work. Indeed, we tried the same thing on a fresh organization: https://agora.decidim.opensourcepolitics.eu/ and it worked !! Proof here : https://agora.decidim.opensourcepolitics.eu/assemblies/ujklm/f/106/proposals/186

📋 Additional Data

• Decidim deployment where you found the issue: https://demo.decidim.opensourcepolitics.eu
• Browser & version: Lastest Firefox
• Screenshot:
• Error messages: Il y a eu des erreurs lors de la sauvegarde de la proposition.
• URL to reproduce the error: https://demo.decidim.opensourcepolitics.eu/assemblies/textes/f/107/proposals