Diego Abadan

I believe that for the main uses, the ideal would be ready-to-use images. I thought of something like: 1) Provide ready-to-use images - eliminating the need for the user to...

Nice, Marc. :) I have ideas for these questions: > The proposal is clear and feasible but, there is a point that stills annoys me, that is "living images security...

I talked to @pablovp86 about this name postfix pattern: `stable-3_3_0-5c2082f ` It could be reserved for docker images created from a commit, by developers.

Ideally, yes for [all supported versions](https://github.com/pkp/ojs/blob/main/SECURITY.md). On the other hand, because of the work that can involve keeping so many versions working well (e.g. supported version of PHP that may...

About this point: > We need faster image building for images if we like to use them in testing process. Let's propose a "docker way" approach: - Use docker images...

Considering that using Alpine can be considered an image size optimization, I like the idea of going Debian now, both for development and production.

We also receive this request from editors of journals we host.

We have cases of journals coming from OJS 2 with hundreds of incomplete submissions. OJS 2 hid these submissions from the editor so they ended up piling up.

To make it easier for people to find, I'm noting references to this issue. It was covered at the Helsinki 2022 Sprint and the summary can be read at: https://pkp.sfu.ca/2022/08/05/helsinki-2022-sprint-notes-released-cleaning-incomplete-submissions/...

Hi @juanCure! Could you check if there is more than one controlled_vocab_entry_id = 100 in the source OJS? One hypothesis is that this duplication exists at the origin, in which...