Transcripción
Extracto de la transcripción automática del vídeo realizada por YouTube.
well thank you for all coming so soon after lunch I'm Andrew hoppin I'm with New Amsterdam ideas we call ourselves the open Civic platforms company basically what that means is we help governments and nonprofit or civic organizations to implement open
software solutions most notably Drupal we're part of a consortium of other organizations many of them nonprofit who are also focused on so-called Civic technology many of which you probably heard of open knowledge foundation Code for America open plans
a number of others and so we really feel like we're part of this a really vibrant Civic tech community movement right now which is really exciting for us in particular today we're going to talk about to Drupal distributions that we built to help not
only contribute to civic technology work for our customers governments but also to help to make the Civic technology development process more efficient and more systematized itself so it's a little a little bit meta what we're going to talk about today
to give you some context in some background I mean they just give you a really brief history from our perspective of civic tech platforms or as we like to call it and try to make governments work like the web right the web works very well and we want to take
some lessons learned from why it works so well and apply those to make in our governments work better so what do I mean by that well the architecture of the web is based on open standards right and that's one of the reasons we think that it works so well
and it really serves as a platform to build on as we all know in our open Civic hypothesis if you will is that when you combine open standards open-source software community collaboration and open data that you are created a foundation for civic innovation
which can drive better software to make our governments work better and hopefully at lower cost as well and in a nutshell that's what we're up to the US federal government spends about 180 billion dollars on on technology every year just the US federal
government alone meanwhile you know increase getting better thankfully today in the US but and starting in 2008 more or less we hit a real economic crisis in the US and of course that continues to ripple through a lot of the world so there's an imperative
to not improve government simply by throwing more money at the problem but actually to do government technology more efficiently and there's a huge cost sort of baseline that we're working from and at the same time of course when we're in economic
tough times government services are needed more than ever you know tough economic times are really when people and communities rely on government services for help most of all so better government more less money doing it I'm going to give you three different
examples of how we've seen Civic tech to help to make a dent in some of these problems a lot in the US has happened out of the white house's leadership as you heard yesterday from Macon Phillips on video and in the dreese note but President Obama issued
the open government directive in his first month in office in January 2009 and that really has been a led to a lot of opening up of data of government data ever since and of course was done through a Drupal website whitehouse gov our team was doing at the
same time starting in 2009 something very analogous in a very local backwater of government the New York State Senate and we rolled out brand-new Drupal site for NY senate gov which we like to think sort of set a new standard for openness transparency and
ability to participate in legislators you know the bodies that make laws at the state level in the US and then we actually collaborated with the White House and that kind of collaboration goes on today between local state and federal government around Drupal
specifically we're actually sharing code on drupal.org and leveraging off of each other's work so we don't have to pay twice to build the same government specific functionality on top of Drupal another example more recently as you heard in the
Druse note yesterday as well as the White House We the People site or the White House petition site which is helped to sort of create a new way that US citizens can get involved in petitioning their government for change or at least 4 answers on on things
that are important to them and this is now been turned into a distribution on drupal.org right so that every other governments can now take it and a use of it at very low marginal cost to re-implement it for themselves we've helped the White House with
that by creating a white label theme to go on top of that distribution so that you don't have to strip out the White House branding and everything when you take that distribution from drupal org and more broadly Drupal is really becoming the de facto content
management system for governments all around the world got the egg of distribution in Australia the web experience toolkit in Canada open public distribution which is widely adopted in the US as well as the White House's own 44 theme so called that it's
going to be using across all of its White House websites and it's about a quarter of all US federal gov websites are now running Drupal so triples playing a huge role in government or civic technology clearly a couple other realms that have nothing to
do with Drupal though that I think are equally important in terms of seeing the model for how Civic innovation and Civic tech can work right here in Portland the trimet agency that we've all been riding around on with our train passes all week was one
of the first to open up its its scheduled data and in because they did that they were able to well they participated actually in the creation of the general transit feed specification which is why if you use google maps on your phone you're able to see
when your next bus or your next train is coming in most cities in the US and that really started right here in portland and over time it because it was an open standard propagated all over the US and is now literally a standard so a really key aspect of civic
innovation is open standards and here in portland for people did all kinds of innovative things that the city might not have thought to do or had the budget to do but that local developers Civic hackers if you will decided would be cool or useful like this
guy put a sign in his bakery that told the patrons inside when the next bus was going to arrive outside so they could figure out when to pay their check and get up so that they could go outside to meet their bus this is an app that would change your wake-up
time so if there are delays in the transit system it would wake you up earlier so that you'd still get to work on time this also propagated to New York where an organization that I'm involved this open plans built a system called bus time which is
now what New York City uses to help help people figure out when their buses in New York City and it was built on an open modular architecture with open and standards and open API is not at all the traditional way that New York City Department of transit or
most cities would typically build their enterprise you know bus management system so it was really different and that's enabled that technology to be reused and propagate to a lot of cities very quickly and it's also allowed again Civic hackers to
do really innovative things like when this data was released in New York City somebody called up on plans and said hey it's great that you could use a smartphone to see when the bus is coming but she had a feature phone and she wanted to be able to text
to get the schedule result and so within 24 hours developer came up with that application to enable that you know much lower tech lower lower barred entry access to that schedule information so again it opened up innovation a third and final example I want
to give is open three on one for those of you don't know this is a new standard for people reporting to their government issues like you know there's a tree down in this street there's a pothole over here or even you know any non emergency issue
is thought of as a 311 report and there's an open standard for that called open 311 and an open API standard that is now being adopted around the country and now around the world and that has enabled a huge burgeoning movement of application development
to use that 301 data to contribute to that three-on-one data in all kinds of innovative ways and so we've got you know literally hundreds of apps that are based on open three-on-one that are being built most of them not being built with government tax
dollars at all but being built by developers who are building it for their own purposes either to create a new business or simply to contribute to their community so in circuit 2013 hundreds of cities are participating in the Civic tech movement thousands
of apps ten thousands of developers hundreds of thousands of datasets have gone into this so that's all great sounds really good right but we know we work on a lot of these sort of backwaters of government you know the places where things are still done
in a very traditional way and most Civic tech projects still look like this you know big spreadsheets you know 58-page requirements documents for one single feature in 178 page RFPs waterfall processes you know expectation of proprietary licenses etc so we're
still I think tip of the iceberg in terms of the cost savings in the efficiency benefit that Civic tech innovation can possibly deliver and that's where we're trying to contribute to or trying to really create a distributed innovation cycle between
government itself industry and communities or citizens so the innovation can happen in any of those three well realms and benefit each of those other two of the three legs of the stool and we've seen this happen historically in a way that makes us feel
really good about the future so GPS data of course was one of the first government data sets to be opened up and now as fundamentals with so many things that we do whether data was another big one that is enabled you know whether com to exist and actually
[ ... ]
Nota: se han omitido las otras 5.173 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.