/awesome-egov-de

A curated list of resources on egovernment in Germany

Creative Commons Attribution 4.0 InternationalCC-BY-4.0

awesome-egov-de

A curated list of resources on e-government in Germany.

Pull requests and feedback via issues welcome! Get in touch via the matrix chat at #awesome-egov-de:tchncs.de

Related awesome lists

Communities

Places to ask questions and find other community resources.

Standardization Working Groups

Veranstaltungen

Torsten Frenzel vom eGovernment-Podcast pflegt einen Kalender mit eGovernment-bezogenen Events.

Learning Resources

Policies

  • Gesetz zur Verbesserung des Onlinezugangs zu Verwaltungsleistungen (Onlinezugangsgesetz)
  • Verwaltungsabkommen zur Umsetzung des Onlinezugangsgesetzes: administrative agreement on the implemenation of the Onlinezugangsgesetz (OZG)
    • Prescribes the use of open standards and open source software (SHOULD)
  • EfA-Mindestanforderungen: minimal technical and legal requirements for the implementation of online services financed by the business activity support program (Konjunkturpaket)
  • Servicestandard für die OZG-Umsetzung: standard quality priciples for online services, by BMI, including a self audit
    • User centricity (assessment of user requirements, simple and intuitive use, accessibility, proximity to citizens and gender neutrality, once-only principle, data protection, promotion of digital use)
    • Approach (legal change requirements, agile approach, interconnected portals („Portalverbund“))
    • Collaboration (cross-level cooperation, implementation communities)
    • Openness (open standards, open source, software re-use)
    • IT operations (IT security and support, interoperability, technological evaluation)
    • Controlling (evaluation of user satisfaction, user-centered further development)
  • Föderale IT-Architekturrichtlinien: IT architecture policies by the federal IT architecture board of IT-Planungsrat
    • Stategic architecture guidelines SR1 and SR3 prescribe the use of open standards (MUST)
    • Stategic architecture guidelines SR2 and SR10 prescribe reusing existing software components and loose coupling (MUST)
    • Stategic architecture guideline SR4 prescribes security by default and privacy by default (MUST)
    • Stategic architecture guideline SR5 prescribes an API-first approach (MUST)
    • Stategic architecture guideline SR6 prescribes usability by design (MUST)
    • Stategic architecture guidelines SR7 and SR8 prescribes for open source licensing (dual-/multi-vendor strategie) (MUST)
    • Stategic architecture guideline SR9 prescribes interoperability between infrastrucutre components (MUST)
    • Stategic architecture guideline SR11 prescribes green IT (MUST)
    • Stategic architecture guideline SR12 prescribes the once-only principle (SHOULD)
    • Stategic architecture guideline SR13 prescribes open data by design (MUST)
  • Eckpunkte Umsetzung des OZG mit Mitteln des Konjunkturpakets
    • Mandatory by IT-PLR decision 2020/39
    • mandatory use of open standards
    • source code of custom software development must be released as open-source-software, if possible. Existing licensing models remain unaffected by this.

Literature

Blogs

Podcasts

Videos

Resources on specific topics

UI/UX

Algorithm Transparency

OZG Progress tracking

Technical Documentation

APIs

Services

Tooling for developers

Code Repositories

Open Source (FOSS) projects

  • Formularium: a privacy-first and user-friendly toolkit for municipalities to support them in making their public services available online
  • IRIS connect: open api for health offices with focus on contract tracing
  • Bayerische Ehrenamtskarte: Fully open-source solution for entitlement cards
  • AusweisApp2: app for the german identity card (neuer Personalausweis, nPA)