Enabling Local Government Innovation with Open Source Software
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Schulmann, Tobias
Tobias's talk was the third talk in the "FOSS4G Adoption" session at FOSS4G SotM Oceania 2019, organised by OSGeo Oceania and held at The National Library in Wellington, New Zealand from November 12-15 2019. FOSS4G SotM Oceania is the coming together of Oceania's geospatial open source and open data community - with four days of workshops, presentations, a community sprint and social events.
 I'm going to come to the topic of the day and that really is why should you be using open source software? And for those of you who've read the abstract to this talk, I've sort of given the answer away in there. But I really want to use this opportunity to focus on two issues that I think are probably the most important things about open source at least for me personally. If I have time at the end, I'll also talk about what I think is the major challenge to overcome. Whenever I speak about open source and innovation, there is one project from New Zealand that really I think has a very inspiring story and that project is very relevant to local government and not at all relevant to GIS. But I'll still talk about it and that's the COHA open source library management system. COHA is a work leading, I should say, library management system. It's used in New Zealand and Australia, widely used in the US and the UK. Think all of Turkey's public libraries are running off COHA. It's used in Scandinavia. And it started about 20 years ago in 1999, just 100 kilometers away from here in Horefinua when the local library trust realized that their existing proprietary software couldn't cope with the year 2000 issue. And some of you may still remember that. And they also realized that that existing proprietary vendor had gone out of business and there was no one there to pick up support and to fix the issues so much for the myth of no support in open source. So they had to relatively quickly find a local vendor to work with and create a solution and they've done that basically overnight. Created the COHA library management system and made sure that the solution is open source particularly to avoid problems like they've had previously in the future. And what I find most interesting about COHA really isn't so much the global reach of the project. It's just that over time more and more people from all over the world have started contributing to COHA, translating the software, improving it, contributing bug fixes, raising issues. In fact, the very first contribution to COHA came from Detroit, which is far away from Horefinua for those of you who aren't familiar with geography. And it didn't come from a library. It came from a car manufacturer in Detroit who realized that, hey, this is a really cool system to manage our internal documentation and manuals and other instruction sheets. And they've just gone away quietly and developed the features that they wanted and thought, all right, look, we've used COHA as our foundation. We've built a couple of features and we're contributing those back to the community. The key thing here for me is that they didn't have to ask for permission first. They didn't have to buy a license fee. They didn't have to go through a particular vendor to do that. They were able to just do it. And so I think this potential for unlocking innovation, this freedom really, is the power that comes with open source. If I'm myself solving a problem today, it's highly likely that someone else has already solved a similar project or a problem in the past. And if I can take their solution and improve it and adapt it to my business reality and then contribute my solution back to the community, I think everybody profits in the end. And COHA, 20 years down the track, is still going strong, still receiving patches, still receiving major releases. It's all community driven these days with a couple of prime vendors supporting it, included. But it's still very much a powerful example of how open source in local government and local services can really drive innovation. And I think, and everybody else so far has touched upon this, this leads me to the second aspect that I want to mention. That's all about community. And community sort of in both directions, both outwards into like the global, but also into the more local areas. And obviously the global part is obvious, right? We wouldn't be here today talking about GIS if it wasn't for all those folks who've come before us doing what they've been doing, developing great software, putting open source, legal frameworks in place, fighting for that freedom to share software solutions and inspect open source code and build solutions. And we all know that by, I think, by adopting those open source technologies, we become part of this global community, right? So if you work in a small organization, if you work in remote parts of the country, of the country and local government, you suddenly have access to this global community of researchers and developers and thinkers who are all extremely helpful people and extremely knowledgeable people. And we've heard previously, I can't remember from whom, that when you reach out to them, they tend to get back to you within a day or two and help you solve your problems. And I just yesterday night for fun sort of looked at my GitHub history over the last half year ever since we kind of started this GIS stuff. I'm not the technical person on the project. I've got multiple code commits in open source projects over the last half year. I've got multiple issues raised. I've had multiple discussions on mailing lists just because I think we're doing this stuff at the moment. But I think it is really important to not forget about the local aspect of open source because it allows organizations to work with and to connect to local experts and users. So rather than having to pull in the ISRIs or Red Hats or IBMs of the world, there is nothing wrong with that. It's often great to bring up local talent who may instinctively understand the business realities of what it's like to work and live in a particular area and to run a business in that area. And those folks, because we're using open source, are free to inspect the source code, are free to become experts in the technology. They do not have to go and climb up the corporate training ladder in a big corporate or come back as a consultant from overseas or far. And I think we've already touched on this community aspect in the context of COA briefly, but we're also doing this in the GIS space. So if you look at Wyradistrict Council, for example, their entire GIS stack is built on open source software, GeoServer, GeoWebCache, MapStore, what have you. They have two GIS stacks. They have a public system and an internal system. The public system we look after, the internal system, is managed by a very talented, smart guy they have locally. And that just works for them and it works for us and everyone involved. They're also forming communities with other New Zealand regions. So for example, together with Wyradistrict Council, they have created an extension to GeoServer and MapStore that lets you automatically generate limlight reports. They're not fully fledged, but they do pull in data from LINZ, they pull in data from internal systems, they pull in data from the internal GIS systems, and they serve that to the end user automatically with the click of a button. Something that they wouldn't have been able to do by themselves. They probably wouldn't necessarily have been able to get a commercial vendor to do for them just for fun, but by getting together and pooling a little bit of money together, they were able to pay a developer and a small team of people to do that over a couple of weeks. And I think this community aspect really combined with this freedom to innovate freely and to not have to ask for permission is really at the heart of what makes open source so powerful for solving business problems. However, I think open source is overly complicated. Very often I think I find that as a purchaser of IT products or services, proprietary vendors tend to give me a solution. It may not be perfect, it may not even be a solution to my problem, but it is a solution and it comes with documentation and specification and a contract and a license and I can do my due diligence and I know what I'm getting and I know what it's going to do and I can sort of weigh up the benefits of getting that solution versus paying them a lot of money to give me their product. With open source on the other hand, it's often just like getting the tools. Like I want to build a house and I buy timber, nails and hammers down from the hardware shop, have it all delivered to side and then I stand there and go like, right, now what? That might be totally fine if I happen to be a builder or if I happen to really want to learn how to do it and if I have the time and the money to invest to do that sort of stuff. But very often when I'm in the market for a solution, it's exactly because I'm not that expert and I cannot become that expert. And I don't have anyone on the team to bring up to speed. And that I think makes it incredibly hard to build and buy and maintain an open source solution. If I'm a small local council, if I'm a small organization, I've got to deal with all of this and more just to get a basic GIS backend running. I need servers, I need to sort out my firewalls, my data storage. Does it need to be in New Zealand, can it be on a cloud provider in Australia? I need to render maps, I need to cache tiles, maybe, how does it all work, how does it all fit together? And then what if that one person who's doing my IT leaves the company? What happens next? Because I cannot afford a huge team of IT experts. And so to me this really is, well, I mean, it's obviously a huge deal for small organizations, but it's a problem that's worth solving as an open source community. And I think we're seeing a couple of projects globally that are starting to pull together sub-projects and distributing them as a coherent whole and that's sort of the space that we're trying to navigate as well as catalysts at the moment. So on this one hand, we have this huge potential for innovation and for collaboration for actually delivering value to our customers. And on the other hand, we've got this almost overwhelming complexity of how do we put the stack together and how do we maintain it long term and who takes care of it when it falls over on a public call-out day. So I'm quite lucky to work with some amazing partners inside my company and in local government in New Zealand to try and tackle this complexity. I think together we've created a managed platform where we can now, I think, create an entire GIS backend deployment within less than a minute on pretty much any cloud provider out there that can be looked after either by us or by any skilled IT department. And the idea here really is that someone like us can take care of the more boring stuff of keeping the service running, of making sure everything ticks over, of making sure everything stays up to date and on the lightest maintained version while our customers and our partners can focus on delivering value either to and that either using their own staff or a local vendor or whomever they prefer. So that's sort of our take on reducing complexity. I'm sure there are other ways of doing that. I'm definitely keen to hear your thoughts on the topic, but just to summarize, I think for me free and open source software done right, I think is the enabler for innovation and for community to thrive. And I think both innovation and community are things that are desperately needed globally and locally in the IT space. Thank you. I have one question, which is, who is your team made up of and does a customer ever ask for you to be embedded to say, give them, like, have some knowledge transfers so that internal people can also manage things long term? Okay, so that's two questions, right? I'll answer the first one first. Our team is currently small. We're about three people out of our Christchurch office. We are bringing on another three students over summer who can work on actual open source projects, which is going to be great. And that small size makes it possible for us to operate relatively quick and agile, but obviously we've got this 300 people strong company behind us, which means that all the stuff we do is peer reviewed and is stable and can be picked up by anyone in the company. The other question, yes and no. No one has explicitly asked us to sit down with them and do knowledge transfer and bring someone up to speed, but yes, it has been explicitly part of sort of our conversations when we sat down with partners and we're trying to figure out how we can do this together. So the people we're working with are fairly small organizations. They may not have an IT team or they may have struggled finding the right people to staff an IT team and until that happens, we help them or we're happy to bring anybody else up to speed, of course. I've often found open source software restrictive at times with licensing. Have you got any recommendations around licences to use or moving forward if there's any complicated issues in mixing different pieces of open source software that may have conflicting licences? Yes, I do. I'm not a lawyer though and that is a bit of a legal minefield sometimes. No, I don't have an answer to the question right now. I find most standard open source licences that are currently out there, BSD, Apache and all the rest are open enough for our purposes. Of course, they do require us to make whatever solution we do open source as well, which we're very happy to do. But there are other people in our organizations in the legal sort of site who are a much better place to help you. So if you give me your card afterwards, I'm happy to put you in touch with someone. The balance of getting your bespoke system against getting that package, at which point does it tilt too far over? Either way, like is there a particular point that you just sort of go hands up, can't do it? I don't think there is a particular point. We've designed the system so that as a customer, you could essentially jump into any part of the stack and modify it. We do have some automated testing around making sure that functionality works, such as authentication, such as the cache isn't broken, you know, you're not pulling in crazy things from websites we don't trust. As long as all those tests pass, we're quite happy to roll with whatever changes you make. But because it's really sort of a foundation and back end service, it allows people to build whatever front end solution on top of it, you know, that they like. That's all APIs all the way down in the end. Kia ora. I just wanted to ask you how are you? Because when you've got open source and everything like that on the cultural landscape within New Zealand, there's a lot of information by Manafenawe and Iwi and everything like that. It's culturally sensitive. So there's a little bit of an issue there about how to protect those layers of information to have a suggestion about how you would do that. Yeah, look, there are two aspects to answering that. The first one is that with what we do, the data firmly belongs to the user who's using our platform and they will have to put controls in place to make sure that the data is not shared in any way that's inappropriate. The other thing and that's a bit of a vendor pitch, of course, is that we're trying to keep data within New Zealand. We're running a public cloud service completely based within New Zealand and that, of course, makes sure that whatever data is stored within the platform as long as it runs in our cloud service, it's not always exclusively under New Zealand jurisdiction and not under any other countries' jurisdiction. But really, I think it's important to architect for those sort of problems from the start before even thinking about adding data to a platform. Thank you. I hope that helps. Thank you. Thank you.
 I'm going to come to the topic of the day and that really is why should you be using  open source software?  And for those of you who've read the abstract to this talk, I've sort of given the answer  away in there.  But I really want to use this opportunity to focus on two issues that I think are probably  the most important things about open source at least for me personally.  If I have time at the end, I'll also talk about what I think is the major challenge  to overcome.  Whenever I speak about open source and innovation, there is one project from New Zealand that  really I think has a very inspiring story and that project is very relevant to local  government and not at all relevant to GIS.  But I'll still talk about it and that's the COHA open source library management system.  COHA is a work leading, I should say, library management system.  It's used in New Zealand and Australia, widely used in the US and the UK.  Think all of Turkey's public libraries are running off COHA.  It's used in Scandinavia.  And it started about 20 years ago in 1999, just 100 kilometers away from here in Horefinua  when the local library trust realized that their existing proprietary software couldn't  cope with the year 2000 issue.  And some of you may still remember that.  And they also realized that that existing proprietary vendor had gone out of business  and there was no one there to pick up support and to fix the issues so much for the myth  of no support in open source.  So they had to relatively quickly find a local vendor to work with and create a solution  and they've done that basically overnight.  Created the COHA library management system and made sure that the solution is open source  particularly to avoid problems like they've had previously in the future.  And what I find most interesting about COHA really isn't so much the global reach of the  project.  It's just that over time more and more people from all over the world have started contributing  to COHA, translating the software, improving it, contributing bug fixes, raising issues.  In fact, the very first contribution to COHA came from Detroit, which is far away from  Horefinua for those of you who aren't familiar with geography.  And it didn't come from a library.  It came from a car manufacturer in Detroit who realized that, hey, this is a really cool  system to manage our internal documentation and manuals and other instruction sheets.  And they've just gone away quietly and developed the features that they wanted and thought,  all right, look, we've used COHA as our foundation.  We've built a couple of features and we're contributing those back to the community.  The key thing here for me is that they didn't have to ask for permission first.  They didn't have to buy a license fee.  They didn't have to go through a particular vendor to do that.  They were able to just do it.  And so I think this potential for unlocking innovation, this freedom really, is the power  that comes with open source.  If I'm myself solving a problem today, it's highly likely that someone else has already  solved a similar project or a problem in the past.  And if I can take their solution and improve it and adapt it to my business reality and  then contribute my solution back to the community, I think everybody profits in the end.  And COHA, 20 years down the track, is still going strong, still receiving patches, still  receiving major releases.  It's all community driven these days with a couple of prime vendors supporting it, included.  But it's still very much a powerful example of how open source in local government and  local services can really drive innovation.  And I think, and everybody else so far has touched upon this, this leads me to the second  aspect that I want to mention.  That's all about community.  And community sort of in both directions, both outwards into like the global, but also  into the more local areas.  And obviously the global part is obvious, right?  We wouldn't be here today talking about GIS if it wasn't for all those folks who've come  before us doing what they've been doing, developing great software, putting open source, legal  frameworks in place, fighting for that freedom to share software solutions and inspect open  source code and build solutions.  And we all know that by, I think, by adopting those open source technologies, we become  part of this global community, right?  So if you work in a small organization, if you work in remote parts of the country, of  the country and local government, you suddenly have access to this global community of researchers  and developers and thinkers who are all extremely helpful people and extremely knowledgeable  people.  And we've heard previously, I can't remember from whom, that when you reach out to them,  they tend to get back to you within a day or two and help you solve your problems.  And I just yesterday night for fun sort of looked at my GitHub history over the last  half year ever since we kind of started this GIS stuff.  I'm not the technical person on the project.  I've got multiple code commits in open source projects over the last half year.  I've got multiple issues raised.  I've had multiple discussions on mailing lists just because I think we're doing this stuff  at the moment.  But I think it is really important to not forget about the local aspect of open source  because it allows organizations to work with and to connect to local experts and users.  So rather than having to pull in the ISRIs or Red Hats or IBMs of the world, there is  nothing wrong with that.  It's often great to bring up local talent who may instinctively understand the business  realities of what it's like to work and live in a particular area and to run a business  in that area.  And those folks, because we're using open source, are free to inspect the source code,  are free to become experts in the technology.  They do not have to go and climb up the corporate training ladder in a big corporate or come  back as a consultant from overseas or far.  And I think we've already touched on this community aspect in the context of COA briefly,  but we're also doing this in the GIS space.  So if you look at Wyradistrict Council, for example, their entire GIS stack is built on  open source software, GeoServer, GeoWebCache, MapStore, what have you.  They have two GIS stacks.  They have a public system and an internal system.  The public system we look after, the internal system, is managed by a very talented, smart  guy they have locally.  And that just works for them and it works for us and everyone involved.  They're also forming communities with other New Zealand regions.  So for example, together with Wyradistrict Council, they have created an extension to  GeoServer and MapStore that lets you automatically generate limlight reports.  They're not fully fledged, but they do pull in data from LINZ, they pull in data from  internal systems, they pull in data from the internal GIS systems, and they serve that  to the end user automatically with the click of a button.  Something that they wouldn't have been able to do by themselves.  They probably wouldn't necessarily have been able to get a commercial vendor to do for  them just for fun, but by getting together and pooling a little bit of money together,  they were able to pay a developer and a small team of people to do that over a couple of  weeks.  And I think this community aspect really combined with this freedom to innovate freely and to  not have to ask for permission is really at the heart of what makes open source so powerful  for solving business problems.  However, I think open source is overly complicated.  Very often I think I find that as a purchaser of IT products or services, proprietary vendors  tend to give me a solution.  It may not be perfect, it may not even be a solution to my problem, but it is a solution  and it comes with documentation and specification and a contract and a license and I can do  my due diligence and I know what I'm getting and I know what it's going to do and I can  sort of weigh up the benefits of getting that solution versus paying them a lot of money  to give me their product.  With open source on the other hand, it's often just like getting the tools.  Like I want to build a house and I buy timber, nails and hammers down from the hardware shop,  have it all delivered to side and then I stand there and go like, right, now what?  That might be totally fine if I happen to be a builder or if I happen to really want  to learn how to do it and if I have the time and the money to invest to do that sort of  stuff.  But very often when I'm in the market for a solution, it's exactly because I'm not  that expert and I cannot become that expert.  And I don't have anyone on the team to bring up to speed.  And that I think makes it incredibly hard to build and buy and maintain an open source  solution.  If I'm a small local council, if I'm a small organization, I've got to deal with all of  this and more just to get a basic GIS backend running.  I need servers, I need to sort out my firewalls, my data storage.  Does it need to be in New Zealand, can it be on a cloud provider in Australia?  I need to render maps, I need to cache tiles, maybe, how does it all work, how does it all  fit together?  And then what if that one person who's doing my IT leaves the company?  What happens next?  Because I cannot afford a huge team of IT experts.  And so to me this really is, well, I mean, it's obviously a huge deal for small organizations,  but it's a problem that's worth solving as an open source community.  And I think we're seeing a couple of projects globally that are starting to pull together  sub-projects and distributing them as a coherent whole and that's sort of the space that we're  trying to navigate as well as catalysts at the moment.  So on this one hand, we have this huge potential for innovation and for collaboration for actually  delivering value to our customers.  And on the other hand, we've got this almost overwhelming complexity of how do we put the  stack together and how do we maintain it long term and who takes care of it when it falls  over on a public call-out day.  So I'm quite lucky to work with some amazing partners inside my company and in local government  in New Zealand to try and tackle this complexity.  I think together we've created a managed platform where we can now, I think, create an entire  GIS backend deployment within less than a minute on pretty much any cloud provider out  there that can be looked after either by us or by any skilled IT department.  And the idea here really is that someone like us can take care of the more boring stuff  of keeping the service running, of making sure everything ticks over, of making sure  everything stays up to date and on the lightest maintained version while our customers and  our partners can focus on delivering value either to and that either using their own  staff or a local vendor or whomever they prefer.  So that's sort of our take on reducing complexity.  I'm sure there are other ways of doing that.  I'm definitely keen to hear your thoughts on the topic, but just to summarize, I think  for me free and open source software done right, I think is the enabler for innovation  and for community to thrive.  And I think both innovation and community are things that are desperately needed globally  and locally in the IT space.  Thank you.  I have one question, which is, who is your team made up of and does a customer ever  ask for you to be embedded to say, give them, like, have some knowledge transfers so that  internal people can also manage things long term?  Okay, so that's two questions, right?  I'll answer the first one first.  Our team is currently small.  We're about three people out of our Christchurch office.  We are bringing on another three students over summer who can work on actual open source  projects, which is going to be great.  And that small size makes it possible for us to operate relatively quick and agile, but  obviously we've got this 300 people strong company behind us, which means that all the  stuff we do is peer reviewed and is stable and can be picked up by anyone in the company.  The other question, yes and no.  No one has explicitly asked us to sit down with them and do knowledge transfer and bring  someone up to speed, but yes, it has been explicitly part of sort of our conversations  when we sat down with partners and we're trying to figure out how we can do this together.  So the people we're working with are fairly small organizations.  They may not have an IT team or they may have struggled finding the right people to staff  an IT team and until that happens, we help them or we're happy to bring anybody else  up to speed, of course.  I've often found open source software restrictive at times with licensing.  Have you got any recommendations around licences to use or moving forward if there's any complicated  issues in mixing different pieces of open source software that may have conflicting licences?  Yes, I do.  I'm not a lawyer though and that is a bit of a legal minefield sometimes.  No, I don't have an answer to the question right now.  I find most standard open source licences that are currently out there, BSD, Apache  and all the rest are open enough for our purposes.  Of course, they do require us to make whatever solution we do open source as well, which  we're very happy to do.  But there are other people in our organizations in the legal sort of site who are a much better  place to help you.  So if you give me your card afterwards, I'm happy to put you in touch with someone.  The balance of getting your bespoke system against getting that package, at which point  does it tilt too far over?  Either way, like is there a particular point that you just sort of go hands up, can't do  it?  I don't think there is a particular point.  We've designed the system so that as a customer, you could essentially jump into any part of  the stack and modify it.  We do have some automated testing around making sure that functionality works, such as authentication,  such as the cache isn't broken, you know, you're not pulling in crazy things from websites  we don't trust.  As long as all those tests pass, we're quite happy to roll with whatever changes you make.  But because it's really sort of a foundation and back end service, it allows people to  build whatever front end solution on top of it, you know, that they like.  That's all APIs all the way down in the end.  Kia ora.  I just wanted to ask you how are you?  Because when you've got open source and everything like that on the cultural landscape within  New Zealand, there's a lot of information by Manafenawe and Iwi and everything like that.  It's culturally sensitive.  So there's a little bit of an issue there about how to protect those layers of information  to have a suggestion about how you would do that.  Yeah, look, there are two aspects to answering that.  The first one is that with what we do, the data firmly belongs to the user who's using  our platform and they will have to put controls in place to make sure that the data is not  shared in any way that's inappropriate.  The other thing and that's a bit of a vendor pitch, of course, is that we're trying to  keep data within New Zealand.  We're running a public cloud service completely based within New Zealand and that, of course,  makes sure that whatever data is stored within the platform as long as it runs in our cloud  service, it's not always exclusively under New Zealand jurisdiction and not under any  other countries' jurisdiction.  But really, I think it's important to architect for those sort of problems from the start  before even thinking about adding data to a platform.  Thank you.  I hope that helps.  Thank you.  Thank you.
Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_0_47.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_48_827.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_828_1379.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_1380_1427.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_1428_1751.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_1752_1931.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_1932_2003.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_2004_2303.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_2304_2351.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_2352_2399.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_2400_14495.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_14496_14771.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_14772_15011.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_15012_15971.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_15972_16271.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_16272_18443.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_18444_18491.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_18492_18587.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_18588_18671.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_18672_19787.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_19788_21887.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_21888_24743.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_24744_28271.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_28272_29375.png Tobias_Schulmann_-_Enabling_Local_Government_Innovation_with_Open_Source_Software_kHGGT_eoRPg_29376_29399.png