GOV.UK staff use this repository as a forum to discuss and make technical decisions
Clone or download
tijmenb Merge pull request #95 from alphagov/long-term-future-of-apps
RFC: Long term future of applications
Latest commit b2ca466 Oct 18, 2018
Permalink
Failed to load latest commit information.
README.md Add documentation for the new process May 18, 2017
rfc-000-template.md Add documentation for the new process May 18, 2017
rfc-008-migrating-to-new-elasticsearch-cluster.md Update rfc-008-migrating-to-new-elasticsearch-cluster.md May 17, 2017
rfc-011-detailed-guide-categories-to-subtopics-work.md Update rfc-011-detailed-guide-categories-to-subtopics-work.md May 17, 2017
rfc-012-content-store-dependencies-and-frontend-publishing-split.md Update rfc-012-content-store-dependencies-and-frontend-publishing-spl… May 17, 2017
rfc-013-thoughts-on-access-limiting-in-draft.md Update rfc-013-thoughts-on-access-limiting-in-draft.md May 17, 2017
rfc-015-environment-names.md Update rfc-015-environment-names.md May 17, 2017
rfc-016-how-to-prevent-published-live-frontends-from-reading-from-the-draft-content-store.md Update rfc-016-how-to-prevent-published-live-frontends-from-reading-f… May 17, 2017
rfc-017-simpler-draft-stack.md Update rfc-017-simpler-draft-stack.md May 17, 2017
rfc-018-environment-internal-ips.md Update rfc-018-environment-internal-ips.md May 17, 2017
rfc-021-monitoring-for-404s.md Update to discuss fetching data from CDN logs, and to recommend that … May 17, 2017
rfc-022-putting-elasticsearch-backups-in-s3.md Update rfc-022-putting-elasticsearch-backups-in-s3.md May 17, 2017
rfc-023-putting-detailed-guides-paths-under-guidance.md Update rfc-023-putting-detailed-guides-paths-under-guidance.md May 17, 2017
rfc-025-managing-special-snowflake-urls-through-the-publishing-api.md Update rfc-025-managing-special-snowflake-urls-through-the-publishing… May 17, 2017
rfc-026-12-factor-rails-apps.md Fix formatting of RFC 26 Dec 19, 2017
rfc-027-supporting-slug-changes-in-the-publishing-api.md Update rfc-027-supporting-slug-changes-in-the-publishing-api.md May 17, 2017
rfc-028-keeping-gov-uk-s-software-current.md Update rfc-028-keeping-gov-uk-s-software-current.md May 17, 2017
rfc-030-customise-call-to-action-text-on-simple-smart-answers-start-page.md Update rfc-030-customise-call-to-action-text-on-simple-smart-answers-… May 17, 2017
rfc-031-requirements-for-tagging-architecture.md tweak illustrative URL for the draft frontend get endpoint May 17, 2017
rfc-035-explicitly-make-the-details-hash-non-opaque.md Update rfc-035-explicitly-make-the-details-hash-non-opaque.md May 17, 2017
rfc-036-stop-preserving-order-for-links.md Update rfc-036-stop-preserving-order-for-links.md May 17, 2017
rfc-041-separate-document-type-from-format.md Updated field names; more detail on frontend deprecation process May 17, 2017
rfc-042-testing-backend-applications-against-production-traffic.md Update rfc-042-testing-backend-applications-against-production-traffi… May 17, 2017
rfc-043-content-items-without-a-base-path.md Update rfc-043-content-items-without-a-base-path.md May 17, 2017
rfc-044-unpublishing-content-items.md Update rfc-044-unpublishing-content-items.md May 17, 2017
rfc-045-consolidate-sidekiq-usage-into-shared-gem.md Update rfc-045-consolidate-sidekiq-usage-into-shared-gem.md May 17, 2017
rfc-046-break-ability-to-replay-publishing-api-event-log.md Update rfc-046-break-ability-to-replay-publishing-api-event-log.md May 17, 2017
rfc-047-add-another-timestamp-to-content-items.md Update rfc-047-add-another-timestamp-to-content-items.md May 17, 2017
rfc-048-govspeak-rendering-and-embedded-content.md Update rfc-048-govspeak-rendering-and-embedded-content.md May 17, 2017
rfc-050-do-end-to-end-testing-of-gov-uk-applications.md Update rfc-050-do-end-to-end-testing-of-gov-uk-applications.md May 17, 2017
rfc-052-pull-request-merging-process.md Fix formatting for proposed standard list May 22, 2017
rfc-053-terminology-for-migration-progress.md Clarified sources of truth May 17, 2017
rfc-055-content-history.md Update rfc-055-content-history.md May 17, 2017
rfc-056-ordered-link-types.md Update rfc-056-ordered-link-types.md May 17, 2017
rfc-057-default-values-for-application-secrets.md Update rfc-057-default-values-for-application-secrets.md May 17, 2017
rfc-058-publishing-api-events.md Update rfc-058-publishing-api-events.md May 17, 2017
rfc-059-workflow-for-making-changes-to-the-schemas.md Fix formatting for RFC 59 May 17, 2017
rfc-063-naming-new-apps-gems-on-gov-uk.md Fix formatting for RFC 63 May 17, 2017
rfc-064-killing-router-data.md Fix formatting for RFC 64 May 17, 2017
rfc-066-use-github-for-rfcs.md Update rfc-066-use-github-for-rfcs.md May 17, 2017
rfc-067-tagging-to-organisations.md Update RFC67 to make status clearer Jun 12, 2017
rfc-069-classifying-and-measuring-tech-debt.md Add suggested Tech Debt edit from Tom Dolan Jul 4, 2018
rfc-070-path-towards-continuous-deployment-cd.md Update rfc-070-path-towards-continuous-deployment-cd.md May 17, 2017
rfc-075-managing-users.md Update link to the original prototype May 25, 2017
rfc-078-re-architect-signin-permissions-in-signon.md Give signon rfc a number Jun 1, 2017
rfc-080-jsonnet-based-single-file-schemas.md First draft of Jsonnet based single file schema RFC Jul 12, 2017
rfc-081-approach-for-next-iteration-of-content-api.md Add HTTP 451 amendments to Content API approach Sep 18, 2017
rfc-083-case-insensitive-routing.md Change from forcing lowercase to single case Oct 20, 2017
rfc-086-draft-stack-rummager.md Add an action plan for a draft Rummager instance Nov 20, 2017
rfc-087-dealing-with-errors.md Fix "Incorrect bubbling up of errors" Nov 29, 2017
rfc-088-external-content.md Rename to RFC 088 Dec 15, 2017
rfc-091-sharing-assets.md Suggest how to share component assets Feb 8, 2018
rfc-093-retire-govuk-cdn-logs-monitor.md Update RFC 93 following feedback Jun 25, 2018
rfc-095-long-term-future-apps.md Remove policy-publisher Oct 18, 2018

