OGS-Main
/
ogs-site


			
				
					
						
						
							
							<!DOCTYPE html>
<html>
    <meta charset="utf-8">
    <head>
        <style>
            #header
            {
                background: #2BA6E3;
                padding: 0.7em;
                text-align: left;
            }
            
            #header a
            {
                color: white;
                text-decoration: none;
                padding: 0.5em 1em 0.5em 1em;
            }
            .news_item
            {
                background: #FFFFFF;
                width: 720px;
                padding: 1em;
                margin-top: 2em;
                margin-bottom: 2em;
                border: 1px solid #E0E0E0;
                text-align: left;
            }
            .news_item_contents
            {
                color: #444;
                line-height: 1.5em;
            }
            .news_item_date
            {
                margin-bottom: 2em;
                color: #aaa;
            }
            body
            {
                background: #FAFAFA;
            }
            code, pre
            {
                font-family: monospace, serif;
                font-size: 1em;
                color: #7f0a0c;
            }
            figure
            {
                margin: 0px;
                padding: 0px;
            }
            img
            {
                width: 720px;
            }
            html
            {
                font-family: sans-serif;
            }
            a
            {
                color: #3A91CB;
                text-decoration: none;
            }
            #lang
            {
                float: right;
            }
            figcaption
            {
                color: #aaa;
            }
            
            table
            {
                border-collapse: collapse;
            }
            
            table, th, td
            {
                border: 1px solid #aaa;
                padding: 0.5em;
                margin-top: 0.5em;
                margin-bottom: 0.5em;
            }
        </style>
    </head>
    <body>
        <center>
        <div id="header">
            <a href="../../en/news/index.html">News</a>
            <a href="../../en/page/games.html">Games</a>
            <a href="../../en/page/about.html">About</a>
            <div id="lang">
                <a href="defending-availability.html">EN</a>
                <a href="../../ru/news/defending-availability.html">RU</a>
            </div>
        </div>
        <h1>In the news</h1>
                <div class="news_item">
                    <h2 class="news_item_title">
                        <a href="defending-availability.html">Defending availability</a>
                    </h2>
                    <p class="news_item_date">
                        2019-04-16 00:00
                    </p>
                    <div class="news_item_contents">
        <figure>
<img src="../../images/2019-04-16_defending-availability.jpg" alt="Altai’s Katun river" /><figcaption>Altai’s Katun river</figcaption>
</figure>
<p>In this article, we describe the beginning of our efforts to protect ourselves from third-party solutions.</p>
<p>Since day one of Opensource Game Studio project, we rely heavily on third-party solutions to help us achieve the goal of creating the best game development tools. To this date, we used forums, task trackers, mailing lists, social networks, code version control systems, hosting providers, compiler suites, libraries, and so on. Each third-party solution we used had its own lifespan.</p>
<p>There are two main reasons why we changed third-party solutions:</p>
<ul>
<li>Change in our needs</li>
<li>Solution shutdown</li>
</ul>
<p>The shutdown of <a href="https://code.google.com/archive/">Google Code</a> in 2016 was the first time we experienced the deadly business hand. We were using SVN, Mercurial, and Google issue tracker. We were forced to let all of them go.</p>
<p>We transferred our source code into both <a href="https://bitbucket.org/ogstudio/">BitBucket</a> and <a href="https://github.com/ogstudio/">GitHub</a> because we didn’t want to put all eggs into one basket. We became wiser thanks to Google Code shutdown experience.</p>
<p>Issue tracking had a different fate. At first, we used Bugzilla to manager our issues. However, Bugzilla was so inconvenient that we dropped it in favor of Google Sheets. To this date, we use Google Sheets to plan and log our work on the project. We also use Google Docs to write this very news and review it before publishing.</p>
<p>The shutdown of <a href="https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html">goo.gl</a> (URL shortener) in 2019 was the second time we experienced that same deadly business hand. We were using goo.gl to shorten Google Docs URLs internally. Not really big damage was done, however, this only proved that third-party solutions are not ours, but theirs.</p>
<p>Microsoft <a href="https://github.blog/2018-10-26-github-and-microsoft/">acquired GitHub</a> in 2018. So far (April 2019) Microsoft is doing a really good job by empowering GitHub with the <a href="https://www.gitpod.io/blog/gitpod-launch/">release of GitPod</a> to allow developers to build GitHub projects in a single click. However, Microsoft is also known for shutting down <a href="https://devblogs.microsoft.com/bharry/shutting-down-codeplex/">Codeplex</a> in 2017.</p>
<p>This short track of shutdowns and acquisitions in the course of the past four years highlights the business’ main objective: making profits. Personally, we have no problem with that objective. It’s really hard to live in the 21st century without earning money. We are no exception to this, we pay bills, too. However, a much more humane option would be to let the source code go into the wild, to let interested developers continue the development of those solutions if they want to. Though, this would lead to even more competition with the business itself, something the business tries to avoid at all costs.</p>
<p>We are no business, we make no profits off our tools. Our goals are only to create tools and let them go into the wild, so you can use them. Currently, we use GitHub to host some of our <a href="https://github.com/OGStudio/openscenegraph-cross-platform-examples">tutorials</a> and <a href="https://github.com/OGStudio/openscenegraph-cross-platform-guide">guides</a>. Now imagine that two years from now Microsoft decides to decommission GitHub. Why? Maybe because <a href="https://hackernoon.com/git-wars-why-im-switching-to-gitlab-e471f5e8be2c">people gradually migrate</a> from GitHub to GitLab.</p>
<p>How are we to protect ourselves from the deadly business hand? We consolidate our tools, tutorials, and games into this very site. The first step, now complete, was to create a static site generator to generate this very site.</p>
<p>So far the generated site has the following functionality:</p>
<ul>
<li>news that span multiple pages</li>
<li>standalone pages</li>
<li>sitewide language selection</li>
</ul>
<p>We will make the site even more convenient during this year. Stay tuned!</p>
<p>That’s it for describing the beginning of our efforts to protect ourselves from third-party solutions.</p>

                    </div>
                </div>
        </center>
    </body>
</html>