Split securedrop into separate repositories?

[micahflee]

SecureDrop is a set of different software that runs on different machines. Some software gets run on the app software, and different software gets run on the monitor server. The source and journalist interfaces also run their own software (though they share many of the same internal python modules).

With #415, we're also adding securedrop-client, securedrop-airgap, and a shared module between them, securedrop-updates (maybe it should python-securedrop-updates).

Should these all start out as separate repositories, and should we split the current freedomofpress/securedrop into separate repos as well?

Or should we continue to stick with just one big repo with all of it (how we've been doing it)?

[runasand]

There would be an added challenge here with issues being opened in the wrong repositories. I'm not sure how easy it is to move issues between repositories within a project.

[garrettr]

FWIW, we've split the OSSEC and grsec packages that we maintain into separate repositories (they were originally tracked in install_files): https://github.com/freedomofpress/ossec and https://github.com/freedomofpress/grsec

[ghost]

Years after this issue was open there seems to be an agreement on how how the repositories are set. Feel free to re-open if you feel differently.