README.md

GOV.UK Request For Comments

GOV.UK staff use this repository as a forum to discuss and make technical decisions. The outcomes of these discussions can be either an Action Plan, or a new Standard that GOV.UK should follow. This repository is open as a reference for other teams within GDS and wider government.

Process

  1. Create a new branch on this repo and copy rfc-000-template.md to rfc-000-my-proposal.md and edit.
  2. Include any images etc in a separate directory named rfc-000 and link to them.
  3. Make a Pull Request (PR) for your branch.
  4. Rename your file and directory with the number of the PR and push as a new commits.
  5. Post a link to your PR in #govuk-developers on Slack and to the govuk-tech-members Google Group. @mention teams in the PR description if you want particular attention from them.
  6. GOV.UK members discuss your proposal using both inline comments against your RFC document and the general PR comments section. Non-technical staff will need to create a free Github account in order to comment.
  7. As changes are requested and agreed in comments, make the changes in your RFC and push them as new commits.
  8. Stay active in the discussion and encourage and remind other relevant people to participate. If you’re unsure who should be involved in a discussion, ask your Tech Lead or a Lead Developer. If you start an RFC it’s up to you to push it through the process and engage people.
  9. Once consensus is reached and approvals given using the Github review system, the PR can be merged.
  10. When an RFC is accepted, ensure the GOV.UK Technical community is made aware of it via Slack and the Google Group.
  11. An RFC can be rejected. This can happen if a consensus isn’t reached, or people agree rejecting it is the right thing to do. In this case the PR should be closed with a suitable comment.

Managing Standards

Standards RFCs shouldn’t be substantially altered after they are accepted, although it’s fine to correct typos and other mistakes via a new PR. In order to change a Standard, the original RFC must be superseded by a new one. The process for this is:

  1. Create a new RFC PR as above, noting in the summary which RFC it is superseding.
  2. In the same branch, mark the old RFC as superseded and link to the new RFC and move (using git mv) it into the archived directory.
  3. When the new RFC is accepted and the PR is merged, the old RFC will no longer be active.

Managing Action Plans

For RFCs where the outcome is an agreed Action Plan, you may want to update the RFC with meaningful status updates in new PRs. Once the plan is either complete or no longer relevant, it should be moved to the archived directory in a new PR.

Historical RFCs

Some RFCs in this repository were migrated from Confluence. They’ve been automatically converted to Markdown, so some formatting might be incorrect. Please fix any issues as you find them in new PRs.