home.social

#gdsteam — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #gdsteam, aggregated by home.social.

  1. I've signed this open letter asking NHS England to keep its code open.

    > Code paid for with public money should be open to the public. This principle is enshrined in the UK Government Design Principles and the NHS Service Standard. It is now being walked back. We are signing this to restate the case.

    Please consider signing, particularly if you've ever contributed to UK public-sector software.

    keepthingsopen.com/

    #GOVUK #GDSTeam #NHSDigital #WorkingInTheOpen #opensource

  2. I've signed this open letter asking NHS England to keep its code open.

    > Code paid for with public money should be open to the public. This principle is enshrined in the UK Government Design Principles and the NHS Service Standard. It is now being walked back. We are signing this to restate the case.

    Please consider signing, particularly if you've ever contributed to UK public-sector software.

    keepthingsopen.com/

    #GOVUK #GDSTeam #NHSDigital #WorkingInTheOpen #opensource

  3. I've signed this open letter asking NHS England to keep its code open.

    > Code paid for with public money should be open to the public. This principle is enshrined in the UK Government Design Principles and the NHS Service Standard. It is now being walked back. We are signing this to restate the case.

    Please consider signing, particularly if you've ever contributed to UK public-sector software.

    keepthingsopen.com/

    #GOVUK #GDSTeam #NHSDigital #WorkingInTheOpen #opensource

  4. I've signed this open letter asking NHS England to keep its code open.

    > Code paid for with public money should be open to the public. This principle is enshrined in the UK Government Design Principles and the NHS Service Standard. It is now being walked back. We are signing this to restate the case.

    Please consider signing, particularly if you've ever contributed to UK public-sector software.

    keepthingsopen.com/

    #GOVUK #GDSTeam #NHSDigital #WorkingInTheOpen #opensource

  5. I've signed this open letter asking NHS England to keep its code open.

    > Code paid for with public money should be open to the public. This principle is enshrined in the UK Government Design Principles and the NHS Service Standard. It is now being walked back. We are signing this to restate the case.

    Please consider signing, particularly if you've ever contributed to UK public-sector software.

    keepthingsopen.com/

    #GOVUK #GDSTeam #NHSDigital #WorkingInTheOpen #opensource

  6. > Public services are built with public money. So unless there’s a good reason not to do so, the code they’re based on should be made available for people to reuse and build on.

    #govuk #gdsteam #workintheopen #publictrust

  7. > Public services are built with public money. So unless there’s a good reason not to do so, the code they’re based on should be made available for people to reuse and build on.

    #govuk #gdsteam #workintheopen #publictrust

  8. > Public services are built with public money. So unless there’s a good reason not to do so, the code they’re based on should be made available for people to reuse and build on.

    #govuk #gdsteam #workintheopen #publictrust

  9. > Public services are built with public money. So unless there’s a good reason not to do so, the code they’re based on should be made available for people to reuse and build on.

    #govuk #gdsteam #workintheopen #publictrust

  10. > Public services are built with public money. So unless there’s a good reason not to do so, the code they’re based on should be made available for people to reuse and build on.

    #govuk #gdsteam #workintheopen #publictrust

  11. Point 12 of the GOV.UK Service Standard:

    > Make new source code open
    >
    > Make all new source code open and reusable, and publish it under appropriate licences. Or if this is not possible, provide a convincing explanation of why this cannot be done for specific subsets of the source code.

    gov.uk/service-manual/service-

    #govuk #gdsteam #workintheopen #publictrust

  12. Point 12 of the GOV.UK Service Standard:

    > Make new source code open
    >
    > Make all new source code open and reusable, and publish it under appropriate licences. Or if this is not possible, provide a convincing explanation of why this cannot be done for specific subsets of the source code.

    gov.uk/service-manual/service-

    #govuk #gdsteam #workintheopen #publictrust

  13. Point 12 of the GOV.UK Service Standard:

    > Make new source code open
    >
    > Make all new source code open and reusable, and publish it under appropriate licences. Or if this is not possible, provide a convincing explanation of why this cannot be done for specific subsets of the source code.

    gov.uk/service-manual/service-

    #govuk #gdsteam #workintheopen #publictrust

  14. Point 12 of the GOV.UK Service Standard:

    > Make new source code open
    >
    > Make all new source code open and reusable, and publish it under appropriate licences. Or if this is not possible, provide a convincing explanation of why this cannot be done for specific subsets of the source code.

    gov.uk/service-manual/service-

    #govuk #gdsteam #workintheopen #publictrust

  15. Point 12 of the GOV.UK Service Standard:

    > Make new source code open
    >
    > Make all new source code open and reusable, and publish it under appropriate licences. Or if this is not possible, provide a convincing explanation of why this cannot be done for specific subsets of the source code.

    gov.uk/service-manual/service-

    #govuk #gdsteam #workintheopen #publictrust

  16. A week late, but here are our #weeknotes for last week which was a break between the project at the Government Digital Service and and a new (to us) project at NHS Digital.

    They include a video of the GFR theme song played live at the Albert Hall!

    gofreerange.com/week-898

    #cooperative #ruby #rails #gdsteam #nhs #stornoway

  17. A busy week at GFR to round off the year!

    * New client project at #gdsteam working on #govuk publishing 💼
    * Value propositions for #jamcoop 🍓
    * Mocha library release ☕️
    * CoTech website revamp 🎨
    * #codeclub up and running 🤖
    * Mission Patch bug fix 🚀
    * Dotfiles on a new laptop 💻

    🎄Merry Christmas🎄 and a 🍾Happy New Year🍾!

    gofreerange.com/week-883

    #weeknotes #ruby #rubyonrails #cooperative

  18. A busy week at GFR to round off the year!

    * New client project at #gdsteam working on #govuk publishing 💼
    * Value propositions for #jamcoop 🍓
    * Mocha library release ☕️
    * CoTech website revamp 🎨
    * #codeclub up and running 🤖
    * Mission Patch bug fix 🚀
    * Dotfiles on a new laptop 💻

    🎄Merry Christmas🎄 and a 🍾Happy New Year🍾!

    gofreerange.com/week-883

    #weeknotes #ruby #rubyonrails #cooperative

  19. A busy week at GFR to round off the year!

    * New client project at #gdsteam working on #govuk publishing 💼
    * Value propositions for #jamcoop 🍓
    * Mocha library release ☕️
    * CoTech website revamp 🎨
    * #codeclub up and running 🤖
    * Mission Patch bug fix 🚀
    * Dotfiles on a new laptop 💻

    🎄Merry Christmas🎄 and a 🍾Happy New Year🍾!

    gofreerange.com/week-883

    #weeknotes #ruby #rubyonrails #cooperative

  20. A busy week at GFR to round off the year!

    * New client project at #gdsteam working on #govuk publishing 💼
    * Value propositions for #jamcoop 🍓
    * Mocha library release ☕️
    * CoTech website revamp 🎨
    * #codeclub up and running 🤖
    * Mission Patch bug fix 🚀
    * Dotfiles on a new laptop 💻

    🎄Merry Christmas🎄 and a 🍾Happy New Year🍾!

    gofreerange.com/week-883

    #weeknotes #ruby #rubyonrails #cooperative

  21. A busy week at GFR to round off the year!

    * New client project at #gdsteam working on #govuk publishing 💼
    * Value propositions for #jamcoop 🍓
    * Mocha library release ☕️
    * CoTech website revamp 🎨
    * #codeclub up and running 🤖
    * Mission Patch bug fix 🚀
    * Dotfiles on a new laptop 💻

    🎄Merry Christmas🎄 and a 🍾Happy New Year🍾!

    gofreerange.com/week-883

    #weeknotes #ruby #rubyonrails #cooperative

  22. > ‘Significant exposure’: AWS outage exposed UK state’s £1.7bn reliance on tech giant

    theguardian.com/technology/202

    Although the GOV.UK PaaS [1] was initially built on AWS, it used Terraform with the intention of using other providers, but then it was decommissioned [2] - perhaps it’s worth reviving…?

    [1]: gov.uk/government/publications
    [2]: gds.blog.gov.uk/2022/07/12/why

    #gdsteam #govuk #aws #cloud #paas

  23. > ‘Significant exposure’: AWS outage exposed UK state’s £1.7bn reliance on tech giant

    theguardian.com/technology/202

    Although the GOV.UK PaaS [1] was initially built on AWS, it used Terraform with the intention of using other providers, but then it was decommissioned [2] - perhaps it’s worth reviving…?

    [1]: gov.uk/government/publications
    [2]: gds.blog.gov.uk/2022/07/12/why

    #gdsteam #govuk #aws #cloud #paas

  24. > ‘Significant exposure’: AWS outage exposed UK state’s £1.7bn reliance on tech giant

    theguardian.com/technology/202

    Although the GOV.UK PaaS [1] was initially built on AWS, it used Terraform with the intention of using other providers, but then it was decommissioned [2] - perhaps it’s worth reviving…?

    [1]: gov.uk/government/publications
    [2]: gds.blog.gov.uk/2022/07/12/why

    #gdsteam #govuk #aws #cloud #paas

  25. > ‘Significant exposure’: AWS outage exposed UK state’s £1.7bn reliance on tech giant

    theguardian.com/technology/202

    Although the GOV.UK PaaS [1] was initially built on AWS, it used Terraform with the intention of using other providers, but then it was decommissioned [2] - perhaps it’s worth reviving…?

    [1]: gov.uk/government/publications
    [2]: gds.blog.gov.uk/2022/07/12/why

    #gdsteam #govuk #aws #cloud #paas

  26. > ‘Significant exposure’: AWS outage exposed UK state’s £1.7bn reliance on tech giant

    theguardian.com/technology/202

    Although the GOV.UK PaaS [1] was initially built on AWS, it used Terraform with the intention of using other providers, but then it was decommissioned [2] - perhaps it’s worth reviving…?

    [1]: gov.uk/government/publications
    [2]: gds.blog.gov.uk/2022/07/12/why

    #gdsteam #govuk #aws #cloud #paas

  27. > Ed Miliband says it is ‘possible’ that UK government should leave X

    theguardian.com/politics/2025/

    Why is this so hard? A Mastodon instance for GOV.UK seems like a no-brainer...

    #gdsteam #govuk #mastodon

  28. > Ed Miliband says it is ‘possible’ that UK government should leave X

    theguardian.com/politics/2025/

    Why is this so hard? A Mastodon instance for GOV.UK seems like a no-brainer...

    #gdsteam #govuk #mastodon

  29. > Ed Miliband says it is ‘possible’ that UK government should leave X

    theguardian.com/politics/2025/

    Why is this so hard? A Mastodon instance for GOV.UK seems like a no-brainer...

    #gdsteam #govuk #mastodon

  30. > Ed Miliband says it is ‘possible’ that UK government should leave X

    theguardian.com/politics/2025/

    Why is this so hard? A Mastodon instance for GOV.UK seems like a no-brainer...

    #gdsteam #govuk #mastodon

  31. Sad to see GDS is still on Twitter and not obviously on the Fediverse…

    SocialMediaService.find_by(name: ‘Twitter’).destroy!

    github.com/alphagov/whitehall/

    #gdsteam #governmentdigitalservice

  32. @DifferentDrummer NHS vs the outcomes of #GDSTeam certainly seems like a night and day experience :/

  33. Does anyone know whether #gdsteam and/or #ukparliament have any plans to run a Mastodon/ActivityPub instance?

    It's a shame that MPs are jumping from the frying pan (X) into the fire (BlueSky)!

    theguardian.com/technology/202