<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jason Rae on Medium]]></title>
        <description><![CDATA[Stories by Jason Rae on Medium]]></description>
        <link>https://medium.com/@JRae_42073?source=rss-683788e4b765------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Kr4GhdiJErNkUqVn.</url>
            <title>Stories by Jason Rae on Medium</title>
            <link>https://medium.com/@JRae_42073?source=rss-683788e4b765------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:00:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@JRae_42073/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Let’s open source by default!]]></title>
            <link>https://medium.com/we-are-futuregov/lets-open-source-by-default-fb06f509dd9e?source=rss-683788e4b765------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb06f509dd9e</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Jason Rae]]></dc:creator>
            <pubDate>Thu, 21 Sep 2017 15:33:56 GMT</pubDate>
            <atom:updated>2017-10-24T09:46:26.369Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MF6LdNkeeucxLJREvFDaDw.png" /></figure><p>As you may be aware, FutureGov (like so many others in our field) use <a href="https://opensource.com/resources/what-open-source">open source technologies</a> every day to deliver the majority of our technical projects. Without it we wouldn’t be able to build prototypes and products at the speed we do. As well as our core programming language and web framework (Ruby on Rails), there is an extensive list of out of the box technologies that we rely on — JavaScript, jQuery, Sass, SCSS, Cucumber, Rspec, Serverspec, Chef, Knife, Solo, Postgres, Centos, the list goes on. All free for us to use!</p><p>At a more granular, application development level, there’s also an incredible list of Ruby/Sass/JavaScript libraries that the open source community has built for everyone to use however they like. Plug and play features like secure login, Facebook integrations and search filtering can be added to our projects with just a few lines of code.</p><h3>So why should we open source?</h3><p>A saying that always sticks in my mind is “if you take a cookie from the cookie jar you should bloody well put one back”. Contributing back to the community that’s given so much to us could be seen as good manners or simply the right thing to do. It has been high on the wishlist for FutureGov developers for some time now.</p><p>From another perspective, the majority of our projects are funded by and built for local Councils. They’re funded by public money. On that basis, one could argue our work should be freely available to the public that paid for it. As well as open sourcing our code, we should also look to share the conclusions we came to from research and user testing. Sometimes a project might not have the resources to carefully document everything we publish online, but at the least people (and Councils) will be able to see how and why something has been built.</p><p>Thirdly, for our own personal progression as developers, we see the process of publicising our work as a great opportunity to get feedback or even collaboration from the community. GDS published a <a href="https://gds.blog.gov.uk/2017/09/04/the-benefits-of-coding-in-the-open/">great article</a> recently that outlines some benefits for us as developers to open source our work. I considered <a href="https://help.github.com/articles/fork-a-repo/">forking</a> it, but it pretty well says it all in a nutshell ;).</p><h3>If we were to build an open source section of our code what would that be?</h3><p>One of the most popular requests we receive from councils is to develop a local service directory. Lantern, Local Offer and Scout all have a searchable, filterable directories of community services. Users are signposted to these services based on the route they take through the app or the filters they select. We’ve come close in the past to building an <a href="http://microservices.io/patterns/microservices.html">independent microservice</a> to manage the service directory data or at least isolate the relevant code into its own reusable unit. We’re reconsidering the possibility again for an upcoming project.</p><p>For our own sake, if we isolated this functionality into a customisable reusable chunk of code, it could potentially save us time in the long run. If we were to open source this, we would hopefully engage with the development community in our sector who would also benefit from sharing this functionality.</p><h3>The value of our work is not necessarily the IP</h3><p>When bringing up the topic of open source, some wonder “how can anyone make money from it?” Some fear that they will not gain any return from all the effort they put into development — but that’s not the case. In our experience, success depends on a broader range of factors and extends way beyond a solid codebase and a simple UI. Ultimately, the most important factor in any technical delivery is how well the tools fits the service in question to meet the user’s needs.</p><p>We’ve rolled out several licence-based products, such as Local Offer, to multiple councils by delivering a ‘one size fits all’ solution. But the real value is often derived from those managing the content and supporting the service. The IP of the codebase is nothing without the right content for those using the site. The value can ultimately lie in the content management and the support to it’s end users.</p><h3>Could we open source the entire code base of a website?</h3><p>There are<a href="https://www.quora.com/Is-it-generally-easier-or-more-difficult-to-hack-open-source-software-Say-for-example-a-WordPress-site"> mixed opinions </a>about the risk of open sourcing products. <a href="http://www.techrepublic.com/article/security-through-visibility-the-secrets-of-open-source-security/">Visibility vs obscurity</a> is definitely a hot topic. For products that store sensitive information, they would, of course, need some prior discussion with clients before we open source them. Some of our more established products already have IP agreements in place which rules them out. Moving forward we would like to have more discussions around this from the start of a project. As more councils adopt <a href="https://www.gov.uk/service-manual/service-standard">digital service standards (8)</a>, we expect to see a requirement that all new technology from all vendors is open sourced.</p><h3>Open sourcing Hackney Opportunities</h3><p>We recently delivered an <a href="https://github.com/wearefuturegov/ways-into-work">open source</a> pilot web application to Hackney Council. Open sourcing the code was a <a href="https://www.gov.uk/service-manual/service-standard/make-all-new-source-code-open">requirement</a> to meet the Local Government Service Standard. It’s been a great experience for us as developers and really made us consider what’s being shared. We recognise that it would be a lot for someone to take on the code base as it stands, in such an early prototype state. The limited time to deliver an MVP, leads to the code being less robust than we’d like. However, by sharing the <a href="https://github.com/wearefuturegov/ways-into-work/tree/master/doc">project progress</a> and <a href="https://github.com/wearefuturegov/ways-into-work/wiki/Research-Insights">research</a> we hope it will be useful to any council considering a similar technical tool for their ways into work programme.</p><p>We’re excited to see that our work will be taken into <a href="https://www.digitalmarketplace.service.gov.uk/digital-outcomes-and-specialists/opportunities/5289?utm_id=20170920">a second phase</a>. Whether it’s us or someone else that develops the code base further, it’s great that the work will continue. By open sourcing from the get go, we’re in a strong position to invite collaboration to the codebase. This is a win for us, our client and potentially other Councils that can benefit from such a tool. We’re really hopeful that we can take it from a simple pilot into a more comprehensive long-term solution.</p><p>What are your own views on using open source technologies for the public sector? We’d love to hear about your thoughts and experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb06f509dd9e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/we-are-futuregov/lets-open-source-by-default-fb06f509dd9e">Let’s open source by default!</a> was originally published in <a href="https://medium.com/we-are-futuregov">FutureGov</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>