diff --git a/example/README.md b/example/README.md deleted file mode 100644 index 2b18a49..0000000 --- a/example/README.md +++ /dev/null @@ -1,16 +0,0 @@ -# My talk title - -My talk description - - -## My name - -My bio - -![Profile picture](https://github.com/euruko2012/call-for-proposals/raw/master/example/profile_picture.jpg) - -- [My website](http://www.example.org) -- [My twitter](https://twitter.com/#!/twitter_handle) -- [Past talk slides](http://www.example.org) -- [Past talk video](http://www.example.org) - diff --git a/example/profile_picture.jpg b/example/profile_picture.jpg deleted file mode 100644 index e2e5b50..0000000 Binary files a/example/profile_picture.jpg and /dev/null differ diff --git a/not_that_kind_of_panopticon/README.md b/not_that_kind_of_panopticon/README.md new file mode 100644 index 0000000..55d74a4 --- /dev/null +++ b/not_that_kind_of_panopticon/README.md @@ -0,0 +1,20 @@ +# Not that kind of Panopticon (or how we're publishing the government in Ruby) + +In January 2012, a team of in-house Ruby developers at the Government Digital Service released the first iteration of the [GOV.UK beta](https://www.gov.uk/), showing how a single domain for the UK government could operate for citizens. This was soon followed by the [INSIDE GOVERNMENT beta](https://www.gov.uk/government/), showing how specialist departmental content could belong on GOV.UK, and later this year, content for business owners will also be available on GOV.UK. + +To meet the needs of citizens, business users and those looking for specialist content, GOV.UK demands a solid publishing platform at its core. This talk will cover our approach to building and evolving a Rails publishing platform which can scale across propositions, provide a full editorial workflow process, and can make accountable each item of content to an user need we have identified. We'll also take a look at how we've iterated our data model to simplify our platform, and discuss a few of the 'growing pains' we've experienced in the process, and how we dealt with them. + +## Jordan Hatch + +Jordan Hatch is a young-ish Ruby developer, almost based in London. He's a developer at the Government Digital Service, working on the cross-proposition team for the GOV.UK beta. He tweets at [@1jh](http://twitter.com/1jh). + +![Profile picture](http://farm7.staticflickr.com/6141/6012987592_f92e29cf92_b_d.jpg) + +## James Stewart + +James Stewart is a software developer based in London with his wife and two small kids. Having been building things for the web since the mid-90s, he was technical lead for Alpha.gov.uk and now works as a technical architect for the Government Digital Service helping shape a new open-source platform for the UK Government. + +![Profile picture](https://github.com/jystewart/call-for-proposals/raw/master/rebuilding_government/profile_picture.jpg) + +- [Blog](http://jystewart.net) +- [Twitter](http://twitter.com/jystewart) diff --git a/rebuilding_government/README.md b/rebuilding_government/README.md new file mode 100644 index 0000000..1478e88 --- /dev/null +++ b/rebuilding_government/README.md @@ -0,0 +1,23 @@ +# Rebuilding government (with a little help from Ruby) + +Starting in February 2010 a small group of developers, designers and product thinkers began work on [Alpha.gov.uk](http://www.alpha.gov.uk), demonstrating what a new, simplified and unified website for the UK government might look and feel like. Now with [GOV.UK](https://www.gov.uk) we're showing how it could operate, working with the intention that this will become the definitive government web presence. It's almost all ruby, largely open source and developed out in the open on github (where else?). + +A key design principle has been "tools over content"; with an in-house team we can be a lot more creative than simply implementing a content management system. Instead we're focussed on providing citizens with clear, simple, appropriate guidance and utilities. That's had a huge impact on our architecture, sometimes good and sometimes less so. This talk will explore some of the trade-offs and what we're doing to simplify in the midst of growing attention, requirements and pace. + +Along the way I'll also cover some of the lessons learned from scaling our team fast, baking in security practices, and practicing continuous delivery in a unique and especially risk-averse world. + +## James Stewart + +James Stewart is a software developer based in London with his wife and two small kids. Having been building things for the web since the mid-90s, he was technical lead for Alpha.gov.uk and now works as a technical architect for the Government Digital Service helping shape a new open-source platform for the UK Government. + +![Profile picture](https://github.com/jystewart/call-for-proposals/raw/master/rebuilding_government/profile_picture.jpg) + +- [Blog](http://jystewart.net) +- [Twitter](http://twitter.com/jystewart) + + +## Jordan Hatch + +Jordan Hatch is a young-ish Ruby developer, almost based in London. He's a developer at the Government Digital Service, working on the cross-proposition team for the GOV.UK beta. He tweets at [@1jh](http://twitter.com/1jh). + +![Profile picture](http://farm7.staticflickr.com/6141/6012987592_f92e29cf92_b_d.jpg) \ No newline at end of file diff --git a/rebuilding_government/profile_picture.jpg b/rebuilding_government/profile_picture.jpg new file mode 100644 index 0000000..0c4811c Binary files /dev/null and b/rebuilding_government/profile_picture.jpg differ