Plugin idea: report destinations (monthly report to an employment office or adviser) #1262

New issue

Open

opened 2026-11-13 10:51:55 +00:00 by tiagoagueda · 0 comments

tiagoagueda commented

2026-11-13 10:51:55 +00:00

Owner

Idea

The monthly report (#1095) lists a person's job-search activity. Some countries require proof of search activity (France Travail's actualisation, the Portuguese IEFP, the German Jobcenter). A report destination plugin would format the report as that body expects and, where it has an API or a form, help the person send it, always by their own action.

What to settle

What each body accepts and where the person submits it; Postulo never submits on its own and never holds the person's credentials for a government portal without a design reviewed for it.
The format per country (a PDF layout, a CSV, a structured file), the language, and what personal data it contains.
The relation to the Europass and France Travail plugins and to the exports (#1095).

Wanted

A survey of three countries' requirements, and a reference plugin that produces the file for one of them.

Rules that apply to every plugin

Off until the person enables it; a plugin that calls a service names the host and the data it sends in its manifest and on the consent screen (plugins/consent.py); nothing is fetched on page load.
Core keeps no import of it: the application runs with it absent, and data it created stays readable as plain data when it is removed.
The plugin surface (plugins/api.py, the published postulo.plugins.testing check) gets a contract test for any new kind; the plugin ships its own translation catalogues (the plugin locale rule); strings go through Weblate only.
Its own repository if it is not bundled (see the plugin repositories and #1170's shared CI).

Filed as an idea after a discussion on plugin kinds, with #1252 (reference data and lookups as plugins). Not started; the maintainer decides if and when.

## Idea The monthly report (#1095) lists a person's job-search activity. Some countries require proof of search activity (France Travail's actualisation, the Portuguese IEFP, the German Jobcenter). A **report destination** plugin would format the report as that body expects and, where it has an API or a form, help the person send it, always by their own action. ## What to settle - What each body accepts and where the person submits it; Postulo never submits on its own and never holds the person's credentials for a government portal without a design reviewed for it. - The format per country (a PDF layout, a CSV, a structured file), the language, and what personal data it contains. - The relation to the Europass and France Travail plugins and to the exports (#1095). ## Wanted A survey of three countries' requirements, and a reference plugin that produces the file for one of them. ## Rules that apply to every plugin - Off until the person enables it; a plugin that calls a service names the host and the data it sends in its manifest and on the consent screen (`plugins/consent.py`); nothing is fetched on page load. - Core keeps no import of it: the application runs with it absent, and data it created stays readable as plain data when it is removed. - The plugin surface (`plugins/api.py`, the published `postulo.plugins.testing` check) gets a contract test for any new kind; the plugin ships its own translation catalogues (the plugin locale rule); strings go through Weblate only. - Its own repository if it is not bundled (see the plugin repositories and #1170's shared CI). Filed as an idea after a discussion on plugin kinds, with #1252 (reference data and lookups as plugins). **Not started; the maintainer decides if and when.**

tiagoagueda added the

enhancement

label

2026-11-13 10:51:55 +00:00

tiagoagueda referenced this issue

2026-11-13 10:56:29 +00:00

Plugins: one tracked manifest for builtin, official and third-party plugins, and nothing installed outside a manifest #1263