How much "integration" in terms of code / infrastructure between this webapp and other RIPARIAS developments? about gbif-alert HOT 2 CLOSED

We have started discussing this with @sronveaux. We both agree it's difficult to make a definitive decision now, but it's something to keep in mind and if possible to decide in the next few weeks/months.

Some major questions that will help us take a decision:

• How much shared data between our developments.
• How convergent are we in terms of tools, infrastructure, best practices, ...
• Would a common timeline (Django updates, ...) hinder/bother us or not?
• How cumbersome is it to work with large Git branches... (thinking of implications for Django migrations for example)

from gbif-alert.

decision: after more discussions with @sronveaux (who also talked about this with colleagues), it's been decided that the early alert web application and the future webapp developed by BBPF/Sébastien will effectively be two separate web applications, living in two different codebases/repositories and (possibly) hosted on a different infrastructure.

There's no perfect answer to this question, but it seems the wisest approach in the current state of affairs.

We do however confirm that's it's crucial for those systems to have some integration together each time it makes sense and that collaboration is essential to reach the goals of LIFE RIPARIAS. We decided to took some measures to make that happen:

• weekly dev meetings between @sronveaux and @niconoe to stay in sync and discuss, among other things, points of convergence
• common base tech stack: Python 3 / Django / Vue.js / Postgres / PostGIS/ Bootstrap
• use of GitHub for codebase, issues, discussions, ... (Sébastien will also push the code to the BBPF Gitlab instance to benefits from its CI/CD feature)
• agreement

from gbif-alert.