Since this repo is MIT licensed and relatively minimal, seeing minimal development activity over the years, and users have a right to know/see/copy what network services support the FOSS apps they rely on, I think it's an easy first step to license our network-accessible server-side components as AGPL to ensure that our users or app aren't "locked in" to private, network-accessible, server-side components.
(Such a guarantee is harder for i.e. the maps-generator which is neither a network service nor redistributed, and so would need some sort of crazy new AAGPL license scheme to guarantee that it is always kept open, but at least this is a more clear-cut case.)
Separately, since we're already considering a revamp of the frontend to make it much more usable (#16), we could discard this repo and make a drop-in replacement that is AGPL licensed from scratch. The existing core logic doesn't seem that hard to reproduce.
Since this repo is MIT licensed and relatively minimal, seeing minimal development activity over the years, and users have a right to know/see/copy what network services support the FOSS apps they rely on, I think it's an easy first step to license our network-accessible server-side components as AGPL to ensure that our users or app aren't "locked in" to private, network-accessible, server-side components.
(Such a guarantee is harder for i.e. the maps-generator which is neither a network service nor redistributed, and so would need some sort of crazy new AAGPL license scheme to guarantee that **_it_** is always kept open, but at least this is a more clear-cut case.)
Separately, since we're already considering a revamp of the frontend to make it much more usable (#16), we could discard this repo and make a drop-in replacement that is AGPL licensed from scratch. The existing core logic doesn't seem that hard to reproduce.