First batch of plugins that would be added here

[alecslupu]

Since there are some companies that have agreed to share their expertise in creating and maintaining various gems, i would suggest on voting for the first iteration of the gems that can be added and maintained collectively.

Please note, they have been selected by usage criteria.

• https://github.com/OpenSourcePolitics/decidim-module-navbar_links (1 PR, 3 issues)
• https://github.com/mainio/decidim-module-term_customizer ( 5 PRs, 6 issues )
• https://github.com/Platoniq/decidim-module-decidim_awesome (7 PRs, 34 issues)

[paulinebessoles]

Thank you @alecslupu for opening this discussion!
IMO, the decidim-module-navbar_links shouldn't be here, as it's not updated in the last versions, before the awesome module is doing the same but better since its 0.6.5 version. If the community think it's relevant, we can add it to this organization, I just wanted to be as transparent as possible about this!

The modules Simon and I were thinking about on OSP side were those ones:

• OpenSourcePolitics/decidim-module-friendly_signup: enhancement of the sign up process (but might be deprecated after the redesign)
• OpenSourcePolitics/decidim-module-question_captcha: accessible captcha on the sign up form
• OpenSourcePolitics/decidim-ludens: gamification to help admins to know what are the possibilities in Decidim

[simonaszilinskas]

Also we're preparing a big update to custom registration fields (based on the populate module) - we'll keep you up to date on that but we think it's gonna be useful to a lot of instances!

[alecslupu]

@paulinebessoles , I have submitted the fixes for decidim-module-navbar_links a while back, and I can tell you that is currently compatible with Decidim 0.27.0 as I am using it, and the last MR done by me, adds Decidim 0.28 suport.
@simonaszilinskas, the custom registration fields, is it the demographics one ? (I have something like that on CoFe, but is not using the questionaire to support dynamic fields). I have seen there are a few modules for emographic data, and maybe we should do something unique. :)

[simonaszilinskas]

It allows to add custom fields to the registration form from the back-office - you can add demographic data for example :)

[microstudi]

I don't think we should "choose" a plugin to start here. My take would be to decide what requisites should the module comply and then it would be the decision of the owner of the plugin to put it here.

As I just said in the other discussion (https://github.com/orgs/decidim-ice/discussions/2#discussioncomment-3933745
), we could start with a 3 simple points to be answered by the owner of the module:

• Why? the relevance of the module
• Who? who is the initial maintainer
• How? Does it fit to our criteria of quality?

If it fits, it's accepted. The owner is still responsible to maintain the plugin unless he/she needs help or goes missing. Which in that case, the board will act to appoint another maintaner.

[basicavisual]

however I think there is some value to collectively do "maintenance parties" for plugins or small hackathons to bring some of them up to speed. It will help us as an ecosystem to familiarize with the innards of the tools and after a while I think we will end up creating conventions or design patters of how things should be done.

[microstudi]

indeed that would be amazing, and a prove that this newly created community is vibrant and active!
However I don't think we can rely only on this kind of events to maintain thinks.
I my opinion, progress will be done when:

1. Some client pays an upgrade
2. The maintainer makes voluntarily
3. Someone makes a PR with the upgrade (then it will be responsibility of the maintainer to respond).
4. Using a collective funding to pay someone to do the upgrade
5. Hackatons! hopefully!

[PierreMesure]

On Digidem Lab's side, happy to add our small modules to the list:

• Analytics, which embeds Matomo in the admin panel and makes it easier to add the snippet in every page's header.
• Budgets_Paper_Ballots, to import paper votes.
• Faceless, which removes some elements of public profiles rarely (never?) used by actual people but commonly used by spammers.

We're not giving up on maintaining them but we have a limited amount of technical resources (basically me a few hours a month). It would be great for instance if we could include these modules in a bigger Crowdin account so they can be translated easily.

In the case of these three modules, updating and testing them for the latest version 0.27 would probably take a couple of hours so a maintenance party like @basicavisual suggest would be ideal and I'd love to join if we can find a common time slot 😊.

Apart from them, happy to add other resources to a common pool:

• decidim-census, which runs without any issue but I don't have any time to improve it. It would be great if others wanted to add their organisation's platforms. The data is also open so it can be reused in other tools.
• decidim-export-extended-data, a little Python script to export aggregated data from the users' table's extended data.

[simonaszilinskas]

Hey @alecslupu ! With Octree we are thinking about collaborating on the https://github.com/OpenSourcePolitics/decidim-module-homepage_interactive_map module so I would like to suggest it as a potential candidate to go into the repo (during yesterday's call people seemed to need this type of module)