3 ms·

> I think the EU Public sector has too much variance in it to be safely serviced by just one distro. I think that's THE problem. Every member country has at le

> I think the EU Public sector has too much variance in it to be safely serviced by just one distro. I think that's THE problem. Every member country has at least one duplicate of some public sector thing (tax agency, property/citizen registry, health registry etc.) and each of them does their thing slightly differently. > I think a better approach would be to <...> allow local administration <...> establish their own FOSS desktop solutions and base information exchange on truly open standards <...>. Part of the problem are data schemas. Even if you mandate some common information exchange format, it is either somewhat opinionated on data schemas anyway or so generic that you need combinatorial explosion of custom middleware to align schemas. You just kick the can of pain down the road and eventually have a bunch of agencies that are in theory connected but cannot exchange data without "a project" anyway. While slower and more painful to initially deploy, a much more fitting solution would be to have common open core software, enforcing common schemas, but allowing custom extensions/middleware.

bilekas 1y ago
> I think that's THE problem. Every member country has at least one duplicate of some public sector thing (tax agency, property/citizen registry, health registry etc.) and each of them does their thing slightly differently. You say this as if it is a bad thing, this is part and parcel of how the EU works. It's not the same as a Federal system where there is one way and the rest are derivatives of it. There is more autonomy for each of the EU member states to do things how they want.
- friendzis 1y ago
  > It's not the same as a Federal system where there is one way and the rest are derivatives of it. The general framework is still based on the same core principles and regulations, therefore cores most of the systems are much more alike than different. The differences come in additional details, where data models can be extended from common core and local workflows and local integrations, where custom development is required anyway. If those custom developments are built on top of common open core, the know-how translates laterally across whole EU and expertise can at the very least be shared.
  - bilekas 1y ago
    > The general framework is still based on the same core principles and regulations, therefore cores most of the systems are much more alike than different. No not really, I can say from an IE point of view, the reason the border at northern Ireland was such an issue for Brexit was because the good Friday agreement was because this was done outside of the EU. If the EU had the same authority as the Federal in the US as an example, there would be a hard border. General framework yes, for regulations, but how you run your government, absolutely is up to you. Just look to Ordaban in Hungary. Not exactly playing well with the EU, doesn't mean the EU can force him to do something. Edit : Again there are nuances with the EU. And there are issues, but overall it works really well. - Was going to correct Orban's name but he's worth less the effort than typing this.
    - friendzis 1y ago
      Okay, it seems there is misunderstanding. What I meant that having multiple, slightly incompatible reimplementations of essentially the same base software is the biggest technical problem for common data access.

bilekas 1y ago

> I think that's THE problem. Every member country has at least one duplicate of some public sector thing (tax agency, property/citizen registry, health registry etc.) and each of them does their thing slightly differently. You say this as if it is a bad thing, this is part and parcel of how the EU works. It's not the same as a Federal system where there is one way and the rest are derivatives of it. There is more autonomy for each of the EU member states to do things how they want.

friendzis 1y ago
> It's not the same as a Federal system where there is one way and the rest are derivatives of it. The general framework is still based on the same core principles and regulations, therefore cores most of the systems are much more alike than different. The differences come in additional details, where data models can be extended from common core and local workflows and local integrations, where custom development is required anyway. If those custom developments are built on top of common open core, the know-how translates laterally across whole EU and expertise can at the very least be shared.
- bilekas 1y ago
  > The general framework is still based on the same core principles and regulations, therefore cores most of the systems are much more alike than different. No not really, I can say from an IE point of view, the reason the border at northern Ireland was such an issue for Brexit was because the good Friday agreement was because this was done outside of the EU. If the EU had the same authority as the Federal in the US as an example, there would be a hard border. General framework yes, for regulations, but how you run your government, absolutely is up to you. Just look to Ordaban in Hungary. Not exactly playing well with the EU, doesn't mean the EU can force him to do something. Edit : Again there are nuances with the EU. And there are issues, but overall it works really well. - Was going to correct Orban's name but he's worth less the effort than typing this.
  - friendzis 1y ago
    Okay, it seems there is misunderstanding. What I meant that having multiple, slightly incompatible reimplementations of essentially the same base software is the biggest technical problem for common data access.