<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>gngr blog</title>
  <subtitle>This is an Atom feed; use a feed reader for best results</subtitle>
  <link href="https://blog.gngr.info/"/>
  <updated>2021-06-20T01:00:00+05:30</updated>
  <author>
    <name>gngr team</name>
  </author>
  <id>https://blog.gngr.info/</id>
  <entry>
    <title>Funding updates</title>
    <link href="/funding.html"/>
    <id>https://blog.gngr.info/funding.html</id>
    <updated>2021-06-20T01:00:00+05:30</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <div class="content"><p> 
      gngr is participating in <a href="https://fundoss.org/collective/gngr">Fund OSS</a>, a democratic funding experiment for OSS projects.</p><p> 
      Every contribution will be matched by a multiple from the common pool. So each buck will
      go a long way.</p><p> 
      The FundOSS pilot ends on 24th June 2021. For the long term, I have also setup <a href="https://opencollective.com/gngr">OpenCollective</a> and <a href="https://github.com/sponsors/gngrOrg">Github Sponsors</a>.</p><p> 
      If we raise 1000$, we can start offering code bounties for new contributors, while I can focus on
      the re-write of the rendering engine to support CSS3.</p></div>
      </div>
    </content>
  </entry><entry>
    <title>Completed: Repo Migration</title>
    <link href="/completedRepoMigration.html"/>
    <id>https://blog.gngr.info/completedRepoMigration.html</id>
    <updated>2020-07-17T01:00:00+05:30</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <div class="content"><p> 
      The repository migration mentioned in the previous post is now complete.</p><p> 
      The new home for the repository is <a href="https://github.com/gngrOrg/gngr">here</a>.</p><p>Github will automatically redirect older URLs to the new URL.</p></div>
      </div>
    </content>
  </entry><entry>
    <title>Upcoming: Repo Migration</title>
    <link href="/upcomingRepoMigration.html"/>
    <id>https://blog.gngr.info/upcomingRepoMigration.html</id>
    <updated>2020-06-26T01:00:00+05:30</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <div class="content"><p> 
      Just a heads up: We will soon be migrating our code repository hosted on Github under a new Github organisation.</p><p> 
      The migration will be done using Github's migration feature which will ensure that issue history, watches, favourties, etc are preserved.
      Github will also automatically redirect old URLs to the new repository URL.</p><p> 
      A commit confirming the migration has been pushed to the repository more than a month back: <a href="https://github.com/UprootLabs/gngr/commit/5aa2c060257411de2be20b93acde2e6e09051975">Commit Hash: 5aa2c060257411de2be20b93acde2e6e09051975</a></p><p> 
      We will post a new blog entry once the migration is complete.</p></div>
      </div>
    </content>
  </entry><entry>
    <title>gngr v0.3.15</title>
    <link href="/v03.15.html"/>
    <id>https://blog.gngr.info/v03.15.html</id>
    <updated>2019-02-06T01:00:00+05:30</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <div class="content"><p> 
      A new release of gngr is available (version 0.3.15) from the <a href="https://gngr.info/download.html">download page</a>.</p><p> 
      The focus of this release was to update dependencies and ensure compatibility with Java 11. A detailed changelog is in the <a href="https://github.com/UprootLabs/gngr/releases/tag/v0.3.15">GitHub release page</a>.</p><p> 
      Two benefits of running gngr under Java 11 are:</p><ul> <li>When a SOCKS5 proxy is configured, gngr will resolve domain names through the proxy itself.</li><li>http/2 support</li></ul></div>
      </div>
    </content>
  </entry><entry>
    <title>gngr v0.3.14</title>
    <link href="/v03.14.html"/>
    <id>https://blog.gngr.info/v03.14.html</id>
    <updated>2019-01-20T01:00:00+05:30</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <div class="content"><p> 
      A new release of gngr is available (version 0.3.14) from the <a href="https://gngr.info/download.html">download page</a>.</p><p> 
      A minor bug fix release. A detailed changelog is available on the <a href="https://github.com/UprootLabs/gngr/releases/tag/v0.3.14">GitHub release page</a>.</p></div>
      </div>
    </content>
  </entry><entry>
    <title>Easier contributions with DCO</title>
    <link href="/move_to_dco.html"/>
    <id>https://blog.gngr.info/move_to_dco.html</id>
    <updated>2018-06-05T01:00:00+05:30</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <div class="content"><p> 
      In order to make contributions easier to the project, we are changing our
      policy to support Developer Certificate of Origin (DCO) and not require a
      CLA anymore. Signing the CLA was a cumbersome process, so we understand
      if some contributors didn't feel comfortable with it.</p><p> 
      The Developer Certificate of Origin (DCO) is a lightweight way for
      contributors to certify that they wrote or otherwise have the right to
      submit the code they are contributing to the project.  The DCO is
      provided by the developer when they add a &quot;Signed off&quot; line to their git
      commit message. The git command line tool supports adding this with &quot;-s&quot;
      command line option.</p><p> 
      Note that to ensure that the commit message originates from the developer, we also
      require that commits be signed with a GPG key. Setting up GPG does require
      some time, but once setup it, it requires very little manual intervention.</p><h3>Further reading</h3><ul> <li> <a href="https://julien.ponge.org/blog/developer-certificate-of-origin-versus-contributor-license-agreements/">Developer Certificate of Origin versus Contributor License Agreements</a></li><li> <a href="https://lwn.net/Articles/592503/">The most powerful contributor agreement</a></li><li> <a href="https://github.com/UprootLabs/gngr/blob/master/CONTRIBUTING.md">Our Contribution Guide</a></li></ul></div>
      </div>
    </content>
  </entry><entry>
    <title>gngr v0.3.13</title>
    <link href="/v03.13.html"/>
    <id>https://blog.gngr.info/v03.13.html</id>
    <updated>2017-06-30T01:00:00+05:30</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <div class="content"><p> 
      A new release of gngr is available (version 0.3.13) from the <a href="https://gngr.info/download.html">download page</a>.</p><p> 
      The focus of this release was on improving security. A detailed changelog is
      available on the <a href="https://github.com/UprootLabs/gngr/releases/tag/v0.3.13">GitHub release page</a>.</p><h3>New contributors</h3><ul> <li> <a href="https://github.com/SanBlig">@SanBlig</a>, who has contributed to the SRI support</li><li> <a href="https://github.com/Kunal-Deshpande">@Kunal-Deshpande</a>, who has contributed to the Strict HTTPS support</li></ul></div>
      </div>
    </content>
  </entry><entry>
    <title>gngr v0.3.12</title>
    <link href="/v03.12.html"/>
    <id>https://blog.gngr.info/v03.12.html</id>
    <updated>2016-11-08T01:00:00+05:30</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <div class="content"><p> 
      A new release of gngr is available (version 0.3.12) from the <a href="https://gngr.info/download.html">download page</a>.</p><p> 
      The focus of this release was on layout improvements. Close to 680
      progressions observed on the CSS2.1 test suite. A detailed changelog is
      available on the <a href="https://github.com/UprootLabs/gngr/releases/tag/v0.3.12">GitHub release page</a>.</p><h3>New contributors</h3><ul> <li> <a href="https://github.com/chetankothari">@chetankothari</a>, who
        is actually a veteran contributor to gngr. He previously worked on
        integrating jStyleParser into gngr, as seen in
        our <a href="https://github.com/UprootLabs/gngrPreHistoric/graphs/contributors">older repository</a>.</li></ul></div>
      </div>
    </content>
  </entry><entry>
    <title>gngr v0.3.11, usability and layout improvements</title>
    <link href="/v03.11.html"/>
    <id>https://blog.gngr.info/v03.11.html</id>
    <updated>2016-05-25T06:00:00+05:30</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <div class="content"><p> 
      A new release of gngr is available (version 0.3.11) from the <a href="https://gngr.info/download.html">download page</a>.</p><p> 
      The focus of this release was on usability and layout improvements. A detailed changelog is available on the <a href="https://github.com/UprootLabs/gngr/releases/tag/v0.3.11">GitHub release page</a>.</p><h3>Automation</h3><p> 
      We automated the building and testing of the browser and we also have continuous integration running on Travis-CI.
      This has allowed us to make rapid improvements.</p><h3>New contributors</h3><ul> <li> <a href="https://github.com/atiqsayyed">@asayed</a></li><li> <a href="https://github.com/bogas04">@bogas04</a></li><li> <a href="https://github.com/apicellaj">@apicellaj</a></li></ul></div>
      </div>
    </content>
  </entry><entry>
    <title>gngr v0.3.10, huge performance and layout improvements</title>
    <link href="/v03.10.html"/>
    <id>https://blog.gngr.info/v03.10.html</id>
    <updated>2015-09-13T06:00:00+05:30</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <div class="content"><p> 
      A new release of gngr is available (version 0.3.10). Grab it from the <a href="https://gngr.info/download.html">download page</a>.</p><p> 
      The focus of this release was on layout improvements. A detailed changelog is available on the <a href="https://github.com/UprootLabs/gngr/releases/tag/v0.3.10">GitHub release page</a>.</p><p> 
      Change log of the intermediate releases (v0.3.8 and v0.3.9) is also available on the GitHub releases page. We missed updating this blog for them.</p></div>
      </div>
    </content>
  </entry>
</feed>
