upgrade to 1.20, fix nginx issue, open jsonrpc for kandroid

[Jibec]

only tested with package_check, please have a look with real installs, i'll do the same on my server soon

Problem

• Description of why you made this PR

Solution

• And how you fix that

PR Status

Obviously, you should really check these affirmations
Work finished. Package_check, basic tests and upgrade from last version OK.
Could be reviewed and tested.

Validation

---

Minor decision

• Upgrade previous version : Maniack C
• Code review : Maniack C
• Approval (LGTM) : JimboJoe
• Approval (LGTM) : Maniack C
• CI succeeded :
  When the PR is mark as ready to merge, you have to wait for 3 days before really merge it.

[Jibec]

tested with package_check, VM upgrade, and personal server upgrade works fine.
I have no plugins, only a few projects with a few hundreds tasks

[JimboJoe]

LGTM, code review and upgrade from previous version OK... except for the Kandroid part: I didn't manage to login from Kandroid...
I guess you need to use skipped_uris instead of unprotected_uris as in ttrss.

[Jibec]

can we go forward? The connection bug is not related to Kanboard: andresth/Kandroid#38

[JimboJoe]

Didn't we need to activate LDAP authentication...?

[maniackcrudelis]

Code review OK and LGTM

[maniackcrudelis]

Will be merged in 3 days.

[frju365]

I wanted just to know, why you removed the maintainer mbugeia ? (I think even if he is not here, we should keep his name, at least to be ok with the copyright allowed by the license). Btw, you can add your name near the other one :) 2 maintainer is ok too. At least it's my point of view.

[maniackcrudelis]

By the way, it could be really interesting to have a way to keep traces of the previous maintainers.
I can understand that now jibec is becoming the main maintainer, but it would be really nice to keep mbugeia somewhere too.

[Jibec]

if you tell me how to do it, I'll be pleased to add previous maintainer name as an INFO in the manifest.json, but I doubt this file aim to keep historic data. I would rather keep it somewhere else (like Readme, but we don't need structured data for this).

[maniackcrudelis]

I opened a issue about that, https://dev.yunohost.org/issues/1095
Let's talk about how handle this over there.

For the moment, an upgrade of kanboard could be interresting and should not be stopped by that.
This field is about the current maintainer, and we have to keep it clear to allow users to ask to the real (and current) maintainer of an app.

As this PR has been accepted, I merge it.

[maniackcrudelis]

if you tell me how to do it, I'll be pleased to add previous maintainer name as an INFO in the manifest.json, but I doubt this file aim to keep historic data. I would rather keep it somewhere else (like Readme, but we don't need structured data for this).

Following our meeting this evening, the idea is to try a new entry in the manifest called "old_maintainers" or "previous_maintainers", which should not causes any trouble to the manifest.
I like the idea to keep this information just next to the current maintainer.