OpenAtlas

We talked about it a few times but you are absolutely right, it really is time to consolidate them because it would have a lot of advantages. It of course would mean that extra steps will be needed when updating the instances but better to do it now than later.
I would even suggest putting the new directory into the project root (already thinking about maybe having one OpenAtlas software installed to run many instances). So the new structure would look like:

• files
  • export (former openatlas/export/sql)
  • processed_images (former openatlas/processed_images, I would keep the processed_ prefix for clarity)
  • uploads (former openatlas/uploads)

• Move folder (locally)
• Adapt .gitignore and taking care of that the empty folders are still tracked in git but not their content
• Adapt paths in config/default.py. Ideally needed only there, if more is needed we should change this
• Adapt install notes in install.md
• Note it in install/upgrade/upgrade.md, also mention that backup scripts might have to be adapted
• When releasing
  • Mention in release news
  • Adapt wiki page Application and database structure

• I was thinking about a script to automate the folder moves but decided against it, it's better to do it manually because e.g. backup scripts might have to be adapted too
• It should be done in an extra branch and only be merged to develop shortly before a release to avoid complications when switching branches while developing
• Would the frontends need adaption too? I would hope not but we should check and change it for future versions, if this is the case.

What do you think? And is this something you would like to do or should I do it (both is fine with me).

So far, I'm done. My last issue is how we want to handle the upgrade of instances. But let's talk in person about this.