outcomes

upcoming tasks

contact Victor about penetration testing
add more e2e tests (Nick)
... maybe leading to better test db seeding/fixtures
maybe helps to support building a full seed database for beta/dev versions
implement symfony kernel + 1 or 2 core-ish modules + add unit tests (Florin)
find more security issues (creating issues about them and/or fixing issues)
remove unused crap from backend/php code (Matthias)
get phpstorm 30 day trials, and aim for open sourcing by the time the trial is over
reducing/cleanup of html/js frontend stuff (Adrian)
maybe start to look at some js frontend components + json data api, not high priority yet

php7 is not a particular focus (quite a lot of work, and not much advantage to us right now (at least until we have good unit tests and symfony stuff in place))
mobile app: would be nice, but probably better to revisit later. mobile notifications would be biggest killer feature says Kristijan.
collaboration: not clear yet, longer term intentions to try and merge with foodsaving tool.

adding more e2e tests
merge existing MRs without waiting for unit testing to be ready
(clear backlog, get fixes into production)
first steps in modular refactoring (with aim to make it unit testable)
- symfony vs no framework?
open sourcing
- how to find enough unknown security issues?
- rest should just be routine work...
- ...fix a few issues, contact copyright holders...

vision for a modern php7 / symfony kind of app?
json data api + spa frontend?
how to support html-only version?
mobile app?
collaboration - how to let others build on our work (international users? sharecy?)