[benilov]

Well, the GOV.UK code (https://www.github.com/alphagov) is your 80% (or more likely higher) solution. It's based around many micro-services that integrate over HTTP, so it's extremely extensible.

However, even with the software being perfect, you still have very high barriers of entry to overcome: 1) the local authority is likely to be locked into a 5- or 10-year contract with its current supplier 2) the choice of supplier is rarely (if ever) based on technical excellence/licensing strategy. Usually the people commissioning the IT don't tend to have a very deep understanding of technology, licensing, etc

[danmaz74]

If the gov.uk code covers a lot of the requirements for local administrations in continental EU, that's terrific. Honestly, for now I'm just thinking about this idea, but I don't have the time to study it.

As for the contracts, at least in Italy I've never seen one longer than 3 years, and practically by law the deciding factor is, most of the time, price (which is a big problem on its own).

[benilov]

Well ok, the GOV.UK is the 80+% solution for publishing; transactions is another matter, although hopefully when the Digital by Default Service Standard starts kicking in (specifically the open source provision: https://www.gov.uk/service-manual/digital-by-default#criteri...) then a lot of code around transactions should start appearing.

[danmaz74]

That's interesting, I'll look into it if I'll ever have the time ;)