sorted json file

Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>
move static files to ghpages
2026-07-04 07:40:09 +05:30 · 2023-01-02 01:38:55 +05:30 · 2023-01-01 12:18:57 +05:30 · 2022-09-16 19:20:48 +05:30 · 2022-09-16 18:49:40 +05:30 · 2022-09-16 17:42:47 +05:30
177 changed files with 13146 additions and 17906 deletions
@@ -1,11 +0,0 @@
 # To get started with Dependabot version updates, you'll need to specify which
 # package ecosystems to update and where the package manifests are located.
 # Please see the documentation for all configuration options:
 # https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
 version: 2
 updates:
  - package-ecosystem: "pip" # See documentation for possible values
    directory: "/" # Location of package manifests
    schedule:
      interval: "weekly"
@@ -0,0 +1,60 @@
 # Sample workflow for building and deploying a Hugo site to GitHub Pages
 name: Deploy Elm site to Pages
 on:
  # Runs on pushes targeting the default branch
  push:
    branches: ["main"]
  # Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:
 # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
 permissions:
  contents: read
  pages: write
  id-token: write
 # Allow one concurrent deployment
 concurrency:
  group: "pages"
  cancel-in-progress: true
 # Default to bash
 defaults:
  run:
    shell: bash
 jobs:
  # Build job
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Download and install elm
        run: |
          curl -L -o elm.gz https://github.com/elm/compiler/releases/download/0.19.1/binary-for-linux-64-bit.gz
          gunzip elm.gz
          sudo mv elm /usr/bin/elm
          sudo chmod +x /usr/bin/elm
      - name: checkout
        uses: actions/checkout@v3
      - name: build
        run: elm make src/Main.elm --output public/app.js --optimize
      - name: copy content for seving
        run: cp -a content public/content 
      - name: Upload artifact
        uses: actions/upload-pages-artifact@v1
        with:
          path: public/
  # Deployment job
  deploy:
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    runs-on: ubuntu-latest
    needs: build
    steps:
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v1
@@ -1,31 +0,0 @@
 # This is a basic workflow to help you get started with Actions
 name: Publish Blog
 # Controls when the action will run. Triggers the workflow on push or pull request
 # events but only for the main branch
 on:
  push:
    branches: [ main ]
  pull_request:
    branches: [ main ]
 # A workflow run is made up of one or more jobs that can run sequentially or in parallel
 jobs:
  # This workflow contains a single job called "build"
  build:
    # The type of runner that the job will run on
    runs-on: ubuntu-latest
    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
      - uses: actions/checkout@v2
      # Runs a single command using the runners shell
      - name: set up permissions
        run: chmod +x pages-publish.sh
      # Runs a set of commands using the runners shell
      - name: Run a multi-line script
        run: ./pages-publish.sh
@@ -1,5 +1,4 @@
-# build folders
+# elm-package generated files
-output
+elm-stuff
-__pycache__
+# elm-repl generated files
-*.txt
+repl-temp-*
 .vscode
@@ -1,38 +0,0 @@
 <!DOCTYPE html>
 <html class="no-js">
 <head>
  <meta charset="utf-8">
  <title>Lost in Space!</title>
  <meta name="description" content="Somewhere out there beneath the pale moon light...">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="author" content="Avinal">
  <link rel="stylesheet" href="https://avinal.space/custom/css/space404.css" />
  <link rel='stylesheet' href='https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.2.0/css/font-awesome.min.css'>
 </head>
 <body>
  <div class='description' align=center>
    <h1>ME CHERCHEZ-VOUS?</h1>
    <p class='links' align=center>
      <a class='fa fa-github-alt icon' href='https://github.com/avinal' target='_blank'></a>
      <a class='fa fa-mail-forward icon' href='mailto:avinal.xlvii@gmail.com' target='_blank'></a>
    </p>
  </div>
  <div class='solar-syst'>
    <div class='sun'></div>
    <div class='mercury'></div>
    <div class='venus'></div>
    <div class='earth'></div>
    <div class='mars'></div>
    <div class='jupiter'></div>
    <div class='saturn'></div>
    <div class='uranus'></div>
    <div class='neptune'></div>
    <div class='pluto'></div>
    <div class='asteroids-belt'></div>
  </div>
 </body>
 </html>
@@ -1,407 +1,373 @@
-Attribution-NonCommercial 4.0 International
+Mozilla Public License Version 2.0
-
+==================================
 =======================================================================
 Creative Commons Corporation ("Creative Commons") is not a law firm and
 does not provide legal services or legal advice. Distribution of
 Creative Commons public licenses does not create a lawyer-client or
 other relationship. Creative Commons makes its licenses and related
 information available on an "as-is" basis. Creative Commons gives no
 warranties regarding its licenses, any material licensed under their
 terms and conditions, or any related information. Creative Commons
 disclaims all liability for damages resulting from their use to the
 fullest extent possible.
 Using Creative Commons Public Licenses
 Creative Commons public licenses provide a standard set of terms and
 conditions that creators and other rights holders may use to share
 original works of authorship and other material subject to copyright
 and certain other rights specified in the public license below. The
 following considerations are for informational purposes only, are not
 exhaustive, and do not form part of our licenses.
     Considerations for licensors: Our public licenses are
     intended for use by those authorized to give the public
     permission to use material in ways otherwise restricted by
     copyright and certain other rights. Our licenses are
     irrevocable. Licensors should read and understand the terms
     and conditions of the license they choose before applying it.
     Licensors should also secure all rights necessary before
     applying our licenses so that the public can reuse the
     material as expected. Licensors should clearly mark any
     material not subject to the license. This includes other CC-
     licensed material, or material used under an exception or
     limitation to copyright. More considerations for licensors:
 	wiki.creativecommons.org/Considerations_for_licensors
     Considerations for the public: By using one of our public
     licenses, a licensor grants the public permission to use the
     licensed material under specified terms and conditions. If
     the licensor's permission is not necessary for any reason--for
     example, because of any applicable exception or limitation to
     copyright--then that use is not regulated by the license. Our
     licenses grant only permissions under copyright and certain
     other rights that a licensor has authority to grant. Use of
     the licensed material may still be restricted for other
     reasons, including because others have copyright or other
     rights in the material. A licensor may make special requests,
     such as asking that all changes be marked or described.
     Although not required by our licenses, you are encouraged to
     respect those requests where reasonable. More considerations
     for the public: 
 	wiki.creativecommons.org/Considerations_for_licensees
 =======================================================================
 Creative Commons Attribution-NonCommercial 4.0 International Public
 License
 By exercising the Licensed Rights (defined below), You accept and agree
 to be bound by the terms and conditions of this Creative Commons
 Attribution-NonCommercial 4.0 International Public License ("Public
 License"). To the extent this Public License may be interpreted as a
 contract, You are granted the Licensed Rights in consideration of Your
 acceptance of these terms and conditions, and the Licensor grants You
 such rights in consideration of benefits the Licensor receives from
 making the Licensed Material available under these terms and
 conditions.
 Section 1 -- Definitions.
  a. Adapted Material means material subject to Copyright and Similar
     Rights that is derived from or based upon the Licensed Material
     and in which the Licensed Material is translated, altered,
     arranged, transformed, or otherwise modified in a manner requiring
     permission under the Copyright and Similar Rights held by the
     Licensor. For purposes of this Public License, where the Licensed
     Material is a musical work, performance, or sound recording,
     Adapted Material is always produced where the Licensed Material is
     synched in timed relation with a moving image.
  b. Adapter's License means the license You apply to Your Copyright
     and Similar Rights in Your contributions to Adapted Material in
     accordance with the terms and conditions of this Public License.
  c. Copyright and Similar Rights means copyright and/or similar rights
     closely related to copyright including, without limitation,
     performance, broadcast, sound recording, and Sui Generis Database
     Rights, without regard to how the rights are labeled or
     categorized. For purposes of this Public License, the rights
     specified in Section 2(b)(1)-(2) are not Copyright and Similar
     Rights.
  d. Effective Technological Measures means those measures that, in the
     absence of proper authority, may not be circumvented under laws
     fulfilling obligations under Article 11 of the WIPO Copyright
     Treaty adopted on December 20, 1996, and/or similar international
     agreements.
  e. Exceptions and Limitations means fair use, fair dealing, and/or
     any other exception or limitation to Copyright and Similar Rights
     that applies to Your use of the Licensed Material.
  f. Licensed Material means the artistic or literary work, database,
     or other material to which the Licensor applied this Public
     License.
  g. Licensed Rights means the rights granted to You subject to the
     terms and conditions of this Public License, which are limited to
     all Copyright and Similar Rights that apply to Your use of the
     Licensed Material and that the Licensor has authority to license.
  h. Licensor means the individual(s) or entity(ies) granting rights
     under this Public License.
  i. NonCommercial means not primarily intended for or directed towards
     commercial advantage or monetary compensation. For purposes of
     this Public License, the exchange of the Licensed Material for
     other material subject to Copyright and Similar Rights by digital
     file-sharing or similar means is NonCommercial provided there is
     no payment of monetary compensation in connection with the
     exchange.
  j. Share means to provide material to the public by any means or
     process that requires permission under the Licensed Rights, such
     as reproduction, public display, public performance, distribution,
     dissemination, communication, or importation, and to make material
     available to the public including in ways that members of the
     public may access the material from a place and at a time
     individually chosen by them.
  k. Sui Generis Database Rights means rights other than copyright
     resulting from Directive 96/9/EC of the European Parliament and of
     the Council of 11 March 1996 on the legal protection of databases,
     as amended and/or succeeded, as well as other essentially
     equivalent rights anywhere in the world.
  l. You means the individual or entity exercising the Licensed Rights
     under this Public License. Your has a corresponding meaning.
 Section 2 -- Scope.
  a. License grant.
       1. Subject to the terms and conditions of this Public License,
          the Licensor hereby grants You a worldwide, royalty-free,
          non-sublicensable, non-exclusive, irrevocable license to
          exercise the Licensed Rights in the Licensed Material to:
            a. reproduce and Share the Licensed Material, in whole or
               in part, for NonCommercial purposes only; and
            b. produce, reproduce, and Share Adapted Material for
               NonCommercial purposes only.
       2. Exceptions and Limitations. For the avoidance of doubt, where
          Exceptions and Limitations apply to Your use, this Public
          License does not apply, and You do not need to comply with
          its terms and conditions.
       3. Term. The term of this Public License is specified in Section
          6(a).
       4. Media and formats; technical modifications allowed. The
          Licensor authorizes You to exercise the Licensed Rights in
          all media and formats whether now known or hereafter created,
          and to make technical modifications necessary to do so. The
          Licensor waives and/or agrees not to assert any right or
          authority to forbid You from making technical modifications
          necessary to exercise the Licensed Rights, including
          technical modifications necessary to circumvent Effective
          Technological Measures. For purposes of this Public License,
          simply making modifications authorized by this Section 2(a)
          (4) never produces Adapted Material.
       5. Downstream recipients.
            a. Offer from the Licensor -- Licensed Material. Every
               recipient of the Licensed Material automatically
               receives an offer from the Licensor to exercise the
               Licensed Rights under the terms and conditions of this
               Public License.
            b. No downstream restrictions. You may not offer or impose
               any additional or different terms or conditions on, or
               apply any Effective Technological Measures to, the
               Licensed Material if doing so restricts exercise of the
               Licensed Rights by any recipient of the Licensed
               Material.
       6. No endorsement. Nothing in this Public License constitutes or
          may be construed as permission to assert or imply that You
          are, or that Your use of the Licensed Material is, connected
          with, or sponsored, endorsed, or granted official status by,
          the Licensor or others designated to receive attribution as
          provided in Section 3(a)(1)(A)(i).
-  b. Other rights.
+1. Definitions
 --------------
-       1. Moral rights, such as the right of integrity, are not
+1.1. "Contributor"
-          licensed under this Public License, nor are publicity,
+    means each individual or legal entity that creates, contributes to
-          privacy, and/or other similar personality rights; however, to
+    the creation of, or owns Covered Software.
          the extent possible, the Licensor waives and/or agrees not to
          assert any such rights held by the Licensor to the limited
          extent necessary to allow You to exercise the Licensed
          Rights, but not otherwise.
       2. Patent and trademark rights are not licensed under this
          Public License.
       3. To the extent possible, the Licensor waives any right to
          collect royalties from You for the exercise of the Licensed
          Rights, whether directly or through a collecting society
          under any voluntary or waivable statutory or compulsory
          licensing scheme. In all other cases the Licensor expressly
          reserves any right to collect such royalties, including when
          the Licensed Material is used other than for NonCommercial
          purposes.
 Section 3 -- License Conditions.
 Your exercise of the Licensed Rights is expressly made subject to the
 following conditions.
  a. Attribution.
-       1. If You Share the Licensed Material (including in modified
+1.2. "Contributor Version"
-          form), You must:
+    means the combination of the Contributions of others (if any) used
    by a Contributor and that particular Contributor's Contribution.
-            a. retain the following if it is supplied by the Licensor
+1.3. "Contribution"
-               with the Licensed Material:
+    means Covered Software of a particular Contributor.
-                 i. identification of the creator(s) of the Licensed
+1.4. "Covered Software"
-                    Material and any others designated to receive
+    means Source Code Form to which the initial Contributor has attached
-                    attribution, in any reasonable manner requested by
+    the notice in Exhibit A, the Executable Form of such Source Code
-                    the Licensor (including by pseudonym if
+    Form, and Modifications of such Source Code Form, in each case
-                    designated);
+    including portions thereof.
-                ii. a copyright notice;
+1.5. "Incompatible With Secondary Licenses"
    means
-               iii. a notice that refers to this Public License;
+    (a) that the initial Contributor has attached the notice described
-
+        in Exhibit B to the Covered Software; or
                iv. a notice that refers to the disclaimer of
                    warranties;
                 v. a URI or hyperlink to the Licensed Material to the
                    extent reasonably practicable;
-            b. indicate if You modified the Licensed Material and
+    (b) that the Covered Software was made available under the terms of
-               retain an indication of any previous modifications; and
+        version 1.1 or earlier of the License, but not also under the
        terms of a Secondary License.
-            c. indicate the Licensed Material is licensed under this
+1.6. "Executable Form"
-               Public License, and include the text of, or the URI or
+    means any form of the work other than Source Code Form.
               hyperlink to, this Public License.
-       2. You may satisfy the conditions in Section 3(a)(1) in any
+1.7. "Larger Work"
-          reasonable manner based on the medium, means, and context in
+    means a work that combines Covered Software with other material, in
-          which You Share the Licensed Material. For example, it may be
+    a separate file or files, that is not Covered Software.
          reasonable to satisfy the conditions by providing a URI or
          hyperlink to a resource that includes the required
          information.
-       3. If requested by the Licensor, You must remove any of the
+1.8. "License"
-          information required by Section 3(a)(1)(A) to the extent
+    means this document.
          reasonably practicable.
-       4. If You Share Adapted Material You produce, the Adapter's
+1.9. "Licensable"
-          License You apply must not prevent recipients of the Adapted
+    means having the right to grant, to the maximum extent possible,
-          Material from complying with this Public License.
+    whether at the time of the initial grant or subsequently, any and
    all of the rights conveyed by this License.
 1.10. "Modifications"
    means any of the following:
-Section 4 -- Sui Generis Database Rights.
+    (a) any file in Source Code Form that results from an addition to,
        deletion from, or modification of the contents of Covered
        Software; or
-Where the Licensed Rights include Sui Generis Database Rights that
+    (b) any new file in Source Code Form that contains any Covered
-apply to Your use of the Licensed Material:
+        Software.
-  a. for the avoidance of doubt, Section 2(a)(1) grants You the right
+1.11. "Patent Claims" of a Contributor
-     to extract, reuse, reproduce, and Share all or a substantial
+    means any patent claim(s), including without limitation, method,
-     portion of the contents of the database for NonCommercial purposes
+    process, and apparatus claims, in any patent Licensable by such
-     only;
+    Contributor that would be infringed, but for the grant of the
    License, by the making, using, selling, offering for sale, having
    made, import, or transfer of either its Contributions or its
    Contributor Version.
-  b. if You include all or a substantial portion of the database
+1.12. "Secondary License"
-     contents in a database in which You have Sui Generis Database
+    means either the GNU General Public License, Version 2.0, the GNU
-     Rights, then the database in which You have Sui Generis Database
+    Lesser General Public License, Version 2.1, the GNU Affero General
-     Rights (but not its individual contents) is Adapted Material; and
+    Public License, Version 3.0, or any later versions of those
    licenses.
-  c. You must comply with the conditions in Section 3(a) if You Share
+1.13. "Source Code Form"
-     all or a substantial portion of the contents of the database.
+    means the form of the work preferred for making modifications.
-For the avoidance of doubt, this Section 4 supplements and does not
+1.14. "You" (or "Your")
-replace Your obligations under this Public License where the Licensed
+    means an individual or a legal entity exercising rights under this
-Rights include other Copyright and Similar Rights.
+    License. For legal entities, "You" includes any entity that
    controls, is controlled by, or is under common control with You. For
    purposes of this definition, "control" means (a) the power, direct
    or indirect, to cause the direction or management of such entity,
    whether by contract or otherwise, or (b) ownership of more than
    fifty percent (50%) of the outstanding shares or beneficial
    ownership of such entity.
 2. License Grants and Conditions
 --------------------------------
-Section 5 -- Disclaimer of Warranties and Limitation of Liability.
+2.1. Grants
-  a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
+Each Contributor hereby grants You a world-wide, royalty-free,
-     EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
+non-exclusive license:
     AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
     ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
     IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
     WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
     PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
     ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
     KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
     ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
-  b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
+(a) under intellectual property rights (other than patent or trademark)
-     TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
+    Licensable by such Contributor to use, reproduce, make available,
-     NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
+    modify, display, perform, distribute, and otherwise exploit its
-     INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
+    Contributions, either on an unmodified basis, with Modifications, or
-     COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
+    as part of a Larger Work; and
     USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
     ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
     DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
     IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
-  c. The disclaimer of warranties and limitation of liability provided
+(b) under Patent Claims of such Contributor to make, use, sell, offer
-     above shall be interpreted in a manner that, to the extent
+    for sale, have made, import, and otherwise transfer either its
-     possible, most closely approximates an absolute disclaimer and
+    Contributions or its Contributor Version.
     waiver of all liability.
 2.2. Effective Date
-Section 6 -- Term and Termination.
+The licenses granted in Section 2.1 with respect to any Contribution
 become effective for each Contribution on the date the Contributor first
 distributes such Contribution.
-  a. This Public License applies for the term of the Copyright and
+2.3. Limitations on Grant Scope
     Similar Rights licensed here. However, if You fail to comply with
     this Public License, then Your rights under this Public License
     terminate automatically.
-  b. Where Your right to use the Licensed Material has terminated under
+The licenses granted in this Section 2 are the only rights granted under
-     Section 6(a), it reinstates:
+this License. No additional rights or licenses will be implied from the
-
+distribution or licensing of Covered Software under this License.
-       1. automatically as of the date the violation is cured, provided
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
-          it is cured within 30 days of Your discovery of the
+Contributor:
-          violation; or
+
-
+(a) for any code that a Contributor has removed from Covered Software;
-       2. upon express reinstatement by the Licensor.
+    or
-
+
-     For the avoidance of doubt, this Section 6(b) does not affect any
+(b) for infringements caused by: (i) Your and any other third party's
-     right the Licensor may have to seek remedies for Your violations
+    modifications of Covered Software, or (ii) the combination of its
-     of this Public License.
+    Contributions with other software (except as part of its Contributor
-
+    Version); or
-  c. For the avoidance of doubt, the Licensor may also offer the
+
-     Licensed Material under separate terms or conditions or stop
+(c) under Patent Claims infringed by Covered Software in the absence of
-     distributing the Licensed Material at any time; however, doing so
+    its Contributions.
-     will not terminate this Public License.
+
-
+This License does not grant any rights in the trademarks, service marks,
-  d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
+or logos of any Contributor (except as may be necessary to comply with
-     License.
+the notice requirements in Section 3.4).
-
+
-
+2.4. Subsequent Licenses
-Section 7 -- Other Terms and Conditions.
+
-
+No Contributor makes additional grants as a result of Your choice to
-  a. The Licensor shall not be bound by any additional or different
+distribute the Covered Software under a subsequent version of this
-     terms or conditions communicated by You unless expressly agreed.
+License (see Section 10.2) or under the terms of a Secondary License (if
-
+permitted under the terms of Section 3.3).
-  b. Any arrangements, understandings, or agreements regarding the
+
-     Licensed Material not stated herein are separate from and
+2.5. Representation
-     independent of the terms and conditions of this Public License.
+
-
+Each Contributor represents that the Contributor believes its
-
+Contributions are its original creation(s) or it has sufficient rights
-Section 8 -- Interpretation.
+to grant the rights to its Contributions conveyed by this License.
-
+
-  a. For the avoidance of doubt, this Public License does not, and
+2.6. Fair Use
-     shall not be interpreted to, reduce, limit, restrict, or impose
+
-     conditions on any use of the Licensed Material that could lawfully
+This License is not intended to limit any rights You have under
-     be made without permission under this Public License.
+applicable copyright doctrines of fair use, fair dealing, or other
-
+equivalents.
-  b. To the extent possible, if any provision of this Public License is
+
-     deemed unenforceable, it shall be automatically reformed to the
+2.7. Conditions
-     minimum extent necessary to make it enforceable. If the provision
+
-     cannot be reformed, it shall be severed from this Public License
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
-     without affecting the enforceability of the remaining terms and
+in Section 2.1.
-     conditions.
+
-
+3. Responsibilities
-  c. No term or condition of this Public License will be waived and no
+-------------------
-     failure to comply consented to unless expressly agreed to by the
+
-     Licensor.
+3.1. Distribution of Source Form
-
+
-  d. Nothing in this Public License constitutes or may be interpreted
+All distribution of Covered Software in Source Code Form, including any
-     as a limitation upon, or waiver of, any privileges and immunities
+Modifications that You create or to which You contribute, must be under
-     that apply to the Licensor or You, including from the legal
+the terms of this License. You must inform recipients that the Source
-     processes of any jurisdiction or authority.
+Code Form of the Covered Software is governed by the terms of this
-
+License, and how they can obtain a copy of this License. You may not
-=======================================================================
+attempt to alter or restrict the recipients' rights in the Source Code
-
+Form.
-Creative Commons is not a party to its public
+
-licenses. Notwithstanding, Creative Commons may elect to apply one of
+3.2. Distribution of Executable Form
-its public licenses to material it publishes and in those instances
+
-will be considered the “Licensor.” The text of the Creative Commons
+If You distribute Covered Software in Executable Form then:
-public licenses is dedicated to the public domain under the CC0 Public
+
-Domain Dedication. Except for the limited purpose of indicating that
+(a) such Covered Software must also be made available in Source Code
-material is shared under a Creative Commons public license or as
+    Form, as described in Section 3.1, and You must inform recipients of
-otherwise permitted by the Creative Commons policies published at
+    the Executable Form how they can obtain a copy of such Source Code
-creativecommons.org/policies, Creative Commons does not authorize the
+    Form by reasonable means in a timely manner, at a charge no more
-use of the trademark "Creative Commons" or any other trademark or logo
+    than the cost of distribution to the recipient; and
-of Creative Commons without its prior written consent including,
+
-without limitation, in connection with any unauthorized modifications
+(b) You may distribute such Executable Form under the terms of this
-to any of its public licenses or any other arrangements,
+    License, or sublicense it under different terms, provided that the
-understandings, or agreements concerning use of licensed material. For
+    license for the Executable Form does not attempt to limit or alter
-the avoidance of doubt, this paragraph does not form part of the
+    the recipients' rights in the Source Code Form under this License.
-public licenses.
+
-
+3.3. Distribution of a Larger Work
-Creative Commons may be contacted at creativecommons.org.
+
 You may create and distribute a Larger Work under terms of Your choice,
 provided that You also comply with the requirements of this License for
 the Covered Software. If the Larger Work is a combination of Covered
 Software with a work governed by one or more Secondary Licenses, and the
 Covered Software is not Incompatible With Secondary Licenses, this
 License permits You to additionally distribute such Covered Software
 under the terms of such Secondary License(s), so that the recipient of
 the Larger Work may, at their option, further distribute the Covered
 Software under the terms of either this License or such Secondary
 License(s).
 3.4. Notices
 You may not remove or alter the substance of any license notices
 (including copyright notices, patent notices, disclaimers of warranty,
 or limitations of liability) contained within the Source Code Form of
 the Covered Software, except that You may alter any license notices to
 the extent required to remedy known factual inaccuracies.
 3.5. Application of Additional Terms
 You may choose to offer, and to charge a fee for, warranty, support,
 indemnity or liability obligations to one or more recipients of Covered
 Software. However, You may do so only on Your own behalf, and not on
 behalf of any Contributor. You must make it absolutely clear that any
 such warranty, support, indemnity, or liability obligation is offered by
 You alone, and You hereby agree to indemnify every Contributor for any
 liability incurred by such Contributor as a result of warranty, support,
 indemnity or liability terms You offer. You may include additional
 disclaimers of warranty and limitations of liability specific to any
 jurisdiction.
 4. Inability to Comply Due to Statute or Regulation
 ---------------------------------------------------
 If it is impossible for You to comply with any of the terms of this
 License with respect to some or all of the Covered Software due to
 statute, judicial order, or regulation then You must: (a) comply with
 the terms of this License to the maximum extent possible; and (b)
 describe the limitations and the code they affect. Such description must
 be placed in a text file included with all distributions of the Covered
 Software under this License. Except to the extent prohibited by statute
 or regulation, such description must be sufficiently detailed for a
 recipient of ordinary skill to be able to understand it.
 5. Termination
 --------------
 5.1. The rights granted under this License will terminate automatically
 if You fail to comply with any of its terms. However, if You become
 compliant, then the rights granted under this License from a particular
 Contributor are reinstated (a) provisionally, unless and until such
 Contributor explicitly and finally terminates Your grants, and (b) on an
 ongoing basis, if such Contributor fails to notify You of the
 non-compliance by some reasonable means prior to 60 days after You have
 come back into compliance. Moreover, Your grants from a particular
 Contributor are reinstated on an ongoing basis if such Contributor
 notifies You of the non-compliance by some reasonable means, this is the
 first time You have received notice of non-compliance with this License
 from such Contributor, and You become compliant prior to 30 days after
 Your receipt of the notice.
 5.2. If You initiate litigation against any entity by asserting a patent
 infringement claim (excluding declaratory judgment actions,
 counter-claims, and cross-claims) alleging that a Contributor Version
 directly or indirectly infringes any patent, then the rights granted to
 You by any and all Contributors for the Covered Software under Section
 2.1 of this License shall terminate.
 5.3. In the event of termination under Sections 5.1 or 5.2 above, all
 end user license agreements (excluding distributors and resellers) which
 have been validly granted by You or Your distributors under this License
 prior to termination shall survive termination.
 ************************************************************************
 *                                                                      *
 *  6. Disclaimer of Warranty                                           *
 *  -------------------------                                           *
 *                                                                      *
 *  Covered Software is provided under this License on an "as is"       *
 *  basis, without warranty of any kind, either expressed, implied, or  *
 *  statutory, including, without limitation, warranties that the       *
 *  Covered Software is free of defects, merchantable, fit for a        *
 *  particular purpose or non-infringing. The entire risk as to the     *
 *  quality and performance of the Covered Software is with You.        *
 *  Should any Covered Software prove defective in any respect, You     *
 *  (not any Contributor) assume the cost of any necessary servicing,   *
 *  repair, or correction. This disclaimer of warranty constitutes an   *
 *  essential part of this License. No use of any Covered Software is   *
 *  authorized under this License except under this disclaimer.         *
 *                                                                      *
 ************************************************************************
 ************************************************************************
 *                                                                      *
 *  7. Limitation of Liability                                          *
 *  --------------------------                                          *
 *                                                                      *
 *  Under no circumstances and under no legal theory, whether tort      *
 *  (including negligence), contract, or otherwise, shall any           *
 *  Contributor, or anyone who distributes Covered Software as          *
 *  permitted above, be liable to You for any direct, indirect,         *
 *  special, incidental, or consequential damages of any character      *
 *  including, without limitation, damages for lost profits, loss of    *
 *  goodwill, work stoppage, computer failure or malfunction, or any    *
 *  and all other commercial damages or losses, even if such party      *
 *  shall have been informed of the possibility of such damages. This   *
 *  limitation of liability shall not apply to liability for death or   *
 *  personal injury resulting from such party's negligence to the       *
 *  extent applicable law prohibits such limitation. Some               *
 *  jurisdictions do not allow the exclusion or limitation of           *
 *  incidental or consequential damages, so this exclusion and          *
 *  limitation may not apply to You.                                    *
 *                                                                      *
 ************************************************************************
 8. Litigation
 -------------
 Any litigation relating to this License may be brought only in the
 courts of a jurisdiction where the defendant maintains its principal
 place of business and such litigation shall be governed by laws of that
 jurisdiction, without reference to its conflict-of-law provisions.
 Nothing in this Section shall prevent a party's ability to bring
 cross-claims or counter-claims.
 9. Miscellaneous
 ----------------
 This License represents the complete agreement concerning the subject
 matter hereof. If any provision of this License is held to be
 unenforceable, such provision shall be reformed only to the extent
 necessary to make it enforceable. Any law or regulation which provides
 that the language of a contract shall be construed against the drafter
 shall not be used to construe this License against a Contributor.
 10. Versions of the License
 ---------------------------
 10.1. New Versions
 Mozilla Foundation is the license steward. Except as provided in Section
 10.3, no one other than the license steward has the right to modify or
 publish new versions of this License. Each version will be given a
 distinguishing version number.
 10.2. Effect of New Versions
 You may distribute the Covered Software under the terms of the version
 of the License under which You originally received the Covered Software,
 or under the terms of any subsequent version published by the license
 steward.
 10.3. Modified Versions
 If you create software not governed by this License, and you want to
 create a new license for such software, you may create and use a
 modified version of this License if you rename the license and remove
 any references to the name of the license steward (except to note that
 such modified license differs from this License).
 10.4. Distributing Source Code Form that is Incompatible With Secondary
 Licenses
 If You choose to distribute Source Code Form that is Incompatible With
 Secondary Licenses under the terms of this version of the License, the
 notice described in Exhibit B of this License must be attached.
 Exhibit A - Source Code Form License Notice
 -------------------------------------------
  This Source Code Form is subject to the terms of the Mozilla Public
  License, v. 2.0. If a copy of the MPL was not distributed with this
  file, You can obtain one at http://mozilla.org/MPL/2.0/.
 If it is not possible or desirable to put the notice in a particular
 file, then You may include the notice in a location (such as a LICENSE
 file in a relevant directory) where a recipient would be likely to look
 for such a notice.
 You may add additional accurate notices of copyright ownership.
 Exhibit B - "Incompatible With Secondary Licenses" Notice
 ---------------------------------------------------------
  This Source Code Form is "Incompatible With Secondary Licenses", as
  defined by the Mozilla Public License, v. 2.0.
@@ -1,88 +0,0 @@
 PY?=python3
 PELICAN?=pelican
 PELICANTHEME?=pelican-themes
 PELICANOPTS=
 BASEDIR=$(CURDIR)
 INPUTDIR=$(BASEDIR)/content
 OUTPUTDIR=$(BASEDIR)/output
 THEMEDIR=$(BASEDIR)/themes/alchemy
 CONFFILE=$(BASEDIR)/pelicanconf.py
 PUBLISHCONF=$(BASEDIR)/publishconf.py
 GITHUB_PAGES_BRANCH=gh-pages
 DEBUG ?= 0
 ifeq ($(DEBUG), 1)
 	PELICANOPTS += -D
 endif
 RELATIVE ?= 0
 ifeq ($(RELATIVE), 1)
 	PELICANOPTS += --relative-urls
 endif
 SERVER ?= "0.0.0.0"
 PORT ?= 0
 ifneq ($(PORT), 0)
 	PELICANOPTS += -p $(PORT)
 endif
 help:
 	@echo 'Makefile for a pelican Web site                                           '
 	@echo '                                                                          '
 	@echo 'Usage:                                                                    '
 	@echo '   make html                           (re)generate the web site          '
 	@echo '   make clean                          remove the generated files         '
 	@echo '   make regenerate                     regenerate files upon modification '
 	@echo '   make publish                        generate using production settings '
 	@echo '	  make theme                          add theme                          '
 	@echo '   make serve [PORT=8000]              serve site at http://localhost:8000'
 	@echo '   make serve-global [SERVER=0.0.0.0]  serve (as root) to $(SERVER):80    '
 	@echo '   make devserver [PORT=8000]          serve and regenerate together      '
 	@echo '   make ssh_upload                     upload the web site via SSH        '
 	@echo '   make rsync_upload                   upload the web site via rsync+ssh  '
 	@echo '   make github                         upload the web site via gh-pages   '
 	@echo '                                                                          '
 	@echo 'Set the DEBUG variable to 1 to enable debugging, e.g. make DEBUG=1 html   '
 	@echo 'Set the RELATIVE variable to 1 to enable relative urls                    '
 	@echo '                                                                          '
 html:
 	"$(PELICAN)" "$(INPUTDIR)" -o "$(OUTPUTDIR)" -s "$(CONFFILE)" $(PELICANOPTS)
 clean:
 	[ ! -d "$(OUTPUTDIR)" ] || rm -rf "$(OUTPUTDIR)"
 regenerate:
 	"$(PELICAN)" -r "$(INPUTDIR)" -o "$(OUTPUTDIR)" -s "$(CONFFILE)" $(PELICANOPTS)
 serve:
 	"$(PELICAN)" -l "$(INPUTDIR)" -o "$(OUTPUTDIR)" -s "$(CONFFILE)" $(PELICANOPTS)
 serve-global:
 	"$(PELICAN)" -l "$(INPUTDIR)" -o "$(OUTPUTDIR)" -s "$(CONFFILE)" $(PELICANOPTS) -b $(SERVER)
 devserver:
 	"$(PELICAN)" -lr "$(INPUTDIR)" -o "$(OUTPUTDIR)" -s "$(CONFFILE)" $(PELICANOPTS)
 devserver-global:
 	$(PELICAN) -lr $(INPUTDIR) -o $(OUTPUTDIR) -s $(CONFFILE) $(PELICANOPTS) -b 0.0.0.0
 publish:
 	"$(PELICAN)" "$(INPUTDIR)" -o "$(OUTPUTDIR)" -s "$(PUBLISHCONF)" $(PELICANOPTS)
 theme:
 	"$(PELICANTHEME)" --install "$(THEMEDIR)" --verbose
 github: publish
 	mkdir -p "$(OUTPUTDIR)/custom"
 	cp -a custom/.  "$(OUTPUTDIR)/custom/"
 	cp 404.html "$(OUTPUTDIR)"
 	ghp-import -m "Generate Pelican site" -b $(GITHUB_PAGES_BRANCH) "$(OUTPUTDIR)"
 	git push -f origin $(GITHUB_PAGES_BRANCH)
 .PHONY: html help clean regenerate serve serve-global devserver publish github
@@ -1 +0,0 @@
 # avinal.github.io
@@ -1,31 +0,0 @@
 ****************
 The Big Red Ants
 ****************
 :date: 2012-02-27 22:47
 :tags: ants, sav 
 :category: article
 :slug: red-big-ants
 :summary: In a bird’s eye view if we see around us, ants are the common and tiniest living entitiy seen by naked eye. One of them are the big red ants, in my view they are unique from others in two ways, first they live on trees and second their anteenas are too long and bent in middle, seems like their fore legs. Their mandible (mouth) seems like eagle’s beak.
 .. raw:: html
    <p style="border: 2px solid var(--cyan);border-radius: 7px;" align=center>This article was published in 3rd edition of नवांकुर , the official magazine of Simultala Awasiya Vidyalaya, Bihar, India.<p>
 In a bird’s eye view if we see around us, ants are the common and tiniest living entitiy seen by naked eye. One of them are the big red ants, in my view they are unique from others in two ways, first they live on trees and second their anteenas are too long and bent in middle, seems like their fore legs. Their mandible (mouth) seems like eagle’s beak.
 As I observed them making and reparing their nests, I concluded that they are very laborious and intellectual. They create their nests by binding two or more leaves (maybe up to 500) together. They stich the leaves using a stinky white substance either excreted by themselves or from trees. This substance is like web of spider. At first builder ants creates an array at the blade of two leaves. Then they make ant-cranes or ant-chain like chain of monomer to form a polymer. They catch the leaves and pull each other to stich. After some time, the parliament of leaves transforms into a leaf-sac called their nest. They also weave translucent cloth like structure to cover remainings of leaf. A nest hangs by a branch of the trees. 
 A nest is skillfully divided into living rooms, barracks, storehouse, egg room and queen’s room. The eggroom, lies at the center of nest to protect from outer attack until last time. Besides that, lies queen’s room. Living rooms are sequenncly joined with eggroom. There are different rooms for workers, food searchers etc. The partition of the room resembles atom’s electron shell, one upon another. At last barracks are the outermost rooms, just like outermost orbit of electron. The defence system is strongest at the nest’s opening. A nest may size as 2-3 footballs and have 50 to 10000 ants. There may be more openings. 
 Now about their attacking and protecting skills. A solider is unique from other ants. It is equipped with many attacking and defending skills. Normally they do not attack. They are social insects. If someone attacks, all other ants go inside, and soldiers come out. They spread allover the nest. They are very sensetive and have sharp vision. If any one of them see their enemy the stand on their hind legs, swinging, their forelegs and anteens in their air as scolding someone. Their spit contains formic acid, present at the end of the abdomen below the rectum. If their nest is broken and eggs fall on ground then the ants make a dome, like the dome of Taj mahal to save the eggs till last their breadth. This shows their caring skills.
 The most amazing is their discipline. They can easily beat a human in race of discipline. Humans must learn from it. When two ants meet, they touch their anteena to communicate. When they walk in a queue, they seem like twinkling dots and dashes. I want to conclude that **All tiny things are not really tiny. It may be as a space having infinite mysteries one has to explore it.** 
@@ -1,45 +0,0 @@
 *************************
 The Interstellar Twilight
 *************************
 :date: 2020-09-28 22:47
 :tags: interstellar, twilight 
 :category: blog
 :slug: this-is-for-you
 :summary: If in the Twilight of dreams we should meet once more, we shell talk again together and I shall sing to you a lullaby till you sleep again to meet me in the Twilight of another dream.
 Yeah, it was a dream someday. I never imagined you. But I do remember glimpses of a wonderful person 
 in my deep slumber. When I go back to last year about the same time, I find myself a manic who gets 
 carried away with every emotion. Becoming too happy about something and then becoming too sad was so 
 common that I never noticed what I was risking. 
 **"If in the Twilight of dreams we should meet once more, we shell talk again together and I shall sing to you a lullaby till you sleep again to meet me in the Twilight of another dream."**
 But 1 year ago many things changed. A never seen dream came true. To be honest I was skeptical if all 
 this happening to me was true. Even until last December. Gradually things started falling into places. 
 And for the most part, the reality became more real. I can now easily see what is happening and why it 
 happened. Everything was so nice until we had a fight. Then another, and now it was every other day 
 story. It was a really hard time collecting everything together and act as nothing happened after every 
 single of those. Everything was plunging. I started imagining the end of something that I did not 
 imagine to happen in the first place. 
 But during all those times, there was a continual intuition that maybe there is something that we both 
 are missing. And that was maybe the root of all chaos. I never came to know that what it was neither did 
 you. But I do realize many mistakes I have been doing since we met. 
 I want to thank you for not losing hope in me. We both always tried to reduce tension as much as we could. 
 And thank you for many other ineffable things happened because of you. 
 As of now I can see things making sense. Every message, every talk now seems to make sense. I am more 
 deeply into this friendship if I was not ever before. The ecstasy of having you is other-worldly. I don't 
 know if I could ever adore a person this much but I adore this ravishing friendship. Only you or only 
 this friendship may mean nothing to me. But I am delighted to say that I have both and I have you. 
 Now, what is all with The Interstellar Twilight. Why this name ? Let me explain it for you. **Interstellar** 
 means between stars and **Twilight** means the soft glow when the sun is below the horizon. 
 **The Interstellar Twilight** means the glow between the stars or simply glow of a cluster of stars. A 
 single star shines but the glow is too low to be noticed against its brightness. But a lot stars together 
 gets a glow. So my friend we are such two stars and our friendship is that glow. 
@@ -1,9 +0,0 @@
 ************
 My Checklist
 ************
 :date: 2021-02-14 22:47
 :slug: checklist
 :category: development
 :tags: rst, github
 :status: draft
@@ -1,432 +0,0 @@
 **************************
 Google Summer of Code 2021
 **************************
 :date: 2021-08-19 23:07
 :tags: gsoc, FOSSology
 :category: report
 :summary: This is the final report of my Google Summer of Code 2021 at The FOSSology Project. 
 :slug: final-evaluation
 :status: published
 .. role:: rd
 .. role:: gr
 .. role:: or
 .. role:: html-raw(raw)
    :format: html
 .. raw:: html
    <style> 
    .rd {color:red;font-weight:bold} 
    .gr{color:green;font-weight:bold}
    .or{color:orange;font-weight:medium} 
    ul{margin-bottom:0}
    </style>
 The CMake Build system
 ----------------------
 FOSSology is quite an old and mature project. The project has been using bare metal **Makefiles**. As the project is growing with new agents and modernization it was required to have a modern build system. 
 The FOSSology is a suite of well-integrated and synchronized sub-projects (called agents) written in C, C++, and PHP. Most of the major agents are in C, C++ and that made CMake an obvious choice for a new build system for FOSSology. CMake is a versatile set of build, test, and packaging tools and is the most popular choice of C/C++ developers. CMake can be extended to create a build system for other languages too via custom scripts. 
 GitHub Actions CI/CD
 --------------------
 .. image:: /images/ci.png
    :class: float-md-right rounded border border-info ml-3
    :alt: A CI Meme
    :width: 350
 Since the FOSSology project moved on Github, it has used only the free Travis CI service for OSS projects. 
 At the time of writing Travis CI has reduced its free tier CI services. GitHub Actions provides faster builds. Since GitHub Actions is a fully managed service by GitHub, we don’t need to know how to scale and operate the infrastructure to run it. 
 It is straightforward to use with GitHub because when we fork a repository, the actions automatically get forked. This allows you to test and build projects very efficiently and even run them closer to the developer. Also, you have readily available access to the GitHub API, making it more popular among developers.
 Improvements over previous build system and CI
 ----------------------------------------------
 The new build system and CI brings a lot of improvements and features. The list below describes them.
 - CMake enforces out-of-source builds. This was already possible with the previous build system but not a strict requirement. This feature keeps the source code clean and makes cleaning the build artifacts easy. (Just remove the build folder :)
 - One of the major improvements over the previous build system is faster build times. CMake generates parallel build-enabled configurations for all generators. In our tests, the new build system is at least twice as fast as the previous one. With further improvement in configuration, we will be able to further cut the build times. 
 - Previously FOSSology can only be built using *Unix Makefiles*. With CMake, we can now use many other popular generators such as *Ninja*.
 - Now it is also very flexible to choose different compilers. This will help support more platforms and architecture in the future. As of now, we are experimenting with Clang compilers. 
 - FOSSology is quite an old project and a lot of agent testing code was written in the last decade. Initially, none of them were compatible with the new build system, but we were able to hack most of the test code using better-improved methods. Test times have also improved.
 - Migrating from Travis CI to GitHub Actions was another big move and for the most part, it removes the dependency on a third-party CI service. Along with that GitHub Actions provides better build times, tons of new features, and better integration with other GitHub services. 
 Deliverables
 --------------
 .. raw:: html
    <div class="alert alert-info" role="alert">
    <ul class="simple">
    <li>Final Pull Request <a class="badge badge-info" href="https://github.com/fossology/fossology/pull/2075">#2075</a></li>
    <li>Pull Request Branch <a class="badge badge-info" href="https://github.com/avinal/fossology/tree/avinal/feat/buildsystem">avinal/feat/buildsystem</a></li>
    <li>Working Branch (individual commits) <ul>
    <li><a class="badge badge-info" href="https://github.com/avinal/fossology/tree/avinal/feat/cmake-buildsystem">avinal/feat/cmake-buildsystem</a></li>
    <li><a class="badge badge-info" href="https://github.com/avinal/fossology/tree/avinal/feat/testing">avinal/feat/testing</a></li>
    </ul></li>
    <li>Project Issue <a class="badge badge-info" href="https://github.com/fossology/fossology/issues/1913">#1913</a></li>
    <li>Project Discussion <a class="badge badge-info" href="https://github.com/fossology/fossology/discussions/1931">#1931</a></li>
    <li>Weekly Reports<ul>
    <li><a class="badge badge-info" href="https://gsoc.avinal.space">Personal Blog</a></li>
    <li><a class="badge badge-info" href="https://fossology.github.io/gsoc/docs/2021/buildsystem/">FOSSology Official Blog</a></li>
    </ul></li></ul>
    </div>
 **CMake Build System Tasks**
 .. table::
    :class: table table-sm table-hover table-bordered table-responsive
    :widths: 5 15 10 10 20 15 25
    :align: center
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | #  | Agents           | Build     | Install   | Testing            | Packaging | Remarks        |
    +====+==================+===========+===========+====================+===========+================+
    | 1  | adj2nest         | :gr:`YES` | :gr:`YES` |                    | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 2  | buckets          | :gr:`YES` | :gr:`YES` |                    |  :gr:`YES`|                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 3  | cli              | :gr:`YES` | :gr:`YES` | - :rd:`Functional` | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 4  | copyright        | :gr:`YES` | :gr:`YES` | - :gr:`Functional` |           |                |
    |    |                  |           |           | - :gr:`Unit`       | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 5  | debug            |           | :gr:`YES` |                    | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 6  | decider          | :gr:`YES` | :gr:`YES` | - :gr:`Functional` |           |                |
    |    |                  |           |           | - :gr:`Unit`       | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 7  | deciderjob       | :gr:`YES` | :gr:`YES` | - :gr:`Functional` | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 8  | delagent         | :gr:`YES` | :gr:`YES` | - :rd:`Functional` |           |                |
    |    |                  |           |           | - :rd:`Unit`       | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 9  | demomod          | :or:`YES` | :or:`YES` | - :or:`Functional` | :or:`NO`  | *(Not Used)*   |
    |    |                  |           |           | - :or:`Unit`       |           |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 10 | example_wc_agent | :or:`YES` | :or:`YES` | - :or:`Functional` |  :or:`NO` | *(Not Used)*   |
    |    |                  |           |           | - :or:`Unit`       |           |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 11 | clib             | :gr:`YES` | :gr:`YES` | - :gr:`Functional` |           |                |
    |    |                  |           |           | - :gr:`Unit`       | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 12 | cpplib           | :gr:`YES` | :gr:`YES` | - :gr:`Unit`       | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 13 | phplib           | :gr:`YES` | :gr:`YES` | - :gr:`Functional` |           | 1 functional   |
    |    |                  |           |           | - :gr:`Unit`       | :gr:`YES` | test needs fix |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 14 | maintagent       | :gr:`YES` | :gr:`YES` |                    | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 15 | mimetype         | :gr:`YES` | :gr:`YES` | - :gr:`Functional` |           |                |
    |    |                  |           |           | - :gr:`Unit`       | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 16 | monk             | :gr:`YES` | :gr:`YES` | - :gr:`Functional` |           |                |
    |    |                  |           |           | - :gr:`Unit`       | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 17 | ninka            | :or:`YES` | :or:`YES` | - :or:`Functional` | :or:`NO`  | *(Deprecated)* |
    |    |                  |           |           | - :or:`Unit`       |           |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 18 | nomos            | :gr:`YES` | :gr:`YES` | - :gr:`Functional` |           |                |
    |    |                  |           |           | - :gr:`Unit`       | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 19 | ojo              | :gr:`YES` | :gr:`YES` | - :gr:`Functional` |           | 1 functional   |
    |    |                  |           |           | - :gr:`Unit`       | :gr:`YES` | test needs fix |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 20 | pkgagent         | :gr:`YES` | :gr:`YES` | - :gr:`Functional` |           |                |
    |    |                  |           |           | - :gr:`Unit`       | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 21 | readmeoss        | :gr:`YES` | :gr:`YES` |                    | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 22 | regexscan        | :or:`YES` | :or:`YES` |                    |  :or:`NO` | *(Deprecated)* |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 23 | reportImport     | :gr:`YES` | :gr:`YES` |                    | :gr:`YES` |                |               
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 24 | reuser           | :gr:`YES` | :gr:`YES` | - :gr:`Functional` | :gr:`YES` |                |                
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 25 | reso             | :gr:`YES` | :gr:`YES` |                    | :gr:`YES` |                |                  
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 26 | scheduler        | :gr:`YES` | :gr:`YES` | - :rd:`Functional` |           | Tests needs    |
    |    |                  |           |           | - :rd:`Unit`       | :gr:`YES` | fix            |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 27 | softwareHeritage | :gr:`YES` | :gr:`YES` |                    | :gr:`YES` |                |                 
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 28 | spasht           | :gr:`YES` | :gr:`YES` |                    | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 29 | spdx2            | :gr:`YES` | :gr:`YES` | - :gr:`Functional` |           | 1 Test failing |
    |    |                  |           |           | - :gr:`Unit`       | :gr:`YES` | in CI          |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 30 | unifiedreport    | :gr:`YES` | :gr:`YES` | - :gr:`Functional` | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 31 | ununpack         | :gr:`YES` | :gr:`YES` | - :gr:`Functional` |           | Unit tests     |
    |    |                  |           |           | - :rd:`Unit`       | :gr:`YES` | needs fix      |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 32 | wget_agent       | :gr:`YES` | :gr:`YES` | - :gr:`Functional` |           |                |
    |    |                  |           |           | - :gr:`Unit`       | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
    | 32 | www              | :gr:`YES` | :gr:`YES` | - :rd:`UI`         | :gr:`YES` |                |
    +----+------------------+-----------+-----------+--------------------+-----------+----------------+
 **GitHub Actions CI Tasks**    
 .. table::
    :class: table table-sm table-hover table-bordered table-responsive
    :widths: 5 25 70
    :align: center
    +---+------------------------+----------------------------------------------------------+
    | # | CI Tasks               | Status                                                   |
    +===+========================+==========================================================+
    | 1 | :gr:`build`            | Added Ubuntu 20.04 GCC 8, 9 and Clang, GCC 7 not working |
    +---+------------------------+----------------------------------------------------------+
    | 2 | :gr:`c/cpp unit test`  | Added, delagent, scheduler and ununpack not working      |
    +---+------------------------+----------------------------------------------------------+
    | 3 | :gr:`phpunit tests`    | Added, delagent and scheduler  functional not working    |
    +---+------------------------+----------------------------------------------------------+
    | 4 | :rd:`cahching`         | Not implemented                                          |
    +---+------------------------+----------------------------------------------------------+
    | 5 |:rd:`source install`    | Not implemented                                          |
    +---+------------------------+----------------------------------------------------------+
 (:gr:`GREEN`: COMPLETED, :rd:`RED`: INCOMPLETE, :or:`ORANGE`: NOT NEEDED/DEPRECATED)
 How does it work and how to use it?
 -----------------------------------
 .. raw:: html
    <div class="embed-responsive embed-responsive-16by9">
        <iframe class="embed-responsive-item" src="/images/second-build.webm" allowfullscreen></iframe>
    </div>
 The new build system retains the modular and hierarchical structure of the previous build system.  On the other hand, the new build system provides several new flags to control the build. The new build system forces out-of-source build instead of the previous in-source builds. This keeps the source clutter-free and reduces the chance of accidentally deleting source files. *Testing still needs some in-source artifacts, this will be solved once all the tests are fixed according to the new build system.* 
 Each agent is a complete CMake sub-project with its independent configuration for building, installing, and testing. That means a single agent can be built and installed separately and even removed from the default build without breaking other builds. The directory structure is as below.
 .. code-block:: bash
    .
    ├── build                           # temporary directory for build artifacts
    ├── cmake                           # CMake modules for FOSSology
    │   ├── FoPackaging.cmake           # CMake Packaging configurations
    │   ├── FoUtilities.cmake           # Custom CMake utilities 
    │   ├── FoVersionFile.cmake         # VERSION version.php CMake template file   
    │   ├── SetDefaults.cmake           # CMake defaults for this project   
    │   ├── TestInstall.make.in         # Template makefile for install during tests
    │   └── VERSION.in                  # VERSION file template
    ├── src                             
    │   ├── agent-1                     # Agent sub-project
    │   │   ├── agent                   # Agent's source code directory
    │   │   │   ├── agent-source-code
    │   │   │   └── CMakeLists.txt
    │   │   ├── agent_tests             # Agent's test directory    
    │   │   │   ├── Unit
    │   │   │   ├── Functional
    │   │   │   └── CMakeLists.txt
    │   │   ├── ui                      # Agent's UI source code
    │   │   │   ├── templates
    │   │   │   └── agent-ui-code
    │   │   └── CMakeLists.txt          # Agent's top-level CMake configuration
    :   :
    │   ├── other agents
    :   :
    │   └── CMakeLists.txt              # Source intermediate CMake configuration
    :
    ├── other directories and files
    :
    └── CMakeLists.txt                  # FOSSology Top-level CMake configuration 
 The :code:`cmake` directory contains customized CMake modules and templates for FOSSology. This directory is required for all the operations. The general workflow of the new build system as well as how to use it is described below.
 1. Since the new build system is still in review. You must fork FOSSology and pull the `#2075 <https://github.com/fossology/fossology/pull/2075>`_ pull request branch. Once you are in FOSSology root, run these commands.
    .. code-block:: bash
        git fetch https://github.com/avinal/fossology avinal/feat/buildsystem:buildsystem
        git checkout buildsystem
 2. The first step towards building is to create a temporary directory for storing intermediate files and build artifacts. By convention we use a directory named :code:`build`, but you can use any name. (**NOTE: For testing do not use other names**)
    .. code-block:: bash
        mkdir build
        cd build
 3. In the next steps, we will configure the CMake project and generate the required configurations. You can use several flags to control the build. Given below are the flags available for this project.
    .. table::
        :class: table table-sm table-hover table-bordered table-responsive
        +-----------------------------------+--------------------------------------------+--------------------+
        | CMake Flags                       | Description                                | Default            |
        +===================================+============================================+====================+
        | **-DCMAKE_INSTALL_PREFIX=<path>** | Sets the install prefix.                   | :code:`/usr/local` |
        +-----------------------------------+--------------------------------------------+--------------------+
        | **-DAGENTS="agent1;agent2..."**   | Only configure these agents.               | ALL AGENTS         |
        +-----------------------------------+--------------------------------------------+--------------------+
        | **-DOFFLINE=<ON/OFF>**            | Controls vendor generation, ON=NO          | **OFF**            |
        +-----------------------------------+--------------------------------------------+--------------------+
        | **-DCMAKE_BUILD_TYPE=<type>**     | - :code:`Debug`                            |                    |
        |                                   | - :code:`Release`                          |  :code:`Debug`     |
        |  - Controls build type aka        | - :code:`RelWithDebInfo`                   |                    |
        |    level optimisation             | - :code:`MinSizeRel`                       |                    |
        +-----------------------------------+--------------------------------------------+--------------------+
        | **-DTESTING=<ON/OFF>**            | Controls testing config generation         |  **OFF**           |
        +-----------------------------------+--------------------------------------------+--------------------+
        | **-DMONOPACK=<ON/OFF>**           | Package adj2nest and ununpack seperately   | **OFF**            |
        +-----------------------------------+--------------------------------------------+--------------------+
        | **-GNinja**                       | Use Ninja instead of Unix Makefiles        | *Unix MakeFiles*   |
        +-----------------------------------+--------------------------------------------+--------------------+
    There are lots of inbuilt CMake command-line options you can see them in the official `documentation <https://cmake.org/cmake/help/v3.10/manual/cmake.1.html>`_. Once you have chosen your flags we can now configure the project using the following commands.
    .. code-block:: bash
        # From build folder
        cd <name-of-build-directory>
        cmake <flags> ..
 4. The next step is to build the project. You can use parallel jobs to build faster. For more options you can type :code:`cmake --help` or :code:`make --help` or :code:`ninja --help`. 
    .. code-block:: bash
        # Common build command for all generators, 
        # Default number of parallel builds depends on generator used
        cmake --build . --parallel <no-of-processes>
        # For Unix Makefiles, no parallel build by default
        make -j <no-of-processes>
        # For Ninja, 8+ parallel build by default (depends on system)
        ninja -j <no-of-processes>
 5. Installing is also as easy as building. You can choose to install only certain components even if you have built the whole project. If you directly invoke the install command without building the project, it will automatically build the project first.
    .. code-block:: bash
        # For Unix Makefiles
        make install
        # For Ninja
        ninja install
 6. While testing has some issues, most of the testing is working fine. For now, you must build and run any test from the FOSSology root directory only. You can choose to configure a single agent if you want to test one agent only. See :code:`ctest --help` for controlling test runs.
    .. code-block:: bash
        # Common testing command
        ctest --parallel <no-of-processes>
        # For Unix Makefiles
        make test
        # For Ninja
        ninja test
 7. You can package FOSSology, the packaging currently lacks copyright and conf files. But for testing purposes, you can use the following commands. Similar to installing, if you run the package command without building the project, it will automatically build the project first. See :code:`cpack --help` for more packaging options.
    .. code-block:: bash
        # Common testing command
        cpack
        # For Unix Makefiles
        make package
        # For Ninja
        ninja package
 Known Issues and Drawbacks
 --------------------------
 Although the transition from Makefiles to CMake and Travis CI to GitHub Actions is almost complete and working as expected. But it is not free of drawbacks and issues. This section outlines the known issues at the time of writing. 
 .. image:: https://imgs.xkcd.com/comics/conference_question.png
    :class: float-md-right rounded border border-info ml-3
    :alt: A Bug Meme
    :width: 350
 - Coverage builds may fail with linking errors.
 - Packaging prefix is the same as the install prefix. This requires the developer to set the install prefix manually before packaging to produce packages with the correct directory structure.
 - Testing and packaging must be used from the FOSSology root directory. Not doing so may or may not configure the project as intended.
 - Previously tests were written hardcoded for the Makefiles. But new build system requires all artifacts to be generated in a separate directory. This required me to add symbolic links wherever a generated script or file is expected. Tests can still leave some artifacts inside source folders.
 - There is no easy way to install a particular agent from the FOSSology root directory.
 - Packages don't contain copyright, readme, and license files. CMake doesn't provide a way to include these files. This is being tracked by issue `#21832 <https://gitlab.kitware.com/cmake/cmake/-/issues/21832>`_.
 - While packaging the symbolic links may or may not be dereferenced and hence results in copying the folder too in the target directory.
 - Running tests locally may require switching to :code:`fossy` user.
 - While configured for testing, it may give permission errors.
 - Scheduler, Ununpack, and Delagent unit and functional tests are not working. I have added an issue `#2084 <https://github.com/fossology/fossology/issues/2084>`_ to track the progress on fixing these tests.
 - CMake doesn't generate uninstall targets. The closest thing to uninstall is `this snippet <https://gitlab.kitware.com/cmake/community/-/wikis/FAQ#can-i-do-make-uninstall-with-cmake>`_. This will be later added to the FOSSology.
 Challenges Faced
 ----------------
 While this whole project was challenging, some aspects of it were unforeseen and more challenging. When I decided to go on with this project I just had enough CMake knowledge to write a configuration for a very small project. I had never used CMake on this big scale. On the other side, the FOSSology community is largely unknown to CMake so for all of us it was learned, practiced, and implement. With support from mentors, I was able to overcome this challenge with flying colors.
 The other challenge was to understand the old build system, how they are all connected and what is the flow. The complexity can be imagined by the fact that the most of code and configurations were written in the decade before the last decade and haven't changed much since then.
 The most challenging task was to make tests work with the new build system. Since tests were mostly hardcoded and the new build system refactored many of the files and directory, the tests were failing initially. The testing part took me the most time. All thanks to my mentor Gaurav and my friend Sarita I was able to hack them to suit the new build system.
 Related Resources and Links
 ---------------------------
 - Fix FOSSology agent tests issue `#2084 <https://github.com/fossology/fossology/issues/2084>`_ 
 - feat(CI): Migrate API docs generation and deployment to GitHub Actions pull request `#1917 <https://github.com/fossology/fossology/pull/1917>`_
 - feat(CI): Migrate Static Checks and Analysis to GitHub Actions from Travis CI `#1919 <https://github.com/fossology/fossology/pull/1919>`_  
 Future Development Plans
 ------------------------
 There is a lot to do with the new build system and CI and it will probably take a year or to reach a maturity point. I was able to meet most of the goals but some of them are remaining. 
 - Fix the tests, probably renovate them from the ground up.
 - Find a hack for packaging problems.
 - Improve and optimize the build.
 - Modernise the source code, remove old, bloated code and replace them according to new standards.
 What did I learn from this project?
 -----------------------------------
 This Google Summer of Code was the busiest time of my life for all good reasons. I learned a lot about license compliance and how it all works in the software industry. The next big thing is CMake. As I mentioned I was just a novice user of CMake. Now I am confident that given any other large project I will be able to migrate it/improve it. I got to learn PHP, of which I did not know a single word before GSoC. And finally, I learned about packing and testing. I had these courses but implementing them myself and fixing them was a wholesome experience. 
 Other than that I improved on my communication and presentation skills. Collaborating with fellow participants was one of the great things that happened during GSoC.
 Acknowledgments
 ---------------
 Google Summer of Code is the best thing that has happened to me this year so far. Although there are numerous people to say thanks to, I want to mention key people who were my motivation and support during this period. 
 First of all, I want to thank and appreciate my mentors `Gaurav Mishra <https://github.com/GMishx>`_, `Michael C. Jaeger <https://github.com/mcjaeger>`_, `Anupam Ghosh <https://github.com/ag4ums>`_, and `Shaheem Azmal M MD <https://github.com/shaheemazmalmmd>`_. Without the help and support from them, all this would not have been possible. They are very polite, knowledgeable, and helpful. 
 I want to thank my friend and :abbr:`fellow participant (Integrating ScanCode Toolkit to FOSSology)` `Sarita <https://github.com/itssingh>`_. Thank you for being a collaborator, support, and motivation for attempting GSoC. 
 Finally, I want to thank, my family and friends. I got to meet many awesome developers as my fellow participants from around the world, I wish we will do more collaboration in the future.
@@ -1,64 +0,0 @@
 **************************************************************************
 :abbr:`HRT (Hudson River Trading)` Systems Internship Interview Experience
 **************************************************************************
 :date: 2021-01-04 21:47
 :tags: HRT, hudsonrivertrading, interview, internship
 :slug: hrt-interview-1
 :category: blog
 :summary: I applied for **Systems Internship - Summer 2021** back in December 2020 at `Hudson River Trading <https://www.hudsonrivertrading.com>`_ , New York.....Questions were clear and of medium level. But they were designed in such a way that you must know the basics before you could attempt.
 I applied for **Systems Internship - Summer 2021** back in December 2020 at `Hudson River Trading <https://www.hudsonrivertrading.com>`_ , New York. The internship description was: -
 .. epigraph::
    We are looking for highly motivated students who are eager to learn and excited about systems to join us for our summer internship 
    program. As a systems intern, you may have the opportunity to work on projects in the following areas:
    * Programming/scripting (Golang, Python, C++, C)
    * FOSS development
    * HPC, Cluster computing
    * System Administration
    * Linux, Debian
    * Linux-based computer security
    * Data Storage
    * Large deployment or config management
 The first step was a coding test on the Codility platform. If you have used any of the online coding platforms, this is similar. It was a :abbr:`2.5 hrs (90 mins)` test consisting of 3 questions. They let you use :abbr:`online references (documentation, man pages, etc.)` but 
 **do not copy the code** as it will highly reduce your chances of qualifying for this first stage. You can choose between **C/C++**, 
 **Python** and **Golang** (no Java 😪). 
 Questions were clear and of medium level. But they were designed in such a way that you must know the basics before you could attempt. 
 Also, they expected a clear and concise approach. Two of the most important points in their instructions were: -
 .. epigraph:: 
    * While correctness and performance are the most important factors for evaluation, we will take test duration into account as well.
    * Please understand that this test is meant to be challenging. A perfect score is not necessary to move on to future interview rounds, so do the best you can!
 So, you must be near perfect in your approach as well as on time. I did them kind of quickly. They will show you a summary of your 
 submission but not the results. It will take almost 2 weeks to get back to you for further steps.
 Next, I received a mail invitation for a telephonic interview. **This interview will last about 45 minutes and will be technical but will not require coding. Interview topics may include your background, programming languages, and Unix/Linux concepts**. Once you receive this 
 mail you can then decide a time slot for an interview. 
 I was not sure what they will ask if this is not a coding interview. The interviewer was very polite, and he was explaining the questions 
 too. Questions were not so tricky but practical and real-life. Since it was **not for SDE role**, the questions were mostly related to 
 Linux/Unix, C++ (mainly pointers and memory), Python/Bash scripting, automation, knowledge of tools (IDEs, Editors, System Administration 
 Tools) and previous experiences. The interview would often explain why he is asking this question, this was very nice. Then some common 
 interview questions, why do you want to work for this role? What makes you fit for this role? etc. 
 One thing that I want to point out is that the interviewer was repeatedly checking my resume, and for the most part he did not ask 
 anything that was not on my resume. So, my tip is to create a nice resume with genuine work/tool experiences. And when you are applying 
 for such a role, it would be helpful if you mention mathematics or other courses that you have taken. *Do not lie on your resume*. They 
 will easily catch that. 
 The other thing is to keep your words short and clear; I was not great at communication, but you can be. If the interviewer allows then 
 use examples for the things you cannot explain. I used nice examples. At last, he gave me short feedback on how well I performed. 
 At last, I want to point out things I should not have done. The first is, I did not ask much about the role, you must do this at least 
 once. Second, I am talkative, I do not know if the interviewer was not faking his expressions (because he would often discuss in-depth), 
 but not all interviewers will be the same. So, do not talk too much, nor too less. At last work on your communication skill, mostly how 
 you to present things and how to answer technical as well as behavioral questions. I was not fluent, but my way of presentation might 
 have saved me. 
@@ -1,12 +0,0 @@
 ************************************
 Google Summer of Code 2021 Selection
 ************************************
 :date: 2021-05-17 23:22
 :slug: finally-gsoc
 :category: gsoc
 :tags: gsoc, gsoc21, fossology
 :status: draft
 Finally after three years I have been selected in **Google Summer of Code** program at **The FOSSology Project**. I will be working on *New Buildsystem and CI/CD* for the project.
@@ -1,239 +0,0 @@
 **************************************************************
 Create the VLC User Documentation for one Mobile Port(Android)
 **************************************************************
 :date: 2020-12-01 23:47
 :modified: 2020-12-31 23:19
 :slug: vlc-gsod-report
 :category: development
 :tags: vlc, gsod, gsod2020
 :summary: The project was to Create the VLC User Documentation for Android Mobile Port which was previously hosted on VLC’s wiki pages. The major portion of this was to start everything from scratch including chapter separation, section organization.
 OVERVIEW
 --------
 VideoLAN is a non-profit organization that develops software for playing video and other media formats. VLC media player (commonly known as just VLC) is a free and Open Source cross-platform multimedia player and framework that plays most multimedia files as well as DVDs, Audio CDs, VCDs, and various streaming protocols built by the VideoLAN organization and a team of volunteers. VLC for Android is a port of the VLC for Android OS.
 The project was to Create the VLC User Documentation for Android Mobile Port which was previously hosted on VLC’s wiki pages. The major portion of this was to start everything from scratch including chapter separation, section organization and an engaging and easy to follow for both technical and non-technical users. The original proposal can be found here.
 PROJECT GOALS
 -------------
 * Propose a new structure for documentation e.g. Chapter Separation, Sections etc
 * Proper balance between technical and non-technical descriptions to serve all kinds of users.
 * Adequate amount of screenshots in each section and other supporting media to make documentation more appealing.
 * Optimized for all Screen Sizes. Especially for Mobile Devices.
 * Ease of navigation
 COMMUNITY BONDING
 -----------------
 This period was mostly utilized for collecting more information and many internal meetings to shape the projects and bonding with fellow writers, developers(mentors). I got to know more about the VLC organization and the project. We decided to create a skeleton of the project and then follow a Issue-Merge Request-Review-Merge system to keep the commit history clean and maintain the proper review of the work before it is merged. 
 I initially proposed that the new documentation should also use the same tools(Sphinx and GitLab Pages) because if in future we want to merge all the documentation into a single one, it will be easier to migrate and will provide a consistency across all documentations.  Later I got to know that this will be an independent project and may not be merged since it solves a lot of problems. I was already familiar with the tools so it took no time to get started. 
 Nicolas Pomepuy, who is the lead developer of VLC for Android was assigned as my primary mentor and Simon Latapie as secondary mentor. 
 DOCUMENTATION DEVELOPMENT PHASE
 -------------------------------
 Initial Preparation
 I first moved my existing demo documentation to an entirely new repository with only the skeleton at the suggestion of my mentor. It was necessary to keep the commit history clean. The skeleton contained the empty directories representing the chapter separation. I got to learn “how to properly develop a project and contribute to open source”. This was a major lesson that got me familiar with the Merge Request and Review system. 
 The Development
 The next part was to frame the actual documentation pages and push to the repository. Since there was a significant time-zone difference we agreed to discuss by creating issues and sometimes my emails. There was one meeting every fortnight to check the process and discuss further development and blockers. Nicolas was really helpful and patient, answering each of my big-small queries. 
 Work Done
 .. raw:: html
    <style>
    table,td,th {
    border-collapse:collapse;
    border: 1px solid #000000;
    }
    </style>
    <table>
    <tr>
    <td><strong>Documentation</strong></td>
    <td><a href="https://avinal.videolan.me/vlc-android-user/">VLC for Android User Documentation </a>
    </td>
    </tr>
    <tr>
    <td><strong>Project Repository</strong>
    </td>
    <td><a href="https://code.videolan.org/avinal/vlc-android-user">Projects · Avinal Kumar / VLC for Android User Documentation</a>
    </td>
    </tr>
    <tr>
    <td><strong>Commits</strong>
    </td>
    <td><a href="https://code.videolan.org/avinal/vlc-android-user/-/commits/master">Commits · Avinal Kumar / VLC for Android User Documentation</a>
    </td>
    </tr>
    <tr>
    <td><strong>Issues/Discussions</strong>
    </td>
    <td><a href="https://code.videolan.org/avinal/vlc-android-user/-/issues">Issues · Avinal Kumar / VLC for Android User Documentation</a>
    </td>
    </tr>
    <tr>
    <td><strong>Merge Requests</strong>
    </td>
    <td><a href="https://code.videolan.org/avinal/vlc-android-user/-/merge_requests">Merge Requests · Avinal Kumar / VLC for Android User Documentation</a>
    </td>
    </tr>
    </table>
 Since the Android port of VLC can be installed on Android Smartphones/Tablets, Android TVs, Amazon Fire Devices and Chromebooks too, a full documentation will cover these all devices. Although these are different form factors, the features provided on each of them is exactly the same and the same documentation can be used for all these devices. As of now only Smartphones/Tablets are covered. And later additional pages will be added to reference different features/User Interface. Regardless of this addition the current documentation can serve a major part for all these form factors. 
 Completed/Remaining
 .. raw:: html
    <table>
    <tr>
    <td><strong>Chapters</strong>
    </td>
    <td><strong>Sections</strong>
    </td>
    <td><strong>Status</strong>
    </td>
    </tr>
    <tr>
    <td><strong>Settings</strong>
    </td>
    <td>
    <ul>
    <li>General Settings
    <li>Interface
    <li>Video
    <li>Subtitles
    <li>Audio
    <li>Casting
    <li>Advanced
    </li>
    </ul>
    </td>
    <td><strong>ALL COMPLETED</strong>
    <p>
    <strong>FOR ALL FORM FACTORS</strong>
    </td>
    </tr>
    <tr>
        <td><strong>Video</strong>
        </td>
        <td>
            <ul>
                <li>Video Explorer
                <li>Video Player
                </li>
            </ul>
        </td>
        <td><strong>COMPLETED FOR SMARTPHONES/TABLETS</strong>
        </td>
    </tr>
    <tr>
        <td><strong>Audio</strong>
        </td>
        <td>
            <ul>
                <li>Audio Explorer
                <li>Audio Player
                </li>
            </ul>
        </td>
        <td><strong>COMPLETED FOR SMARTPHONES/TABLETS</strong>
        </td>
    </tr>
    <tr>
        <td><strong>Browse</strong>
        </td>
        <td>
            <ul>
                <li>Explorer
                <li>Local Network
                </li>
            </ul>
        </td>
        <td><strong>ONLY SMB IN LOCAL NETWORK COMPLETED</strong>
        </td>
    </tr>
    <tr>
        <td><strong>Installation</strong>
        </td>
        <td>
            <ul>
                <li>Smartphones/Tablets
                <li>Android TV
                <li>Fire Devices
                <li>Chromebooks
                </li>
            </ul>
        </td>
        <td><strong>COMPLETED FOR SMARTPHONES/TABLETS</strong>
        </td>
    </tr>
    <tr>
        <td><strong>User Interface</strong>
        </td>
        <td>
            <ul>
                <li>Smartphones/Tablets
                <li>Android TV
                <li>Fire Devices
                <li>Chromebooks
                </li>
            </ul>
        </td>
        <td><strong>COMPLETED FOR SMARTPHONES/TABLETS</strong>
        </td>
    </tr>
    <tr>
        <td><strong>Support</strong>
        </td>
        <td>
            <ul>
                <li>FAQs
                <li>Help
                </li>
            </ul>
        </td>
        <td><strong>IN PROGRESS</strong>
        </td>
    </tr>
    <tr>
        <td><strong>Guidelines</strong>
        </td>
        <td>
            <ul>
                <li>Contribution Guideline
                <li>Screenshot Guidelines
                <li>READMEs
                </li>
            </ul>
        </td>
        <td><strong>IN PROGRESS</strong>
        </td>
    </tr>
    </table>
 CHALLENGES
 ----------
 The major obstacle was to get screenshots for all form factors. Since screenshots were the major part of this documentation it was necessary to provide proper screenshots in each chapter and with every step. For Android TV and Smartphone this was solved by using emulators instead of actual devices, but to emulate the actual scenario in an emulator was sometimes very difficult. 
 There were many occasions where I was not able to gather the exact information about devices other than smartphones/tables. Since all form factors share a common pool of features, my mentor suggested that I focus on smartphones/tables. And to create issues mentioning missing parts so that it could be solved later. 
 THANKS
 ------
 I want to thank my mentors for being supporting and helpful. I want to thank every person at VLC and Google who were involved in this whole process. Thanks and Congrats to my fellow writer Abhishek Pratap Singh. This was a great opportunity to learn and meet awesome people. I learned a lot about Sphinx, reStructured Text and many other things. 
@@ -1,96 +0,0 @@
 .. |redhat_logo| image:: /images/redhat_logo.png
    :width: 1.5em
    :align: middle
    :target: https://redhat.com
 **************************************
 My internship at Red Hat |redhat_logo|
 **************************************
 :date: 2022-02-25 20:47
 :slug: i-am-loving-it-redhat
 :category: development
 :tags: kubernetes, redhat, docker, golang, tekton, openshift, intern
 :summary: I made it to the Red Hat as a DevTools intern. This post is about onboarding and how I prepared myself for working on the actual project.
 I have been contributing to open source for the last 3 years and Red Hat was one of the companies that I was very fond of. I must say all my contributions and consistency paid off, and I made it to the Red Hat as a DevTools intern. This post is about onboarding and how I prepared myself for working on the actual project. 
 On the first day of my internship, I met two amazing teammates `Saytam <https://github.com/>`_ and `Utkarsh <https://github.com/>`_. We were also introduced to a Senior Software Engineer `Piyush Garg <https://github.com>`_ who later mentored us. The initial few meetings were more on the introduction and what to learn topics. Before I jump into more details let me explain first what does a **DevTools Developer/Engineer** do? 
 What does a DevTools Developer/Engineer do?
 -------------------------------------------
 From `MDN Web Docs <https://developer.mozilla.org/en-US/docs/Glossary/Developer_Tools>`_ **Developer tools (or "development tools" or short "DevTools") are programs that allow a developer to create, test, and debug software.** At RedHat, a lot of open source developer tools of industry standards are developed. There are many, OpenShift, Tekton, CodeReady containers, and many more. 
 .. |golang_logo| image:: /images/golang.png
    :width: 2.5em
    :align: top
 Learning on the |golang_logo|
 -----------------------------
 There was a lot of learning and still a lot to learn. In a meeting with my manager Pradeepto Bhattacharya, I was told that I will be working on TektonCD or OpenShift Pipelines, and both of them require a sound knowledge of Golang, CI/CD, Containers, Docker, and Kubernetes. I was familiar with CI/CD, containers, and Docker but never used Golang and Kubernetes. We were provided plenty of good resources and my teammates also helped with many awesome resources. I am listing all the resources with their category.
 `Golang <https://go.dev/>`_
 """""""""""""""""""""""""""
 .. image:: /images/goladder.png
    :class: float-md-right rounded ml-3
    :alt: Gopher on the ladder
    :height: 20em
 One of Golang’s biggest advantages is that it offers the clarity and ease of use that other languages lack. Golang’s advantages make it easy for new programmers to quickly understand the language and for seasoned veterans to easily read each other’s code.
 - `Official Go Documentation <https://go.dev/doc/>`_ - *Start from here*
 - `Go by Example <https://gobyexample.com/>`_ - *bite-size examples for most of the golang features*
 - `Golang tutorial series - GOLANGBOT.COM <https://golangbot.com/learn-golang-series/>`_ - *in-depth tutorial of golang*
 - `Effective Go <https://go.dev/doc/effective_go>`_ - *writing good golang programs*
 - `The Go Playground <https://go.dev/play/>`_ - *official online golang ide*
 - `The Go Programming Language - Book <https://www.gopl.io/>`_ *for learning advanced level golang*
 - `Golang Tutorial for Beginners | Full Go Course - TechWorld with Nana <https://youtu.be/yyUHQIec83I>`_ *if you prefer video tutorials, I don't :)*
 `Docker <https://www.docker.com/>`_
 """""""""""""""""""""""""""""""""""
 Docker takes away repetitive, mundane configuration tasks and is used throughout the development lifecycle for fast, easy, and portable application development - desktop and cloud. Docker’s comprehensive end-to-end platform includes UIs, CLIs, APIs, and security that are engineered to work together across the entire application delivery lifecycle.
 .. image:: /images/docker-architecture.png
    :class: float-md-right img-fluid my-3
    :alt: The Docker Architecture
 - `Docker and Containers - Katacoda <https://www.katacoda.com/courses/docker>`_ *interactive lessons on docker and containers*
 - `Docker for beginners <https://docker-curriculum.com/>`_
 - `Docker Tutorial for Beginners | TechWorld with Nana <https://youtu.be/3c-iBn73dDE>`_ *video tutorial*
 `Kubernetes <https://kubernetes.io/>`_
 """"""""""""""""""""""""""""""""""""""
 .. image:: /images/kubernetes-meme.png
    :width: 200
    :alt: Kubernetes tech
    :class: float-md-left border mr-3 
 **Kubernetes** is the Greek word for a ship’s captain. We get the words Cybernetic and Gubernatorial from it. The Kubernetes project focuses on building a robust platform for running thousands of containers in production. 
 - `Learn Kubernetes - Katacoda <https://www.katacoda.com/courses/kubernetes>`_ *interactive lessons with kubernetes*
 - `kube by example <https://kubebyexample.com/>`_ *learn by doing*
 - `Kubernetes Tutorial for Beginners <https://youtu.be/X48VuDVv0do>`_ *video tutorial*
 *Not so Minimal* Tekton Server
 ------------------------------
 In late January, we were asked to implement our learnings and deep dive into Kubernetes and TektonCD through an assignment project. Soon we realized that whatever we were learning so far was not even close to what we were going to implement. We were given a document containing the requirements of the applications we were supposed to create along with all the documentation and architectural diagrams. 
 The application was called **Minimal Tekton Server**. It is a set of three different applications, i.e a server, a CLI, and a dashboard. In short, this application is supposed to *listen to custom resources being created and then transfer the request to Tekton API to create the corresponding resource on the OpenShift/Kubernetes cluster.* 
 So are you interested in how it went? Please follow up with my `next blog <https://avinal.space/posts/development/lovely-dangerous-things-redhat.html>`_.
@@ -1,174 +0,0 @@
 .. |redhat_logo| image:: /images/redhat_logo.png
    :width: 1.5em
    :align: middle
    :target: https://redhat.com
 .. |mks_logo| image:: /images/mks_logo.png
    :width: 1.5em
    :align: middle
    :target: https://github.com/MiniTeks
 *******************************************
 Developing Minimal Tekton Server |mks_logo|
 *******************************************
 :date: 2022-02-27 20:47
 :modified: 2022-03-07 22:47
 :slug: lovely-dangerous-things-redhat
 :category: development
 :tags: kubernetes, redhat, docker, golang, tekton, openshift, intern
 :summary: We will be designing and implementing an application that will be talking to Tekton APIs to create resources on a Kubernetes/OpenShift Cluster.
 .. raw:: html
    <p style="border: 2px solid var(--pink);border-radius: 7px;" align=center>This blog is a descreptive account of the development of Minimal Tekton Server. This is highly technical in nature, so please make sure that you have sufficient knowledge about Golang, Docker, Kubernetes and TektonCD. You can refer to my <a href="https://avinal.space/posts/development/i-am-loving-it-redhat.html">previous blog</a> to know about these topics.<p>
 As mentioned in my last blog, we were given to implement an application named **Minimal Tekton Server**. The problem statement reads:
 .. epigraph::
    We will be designing and implementing an application that will be talking to Tekton APIs to create resources on a Kubernetes/OpenShift Cluster. The application will expose some fields of the Tekton Resources which the user will provide and then this application will create Tekton resources by talking to Tekton APIs available on the cluster to create the resources based on the user-provided fields.
 There are three parts in this project for the application and two more parts for the CI/CD using TektonCD and Kubernetes/OpenShift. I will go through each part descriptively and try to explain what we did.
 The Architecture of MKS
 -----------------------
 The first task in the development of the Minimal Tekton Server was creating its architectural diagram. Our first diagram was trash compared to the final diagram. Yeah, we learned. I will be explaining our final(obviously) architectural diagram and try to make some sense out of band-aids and duct tapes. 
 .. image:: /images/mks-architecture.png
    :alt: The MKS Arhitecture
    :class: img-fluid my-3
 Let me start with explaining **What are MKS Resources?**. I hope you know at least tidbits about Kubernetes and by the definition: *A resource is an endpoint in the Kubernetes API that stores a collection of API objects of a certain kind; for example, the built-in :code:`pods` resource contains a collection of Pod objects.* But developers soon realized that these in-built resources were not enough for the ever-growing applications of Kubernetes. Here `custom resource <https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/>`_ comes into the picture. *A custom resource is an extension of the Kubernetes API that is not necessarily available in a default Kubernetes installation.* To define a custom resource we use something called `Custom Resource Definition <https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/>`_. So MKS Resources are such custom resources that correspond to the TektonCD custom resources. 
 .. image:: /images/venus-flytrap.gif
    :class: float-md-right ml-3
    :width: 250
    :alt: A venus flytrap engulphing an insect.
 Let us now focus on the box containing :code:`Controller` and :code:`API server`. The controller can be said as a stimulus-response mechanism. Take the analogy of a Venus Flytrap plant. The trap is initially open. There are :code:`trigger` hairs on the inside of the trap. Once an insect is detected, there is a change of state and the trap closes in a blick on the eye. The controller works the same way. It listens for the change in the state of the MKS resources and immediately transfers the request to the Tekton API to reflect the change in the corresponding Tekton resources. The changes can be creation, deletion, or updating. The API server ensures that there is a working connection between our controller and the Tekton API. 
 MKS Server also exposes APIs to introduce a change of state in the MKS resources. In technical terms these are called :code:`verbs`. There are five such verbs that we have exposed: :code:`create`, :code:`update`, :code:`get`, :code:`delete`, and :code:`list`. They can be utilized by a REST client, or in our case **MKS CLI** to introduce desired change. The MKS command-line interface provides commands and subcommands to do the desired tasks. 
 Whenever there is a change in the state, there is a logic running inside the controller to react on that and that also affects our database. We store four datapoints in our database: :code:`created`, :code:`deleted`, :code:`completed`, and :code:`failed`. They tell us about the current statistcs of our MKS resource using a single-page web app called **MKS Dashboard** (or UI).
 This was about the architecture of the Minimal Tekton Server. Let us jump into more technical stuff.
 How to implement a CRD controller?
 ----------------------------------
 During this assignment, something that took the most time and effort was the implementation of a controller for our custom resources. This isn't very hard if you go by the rules and do the things according to the well-defined documents and blogs since this is a standard step in the implementation of any custom resource controller. But did we follow the rules? Hell no! But this time, let us go step-by-step. 
 1. The first step is to define a :code:`CustomResourceDefinition` for our custom resource. Let us define a CRD called :code:`spacetime`. To do this you can write a YAML file like below.
 .. code-block:: yaml
    # file: spacetime-crd.yaml
    apiVersion: apiextensions.k8s.io/v1
    kind: CustomResourceDefinition
    metadata:
    # name must match the spec fields below, and be in the form: <plural>.<group>
    name: spacetimes.example.com
    spec:
    # group name to use for REST API: /apis/<group>/<version>
    group: example.com
    # list of versions supported by this CustomResourceDefinition
    versions:
      - name: v1alpha1
      # Each version can be enabled/disabled by Served flag.
      served: true
      # One and only one version must be marked as the storage version.
      storage: true
      schema:
        openAPIV3Schema:
        type: object
        properties:
          spec:
          type: object
          properties:
            message:
            type: string
    # either Namespaced or Cluster
    scope: Namespaced
    names:
      # plural name to be used in the URL: /apis/<group>/<version>/<plural>
      plural: spacetimes
      # singular name to be used as an alias on the CLI and for display
      singular: spacetime
      # kind is normally the CamelCased singular type. Your resource manifests use this.
      kind: SpaceTime
      # shortNames allow shorter string to match your resource on the CLI
      shortNames:
      - st
 You can learn more about the fields and options `here <https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/>`_. The CRD that we defined above corresponds to the :code:`CustomResource` given below. Once you apply the above file you will be able to see the :code:`spacetime` custom resource on your Kubernetes/OpenShift cluster.
 .. code-block:: yaml
    # file: spacetime-cr.yaml
    apiVersion: spacetimes.example.com/v1alpha1
    kind: SpaceTime
    metadata:
      name: spacetime-cr
    spec:
      message: "Hello from space!"
 Apply them using the following commands:
 .. code-block:: bash
    kubectl apply -f spacetime-crd.yaml
    kubectl apply -f spacetime-cr.yaml
 2. Once we have defined our custom resources, we need to define the types that will correspond to this custom resource definition. This can be done using :code:`k8s.io/apimachinery/pkg/apis/meta/v1` package written in golang. Did I tell you that this is all in golang? Well, now you know. Create a package structure for a golang project and add the definition of the type as given below.
 .. code-block:: bash
    mkdir -p pkg/api/spacetime/v1alpha1
    touch pkg/api/spacetime/v1alpha1/{spacetime_types,register,doc}.go pkg/api/spacetime/register.go
 Add the following content to the corresponding files.
 .. code-block:: golang
    // file: /pkg/api/spacetime/v1alpha1/spacetime_types.go
    package v1alpha1
    import (
      metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
    )
    type SpaceTime struct {
      metav1.TypeMeta   `json:",inline"`
      metav1.ObjectMeta `json:"metadata,omitempty"`
      Spec SpaceTimeSpec `json:"spec"`
    }
    type SpaceTimeSpec struct {
      Message string  `json:"message"`
    }
    type SpaceTimeList struct {
      metav1.TypeMeta     `json:",inline"`
      metav1.ListMeta     `json:"metadata"`
      Items []SpaceTime   `json:"items"`
    }
 **To be Continued**
@@ -1,134 +0,0 @@
 **************************
 reStructuredText in GitHub
 **************************
 :date: 2021-02-14 22:47
 :slug: rst-guide
 :category: development
 :tags: rst, github
 :summary: reStructuredText syntax
 - Headers
  .. code-block:: rst
    Top Title
    =========
    Sub Title
    ---------
    Sub Sub Title
    ^^^^^^^^^^^^^
 - Images
  - Direct
    .. code-block:: rst
        .. figure:: image-path-or-url
            :align: center
            :target: link-to-go-when-image-is-clicked
            :alt: alternative-text-if-any
  - Indirect
    .. code-block:: rst
        .. |substitution| image:: image-path-or-url
            :target: link-to-go-when-image-is-clicked
    You can use :code:`|substitution|` where you want to put your image.
 - Links
  .. code-block:: rst
    `Link Text <link-itself>`__
 - Lists
  .. code-block:: rst
    - item 1 
    - item 2
    * item 1
    * itme 2
    #. item 1
    #. item 2
    1. item 1
    2. item 2
  First two lists are unordered next two are ordered.
 - Code
  - Inline
    .. code-block:: rst
        :code:`your-code`
  - Code block
    .. code-block:: rst
        .. code-block:: language(optional)
            Your code 
            in multiple lines. You may enable line numbers too.
 - Tables
  .. code-block:: rst
    +----------------+----------------+
    | Header Cell    | Header Cell    |
    +================+================+
    | Data cell      | Data Cell      |
    +----------------+----------------+
    | Header Cell    | Header Cell    |
    +----------------+----------------+
 - Raw HTML block
  .. code-block:: rst
    .. raw:: html
        <put>
            your html code here
        </put>
 - Notes, warnings
  .. code-block:: rst
    .. note::
        Put your note here.
    .. warning::
        Put your warning here.
    .. important::
        Put instructions here.
    .. admonition:: custom-text
        Custom description here.
 These all are supported by GitHub very well. For more exhautive list specific to Sphinx see `this <https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html>`__ link.
 Tips
 ----
 - There must be a blank line before and after any directive. Such as after title or code block, tables etc.
 - The options and content of a directives must be 1 tab indented to the directives.
@@ -1,157 +0,0 @@
 ************************
 How I Created This Blog?
 ************************
 :date: 2021-01-26 16:47
 :updated: 2021-05-05 22:30
 :tags: blog, pelican, ssg
 :slug: twilight-blog
 :category: development
 :summary: As you would have guessed by now, this blog is created using one such awesome SSG named **Pelican**. Pelican is simple, customizable and offers lots of themes and plugins. Pelican is python based SSG and is available through :code:`pip`.
 .. role:: html-raw(raw)
    :format: html
 :html-raw:`<div class="alert alert-info" role="alert">This article may not be for you if you are a web developer. You already got better options. 😉</div>`
 There are lots of ways to create a personal website or a blog. You can design your own user interface and write the backend code. But not everyone is a web developer. And here comes :abbr:`SSGs (Static Site Generator)` to the rescue. **Static Site Generators** are little more than just website generators. In general, if you are looking for a simple blog, its better to use SSG than writing a lot of html and css. They are simple and elegant. Easy to maintain and you can add lots of customizations to your site without breaking or bloating your blog. There are lots of SSGs, `Jekyll <https://jekyllrb.com/>`_, `Pelican <https://blog.getpelican.com/>`_ and more complex ones like `Gatsby <https://www.gatsbyjs.com/>`_, `Hugo <https://gohugo.io/>`_ .
 As you would have guessed by now, this blog is created using one such awesome SSG named **Pelican**. Pelican is simple, customizable and offers lots of `themes <http://www.pelicanthemes.com/>`_ and `plugins <https://github.com/getpelican/pelican-plugins>`_. Pelican is python based SSG and is available through :code:`pip`. 
 .. code-block:: shell
    # for reStructuredText only (recommended)
    python -m pip install pelican
    # for markdown and reStructuredText both
    python -m pip install "pelican[markdown]"
 You can start a pelican project by typing following command. It will create a basic template and build configurations.
 .. code-block:: shell
    pelican-quickstart
    # output
    yourproject/
    ├── content              # Put your content here
    │   └── (pages)          
    ├── output               # Output files
    ├── tasks.py             
    ├── Makefile             # Makefile to run build and publish command
    ├── pelicanconf.py       # Main settings file
    └── publishconf.py       # Settings to use when ready to publish
 Next step is to choose themes. As I said earlier there are lots of `themes <http://www.pelicanthemes.com/>`_ . And it is easy to create your own theme. Check `here <https://docs.getpelican.com/en/latest/themes.html>`_ to create your own theme. My choice of theme was `pelican-alchemy <https://nairobilug.github.io/pelican-alchemy/>`_ . This is a simple and great theme. Installing and removing themes in pelican is very easy. 
 .. code-block:: shell
    # list all installed themes
    pelican-themes -l
    # output
    simple
    alchemy
    notmyidea
    # install new theme 
    pelican-themes -i theme-path
    # remove a theme
    pelican-themes -r theme-name
 To use a particular theme, set the :code:`THEME` variable in the **pelicanconf.py** file. 
 .. code-block:: python
    THEME = 'alchemy'
 You can also use a theme that is not installed if you have all the required theme files. Just set this variable to its path.
 .. code-block:: python
    THEME = 'path-to-theme-directory'
 Various themes will have different feature, choose according to your need, or you can always add a feature through plugin. The next step is to build and check your blog. Pelican got it all set up. 
 .. code-block:: shell
    # build your website
    make html
    # output
    "pelican" "/mnt/z/my_git/avinal.github.io/content" -o "/mnt/z/my_git/avinal.github.io/output" -s "/mnt/z/my_git/avinal.github.io/pelicanconf.py" 
    Done: Processed 6 articles, 0 drafts, 1 page, 0 hidden pages and 0 draft pages in 2.43 seconds.
    # build and test/serve on localhost
    make serve
    # output
    "pelican" -l "/mnt/z/my_git/avinal.github.io/content" -o "/mnt/z/my_git/avinal.github.io/output" -s "/mnt/z/my_git/avinal.github.io/pelicanconf.py" 
    Serving site at: 127.0.0.1:8000 - Tap CTRL-C to stop
 Now open your browser and open `127.0.0.1:8000 <127.0.0.1:8000>`_ or `localhost:8000 <localhost:8000>`_. You should be able to see your new blog. Stop local server using :code:`CTRL+C`. Next step is to publish it to github pages. Pelican has tools for this too. But wait we can do something more interesting here. Why not let GitHub take care of both building and publishing? Just push this project to a GitHub repository and set up GitHub pages. See `this <https://pages.github.com/>`_ help for instructions on that. Before pushing to GitHub add this little script to your project.
 .. code-block:: shell
    #! /bin/bash
    ## file: publi.sh
    # install tools
    sudo apt-get install -y git make python3 python3-pip python3-setuptools python3-wheel
    # setup github config
    git config user.email "your-email"
    git config user.name "your-username"
    # install dependencies
    sudo pip3 install -r requirements.txt
    # pelican commands - install theme put your theme in themes directory
    pelican-themes --install themes/theme-name
    # publish to github pages
    ghp-import -m "Generate Pelican site" -b gh-pages output
 	git push -f origin gh-pages
 Now once your project is on GitHub, go to the **Actions** tab and click on *set up a workflow yourself* and paste the following code into the file and commit it.
 .. code-block:: yaml
    # file: publish.yml
    name: Publish Blog
    on:
      push:
        branches: [ main ]
      pull_request:
        branches: [ main ]
    jobs:
      build:
        runs-on: ubuntu-latest
        steps:
          - uses: actions/checkout@v2
          - name: set up permissions
            run: chmod +x publi.sh
          - name: Run a multi-line script
            run: ./publi.sh
 If you have done everything correctly then go to *https://username.github.io* and you should see your blog. From now on whenever you want to add an article, just write it, test locally and push. Yay your blog is ready.
 :html-raw:`<h2 style=font-family:Exodar;font-weight:lighter;">But My Blog is Special 🥰</h2>`
 My blog looks different, that is because I customized this theme a lot, especially headers, footers, and link appearance. And sorry I won't be publish my theme any time sooner. But I am listing down all the resources I have used for finally getting this result. You can always get my help by sending me a :html-raw:`<a href="mailto:avinal.xlvii@gmail.com" class="fa fa-envelope" style="text-decoration: none;"></a>` or starting a discussion on :html-raw:`<a href="https://github.com/avinal/avinal/discussions/2" class="fab fa-github" style="text-decoration: none;"></a>`.
 * `Pelican Blog <https://blog.getpelican.com/>`_
 * `Pelican Docs <https://docs.getpelican.com/en/latest/>`_
 * `Pelican Themes <http://www.pelicanthemes.com/>`_
 * `Pelican Alchemy Theme <https://github.com/nairobilug/pelican-alchemy>`_
 * `Parallax Star background in CSS <https://codepen.io/saransh/pen/BKJun>`_
 * `Solar System animation <https://codepen.io/kowlor/pen/ZYYQoy>`_
 * :html-raw:`<a href="https://www.dafont.com/exodar.font" style="font-family: Exodar;font-weight: lighter;text-decoration: none;">EXODAR Font</a>`
 * `Overpass Mono <https://fonts.google.com/specimen/Overpass+Mono>`_
 * `Font Awesome <https://fontawesome.com/how-to-use/on-the-web/setup/hosting-font-awesome-yourself>`_
 :html-raw:`<div class="alert alert-warning" role="alert">Some of the fonts I have used in my blog may not be available for commercial use. Please check if you intend to do so. Alternatively you may use fonts from this wonderful collection, <a href="https://www.websiteplanet.com/blog/best-free-fonts/">70+ Best Free Fonts for Designers – Free for Commercial Use in 2021</a> <i>(Thanks Ritta Blens for this suggestion)</i></div>`
 :html-raw:`<p align=center>Thanks!</p>`
@@ -1,160 +0,0 @@
 *******************************************************
 How I implemented WakaTime embeddable Coding Graph GHA?
 *******************************************************
 :date: 2021-02-02 21:47
 :tags: wakatime, github-action, coding
 :category: development
 :slug: wakatime-readme
 :summary: f you use WakaTime to track your coding activity. You can add that to your README as a bar graph or embed it in your blog/portfolio. Just add this action to any of your repositories and there you have it.
 .. raw:: html
 	<a href="https://github.com/avinal/Profile-Readme-WakaTime"><img src="https://raw.githubusercontent.com/avinal/Profile-Readme-WakaTime/b281d074ee75f9626b39d10e2e518c6a297208a3/waka.png" class="img-fluid"></a>
 Implementation Details
 ----------------------
 This GitHub Action is divided into three parts. I didn't want to use Docker but it seems it doesn't work well without it. Let dive a little into technical details. Three parts are as below.
 1. `main.py <https://github.com/avinal/Profile-Readme-WakaTime/blob/master/main.py>`_ python script. This script contains many procedures.
 * `Getting JSON data file via WakaTime API <https://github.com/avinal/Profile-Readme-WakaTime/blob/master/main.py#L52>`_
    .. code-block:: python
 		def get_stats() -> list:
 			...
 			return data_list
  This function parses the JSON file received and scraps out the useful data as a list of lists. Data scraped are language list, time spent on each language, percentage of the time, start date, and end date. For this action, I have limited the number of languages to 5 however it should be very easy to increase that number.
 * `Setting the Timeline <https://github.com/avinal/Profile-Readme-WakaTime/blob/master/main.py#L13>`_
    .. code-block:: python
 		def this_week(dates: list) -> str:
       		...
       		return f"Coding Activity During: {week_start.strftime('%d %B, %Y')} to {week_end.strftime('%d %B, %Y')}"
  The start date and end date scraped in the last function are used here to set the timeline. Because date in JSON is provided in UTC as below :
    .. code-block:: json
    	date:	"YYYY-MM-DDTHH:MM:SSZ"
  I striped it to simple dates only. We can set them manually by taking the current time from the system. But that method is flawed. But this method ensures that JSON was received latest and the request was successful. Any anomaly will point to a failure in request.
 * `Creating a bar graph <https://github.com/avinal/Profile-Readme-WakaTime/blob/master/main.py#L21>`_
    .. code-block:: python
    	def make_graph(data: list):
 			...
    		savefig(...)
  Lastly, it is time to generate the graph and save them as an image. This function uses the data scraped in the first step. Creating a bar graph using `matplotlib` is easy. Decorating was a bit difficult. I wanted this graph to merge with GitHub's look so I chose to color the bar as GitHub colors the languages. That data is stored as `colors.json`. Many of the languages have slightly different spelling in GitHub as compared to WakaTime. So some languages are shown in default color. That can be improved if we notice that language and change its color manually. Lastly, the graph is saved both as SVG and PNG. SVGs are better to put on a responsive page.
 2. `entrypoint.py <https://github.com/avinal/Profile-Readme-WakaTime/blob/master/entrypoint.sh>`_ shell script. This shell script clones the repository copies the image and pushes changes to the master. There were several problems. First of all authentication. This was solved by using a remote repository address using GitHub Token. And it seems that GitHub doesn't allow to commit without a username and email. So I used **github-actions** bot email.
 	.. code-block:: bash
 		remote_repo-"https://${GITHUB_ACTOR}:${INPUT_GITHUB_TOKEN}@github.com/${GITHUB_REPOSITORY}.git"
 		git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
 		git config user.name "GitHub Actions"
  :code:`41898282` is the id assigned to the github-actions bot. Don't ask where I found them 🙂.
  Another problem was to separate repository name from combined *username/repository-name* provided by `${GITHUB_REPOSITORY}`. GitHub doesn't provides a direct way to get just the repo name. We used *Internal Field Separator*. It returns an array and works similar to :code:`split()` command in Python and Java. 
 	.. code-block:: bash
 		# '/' is the seperator
 		IFS-'/' read -ra reponame <<< "${GITHUB_REPOSITORY}"
 		# returned {username, repository}
 		repository-"${reponame[1]}"
 After that, all other commands are pretty straight. Commit the added files and push them.
 3. `Dockerfile <https://github.com/avinal/Profile-Readme-WakaTime/blob/master/Dockerfile>`_ **IMPORTANT** It took a lot of time to reach this state 🥱. This is where all the magic happens. I am running `ubuntu:latest` inside the container. I first update the distribution. Then install the required python packages. Lastly, I invoke the python script and shell script. 
 There was an almost impossible problem, I searched hundreds of posts that *how can I access the generated files inside Docker container*, but no luck. But at last, I found a workaround(obviously otherwise you wouldn't be reading this by now 🤣) each command is run in a separate virtual sub-container. As the command ends its output is also lost but not when you club multiple commands together. At least not until every command is finished. The generated files are available to the next clubbed process. I did that by combining the python script run and shell script run.
 .. code-block:: dockerfile
    CMD python3 /main.py && /entrypoint.sh
 This part is the smallest yet took the most time and tries while developing this action.
 How to use this GitHub Actions?
 -------------------------------
 1. First get your WakaTime API Key. You can get it from your [WakaTime](https://wakatime.com) account settings. 
 2. Save WakaTime API Key to Repository Secret. Find that by clicking the Settings tab. Keep the name of the secret as **WAKATIME_API_KEY**.
 3. Add the following line in your README.md of your repo.
 	.. code-block:: html
 		<img src-"https://github.com/<username>/<repository-name>/blob/<branch-name>/images/stat.svg" alt-"Alternative Text"/>
 		Example: <img src-"https://github.com/avinal/avinal/blob/main/images/stat.svg" alt-"Avinal WakaTime Activity"/>
  You can use this method to embed in web pages too. **Do not use the markdown method of inserting images. It does not work sometimes.**
 4. Click the **Action** tab and **choose to set up a workflow yourself**.
 5. Copy the following code into the opened file, you can search for **WakaTime Stat** in the marketplace tab for assistance.
 	.. code-block:: yaml
 		name: WakaTime status update
 		on:
 		  schedule:
 			# Runs at 12 am  '0 0 * * *'  UTC
 			- cron: "1 0 * * *"
 		jobs:
 		  update-readme:
 			name: Update the WakaTime Stat
 			runs-on: ubuntu-latest
 			steps:
 			  # Use avinal/Profile-Readme-WakaTime@<latest-release-tag> for latest stable release
 			  # Do not change the line below except the word master with tag number maybe
 			  # If you have forked this project you can use <username>/Profile-Readme-WakaTime@master instead
 			  - uses: avinal/Profile-Readme-WakaTime@master
 			    with:
 				  # WakaTime API key stored in secrets, do not directly paste it here
 				  WAKATIME_API_KEY: ${{ secrets.WAKATIME_API_KEY }}
 				  # Automatic github token
 				  GITHUB_TOKEN: ${{ github.token }}
 				  # Branch - newer GitHub repositories have "main" as default branch, change to main in that case, default is master
 				  BRANCH: "master"
 				  # Manual Commit messages - write your own messages here
 				  COMMIT_MSG: "Automated Coding Activity Update :alien:"
 6. Please wait till 12 AM UTC to run this workflow automatically. Or you can force run it by going to the Actions tab. Or you can add the following lines under `on:` to run with every push. Search for 12 AM UTC to find the equivalent time in your time zone. 
 	.. code-block:: yaml
 		on:
 		  push:
 			branches: [ master ]
 		  schedule:
 			- cron: '1 0 * * *'
 My Coding Activity
 ------------------
 .. raw:: html
 	<img class="img-fluid" src="https://raw.githubusercontent.com/avinal/avinal/main/images/stat.svg">
@@ -1,95 +0,0 @@
 **********************************
 Move WSL 2 Safely to another Drive
 **********************************
 :date: 2020-12-31 19:07
 :tags: wsl, wsl2
 :category: development
 :slug: wsl1
 :summary: It is real pain when you have small SSD and Windows Subsystem for Linux (WSL) is growing exponentially in size. There is no easy way to move the WSL installation to another drive. Here in this blog I will discuss how to tackle this problem with bite size steps.
 It is real pain when you have small SSD and Windows Subsystem for Linux (WSL) is growing exponentially in size. There is no easy way to move 
 the WSL installation to another drive. Here in this blog I will discuss how to tackle this problem with bite size steps. 
 .. |powershell| image:: /images/powershell.png
    :width: 5%
    :align: middle
 .. |command-line| image:: /images/command-line.png
    :width: 5%
    :align: middle
 .. |windows10| image:: /images/windows10.png
    :width: 5%
    :align: middle
    :alt: WinKey
 .. role:: html-raw(raw)
    :format: html
 1. Open a PowerShell |powershell| or Command Prompt |command-line| with *Admin* access. For this you can use |windows10| + X shortcut and select **Windows PowerShell(Admin)**.
 2. Check if the WSL 2 installation you are planning to move is is currently running/stopped.
 .. code-block:: powershell
    PS C:\Users\Avinal> wsl -l -v
    PS C:\Users\Avinal>
      NAME      STATE           VERSION
    * Ubuntu    Running         2
      Kali      Stopped         2
 3. If its running then you must stop the particular WSL distribution. (*Ubuntu* used as example)
 .. code-block:: powershell
    PS C:\Users\Avinal> wsl -t Ubuntu
 4. Export to some folder. (Here exporting *Ubuntu* as *ubuntu-ex.tar* to *Z:\wsl2*)
 .. code-block:: powershell
    PS C:\Users\Avinal> wsl --export Ubuntu "Z:\export\ubuntu-ex.tar"
 5. Unregister previous WSL installation
 .. code-block:: powershell
    PS C:\Users\Avinal> wsl --unregister Ubuntu
 6. Create a new folder and import your WSL installation to that folder.
 .. code-block:: powershell
    PS C:\Users\Avinal> New-Item -Path "Z:\wsl2" -ItemType Directory
        Directory: Z:\
    Mode                 LastWriteTime         Length Name
    ----                 -------------         ------ ----
    d-----        31-12-2020     21:03                wsl2
    PS C:\Users\Avinal> wsl --import Ubuntu "Z:\wsl2" "Z:\export\ubuntu-ex.tar"
 7. Check after import is complete
 .. code-block:: powershell
    PS C:\Users\Avinal> wsl -l -v
    PS C:\Users\Avinal>
      NAME      STATE           VERSION
    * Ubuntu    Running         2
      Kali      Stopped         2
 8. Mark one of your WSL distribution as *(default)*.
 .. code-block:: powershell
    PS C:\Users\Avinal> wsl -s Ubuntu
 9. After exporting your default user will be set as :html-raw:`<i style="color:red">root</i>` , to change it to your desired username, run following command
 .. code-block:: powershell
    PS C:\Users\Avinal> ubuntu config --default-user user_name
 10. Finally run :code:`wsl` and you have successfully moved your WSL 2 installation to another drive.
@@ -1 +0,0 @@
 avinal.space
@@ -1,29 +0,0 @@
 <?xml version="1.0" standalone="no"?>
 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 20010904//EN"
 "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
 <svg version="1.0" xmlns="http://www.w3.org/2000/svg"
 width="700.000000pt" height="700.000000pt" viewBox="0 0 700.000000 700.000000"
 preserveAspectRatio="xMidYMid meet">
 <metadata>
 Created by potrace 1.11, written by Peter Selinger 2001-2013
 </metadata>
 <g transform="translate(0.000000,700.000000) scale(0.100000,-0.100000)"
 fill="#000000" stroke="none">
 <path d="M3458 6985 c-2 -1 -43 -5 -93 -9 -49 -3 -103 -8 -120 -10 -475 -64
 -918 -318 -1215 -696 -91 -115 -93 -119 -152 -220 -62 -108 -49 -82 -260 -545
 -87 -192 -165 -364 -173 -381 -8 -16 -27 -59 -43 -95 -16 -35 -43 -93 -60
 -129 -75 -161 -92 -202 -86 -211 3 -5 0 -9 -6 -9 -13 0 -13 2 40 -165 21 -66
 66 -208 100 -315 34 -107 70 -220 80 -250 l17 -55 -31 -7 c-17 -4 -44 -10 -61
 -13 -16 -3 -38 -8 -47 -11 -9 -3 -27 -7 -40 -9 -13 -3 -94 -21 -181 -42 l-158
 -37 -63 -116 c-35 -63 -78 -142 -96 -175 -42 -78 -89 -164 -160 -295 -101
 -186 -119 -220 -317 -585 -108 -198 -209 -385 -225 -415 -17 -30 -48 -87 -69
 -127 l-39 -72 2 -543 3 -543 572 0 c387 1 573 -3 574 -10 0 -5 1 -206 2 -445
 l2 -434 2345 -1 2345 0 5 445 5 445 570 0 570 0 3 549 2 550 -112 205 c-61
 113 -125 231 -141 261 -16 30 -53 98 -82 150 -29 52 -67 122 -85 155 -18 33
 -45 83 -60 110 -42 76 -79 143 -118 215 -19 36 -62 115 -95 175 -33 61 -70
 128 -82 150 -156 287 -192 349 -210 355 -11 5 -123 32 -250 60 -126 29 -234
 56 -238 60 -5 4 23 108 63 231 39 123 94 295 121 382 l50 158 -44 102 c-91
 209 -526 1155 -562 1222 -143 268 -354 500 -610 670 -305 203 -621 305 -987
 318 -54 2 -99 3 -100 2z"/>
 </g>
 </svg>
@@ -1,6 +0,0 @@
 ********
 About Me
 ********
 :slug: about-me
@@ -0,0 +1,60 @@
 ---
 title: The Big Red Ants
 date: 2012-02-27 22:47
 tags: [ants, sav] 
 category: article
 description: 'The Big Red Ants'
 image: /images/ants.jpg
 ---
 # The Big Red Ants
 In a bird's eye view if we see around us, ants are the common and
 tiniest living entitiy seen by naked eye. One of them are the big red
 ants, in my view they are unique from others in two ways, first they
 live on trees and second their anteenas are too long and bent in middle,
 seems like their fore legs. Their mandible (mouth) seems like eagle's
 beak.
 As I observed them making and reparing their nests, I concluded that
 they are very laborious and intellectual. They create their nests by
 binding two or more leaves (maybe up to 500) together. They stich the
 leaves using a stinky white substance either excreted by themselves or
 from trees. This substance is like web of spider. At first builder ants
 creates an array at the blade of two leaves. Then they make ant-cranes
 or ant-chain like chain of monomer to form a polymer. They catch the
 leaves and pull each other to stich. After some time, the parliament of
 leaves transforms into a leaf-sac called their nest. They also weave
 translucent cloth like structure to cover remainings of leaf. A nest
 hangs by a branch of the trees.
 A nest is skillfully divided into living rooms, barracks, storehouse,
 egg room and queen's room. The eggroom, lies at the center of nest to
 protect from outer attack until last time. Besides that, lies queen's
 room. Living rooms are sequenncly joined with eggroom. There are
 different rooms for workers, food searchers etc. The partition of the
 room resembles atom's electron shell, one upon another. At last barracks
 are the outermost rooms, just like outermost orbit of electron. The
 defence system is strongest at the nest's opening. A nest may size as
 2-3 footballs and have 50 to 10000 ants. There may be more openings.
 Now about their attacking and protecting skills. A solider is unique
 from other ants. It is equipped with many attacking and defending
 skills. Normally they do not attack. They are social insects. If someone
 attacks, all other ants go inside, and soldiers come out. They spread
 allover the nest. They are very sensetive and have sharp vision. If any
 one of them see their enemy the stand on their hind legs, swinging,
 their forelegs and anteens in their air as scolding someone. Their spit
 contains formic acid, present at the end of the abdomen below the
 rectum. If their nest is broken and eggs fall on ground then the ants
 make a dome, like the dome of Taj mahal to save the eggs till last their
 breadth. This shows their caring skills.
 The most amazing is their discipline. They can easily beat a human in
 race of discipline. Humans must learn from it. When two ants meet, they
 touch their anteena to communicate. When they walk in a queue, they seem
 like twinkling dots and dashes. I want to conclude that **All tiny
 things are not really tiny. It may be as a space having infinite
 mysteries one has to explore it.**
 Photo Attribution : Photo by Michael Willinger from Pexels:
@@ -1,17 +1,11 @@
-****************
+---
-प्रेम रतन धन पायो 
+title: प्रेम रतन धन पायो
-****************
+date: 2019-09-21 15:47
-
+category: article
-:date: 2019-09-21 15:47
+tags: [love, article, hindi]
-:slug: for-sunshine
+---
 :category: article
 :tags: love, article, hindi
 :summary: टूटता तारा देखना एक अलौकिक अनुभव है। हिमाद्रि के छत से आसमान कुछ ज्यादा ही करीब प्रतीत होता है । लोग सदियों से हिमालय को पूजते आयें हैं । दादा-दादी कहा करते थे ये जिंदा पहाड़ हैं । सारी बातें सुनते हैं लोगों की । उनके दुख दर्द दूर करते हैं, ये देवता हैं ।
 .. raw:: html
    <p style="border: 2px solid var(--cyan);border-radius: 7px;" align=center>This article was published in 18th edition of SRIJAN, the official magazine of <a href="https://nith.ac.in" style="text-decoration: none;">National Institute of Technology, Hamirpur</a>, India. The magazine can be accessed <a href="https://issuu.com/srijandesk/docs/srijan2020" style="text-decoration: none;">here</a>.<p>
 # प्रेम रतन धन पायो
 टूटता तारा देखना एक अलौकिक अनुभव है। हिमाद्रि के छत से आसमान कुछ ज्यादा ही करीब प्रतीत होता है । लोग सदियों से हिमालय को पूजते आयें हैं ।
 दादा-दादी कहा करते थे ये जिंदा पहाड़ हैं । सारी बातें सुनते हैं लोगों की । उनके दुख दर्द दूर करते हैं, ये देवता हैं । आजकल जब रोज़ क्लास
@@ -23,7 +17,6 @@
 तप करते हुए अपना जीवन अर्पित कर दिया । इसलिए हिमालय की पहाड़ों से टूटता तारा देखना दैविक हैं क्योंकि शायद वो तारे उन ऋषि-मुनियों की पवित्र
 आत्माओं का संकेत हैं ।
 प्रकृति की सुंदरता और कलाकारी हिमालय की कण-कण में झलकती है। प्रकृति ने प्रेम को भी हिमालय के जितना ही विशाल और अलौकिक बनाया है । ये एक
 अलग चर्चा का विषय है कि हिमालय पहले आया या प्रेम। मैं तो प्रेम के पक्ष में हूँ । वो हर अणु-परमाणु जिन्होंने इतने बड़ा पहाड़ खड़ा किया वो सब
 आपस में प्रेम से बंधे हुए हैं। ये पृथ्वी, सूर्य, चंद्रमा, आकाश-गंगा इत्यादि सब प्रेम से बंधे हुए हैं । और हिमाद्रि के छत पर मैं इसी प्रेम
@@ -37,7 +30,6 @@
 चैतन्य अवस्था में होते हैं तो रहस्य, प्रतिभज्ञान इत्यादि के रास्ते खुल जाते हैं। और विज्ञान ये भी कहता है कि निद्रा के माध्यम से इस
 अवस्था में जाना उतना ही अनिश्चित है जितना किसी बाला का मेरे लिए प्रेम-प्रस्ताव । सरल शब्दों में – मैं कुछ समय के लिए सो गया।
 आज से ठीक 2 महीने पहले अगर ये मुझसे कोई पूछता की क्या चाहिए तुम्हें तो शायद मेरे पास जबाव होता। दोस्त तो बहुत हैं पर जब कोई ऐसा हो जो
 आपके अधूरे वाक्य पूरे कर सके, कोई ऐसा जो आपकी भावनाओं को आपकी तरह समझ सके, कोई ऐसा जो आपको आपके असल रूप में पसंद करता हो । आपको लग रहा
 होगा की मैं एक प्रेमिका का विवरण दे रहा हूँ, पर नहीं या शायद हाँ , मैं समझता हूँ की अधिकतर लोग प्रेमिका शब्द का प्रयोग अनुचित ढंग से करते
@@ -58,7 +50,6 @@
 पर जो प्रेम लोगों के अंदर व्याप्त है ये हर कोई नहीं समझता। मैं उस विशेष व्यक्ति का कृतज्ञ हूँ जिसने ने मुझे इस दोहे के मूल भाव का अहसास
 करवाया।
 कभी-कभी डर लगता है, खोने का उसे। आजकल दुनिया में सब अनिश्चित है। कब-क्या हो जाए ये कोई नहीं बता सकता। पहले सिर्फ पृथ्वी थी फिर लोग हुए और
 तब से पृथ्वी अस्थमा की मरीज है। किसी प्रसिद्ध कवि ने लिखा है :
@@ -68,4 +59,3 @@
 ठंडी-ठंडी हवाओं ने मेरी सारी नींद उड़ा दी। प्रकृति शायद मुझे खुश करके मारना चाहती थी। आसमान ने एक बड़े काले पर्दे का रूप ले लिया था और उस
 पर्दे पर दसियो उजले साँप रेंगते नज़र आ रहे थे। मानो दस सालो के टूटते तारे एक साथ दिख रहे हों और आसमान कह रहा हो – जो चाहिए, जितना चाहिए
 माँग लो। और मैंने सच में माँग लिए , लगभग सब कुछ । और उसको हमेशा पास रखने की दुआ तो नहीं माँग सका , पर वो जहां रहे, खुश रहे, सलामत रहे।
@@ -0,0 +1,275 @@
 ---
 title: Create the VLC User Documentation for one Mobile Port(Android)
 date: 2020-12-01 23:47
 modified: 2020-12-31 23:19
 category: development
 tags: [vlc, gsod, gsod2020]
 description: 'The project was to Create the VLC User Documentation for Android 
 Mobile Port which was previously hosted on VLC wiki pages. The major portion 
 of this was to start everything from scratch including chapter separation, 
 section organization.'
 ---
 # Create the VLC User Documentation for one Mobile Port(Android)
 VideoLAN is a non-profit organization that develops software for playing
 video and other media formats. VLC media player (commonly known as just
 VLC) is a free and Open Source cross-platform multimedia player and
 framework that plays most multimedia files as well as DVDs, Audio CDs,
 VCDs, and various streaming protocols built by the VideoLAN organization
 and a team of volunteers. VLC for Android is a port of the VLC for
 Android OS.
 The project was to Create the VLC User Documentation for Android Mobile
 Port which was previously hosted on VLC's wiki pages. The major portion
 of this was to start everything from scratch including chapter
 separation, section organization and an engaging and easy to follow for
 both technical and non-technical users. The original proposal can be
 found here.
 ## PROJECT GOALS
 - Propose a new structure for documentation e.g. Chapter Separation,
  Sections etc
 - Proper balance between technical and non-technical descriptions to
  serve all kinds of users.
 - Adequate amount of screenshots in each section and other supporting
  media to make documentation more appealing.
 - Optimized for all Screen Sizes. Especially for Mobile Devices.
 - Ease of navigation
 ## COMMUNITY BONDING
 This period was mostly utilized for collecting more information and many
 internal meetings to shape the projects and bonding with fellow writers,
 developers(mentors). I got to know more about the VLC organization and
 the project. We decided to create a skeleton of the project and then
 follow a Issue-Merge Request-Review-Merge system to keep the commit
 history clean and maintain the proper review of the work before it is
 merged.
 I initially proposed that the new documentation should also use the same
 tools(Sphinx and GitLab Pages) because if in future we want to merge all
 the documentation into a single one, it will be easier to migrate and
 will provide a consistency across all documentations. Later I got to
 know that this will be an independent project and may not be merged
 since it solves a lot of problems. I was already familiar with the tools
 so it took no time to get started.
 Nicolas Pomepuy, who is the lead developer of VLC for Android was
 assigned as my primary mentor and Simon Latapie as secondary mentor.
 ## DOCUMENTATION DEVELOPMENT PHASE
 Initial Preparation I first moved my existing demo documentation to an
 entirely new repository with only the skeleton at the suggestion of my
 mentor. It was necessary to keep the commit history clean. The skeleton
 contained the empty directories representing the chapter separation. I
 got to learn “how to properly develop a project and contribute to open
 source”. This was a major lesson that got me familiar with the Merge
 Request and Review system.
 The Development The next part was to frame the actual documentation
 pages and push to the repository. Since there was a significant
 time-zone difference we agreed to discuss by creating issues and
 sometimes my emails. There was one meeting every fortnight to check the
 process and discuss further development and blockers. Nicolas was really
 helpful and patient, answering each of my big-small queries.
 Work Done
 <style>
 table,td,th {
 border-collapse:collapse;
 border: 1px solid #000000;
 }
 </style>
 <table>
 <tr>
 <td><strong>Documentation</strong></td>
 <td><a href="https://avinal.videolan.me/vlc-android-user/">VLC for Android User Documentation </a>
 </td>
 </tr>
 <tr>
 <td><strong>Project Repository</strong>
 </td>
 <td><a href="https://code.videolan.org/avinal/vlc-android-user">Projects · Avinal Kumar / VLC for Android User Documentation</a>
 </td>
 </tr>
 <tr>
 <td><strong>Commits</strong>
 </td>
 <td><a href="https://code.videolan.org/avinal/vlc-android-user/-/commits/master">Commits · Avinal Kumar / VLC for Android User Documentation</a>
 </td>
 </tr>
 <tr>
 <td><strong>Issues/Discussions</strong>
 </td>
 <td><a href="https://code.videolan.org/avinal/vlc-android-user/-/issues">Issues · Avinal Kumar / VLC for Android User Documentation</a>
 </td>
 </tr>
 <tr>
 <td><strong>Merge Requests</strong>
 </td>
 <td><a href="https://code.videolan.org/avinal/vlc-android-user/-/merge_requests">Merge Requests · Avinal Kumar / VLC for Android User Documentation</a>
 </td>
 </tr>
 </table>
 Since the Android port of VLC can be installed on Android
 Smartphones/Tablets, Android TVs, Amazon Fire Devices and Chromebooks
 too, a full documentation will cover these all devices. Although these
 are different form factors, the features provided on each of them is
 exactly the same and the same documentation can be used for all these
 devices. As of now only Smartphones/Tablets are covered. And later
 additional pages will be added to reference different features/User
 Interface. Regardless of this addition the current documentation can
 serve a major part for all these form factors. Completed/Remaining
 <table>
 <tr>
 <td><strong>Chapters</strong>
 </td>
 <td><strong>Sections</strong>
 </td>
 <td><strong>Status</strong>
 </td>
 </tr>
 <tr>
 <td><strong>Settings</strong>
 </td>
 <td>
 <ul>
 <li>General Settings
 <li>Interface
 <li>Video
 <li>Subtitles
 <li>Audio
 <li>Casting
 <li>Advanced
 </li>
 </ul>
 </td>
 <td><strong>ALL COMPLETED</strong>
 <p>
 <strong>FOR ALL FORM FACTORS</strong>
 </td>
 </tr>
 <tr>
    <td><strong>Video</strong>
    </td>
    <td>
        <ul>
            <li>Video Explorer
            <li>Video Player
            </li>
        </ul>
    </td>
    <td><strong>COMPLETED FOR SMARTPHONES/TABLETS</strong>
    </td>
 </tr>
 <tr>
    <td><strong>Audio</strong>
    </td>
    <td>
        <ul>
            <li>Audio Explorer
            <li>Audio Player
            </li>
        </ul>
    </td>
    <td><strong>COMPLETED FOR SMARTPHONES/TABLETS</strong>
    </td>
 </tr>
 <tr>
    <td><strong>Browse</strong>
    </td>
    <td>
        <ul>
            <li>Explorer
            <li>Local Network
            </li>
        </ul>
    </td>
    <td><strong>ONLY SMB IN LOCAL NETWORK COMPLETED</strong>
    </td>
 </tr>
 <tr>
    <td><strong>Installation</strong>
    </td>
    <td>
        <ul>
            <li>Smartphones/Tablets
            <li>Android TV
            <li>Fire Devices
            <li>Chromebooks
            </li>
        </ul>
    </td>
    <td><strong>COMPLETED FOR SMARTPHONES/TABLETS</strong>
    </td>
 </tr>
 <tr>
    <td><strong>User Interface</strong>
    </td>
    <td>
        <ul>
            <li>Smartphones/Tablets
            <li>Android TV
            <li>Fire Devices
            <li>Chromebooks
            </li>
        </ul>
    </td>
    <td><strong>COMPLETED FOR SMARTPHONES/TABLETS</strong>
    </td>
 </tr>
 <tr>
    <td><strong>Support</strong>
    </td>
    <td>
        <ul>
            <li>FAQs
            <li>Help
            </li>
        </ul>
    </td>
    <td><strong>IN PROGRESS</strong>
    </td>
 </tr>
 <tr>
    <td><strong>Guidelines</strong>
    </td>
    <td>
        <ul>
            <li>Contribution Guideline
            <li>Screenshot Guidelines
            <li>READMEs
            </li>
        </ul>
    </td>
    <td><strong>IN PROGRESS</strong>
    </td>
 </tr>
 </table>
 ## CHALLENGES
 The major obstacle was to get screenshots for all form factors. Since
 screenshots were the major part of this documentation it was necessary
 to provide proper screenshots in each chapter and with every step. For
 Android TV and Smartphone this was solved by using emulators instead of
 actual devices, but to emulate the actual scenario in an emulator was
 sometimes very difficult. There were many occasions where I was not able
 to gather the exact information about devices other than
 smartphones/tables. Since all form factors share a common pool of
 features, my mentor suggested that I focus on smartphones/tables. And to
 create issues mentioning missing parts so that it could be solved later.
 ## THANKS
 I want to thank my mentors for being supporting and helpful. I want to
 thank every person at VLC and Google who were involved in this whole
 process. Thanks and Congrats to my fellow writer Abhishek Pratap Singh.
 This was a great opportunity to learn and meet awesome people. I learned
 a lot about Sphinx, reStructured Text and many other things.
@@ -0,0 +1,89 @@
 ---
 title: HRT (Hudson River Trading) Systems Internship Interview Experience
 date: 2021-01-04 21:47
 tags: [HRT, hudsonrivertrading, interview, internship]
 category: blog
 ---
 # `HRT (Hudson River Trading)` Systems Internship Interview Experience
 I applied for **Systems Internship - Summer 2021** back in December 2020
 at [Hudson River Trading](https://www.hudsonrivertrading.com) , New
 York. The internship description was: -
 > We are looking for highly motivated students who are eager to learn
 > and excited about systems to join us for our summer internship
 > program. As a systems intern, you may have the opportunity to work on
 > projects in the following areas:
 >
 > - Programming/scripting (Golang, Python, C++, C)
 > - FOSS development
 > - HPC, Cluster computing
 > - System Administration
 > - Linux, Debian
 > - Linux-based computer security
 > - Data Storage
 > - Large deployment or config management
 The first step was a coding test on the Codility platform. If you have
 used any of the online coding platforms, this is similar. It was a
 `2.5 hrs (90 mins)` test consisting of 3 questions. They let you use
 `online references (documentation, man pages, etc.)` but **do not copy
 the code** as it will highly reduce your chances of qualifying for this
 first stage. You can choose between **C/C++**, **Python** and **Golang**
 (no Java 😪).
 Questions were clear and of medium level. But they were designed in such
 a way that you must know the basics before you could attempt. Also, they
 expected a clear and concise approach. Two of the most important points
 in their instructions were: -
 > - While correctness and performance are the most important factors
 >     for evaluation, we will take test duration into account as well.
 > - Please understand that this test is meant to be challenging. A
 >     perfect score is not necessary to move on to future interview
 >     rounds, so do the best you can!
 So, you must be near perfect in your approach as well as on time. I did
 them kind of quickly. They will show you a summary of your submission
 but not the results. It will take almost 2 weeks to get back to you for
 further steps.
 Next, I received a mail invitation for a telephonic interview. **This
 interview will last about 45 minutes and will be technical but will not
 require coding. Interview topics may include your background,
 programming languages, and Unix/Linux concepts**. Once you receive this
 mail you can then decide a time slot for an interview.
 I was not sure what they will ask if this is not a coding interview. The
 interviewer was very polite, and he was explaining the questions too.
 Questions were not so tricky but practical and real-life. Since it was
 **not for SDE role**, the questions were mostly related to Linux/Unix,
 C++ (mainly pointers and memory), Python/Bash scripting, automation,
 knowledge of tools (IDEs, Editors, System Administration Tools) and
 previous experiences. The interview would often explain why he is asking
 this question, this was very nice. Then some common interview questions,
 why do you want to work for this role? What makes you fit for this role?
 etc.
 One thing that I want to point out is that the interviewer was
 repeatedly checking my resume, and for the most part he did not ask
 anything that was not on my resume. So, my tip is to create a nice
 resume with genuine work/tool experiences. And when you are applying for
 such a role, it would be helpful if you mention mathematics or other
 courses that you have taken. *Do not lie on your resume*. They will
 easily catch that.
 The other thing is to keep your words short and clear; I was not great
 at communication, but you can be. If the interviewer allows then use
 examples for the things you cannot explain. I used nice examples. At
 last, he gave me short feedback on how well I performed.
 At last, I want to point out things I should not have done. The first
 is, I did not ask much about the role, you must do this at least once.
 Second, I am talkative, I do not know if the interviewer was not faking
 his expressions (because he would often discuss in-depth), but not all
 interviewers will be the same. So, do not talk too much, nor too less.
 At last work on your communication skill, mostly how you to present
 things and how to answer technical as well as behavioral questions. I
 was not fluent, but my way of presentation might have saved me.
@@ -0,0 +1,834 @@
 ---
 title: Google Summer of Code 2021
 date: 2021-08-19 23:07
 tags: [gsoc, FOSSology]
 category: development
 description: This is the final report of my Google Summer of Code 2021 at The FOSSology Project. 
 ---
 # Google Summer of Code 2021
 <style>
 .rd {color:red;font-weight:bold}
 .gr{color:green;font-weight:bold}
 .or{color:orange;font-weight:medium}
 ul{margin-bottom:0}
 </style>
 ## The CMake Build system
 FOSSology is quite an old and mature project. The project has been using
 bare metal **Makefiles**. As the project is growing with new agents and
 modernization it was required to have a modern build system.
 The FOSSology is a suite of well-integrated and synchronized
 sub-projects (called agents) written in C, C++, and PHP. Most of the
 major agents are in C, C++ and that made CMake an obvious choice for a
 new build system for FOSSology. CMake is a versatile set of build, test,
 and packaging tools and is the most popular choice of C/C++ developers.
 CMake can be extended to create a build system for other languages too
 via custom scripts.
 ## GitHub Actions CI/CD
 <img src="/images/ci.png"
 class="float-md-right rounded border border-info ml-3 float-md-right rounded border border-info ml-3"
 width="350" alt="A CI Meme" />
 Since the FOSSology project moved on Github, it has used only the free
 Travis CI service for OSS projects. At the time of writing Travis CI has
 reduced its free tier CI services. GitHub Actions provides faster
 builds. Since GitHub Actions is a fully managed service by GitHub, we
 don't need to know how to scale and operate the infrastructure to run
 it.
 It is straightforward to use with GitHub because when we fork a
 repository, the actions automatically get forked. This allows you to
 test and build projects very efficiently and even run them closer to the
 developer. Also, you have readily available access to the GitHub API,
 making it more popular among developers.
 ## Improvements over previous build system and CI
 The new build system and CI brings a lot of improvements and features.
 The list below describes them.
 - CMake enforces out-of-source builds. This was already possible with
 the previous build system but not a strict requirement. This feature
 keeps the source code clean and makes cleaning the build artifacts
 easy. (Just remove the build folder :)
 - One of the major improvements over the previous build system is faster
  build times. CMake generates parallel build-enabled configurations for
  all generators. In our tests, the new build system is at least twice
  as fast as the previous one. With further improvement in
  configuration, we will be able to further cut the build times.
 - Previously FOSSology can only be built using *Unix Makefiles*. With
  CMake, we can now use many other popular generators such as *Ninja*.
 - Now it is also very flexible to choose different compilers. This will
  help support more platforms and architecture in the future. As of now,
  we are experimenting with Clang compilers.
 - FOSSology is quite an old project and a lot of agent testing code was
  written in the last decade. Initially, none of them were compatible
  with the new build system, but we were able to hack most of the test
  code using better-improved methods. Test times have also improved.
 - Migrating from Travis CI to GitHub Actions was another big move and
  for the most part, it removes the dependency on a third-party CI
  service. Along with that GitHub Actions provides better build times,
  tons of new features, and better integration with other GitHub
  services.
 ## Deliverables
 - Final Pull Request [#2075](https://github.com/fossology/fossology/pull/2075)
 - Pull Request Branch [avinal/feat/buildsystem](https://github.com/avinal/fossology/tree/avinal/feat/buildsystem)
 - Working Branch (individual commits)
  - [avinal/feat/cmake-buildsystem](https://github.com/avinal/fossology/tree/avinal/feat/cmake-buildsystem)
  - [avinal/feat/testing](https://github.com/avinal/fossology/tree/avinal/feat/testing)
 - Project Issue [#1913](https://github.com/fossology/fossology/issues/1913)
 - Project Discussion [#1931](https://github.com/fossology/fossology/discussions/1931)
 - Weekly Reports
  - [Personal Blog](https://gsoc.avinal.space)
  - [FOSSology Official Blog](https://fossology.github.io/gsoc/docs/2021/buildsystem/)
 ### CMake Build System Tasks
 <table>
 <colgroup>
 <col style="width: 7%" />
 <col style="width: 23%" />
 <col style="width: 15%" />
 <col style="width: 15%" />
 <col style="width: 30%" />
 <col style="width: 23%" />
 <col style="width: 38%" />
 </colgroup>
 <thead>
 <tr class="header">
 <th>#</th>
 <th>Agents</th>
 <th>Build</th>
 <th>Install</th>
 <th>Testing</th>
 <th>Packaging</th>
 <th>Remarks</th>
 </tr>
 </thead>
 <tbody>
 <tr class="odd">
 <td>1</td>
 <td>adj2nest</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="even">
 <td>2</td>
 <td>buckets</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 <td><blockquote>
 <p><span class="gr">YES</span></p>
 </blockquote></td>
 <td></td>
 </tr>
 <tr class="odd">
 <td>3</td>
 <td>cli</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="rd">Functional</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="even">
 <td>4</td>
 <td>copyright</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 <li><span class="gr">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="odd">
 <td>5</td>
 <td>debug</td>
 <td></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="even">
 <td>6</td>
 <td>decider</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 <li><span class="gr">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="odd">
 <td>7</td>
 <td>deciderjob</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="even">
 <td>8</td>
 <td>delagent</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="rd">Functional</span></li>
 <li><span class="rd">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="odd">
 <td>9</td>
 <td>demomod</td>
 <td><span class="or">YES</span></td>
 <td><span class="or">YES</span></td>
 <td><ul>
 <li><span class="or">Functional</span></li>
 <li><span class="or">Unit</span></li>
 </ul></td>
 <td><span class="or">NO</span></td>
 <td><em>(Not Used)</em></td>
 </tr>
 <tr class="even">
 <td>10</td>
 <td>example_wc_agent</td>
 <td><span class="or">YES</span></td>
 <td><span class="or">YES</span></td>
 <td><ul>
 <li><span class="or">Functional</span></li>
 <li><span class="or">Unit</span></li>
 </ul></td>
 <td><blockquote>
 <p><span class="or">NO</span></p>
 </blockquote></td>
 <td><em>(Not Used)</em></td>
 </tr>
 <tr class="odd">
 <td>11</td>
 <td>clib</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 <li><span class="gr">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="even">
 <td>12</td>
 <td>cpplib</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="odd">
 <td>13</td>
 <td>phplib</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 <li><span class="gr">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td>1 functional test needs fix</td>
 </tr>
 <tr class="even">
 <td>14</td>
 <td>maintagent</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="odd">
 <td>15</td>
 <td>mimetype</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 <li><span class="gr">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="even">
 <td>16</td>
 <td>monk</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 <li><span class="gr">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="odd">
 <td>17</td>
 <td>ninka</td>
 <td><span class="or">YES</span></td>
 <td><span class="or">YES</span></td>
 <td><ul>
 <li><span class="or">Functional</span></li>
 <li><span class="or">Unit</span></li>
 </ul></td>
 <td><span class="or">NO</span></td>
 <td><em>(Deprecated)</em></td>
 </tr>
 <tr class="even">
 <td>18</td>
 <td>nomos</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 <li><span class="gr">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="odd">
 <td>19</td>
 <td>ojo</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 <li><span class="gr">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td>1 functional test needs fix</td>
 </tr>
 <tr class="even">
 <td>20</td>
 <td>pkgagent</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 <li><span class="gr">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="odd">
 <td>21</td>
 <td>readmeoss</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="even">
 <td>22</td>
 <td>regexscan</td>
 <td><span class="or">YES</span></td>
 <td><span class="or">YES</span></td>
 <td></td>
 <td><blockquote>
 <p><span class="or">NO</span></p>
 </blockquote></td>
 <td><em>(Deprecated)</em></td>
 </tr>
 <tr class="odd">
 <td>23</td>
 <td>reportImport</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="even">
 <td>24</td>
 <td>reuser</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="odd">
 <td>25</td>
 <td>reso</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="even">
 <td>26</td>
 <td>scheduler</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="rd">Functional</span></li>
 <li><span class="rd">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td>Tests needs fix</td>
 </tr>
 <tr class="odd">
 <td>27</td>
 <td>softwareHeritage</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="even">
 <td>28</td>
 <td>spasht</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="odd">
 <td>29</td>
 <td>spdx2</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 <li><span class="gr">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td>1 Test failing in CI</td>
 </tr>
 <tr class="even">
 <td>30</td>
 <td>unifiedreport</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="odd">
 <td>31</td>
 <td>ununpack</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 <li><span class="rd">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td>Unit tests needs fix</td>
 </tr>
 <tr class="even">
 <td>32</td>
 <td>wget_agent</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="gr">Functional</span></li>
 <li><span class="gr">Unit</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 <tr class="odd">
 <td>32</td>
 <td>www</td>
 <td><span class="gr">YES</span></td>
 <td><span class="gr">YES</span></td>
 <td><ul>
 <li><span class="rd">UI</span></li>
 </ul></td>
 <td><span class="gr">YES</span></td>
 <td></td>
 </tr>
 </tbody>
 </table>
 ### GitHub Actions CI Tasks
 | #  | CI Tasks                                | Status                                                   |
 |-----|-----------------------------------------|----------------------------------------------------------|
 | 1   | <span class="gr">build</span>           | Added Ubuntu 20.04 GCC 8, 9 and Clang, GCC 7 not working |
 | 2   | <span class="gr">c/cpp unit test</span> | Added, delagent, scheduler and ununpack not working      |
 | 3   | <span class="gr">phpunit tests</span>   | Added, delagent and scheduler functional not working     |
 | 4   | <span class="rd">cahching</span>        | Not implemented                                          |
 | 5   | <span class="rd">source install</span>  | Not implemented                                          |
 (<span class="gr">GREEN</span>: COMPLETED, <span class="rd">RED</span>:
 INCOMPLETE, <span class="or">ORANGE</span>: NOT NEEDED/DEPRECATED)
 ## How does it work and how to use it?
 <div class="embed-responsive embed-responsive-16by9">
    <iframe class="embed-responsive-item" src="/images/second-build.webm" allowfullscreen></iframe>
 </div>
 The new build system retains the modular and hierarchical structure of
 the previous build system. On the other hand, the new build system
 provides several new flags to control the build. The new build system
 forces out-of-source build instead of the previous in-source builds.
 This keeps the source clutter-free and reduces the chance of
 accidentally deleting source files. *Testing still needs some in-source
 artifacts, this will be solved once all the tests are fixed according to
 the new build system.*
 Each agent is a complete CMake sub-project with its independent
 configuration for building, installing, and testing. That means a single
 agent can be built and installed separately and even removed from the
 default build without breaking other builds. The directory structure is
 as below.
 ```bash
 .
 ├── build                           # temporary directory for build artifacts
 ├── cmake                           # CMake modules for FOSSology
 │   ├── FoPackaging.cmake           # CMake Packaging configurations
 │   ├── FoUtilities.cmake           # Custom CMake utilities 
 │   ├── FoVersionFile.cmake         # VERSION version.php CMake template file   
 │   ├── SetDefaults.cmake           # CMake defaults for this project   
 │   ├── TestInstall.make.in         # Template makefile for install during tests
 │   └── VERSION.in                  # VERSION file template
 ├── src                             
 │   ├── agent-1                     # Agent sub-project
 │   │   ├── agent                   # Agent's source code directory
 │   │   │   ├── agent-source-code
 │   │   │   └── CMakeLists.txt
 │   │   ├── agent_tests             # Agent's test directory    
 │   │   │   ├── Unit
 │   │   │   ├── Functional
 │   │   │   └── CMakeLists.txt
 │   │   ├── ui                      # Agent's UI source code
 │   │   │   ├── templates
 │   │   │   └── agent-ui-code
 │   │   └── CMakeLists.txt          # Agent's top-level CMake configuration
 :   :
 │   ├── other agents
 :   :
 │   └── CMakeLists.txt              # Source intermediate CMake configuration
 :
 ├── other directories and files
 :
 └── CMakeLists.txt                  # FOSSology Top-level CMake configuration 
 ```
 The `cmake` directory contains customized CMake modules and templates
 for FOSSology. This directory is required for all the operations. The
 general workflow of the new build system as well as how to use it is
 described below.
 1. Since the new build system is still in review. You must fork
    FOSSology and pull the
    [#2075](https://github.com/fossology/fossology/pull/2075) pull
    request branch. Once you are in FOSSology root, run these commands.
    ```bash
    git fetch https://github.com/avinal/fossology avinal/feat/buildsystem:buildsystem
    git checkout buildsystem
    ```
 2. The first step towards building is to create a temporary directory
    for storing intermediate files and build artifacts. By convention we
    use a directory named `build`, but you can use any name. (**NOTE:
    For testing do not use other names**)
    ```bash
    mkdir build
    cd build
    ```
 3. In the next steps, we will configure the CMake project and generate
    the required configurations. You can use several flags to control
    the build. Given below are the flags available for this project.
    <table style="width:99%;">
    <colgroup>
    <col style="width: 34%" />
    <col style="width: 43%" />
    <col style="width: 20%" />
    </colgroup>
    <thead>
    <tr class="header">
    <th>CMake Flags</th>
    <th>Description</th>
    <th>Default</th>
    </tr>
    </thead>
    <tbody>
    <tr class="odd">
    <td><strong>-DCMAKE_INSTALL_PREFIX=&lt;path&gt;</strong></td>
    <td>Sets the install prefix.</td>
    <td><code>/usr/local</code></td>
    </tr>
    <tr class="even">
    <td><strong>-DAGENTS="agent1;agent2..."</strong></td>
    <td>Only configure these agents.</td>
    <td>ALL AGENTS</td>
    </tr>
    <tr class="odd">
    <td><strong>-DOFFLINE=&lt;ON/OFF&gt;</strong></td>
    <td>Controls vendor generation, ON=NO</td>
    <td><strong>OFF</strong></td>
    </tr>
    <tr class="even">
    <td><p><strong>-DCMAKE_BUILD_TYPE=&lt;type&gt;</strong></p>
    <blockquote>
    <ul>
    <li>Controls build type aka level optimisation</li>
    </ul>
    </blockquote></td>
    <td><ul>
    <li><code>Debug</code></li>
    <li><code>Release</code></li>
    <li><code>RelWithDebInfo</code></li>
    <li><code>MinSizeRel</code></li>
    </ul></td>
    <td><code>Debug</code></td>
    </tr>
    <tr class="odd">
    <td><strong>-DTESTING=&lt;ON/OFF&gt;</strong></td>
    <td>Controls testing config generation</td>
    <td><blockquote>
    <p><strong>OFF</strong></p>
    </blockquote></td>
    </tr>
    <tr class="even">
    <td><strong>-DMONOPACK=&lt;ON/OFF&gt;</strong></td>
    <td>Package adj2nest and ununpack seperately</td>
    <td><strong>OFF</strong></td>
    </tr>
    <tr class="odd">
    <td><strong>-GNinja</strong></td>
    <td>Use Ninja instead of Unix Makefiles</td>
    <td><em>Unix MakeFiles</em></td>
    </tr>
    </tbody>
    </table>
    There are lots of inbuilt CMake command-line options you can see
    them in the official
    [documentation](https://cmake.org/cmake/help/v3.10/manual/cmake.1.html).
    Once you have chosen your flags we can now configure the project
    using the following commands.
    ```bash
    # From build folder
    cd <name-of-build-directory>
    cmake <flags> ..
    ```
 4. The next step is to build the project. You can use parallel jobs to
    build faster. For more options you can type `cmake --help` or
    `make --help` or `ninja --help`.
    ```bash
    # Common build command for all generators, 
    # Default number of parallel builds depends on generator used
    cmake --build . --parallel <no-of-processes>
    # For Unix Makefiles, no parallel build by default
    make -j <no-of-processes>
    # For Ninja, 8+ parallel build by default (depends on system)
    ninja -j <no-of-processes>
    ```
 5. Installing is also as easy as building. You can choose to install
    only certain components even if you have built the whole project. If
    you directly invoke the install command without building the
    project, it will automatically build the project first.
    ```bash
    # For Unix Makefiles
    make install
    # For Ninja
    ninja install
    ```
 6. While testing has some issues, most of the testing is working fine.
    For now, you must build and run any test from the FOSSology root
    directory only. You can choose to configure a single agent if you
    want to test one agent only. See `ctest --help` for controlling test
    runs.
    ```bash
    # Common testing command
    ctest --parallel <no-of-processes>
    # For Unix Makefiles
    make test
    # For Ninja
    ninja test
    ```
 7. You can package FOSSology, the packaging currently lacks copyright
    and conf files. But for testing purposes, you can use the following
    commands. Similar to installing, if you run the package command
    without building the project, it will automatically build the
    project first. See `cpack --help` for more packaging options.
    ```bash
    # Common testing command
    cpack
    # For Unix Makefiles
    make package
    # For Ninja
    ninja package
    ```
 ## Known Issues and Drawbacks
 Although the transition from Makefiles to CMake and Travis CI to GitHub
 Actions is almost complete and working as expected. But it is not free
 of drawbacks and issues. This section outlines the known issues at the
 time of writing.
 ![A Bug Meme](https://imgs.xkcd.com/comics/conference_question.png)
 - Coverage builds may fail with linking errors.
 - Packaging prefix is the same as the install prefix. This requires the
  developer to set the install prefix manually before packaging to
  produce packages with the correct directory structure.
 - Testing and packaging must be used from the FOSSology root directory.
  Not doing so may or may not configure the project as intended.
 - Previously tests were written hardcoded for the Makefiles. But new
  build system requires all artifacts to be generated in a separate
  directory. This required me to add symbolic links wherever a generated
  script or file is expected. Tests can still leave some artifacts
  inside source folders.
 - There is no easy way to install a particular agent from the FOSSology
  root directory.
 - Packages don't contain copyright, readme, and license files. CMake
  doesn't provide a way to include these files. This is being tracked by
  issue
  [#21832](https://gitlab.kitware.com/cmake/cmake/-/issues/21832).
 - While packaging the symbolic links may or may not be dereferenced and
  hence results in copying the folder too in the target directory.
 - Running tests locally may require switching to `fossy` user.
 - While configured for testing, it may give permission errors.
 - Scheduler, Ununpack, and Delagent unit and functional tests are not
  working. I have added an issue
  [#2084](https://github.com/fossology/fossology/issues/2084) to track
  the progress on fixing these tests.
 - CMake doesn't generate uninstall targets. The closest thing to
  uninstall is [this snippet](https://gitlab.kitware.com/cmake/community/-/wikis/FAQ#can-i-do-make-uninstall-with-cmake).
  This will be later added to the FOSSology.
 ## Challenges Faced
 While this whole project was challenging, some aspects of it were
 unforeseen and more challenging. When I decided to go on with this
 project I just had enough CMake knowledge to write a configuration for a
 very small project. I had never used CMake on this big scale. On the
 other side, the FOSSology community is largely unknown to CMake so for
 all of us it was learned, practiced, and implement. With support from
 mentors, I was able to overcome this challenge with flying colors.
 The other challenge was to understand the old build system, how they are
 all connected and what is the flow. The complexity can be imagined by
 the fact that the most of code and configurations were written in the
 decade before the last decade and haven't changed much since then.
 The most challenging task was to make tests work with the new build
 system. Since tests were mostly hardcoded and the new build system
 refactored many of the files and directory, the tests were failing
 initially. The testing part took me the most time. All thanks to my
 mentor Gaurav, I was able to hack them to suit the
 new build system.
 ## Related Resources and Links
 - Fix FOSSology agent tests issue
  [#2084](https://github.com/fossology/fossology/issues/2084)
 - feat(CI): Migrate API docs generation and deployment to GitHub Actions
  pull request
  [#1917](https://github.com/fossology/fossology/pull/1917)
 - feat(CI): Migrate Static Checks and Analysis to GitHub Actions from
  Travis CI [#1919](https://github.com/fossology/fossology/pull/1919)
 ## Future Development Plans
 There is a lot to do with the new build system and CI and it will
 probably take a year or to reach a maturity point. I was able to meet
 most of the goals but some of them are remaining.
 - Fix the tests, probably renovate them from the ground up.
 - Find a hack for packaging problems.
 - Improve and optimize the build.
 - Modernise the source code, remove old, bloated code and replace them
  according to new standards.
 ## What did I learn from this project?
 This Google Summer of Code was the busiest time of my life for all good
 reasons. I learned a lot about license compliance and how it all works
 in the software industry. The next big thing is CMake. As I mentioned I
 was just a novice user of CMake. Now I am confident that given any other
 large project I will be able to migrate it/improve it. I got to learn
 PHP, of which I did not know a single word before GSoC. And finally, I
 learned about packing and testing. I had these courses but implementing
 them myself and fixing them was a wholesome experience.
 Other than that I improved on my communication and presentation skills.
 Collaborating with fellow participants was one of the great things that
 happened during GSoC.
 ## Acknowledgments
 Google Summer of Code is the best thing that has happened to me this
 year so far. Although there are numerous people to say thanks to, I want
 to mention key people who were my motivation and support during this
 period.
 First of all, I want to thank and appreciate my mentors [Gaurav
 Mishra](https://github.com/GMishx), [Michael C.
 Jaeger](https://github.com/mcjaeger), [Anupam
 Ghosh](https://github.com/ag4ums), and [Shaheem Azmal M
 MD](https://github.com/shaheemazmalmmd). Without the help and support
 from them, all this would not have been possible. They are very polite,
 knowledgeable, and helpful.
 Finally, I want to thank, my family and friends. I got to meet many
 awesome developers as my fellow participants from around the world, I
 wish we will do more collaboration in the future.
@@ -0,0 +1,118 @@
 ---
 title: I am loving it! RedHat
 date: 2022-02-25 20:47
 category: development
 tags: [kubernetes, redhat, docker, golang, tekton, openshift, intern]
 description: I made it to the Red Hat as a DevTools intern. This post is about onboarding and how I prepared myself for working on the actual project.
 ---
 # My internship at Red Hat
 I have been contributing to open source for the last 3 years and Red Hat
 was one of the companies that I was very fond of. I must say all my
 contributions and consistency paid off, and I made it to the Red Hat as
 a DevTools intern. This post is about onboarding and how I prepared
 myself for working on the actual project.
 On the first day of my internship, I met two amazing teammates
 [Saytam](https://github.com/) and [Utkarsh](https://github.com/). We
 were also introduced to a Senior Software Engineer [Piyush
 Garg](https://github.com) who later mentored us. The initial few
 meetings were more on the introduction and what to learn topics. Before
 I jump into more details let me explain first what does a **DevTools
 Developer/Engineer** do?
 ## What does a DevTools Developer/Engineer do?
 From [MDN Web
 Docs](https://developer.mozilla.org/en-US/docs/Glossary/Developer_Tools)
 **Developer tools (or "development tools" or short "DevTools") are
 programs that allow a developer to create, test, and debug software.**
 At RedHat, a lot of open source developer tools of industry standards
 are developed. There are many, OpenShift, Tekton, CodeReady containers,
 and many more.
 ## Learning on the Go
 There was a lot of learning and still a lot to learn. In a meeting with
 my manager Pradeepto Bhattacharya, I was told that I will be working on
 TektonCD or OpenShift Pipelines, and both of them require a sound
 knowledge of Golang, CI/CD, Containers, Docker, and Kubernetes. I was
 familiar with CI/CD, containers, and Docker but never used Golang and
 Kubernetes. We were provided plenty of good resources and my teammates
 also helped with many awesome resources. I am listing all the resources
 with their category.
 ### Go Programming Language
 One of Golang's biggest advantages is that it offers the clarity and
 ease of use that other languages lack. Golang's advantages make it easy
 for new programmers to quickly understand the language and for seasoned
 veterans to easily read each other's code.
 - [Official Go Documentation](https://go.dev/doc/) - *Start from here*
 - [Go by Example](https://gobyexample.com/) - *bite-size examples for
  most of the golang features*
 - [Golang tutorial series -
  GOLANGBOT.COM](https://golangbot.com/learn-golang-series/) - *in-depth
  tutorial of golang*
 - [Effective Go](https://go.dev/doc/effective_go) - *writing good golang
  programs*
 - [The Go Playground](https://go.dev/play/) - *official online golang
  ide*
 - [The Go Programming Language - Book](https://www.gopl.io/) *for
  learning advanced level golang*
 - [Golang Tutorial for Beginners | Full Go Course - TechWorld with
  Nana](https://youtu.be/yyUHQIec83I) *if you prefer video tutorials, I
  don't :)*
 ### Docker
 Docker takes away repetitive, mundane configuration tasks and is used
 throughout the development lifecycle for fast, easy, and portable
 application development - desktop and cloud. Docker's comprehensive
 end-to-end platform includes UIs, CLIs, APIs, and security that are
 engineered to work together across the entire application delivery
 lifecycle.
 ![The Docker Architecture](/images/docker-architecture.png)
 - [Docker and Containers -
  Katacoda](https://www.katacoda.com/courses/docker) *interactive
  lessons on docker and containers*
 - [Docker for beginners](https://docker-curriculum.com/)
 - [Docker Tutorial for Beginners | TechWorld with
  Nana](https://youtu.be/3c-iBn73dDE) *video tutorial*
 ### Kubernetes
 ![Kubernetes tech](/images/kubernetes-architecture.png)
 **Kubernetes** is the Greek word for a ship's captain. We get the words
 Cybernetic and Gubernatorial from it. The Kubernetes project focuses on
 building a robust platform for running thousands of containers in
 production.
 - [Learn Kubernetes -
  Katacoda](https://www.katacoda.com/courses/kubernetes) *interactive
  lessons with kubernetes*
 - [kube by example](https://kubebyexample.com/) *learn by doing*
 - [Kubernetes Tutorial for Beginners](https://youtu.be/X48VuDVv0do)
  *video tutorial*
 ## *Not so Minimal* Tekton Server
 In late January, we were asked to implement our learnings and deep dive
 into Kubernetes and TektonCD through an assignment project. Soon we
 realized that whatever we were learning so far was not even close to
 what we were going to implement. We were given a document containing the
 requirements of the applications we were supposed to create along with
 all the documentation and architectural diagrams.
 The application was called **Minimal Tekton Server**. It is a set of
 three different applications, i.e a server, a CLI, and a dashboard. In
 short, this application is supposed to *listen to custom resources being
 created and then transfer the request to Tekton API to create the
 corresponding resource on the OpenShift/Kubernetes cluster.*
 So are you interested in how it went? Please follow up with my [next
 blog](https://avinal.space/posts/development/lovely-dangerous-things-redhat.html).
@@ -0,0 +1,209 @@
 ---
 title: Developing Minimal Tekton Server
 date: 2022-02-27 20:47
 modified: 2022-03-07 22:47
 category: development
 tags: [tekton, go, kubernetes, openshift, redhat, intern, golang, openshift-pipelines]
 description: 'This blog is a descreptive account of the development of Minimal Tekton Server. This is highly technical in nature, so please make sure that you have sufficient knowledge about Golang, Docker, Kubernetes and TektonCD. You can refer to my [previous blog]("https://avinal.space/posts/development/i-am-loving-it-redhat.html") to know about these topics.'
 ---
 # Developing Minimal Tekton Server
 This blog is a descreptive account of the development of Minimal Tekton Server.
 This is highly technical in nature, so please make sure that you have sufficient
 knowledge about Golang, Docker, Kubernetes and TektonCD. You can refer to my
 [previous blog]("https://avinal.space/posts/development/i-am-loving-it-redhat.html")
 to know about these topics.
 As mentioned in my last blog, we were given to implement an application
 named **Minimal Tekton Server**. The problem statement reads:
 > We will be designing and implementing an application that will be
 > talking to Tekton APIs to create resources on a Kubernetes/OpenShift
 > Cluster. The application will expose some fields of the Tekton
 > Resources which the user will provide and then this application will
 > create Tekton resources by talking to Tekton APIs available on the
 > cluster to create the resources based on the user-provided fields.
 There are three parts in this project for the application and two more
 parts for the CI/CD using TektonCD and Kubernetes/OpenShift. I will go
 through each part descriptively and try to explain what we did.
 ## The Architecture of MKS
 The first task in the development of the Minimal Tekton Server was
 creating its architectural diagram. Our first diagram was trash compared
 to the final diagram. Yeah, we learned. I will be explaining our
 final(obviously) architectural diagram and try to make some sense out of
 band-aids and duct tapes.
 <img src="/images/mks-architecture.png"
 class="img-fluid my-3 img-fluid my-3" alt="The MKS Arhitecture" />
 Let me start with explaining **What are MKS Resources?**. I hope you
 know at least tidbits about Kubernetes and by the definition: *A
 resource is an endpoint in the Kubernetes API that stores a collection
 of API objects of a certain kind; for example, the built-in
 :code:\`pods\` resource contains a collection of Pod objects.* But
 developers soon realized that these in-built resources were not enough
 for the ever-growing applications of Kubernetes. Here [custom
 resource](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
 comes into the picture. *A custom resource is an extension of the
 Kubernetes API that is not necessarily available in a default Kubernetes
 installation.* To define a custom resource we use something called
 [Custom Resource
 Definition](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/).
 So MKS Resources are such custom resources that correspond to the
 TektonCD custom resources.
 <img src="/images/venus-flytrap.gif"
 class="float-md-right ml-3 float-md-right ml-3" width="250"
 alt="A venus flytrap engulphing an insect." />
 Let us now focus on the box containing `Controller` and `API server`.
 The controller can be said as a stimulus-response mechanism. Take the
 analogy of a Venus Flytrap plant. The trap is initially open. There are
 `trigger` hairs on the inside of the trap. Once an insect is detected,
 there is a change of state and the trap closes in a blick on the eye.
 The controller works the same way. It listens for the change in the
 state of the MKS resources and immediately transfers the request to the
 Tekton API to reflect the change in the corresponding Tekton resources.
 The changes can be creation, deletion, or updating. The API server
 ensures that there is a working connection between our controller and
 the Tekton API.
 MKS Server also exposes APIs to introduce a change of state in the MKS
 resources. In technical terms these are called `verbs`. There are five
 such verbs that we have exposed: `create`, `update`, `get`, `delete`,
 and `list`. They can be utilized by a REST client, or in our case **MKS
 CLI** to introduce desired change. The MKS command-line interface
 provides commands and subcommands to do the desired tasks.
 Whenever there is a change in the state, there is a logic running inside
 the controller to react on that and that also affects our database. We
 store four datapoints in our database: `created`, `deleted`,
 `completed`, and `failed`. They tell us about the current statistcs of
 our MKS resource using a single-page web app called **MKS Dashboard**
 (or UI).
 This was about the architecture of the Minimal Tekton Server. Let us
 jump into more technical stuff.
 ## How to implement a CRD controller?
 During this assignment, something that took the most time and effort was
 the implementation of a controller for our custom resources. This isn't
 very hard if you go by the rules and do the things according to the
 well-defined documents and blogs since this is a standard step in the
 implementation of any custom resource controller. But did we follow the
 rules? Hell no! But this time, let us go step-by-step.
 1. The first step is to define a `CustomResourceDefinition` for our custom
 resource. Let us define a CRD called `spacetime`. To do this you can write a
 YAML file like below.
 ```yaml
 # file: spacetime-crd.yaml
 apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
 # name must match the spec fields below, and be in the form: <plural>.<group>
 name: spacetimes.example.com
 spec:
 # group name to use for REST API: /apis/<group>/<version>
 group: example.com
 # list of versions supported by this CustomResourceDefinition
 versions:
  - name: v1alpha1
  # Each version can be enabled/disabled by Served flag.
  served: true
  # One and only one version must be marked as the storage version.
  storage: true
  schema:
    openAPIV3Schema:
    type: object
    properties:
      spec:
      type: object
      properties:
        message:
        type: string
 # either Namespaced or Cluster
 scope: Namespaced
 names:
  # plural name to be used in the URL: /apis/<group>/<version>/<plural>
  plural: spacetimes
  # singular name to be used as an alias on the CLI and for display
  singular: spacetime
  # kind is normally the CamelCased singular type. Your resource manifests use this.
  kind: SpaceTime
  # shortNames allow shorter string to match your resource on the CLI
  shortNames:
  - st
 ```
 You can learn more about the fields and options
 [here](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/).
 The CRD that we defined above corresponds to the `CustomResource` given
 below. Once you apply the above file you will be able to see the
 `spacetime` custom resource on your Kubernetes/OpenShift cluster.
 ```yaml
 # file: spacetime-cr.yaml
 apiVersion: spacetimes.example.com/v1alpha1
 kind: SpaceTime
 metadata:
  name: spacetime-cr
 spec:
  message: "Hello from space!"
 ```
 Apply them using the following commands:
 ```bash
 kubectl apply -f spacetime-crd.yaml
 kubectl apply -f spacetime-cr.yaml
 ```
 1. Once we have defined our custom resources, we need to define the
    types that will correspond to this custom resource definition. This
    can be done using `k8s.io/apimachinery/pkg/apis/meta/v1` package
    written in golang. Did I tell you that this is all in golang? Well,
    now you know. Create a package structure for a golang project and
    add the definition of the type as given below.
 ```bash
 mkdir -p pkg/api/spacetime/v1alpha1
 touch pkg/api/spacetime/v1alpha1/{spacetime_types,register,doc}.go pkg/api/spacetime/register.go
 ```
 Add the following content to the corresponding files.
 ```go
 // file: /pkg/api/spacetime/v1alpha1/spacetime_types.go
 package v1alpha1
 import (
  metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
 )
 type SpaceTime struct {
  metav1.TypeMeta   `json:",inline"`
  metav1.ObjectMeta `json:"metadata,omitempty"`
  Spec SpaceTimeSpec `json:"spec"`
 }
 type SpaceTimeSpec struct {
  Message string  `json:"message"`
 }
 type SpaceTimeList struct {
  metav1.TypeMeta     `json:",inline"`
  metav1.ListMeta     `json:"metadata"`
  Items []SpaceTime   `json:"items"`
 }
 ```
 ### To be Continued
@@ -0,0 +1,211 @@
 ---
 title: How I implemented WakaTime embeddable Coding Graph GHA?
 date: 2021-02-02 21:47
 tags: [wakatime, github-action, coding]
 category: development
 image: https://raw.githubusercontent.com/avinal/Profile-Readme-WakaTime/b281d074ee75f9626b39d10e2e518c6a297208a3/waka.png
 description: 'If you use WakaTime to track your coding activity. You can add that to 
 your README as a bar graph or embed it in your blog/portfolio. Just add this 
 action to any of your repositories and there you have it.'
 ---
 # How I implemented WakaTime embeddable Coding Graph GHA?
 If you use WakaTime to track your coding activity. You can add that to
 your README as a bar graph or embed it in your blog/portfolio. Just add this
 action to any of your repositories and there you have it.
 ## Implementation Details
 This GitHub Action is divided into three parts. I didn't want to use
 Docker but it seems it doesn't work well without it. Let dive a little
 into technical details. Three parts are as below.
 1. [main.py](https://github.com/avinal/Profile-Readme-WakaTime/blob/master/main.py)
    python script. This script contains many procedures.
    - [Getting JSON data file via WakaTime
    API](https://github.com/avinal/Profile-Readme-WakaTime/blob/master/main.py#L52)
    ```python
    def get_stats() -> list:
        ...
        return data_list
    ```
    This function parses the JSON file received and scraps out the useful
    data as a list of lists. Data scraped are language list, time spent on
    each language, percentage of the time, start date, and end date. For
    this action, I have limited the number of languages to 5 however it
    should be very easy to increase that number.
    - [Setting the
    Timeline](https://github.com/avinal/Profile-Readme-WakaTime/blob/master/main.py#L13)
    ```python
    def this_week(dates: list) -> str:
        ...
        return f"Coding Activity During: {week_start.strftime('%d %B, %Y')} to {week_end.strftime('%d %B, %Y')}"
    ```
    The start date and end date scraped in the last function are used here
    to set the timeline. Because date in JSON is provided in UTC as below
    :
    ```json
    date:   "YYYY-MM-DDTHH:MM:SSZ"
    ```
    I striped it to simple dates only. We can set them manually by taking
    the current time from the system. But that method is flawed. But this
    method ensures that JSON was received latest and the request was
    successful. Any anomaly will point to a failure in request.
    - [Creating a bar
    graph](https://github.com/avinal/Profile-Readme-WakaTime/blob/master/main.py#L21)
    ```python
    def make_graph(data: list):
        ...
        savefig(...)
    ```
    Lastly, it is time to generate the graph and save them as an image.
    This function uses the data scraped in the first step. Creating a bar
    graph using matplotlib is easy.
    Decorating was a bit difficult. I wanted this graph to merge with
    GitHub's look so I chose to color the bar as GitHub colors the
    languages. That data is stored as colors.json. Many of the languages have
    slightly different spelling in GitHub as compared to WakaTime. So some
    languages are shown in default color. That can be improved if we
    notice that language and change its color manually. Lastly, the graph
    is saved both as SVG and PNG. SVGs are better to put on a responsive
    page.
 2. [entrypoint.py](https://github.com/avinal/Profile-Readme-WakaTime/blob/master/entrypoint.sh)
    shell script. This shell script clones the repository copies the
    image and pushes changes to the master. There were several problems.
    First of all authentication. This was solved by using a remote
    repository address using GitHub Token. And it seems that GitHub
    doesn't allow to commit without a username and email. So I used
    **github-actions** bot email.
    ```bash
    remote_repo-"https://${GITHUB_ACTOR}:${INPUT_GITHUB_TOKEN}@github.com/${GITHUB_REPOSITORY}.git"
    git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
    git config user.name "GitHub Actions"
    ```
    `41898282` is the id assigned to the github-actions bot. Don't ask
    where I found them 🙂.
    Another problem was to separate repository name from combined
    *username/repository-name* provided by `${GITHUB_REPOSITORY}`. GitHub doesn't
    provides a direct way to get just the repo name. We used *Internal
    Field Separator*. It returns an array and works similar to `split()`
    command in Python and Java.
    ```bash
    # '/' is the seperator
    IFS-'/' read -ra reponame <<< "${GITHUB_REPOSITORY}"
    # returned {username, repository}
    repository-"${reponame[1]}"
    ```
    After that, all other commands are pretty straight. Commit the added
    files and push them.
 3. [Dockerfile](https://github.com/avinal/Profile-Readme-WakaTime/blob/master/Dockerfile)
    **IMPORTANT** It took a lot of time to reach this state 🥱. This is
    where all the magic happens. I am running <span
    class="title-ref">ubuntu:latest</span> inside the container. I first
    update the distribution. Then install the required python packages.
    Lastly, I invoke the python script and shell script.
    There was an almost impossible problem, I searched hundreds of posts
    that *how can I access the generated files inside Docker container*, but
    no luck. But at last, I found a workaround(obviously otherwise you
    wouldn't be reading this by now 🤣) each command is run in a separate
    virtual sub-container. As the command ends its output is also lost but
    not when you club multiple commands together. At least not until every
    command is finished. The generated files are available to the next
    clubbed process. I did that by combining the python script run and shell
    script run.
    ```dockerfile
    CMD python3 /main.py && /entrypoint.sh
    ```
    This part is the smallest yet took the most time and tries while
    developing this action.
 ## How to use this GitHub Actions?
 1. First get your WakaTime API Key. You can get it from your
    [WakaTime](<https://wakatime.com>) account settings.
 2. Save WakaTime API Key to Repository Secret. Find that by clicking
    the Settings tab. Keep the name of the secret as
    **WAKATIME_API_KEY**.
 3. Add the following line in your README.md of your repo.
    ```html
    <img src="https://github.com/<username>/<repository-name>/blob/<branch-name>/images/stat.svg" alt="Alternative Text"/>
    Example: <img src="https://github.com/avinal/avinal/blob/main/images/stat.svg" alt="Avinal WakaTime Activity"/>
    ```
    > You can use this method to embed in web pages too. **Do not use the
    > markdown method of inserting images. It does not work sometimes.**
 4. Click the **Action** tab and **choose to set up a workflow
    yourself**.
 5. Copy the following code into the opened file, you can search for
    **WakaTime Stat** in the marketplace tab for assistance.
    ```yaml
    name: WakaTime status update
    on:
      schedule:
        # Runs at 12 am  '0 0 * * *'  UTC
        - cron: "1 0 * * *"
    jobs:
      update-readme:
        name: Update the WakaTime Stat
        runs-on: ubuntu-latest
        steps:
          # Use avinal/Profile-Readme-WakaTime@<latest-release-tag> for latest stable release
          # Do not change the line below except the word master with tag number maybe
          # If you have forked this project you can use <username>/Profile-Readme-WakaTime@master instead
          - uses: avinal/Profile-Readme-WakaTime@master
            with:
              # WakaTime API key stored in secrets, do not directly paste it here
              WAKATIME_API_KEY: ${{ secrets.WAKATIME_API_KEY }}
              # Automatic github token
              GITHUB_TOKEN: ${{ github.token }}
              # Branch - newer GitHub repositories have "main" as default branch, change to main in that case, default is master
              BRANCH: "master"
              # Manual Commit messages - write your own messages here
              COMMIT_MSG: "Automated Coding Activity Update :alien:"
    ```
 6. Please wait till 12 AM UTC to run this workflow automatically. Or
    you can force run it by going to the Actions tab. Or you can add the
    following lines under `on:` to run with
    every push. Search for 12 AM UTC to find the equivalent time in your
    time zone.
    ```yaml
    on:
      push:
        branches: [ master ]
      schedule:
        - cron: '1 0 * * *'
    ```
 ## My Coding Activity
 ![Avinal's GitHub stats](https://raw.githubusercontent.com/avinal/avinal/main/images/stat.svg)
@@ -0,0 +1,91 @@
 ---
 title: Move WSL 2 Safely to another Drive
 date: 2020-12-31 19:07
 tags: [wsl, wsl2]
 category: development
 description: 'It is real pain when you have small SSD and Windows Subsystem for Linux
 (WSL) is growing exponentially in size. There is no easy way to move the
 WSL installation to another drive. Here in this blog I will discuss how
 to tackle this problem with bite size steps.'
 ---
 # Move WSL 2 Safely to another Drive
 It is real pain when you have small SSD and Windows Subsystem for Linux
 (WSL) is growing exponentially in size. There is no easy way to move the
 WSL installation to another drive. Here in this blog I will discuss how
 to tackle this problem with bite size steps.
 1. Open a PowerShell or Command Prompt with *Admin* access. For this you can
 use WinKey + X shortcut and select **Windows PowerShell(Admin)**.
 2. Check if the WSL 2 installation you are planning to move is is
 currently running/stopped.
  ```powershell
  PS C:\\Users\\Avinal> wsl -l -v
  PS C:\\Users\\Avinal>
    NAME      STATE           VERSION
  * Ubuntu    Running         2
    Kali      Stopped         2
  ```
 3. If its running then you must stop the particular WSL distribution.
 (*Ubuntu* used as example)
 ```powershell
 PS C:\\Users\\Avinal> wsl -t Ubuntu
 ```
 4. Export to some folder. (Here exporting *Ubuntu* as *ubuntu-ex.tar*
    to *Z:wsl2*)
 ```powershell
 PS C:\\Users\\Avinal> wsl --export Ubuntu "Z:\\export\\ubuntu-ex.tar"
 ```
 5. Unregister previous WSL installation
 ```powershell
 PS C:\\Users\\Avinal> wsl --unregister Ubuntu
 ```
 6. Create a new folder and import your WSL installation to that folder.
 ```powershell
 PS C:\\Users\\Avinal> New-Item -Path "Z:\\wsl2" -ItemType Directory
    Directory: Z:\\
 Mode                 LastWriteTime         Length Name
 ----                 -------------         ------ ----
 d-----        31-12-2020     21:03                wsl2
 PS C:\\Users\\Avinal> wsl --import Ubuntu "Z:\\wsl2" "Z:\\export\\ubuntu-ex.tar"
 ```
 7. Check after import is complete
 ```powershell
 PS C:\\Users\\Avinal> wsl -l -v
 PS C:\\Users\\Avinal>
  NAME      STATE           VERSION
 * Ubuntu    Running         2
  Kali      Stopped         2
 ```
 8. Mark one of your WSL distribution as *(default)*.
 ```powershell
 PS C:\\Users\\Avinal> wsl -s Ubuntu
 ```
 9. After exporting your default user will be set as
    <i style="color:red">root</i> , to change it to your desired
    username, run following command
 ```powershell
 PS C:\\Users\\Avinal> ubuntu config --default-user user_name
 ```
 10. Finally run `wsl` and you have successfully moved your WSL 2
    installation to another drive.
@@ -0,0 +1 @@
 # This page does not exists
@@ -0,0 +1 @@
 [{"title":"Developing Minimal Tekton Server","date":"2022-02-27 20:47","category":"development","description":"This blog is a descreptive account of the development of Minimal Tekton Server. This is highly technical in nature, so please make sure that you have sufficient knowledge about Golang, Docker, Kubernetes and TektonCD. You can refer to my [previous blog](\"https://avinal.space/posts/development/i-am-loving-it-redhat.html\") to know about these topics.","slug":"lovely-dangerous-things-redhat"},{"title":"I am loving it! RedHat","date":"2022-02-25 20:47","category":"development","description":"I made it to the Red Hat as a DevTools intern. This post is about onboarding and how I prepared myself for working on the actual project.","slug":"i-am-loving-it-redhat"},{"title":"Google Summer of Code 2021","date":"2021-08-19 23:07","category":"development","description":"This is the final report of my Google Summer of Code 2021 at The FOSSology Project. One of the major improvements over the previous build system is faster build times. CMake generates parallel build-enabled configurations for all generators.","slug":"final-evaluation"},{"title":"How I implemented WakaTime embeddable Coding Graph GHA?","date":"2021-02-02 21:47","category":"development","description":"If you use WakaTime to track your coding activity. You can add that to your README as a bar graph or embed it in your blog/portfolio. Just add this action to any of your repositories and there you have it.","slug":"wakatime"},{"title":"HRT (Hudson River Trading) Systems Internship Interview Experience","date":"2021-01-04 21:47","category":"blogs","slug":"hrt-interview-1","description":"uestions were clear and of medium level. But they were designed in such a way that you must know the basics before you could attempt. Also, they expected a clear and concise approach."},{"title":"Move WSL 2 Safely to another Drive","date":"2020-12-31 19:07","category":"development","description":"It is real pain when you have small SSD and Windows Subsystem for Linux (WSL) is growing exponentially in size. There is no easy way to move the WSL installation to another drive. Here in this blog I will discuss how to tackle this problem with bite size steps.","slug":"wsl2-move"},{"title":"Create the VLC User Documentation for one Mobile Port(Android)","date":"2020-12-01 23:47","category":"blogs","description":"The project was to Create the VLC User Documentation for Android Mobile Port which was previously hosted on VLC wiki pages. The major portion of this was to start everything from scratch including chapter separation, section organization.","slug":"gsod2020-report"},{"title":"प्रेम रतन धन पायो","date":"2019-09-21 15:47","category":"articles","slug":"for-sunshine","description":"प्रकृति की सुंदरता और कलाकारी हिमालय की कण-कण में झलकती है। प्रकृति ने प्रेम को भी हिमालय के जितना ही विशाल और अलौकिक बनाया है । ये एक अलग चर्चा का विषय है कि हिमालय पहले आया या प्रेम। मैं तो प्रेम के पक्ष में हूँ । वो हर अणु-परमाणु जिन्होंने इतने बड़ा पहाड़ खड़ा किया वो सब आपस में प्रेम से बंधे हुए हैं। ये पृथ्वी, सूर्य, चंद्रमा, आकाश-गंगा इत्यादि सब प्रेम से बंधे हुए हैं"},{"title":"The Big Red Ants","date":"2012-02-27 22:47","category":"articles","description":"As I observed them making and reparing their nests, I concluded that they are laborious and intellectual. They create their nests bybinding two or more leaves (maybe up to 500) together. They stich the leaves using a stinky white substance either excreted by themselves or from trees.","slug":"big-red-ants"}]
@@ -1,28 +0,0 @@
 *****************************
 Introduction to Prime Numbers
 *****************************
 :date: 2021-01-09 22:29
 :tags: prime, primenumbers
 :category: prime
 :slug: prime1
 :summary: A prime is a positive integer *p* having exactly two positive divisors, namely *1* and *p*. An integer *n* is composite if *n* > *1* and *n* is not prime. (The number 1 is considered neither prime nor composite.)
 .. epigraph::
    A prime is a positive integer *p* having exactly two positive divisors, namely *1* and *p*. An integer *n* is composite if *n* > *1* and *n* is not prime. (The number 1 is considered neither prime nor composite.)
 We can frame a brute force algorithm for checking primality of numbers using the above statement.
 .. code-block:: cpp
    bool is_prime(int number) {
        int factor = 0;
        for (int i = 0; i <= number; ++i) {
            if (number % i == 0) {
                factor++;
            }
        }
        return (factor == 2)? true : false;
    }
@@ -0,0 +1,32 @@
 {
    "type": "application",
    "source-directories": [
        "src"
    ],
    "elm-version": "0.19.1",
    "dependencies": {
        "direct": {
            "MaybeJustJames/yaml": "2.1.2",
            "elm/browser": "1.0.2",
            "elm/core": "1.0.5",
            "elm/html": "1.0.0",
            "elm/http": "2.0.0",
            "elm/json": "1.1.3",
            "elm/parser": "1.1.0",
            "elm/url": "1.0.0"
        },
        "indirect": {
            "elm/bytes": "1.0.8",
            "elm/file": "1.0.5",
            "elm/regex": "1.0.0",
            "elm/time": "1.0.0",
            "elm/virtual-dom": "1.0.3"
        }
    },
    "test-dependencies": {
        "direct": {},
        "indirect": {
            "rtfeldman/elm-hex": "1.0.0"
        }
    }
 }
@@ -1,10 +0,0 @@
 #! /bin/bash
 # install tools
 sudo apt-get install -y git make python3 python3-pip python3-setuptools python3-wheel
 # install dependencies
 sudo pip3 install -r requirements.txt
 # publish to github pages
 sudo make github
@@ -1,78 +0,0 @@
 #!/usr/bin/env python
 # -*- coding: utf-8 -*- #
 AUTHOR = 'Avinal'
 HIDE_AUTHORS = True
 SITENAME = 'Be My SpaceTime'
 SITESUBTITLE = '눈치'
 SITEURL = 'https://avinal.space'
 THEME = 'themes/alchemy'
 PATH = 'content'
 MAIL = 'blog@avinal.space'
 TIMEZONE = 'Asia/Kolkata'
 DEFAULT_LANG = 'en'
 # Feed generation is usually not desired when developing
 FEED_ALL_ATOM = None
 CATEGORY_FEED_ATOM = None
 TRANSLATION_FEED_ATOM = None
 AUTHOR_FEED_ATOM = None
 AUTHOR_FEED_RSS = None
 # URL Flexibility
 ARTICLE_URL = 'posts/{category}/{slug}.html'
 ARTICLE_SAVE_AS = ARTICLE_URL
 PAGE_URL = 'pages/{slug}.html'
 PAGE_SAVE_AS = PAGE_URL
 # static content setting
 STATIC_PATHS = ['extras', 'images']
 EXTRA_PATH_METADATA = {
    'extras/android-chrome-192x192.png': {'path': 'android-chrome-192x192.png'},
    'extras/android-chrome-512x512.png': {'path': 'android-chrome-512x512.png'},
    'extras/apple-touch-icon.png': {'path': 'apple-touch-icon.png'},
    'extras/browserconfig.xml': {'path': 'browserconfig.xml'},
    'extras/favicon-16x16.png': {'path': 'favicon-16x16.png'},
    'extras/favicon-32x32.png': {'path': 'favicon-32x32.png'},
    'extras/favicon.ico': {'path': 'favicon.ico'},
    'extras/site.webmanifest': {'path': 'site.webmanifest'},
    'extras/mstile-150x150.png': {'path': 'mstile-150x150.png'},
    'extras/mstile-70x70.png': {'path': 'mstile-70x70.png'},
    'extras/mstile-310x310.png': {'path': 'mstile-310x310.png'},
    'extras/mstile-144x144.png': {'path': 'mstile-144x144.png'},
    'extras/safari-pinned-tab.svg': {'path': 'safari-pinned-tab.svg'},
    'extras/CNAME': {'path': 'CNAME'},
 }
 RFG_FAVICONS = True
 LINKS = [
    ('gsoc', 'https://gsoc.avinal.space')
 ]
 # icons
 ICONS = [
    ('github', "https://github.com/avinal"),
    ('linkedin', 'https://www.linkedin.com/in/avinal/'),
    ('instagram', 'https://instagram.com/avinal.k'),
    ('calendar', 'https://meet.avinal.space')
 ]
 DIRECT_TEMPLATES = ('index', 'tags', 'categories', 'archives', 'sitemap')
 SITEMAP_SAVE_AS = 'sitemap.xml'
 DEFAULT_PAGINATION = 5
 PYGMENTS_STYLE = 'manni'
 # Comments config
 FORM_COMMENTS = True
 FORM_PROPERTIES = {
    'name' : 'entry.982725972',
    'email':'entry.1652853191',
    'link':'entry.1641222305',
    'comment':'entry.1062656232',
    'action':'https://docs.google.com/forms/u/0/d/e/1FAIpQLSfL9T8WBRm-Ac2uyu74lJXSYOqAuF6lLIUAulRArCsuiI1ZRQ/formResponse'
 }
@@ -0,0 +1,65 @@
 <!DOCTYPE html>
 <html>
 <head>
  <meta charset="utf-8" />
  <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
  <link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
  <link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">
  <link rel="manifest" href="/site.webmanifest">
  <link rel="mask-icon" href="/safari-pinned-tab.svg" color="#5bbad5">
  <meta name="msapplication-TileColor" content="#2d89ef">
  <meta name="theme-color" content="#ffffff">
  <title>Single Page Apps for GitHub Pages</title>
  <script type="text/javascript">
    // Single Page Apps for GitHub Pages
    // https://github.com/rafrex/spa-github-pages
    // Copyright (c) 2016 Rafael Pedicini, licensed under the MIT License
    // ----------------------------------------------------------------------
    // This script takes the current url and converts the path and query
    // string into just a query string, and then redirects the browser
    // to the new url with only a query string and hash fragment,
    // e.g. http://www.foo.tld/one/two?a=b&c=d#qwe, becomes
    // http://www.foo.tld/?p=/one/two&q=a=b~and~c=d#qwe
    // Note: this 404.html file must be at least 512 bytes for it to work
    // with Internet Explorer (it is currently > 512 bytes)
    // If you're creating a Project Pages site and NOT using a custom domain,
    // then set segmentCount to 1 (enterprise users may need to set it to > 1).
    // This way the code will only replace the route part of the path, and not
    // the real directory in which the app resides, for example:
    // https://username.github.io/repo-name/one/two?a=b&c=d#qwe becomes
    // https://username.github.io/repo-name/?p=/one/two&q=a=b~and~c=d#qwe
    // Otherwise, leave segmentCount as 0.
    var segmentCount = 0;
    var l = window.location;
    l.replace(
      l.protocol +
      "//" +
      l.hostname +
      (l.port ? ":" + l.port : "") +
      l.pathname
        .split("/")
        .slice(0, 1 + segmentCount)
        .join("/") +
      "/?p=/" +
      l.pathname
        .slice(1)
        .split("/")
        .slice(segmentCount)
        .join("/")
        .replace(/&/g, "~and~") +
      (l.search ? "&q=" + l.search.slice(1).replace(/&/g, "~and~") : "") +
      l.hash
    );
  </script>
 </head>
 <body></body>
 </html>
@@ -3,7 +3,7 @@
    <msapplication>
        <tile>
            <square150x150logo src="/mstile-150x150.png"/>
-            <TileColor>#00aba9</TileColor>
+            <TileColor>#2d89ef</TileColor>
        </tile>
    </msapplication>
 </browserconfig>
@@ -0,0 +1,295 @@
 <?xml version="1.0" standalone="no"?>
 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
 <svg xmlns="http://www.w3.org/2000/svg">
 <defs >
 <font id="ShareTechMono" horiz-adv-x="544" ><font-face
    font-family="Share Tech Mono"
    units-per-em="1000"
    panose-1="2 11 5 9 5 0 0 2 0 4"
    ascent="885"
    descent="-242"
    alphabetic="0" />
 <glyph unicode=" " glyph-name="space" horiz-adv-x="540" />
 <glyph unicode="!" glyph-name="exclam" horiz-adv-x="540" d="M312 700V208H227V700H312ZM320 100V0H220V100H320Z" />
 <glyph unicode="&quot;" glyph-name="quotedbl" horiz-adv-x="540" d="M145 610V700H240V610L220 453H165L145 610ZM300 610V700H395V610L375 453H320L300 610Z" />
 <glyph unicode="#" glyph-name="numbersign" horiz-adv-x="540" d="M310 0V180H230V0H150V180H80V255H150V455H80V530H150V700H230V530H310V700H390V530H460V455H390V255H460V180H390V0H310ZM230 255H310V455H230V255Z" />
 <glyph unicode="$" glyph-name="dollar" horiz-adv-x="540" d="M122 0V76H264Q301 76 324 98T347 151V235Q347 265 332 283T285 302H265Q191 302 148 345T105 472V500Q105 638 227 664V780H312V670H418V594H275Q238 594 215 572T192 519V453Q192 422 212 402T264
 381H284Q355 381 394 340T434 216V170Q434 101 403 60T312 5V-110H227V0H122Z" />
 <glyph unicode="%" glyph-name="percent" horiz-adv-x="540" d="M289 469T257 437T167 404H159Q101 404 69 436T37 532V572Q37 635 69 667T159 700H167Q225 700 257 668T289 572V532Q289 469 257 437ZM219 608T206 624T167 640H159Q133 640 120 624T107 583V521Q107
 496 120 480T159 464H167Q193 464 206 480T219 521V583Q219 608 206 624ZM527 416V354L12 281V343L527 416ZM499 65T467 33T377 0H369Q311 0 279 32T247 128V168Q247 231 279 263T369 296H377Q435 296 467 264T499 168V128Q499 65 467 33ZM429 204T416 220T377
 236H369Q343 236 330 220T317 179V117Q317 92 330 76T369 60H377Q403 60 416 76T429 117V179Q429 204 416 220Z" />
 <glyph unicode="&amp;" glyph-name="ampersand" horiz-adv-x="540" d="M163 0T123 37T83 158V284Q83 371 148 407Q93 446 93 523V544Q93 625 136 662T265 700H371V625H253Q215 625 198 608T180 553V513Q180 480 201 460T253 440H496V365H417V0H253Q163 0 123 37ZM210
 365T190 346T170 293V148Q170 110 188 93T244 75H336V365H243Q210 365 190 346Z" />
 <glyph unicode="&apos;" glyph-name="quotesingle" horiz-adv-x="540" d="M222 610V700H317V610L297 453H242L222 610Z" />
 <glyph unicode="(" glyph-name="parenleft" horiz-adv-x="540" d="M170 621T199 693T282 820H370Q322 762 299 723T266 634T255 507V193Q255 115 265 66T299 -22T370 -120H282Q229 -65 200 7T170 195V505Q170 621 199 693Z" />
 <glyph unicode=")" glyph-name="parenright" horiz-adv-x="540" d="M370 79T341 7T258 -120H170Q218 -62 241 -23T274 66T285 193V507Q285 585 275 634T241 722T170 820H258Q311 765 340 693T370 505V195Q370 79 341 7Z" />
 <glyph unicode="*" glyph-name="asterisk" horiz-adv-x="540" d="M357 340L269 482L178 340L108 393L215 515L70 547L97 627L238 570L225 722H315L302 570L445 625L470 546L323 515L429 392L357 340Z" />
 <glyph unicode="+" glyph-name="plus" horiz-adv-x="540" d="M230 118V275H79V350H230V508H310V350H460V275H310V118H230Z" />
 <glyph unicode="," glyph-name="comma" horiz-adv-x="540" d="M240 0V100H340V0L278 -140H200L240 0Z" />
 <glyph unicode="-" glyph-name="hyphen" horiz-adv-x="540" d="M432 350V275H107V350H432Z" />
 <glyph unicode="." glyph-name="period" horiz-adv-x="540" d="M320 100V0H220V100H320Z" />
 <glyph unicode="/" glyph-name="slash" horiz-adv-x="540" d="M406 810H490L134 -110H50L406 810Z" />
 <glyph unicode="0" glyph-name="zero" horiz-adv-x="540" d="M448 87T403 44T280 0H260Q183 0 138 43T92 170V530Q92 614 137 657T260 700H280Q358 700 403 657T448 530V170Q448 87 403 44ZM363 580T340 602T280 625H260Q224 625 201 603T177 549V278L363 549Q363
 580 340 602ZM177 120T200 98T260 75H280Q316 75 339 97T363 151V421L177 151Q177 120 200 98Z" />
 <glyph unicode="1" glyph-name="one" horiz-adv-x="540" d="M243 75V621L102 569V650L233 700H328V75H437V0H112V75H243Z" />
 <glyph unicode="2" glyph-name="two" horiz-adv-x="540" d="M265 316Q297 362 308 381T324 421T328 479V549Q328 580 305 602T245 624H125V700H235Q322 700 368 658T415 530V488Q415 438 408 407T388 352T345 285L197 76H435V0H105V88L265 316Z" />
 <glyph unicode="3" glyph-name="three" horiz-adv-x="540" d="M419 75T379 38T249 0H121V75H258Q296 75 314 92T332 148V251Q332 284 312 303T259 323H152V398H249Q280 398 301 418T322 471V553Q322 591 305 608T249 625H121V700H237Q322 700 365 663T409 544V481Q409
 404 354 365Q419 329 419 242V158Q419 75 379 38Z" />
 <glyph unicode="4" glyph-name="four" horiz-adv-x="540" d="M293 0V156H87V242L194 700H275L173 229H293V457H378V229H453V156H378V0H293Z" />
 <glyph unicode="5" glyph-name="five" horiz-adv-x="540" d="M420 75T380 38T250 0H119V75H259Q297 75 315 92T333 148V275Q333 308 313 327T260 347H129V700H405V625H214V422H255Q332 422 376 384T420 266V158Q420 75 380 38Z" />
 <glyph unicode="6" glyph-name="six" horiz-adv-x="540" d="M448 88T403 44T290 0H255Q187 0 142 44T97 170V530Q97 615 142 657T275 700H400V624H265Q228 624 205 602T182 549V440H280Q366 440 407 402T448 280V170Q448 88 403 44ZM182 119T203 97T260 75H285Q321
 75 342 97T363 151V299Q363 330 345 347T290 365H182V151Q182 119 203 97Z" />
 <glyph unicode="7" glyph-name="seven" horiz-adv-x="540" d="M346 625H104V700H429V603L253 0H164L346 625Z" />
 <glyph unicode="8" glyph-name="eight" horiz-adv-x="540" d="M454 75T414 38T284 0H256Q166 0 126 37T86 158V242Q86 329 151 365Q98 402 98 481V544Q98 624 140 662T260 700H280Q358 700 400 662T442 544V481Q442 402 389 365Q454 329 454 242V158Q454 75 414
 38ZM214 624T200 607T185 553V471Q185 439 203 420T250 398H284Q315 398 335 418T355 471V553Q355 591 339 608T284 625H248Q214 624 200 607ZM367 284T347 303T294 323H246Q213 323 193 304T173 251V148Q173 111 189 93T239 75H293Q331 75 349 92T367 148V251Q367
 284 347 303Z" />
 <glyph unicode="9" glyph-name="nine" horiz-adv-x="540" d="M96 612T141 656T254 700H289Q357 700 402 656T447 530V170Q447 85 402 43T269 0H154V76H279Q316 76 339 98T362 151V260H264Q178 260 137 298T96 420V530Q96 612 141 656ZM362 581T341 603T284 625H259Q223
 625 202 603T181 549V401Q181 370 199 353T254 335H362V549Q362 581 341 603Z" />
 <glyph unicode=":" glyph-name="colon" horiz-adv-x="540" d="M320 500V400H220V500H320ZM320 100V0H220V100H320Z" />
 <glyph unicode=";" glyph-name="semicolon" horiz-adv-x="540" d="M340 500V400H240V500H340ZM240 0V100H340V0L278 -140H200L240 0Z" />
 <glyph unicode="&lt;" glyph-name="less" horiz-adv-x="540" d="M460 564V472L150 336L460 199V105L80 280V385L460 564Z" />
 <glyph unicode="=" glyph-name="equal" horiz-adv-x="540" d="M460 450V375H80V450H460ZM460 250V175H80V250H460Z" />
 <glyph unicode="&gt;" glyph-name="greater" horiz-adv-x="540" d="M396 336L80 472V564L460 385V280L80 105V199L396 336Z" />
 <glyph unicode="?" glyph-name="question" horiz-adv-x="540" d="M409 476T405 456T387 415T338 358L285 304V208H200V329L258 390Q290 424 303 441T320 471T324 509V559Q324 590 306 607T251 624H126V700H241Q409 700 409 550V518Q409 476 405 456ZM293 100V0H193V100H293Z"
 />
 <glyph unicode="@" glyph-name="at" horiz-adv-x="540" d="M95 0T62 32T29 140V550Q29 629 66 664T189 700H354Q438 700 474 666T511 550V223Q511 163 487 139T411 115Q378 115 357 130T332 175Q317 159 299 152T251 144Q200 144 177 169T154 259V403Q154 457
 169 486T216 527T308 539H380V211Q380 190 386 180T410 170Q429 170 435 179T441 216V560Q441 598 423 617T364 637H179Q136 637 118 618T99 560V130Q99 63 166 63H351V0H166Q95 0 62 32ZM286 202T299 217T312 254V482H297Q254 482 238 468T222 409V253Q222 229
 229 216T260 202Q286 202 299 217Z" />
 <glyph unicode="A" glyph-name="A" horiz-adv-x="540" d="M173 177L134 0H45L214 700H329L495 0H406L368 177H173ZM352 252L270 634L189 252H352Z" />
 <glyph unicode="B" glyph-name="B" horiz-adv-x="540" d="M455 72T416 36T285 0H85V700H273Q362 700 403 664T445 544V487Q445 410 390 371Q455 335 455 248V158Q455 72 416 36ZM358 591T341 608T285 625H172V404H285Q316 404 337 424T358 477V553Q358 591 341
 608ZM368 290T348 309T295 329H172V75H294Q332 75 350 92T368 148V257Q368 290 348 309Z" />
 <glyph unicode="C" glyph-name="C" horiz-adv-x="540" d="M202 0T156 42T109 170V530Q109 615 155 657T289 700H431V624H279Q242 624 219 602T196 549V151Q196 120 219 98T279 76H431V0H289Q202 0 156 42Z" />
 <glyph unicode="D" glyph-name="D" horiz-adv-x="540" d="M458 72T419 36T288 0H82V700H276Q366 700 412 664T458 544V158Q458 72 419 36ZM371 586T351 605T298 625H169V75H297Q335 75 353 92T371 148V553Q371 586 351 605Z" />
 <glyph unicode="E" glyph-name="E" horiz-adv-x="540" d="M437 700V627H190V398H412V325H190V73H437V0H103V700H437Z" />
 <glyph unicode="F" glyph-name="F" horiz-adv-x="540" d="M415 388V315H193V0H106V700H440V627H193V388H415Z" />
 <glyph unicode="G" glyph-name="G" horiz-adv-x="540" d="M187 0T141 42T94 170V530Q94 615 140 657T274 700H415V624H264Q227 624 204 602T181 549V151Q181 120 204 98T264 76H362V293H275V368H445V0H274Q187 0 141 42Z" />
 <glyph unicode="H" glyph-name="H" horiz-adv-x="540" d="M167 322V0H80V700H167V396H373V700H460V0H373V322H167Z" />
 <glyph unicode="I" glyph-name="I" horiz-adv-x="540" d="M226 73V627H136V700H403V627H313V73H403V0H136V73H226Z" />
 <glyph unicode="J" glyph-name="J" horiz-adv-x="540" d="M410 85T364 43T230 0H125V76H240Q277 76 300 98T323 151V625H162V700H410V170Q410 85 364 43Z" />
 <glyph unicode="K" glyph-name="K" horiz-adv-x="540" d="M168 258V0H81V700H168V398L358 700H453L260 391L465 0H365L206 315L168 258Z" />
 <glyph unicode="L" glyph-name="L" horiz-adv-x="540" d="M202 700V76H425V0H115V700H202Z" />
 <glyph unicode="M" glyph-name="M" horiz-adv-x="540" d="M310 235H227L129 628V0H53V700H192L272 342L353 700H488V0H410V628L310 235Z" />
 <glyph unicode="N" glyph-name="N" horiz-adv-x="540" d="M160 0H79V700H221L379 74V700H460V0H317L160 626V0Z" />
 <glyph unicode="O" glyph-name="O" horiz-adv-x="540" d="M470 85T424 43T290 0H250Q163 0 117 42T70 170V530Q70 615 116 657T250 700H290Q377 700 423 658T470 530V170Q470 85 424 43ZM383 580T360 602T300 624H240Q203 624 180 602T157 549V151Q157 120 180
 98T240 76H300Q337 76 360 98T383 151V549Q383 580 360 602Z" />
 <glyph unicode="P" glyph-name="P" horiz-adv-x="540" d="M451 349T408 311T281 272H177V0H90V700H279Q364 700 407 663T451 544V430Q451 349 408 311ZM364 591T347 608T291 625H177V347H291Q329 347 346 364T364 420V553Q364 591 347 608Z" />
 <glyph unicode="Q" glyph-name="Q" horiz-adv-x="540" d="M347 0T290 0H250Q163 0 117 42T70 170V530Q70 615 116 657T250 700H290Q377 700 423 658T470 530V170Q470 111 447 71L520 -2L463 -59L386 18Q347 0 290 0ZM383 580T360 602T300 624H240Q203 624 180
 602T157 549V151Q157 120 180 98T240 76H300Q337 76 360 98T383 151V549Q383 580 360 602Z" />
 <glyph unicode="R" glyph-name="R" horiz-adv-x="540" d="M157 290V0H70V700H258Q343 700 386 663T430 544V448Q430 335 340 307L479 0H384L255 290H157ZM343 591T326 608T270 625H157V365H270Q308 365 325 382T343 438V553Q343 591 326 608Z" />
 <glyph unicode="S" glyph-name="S" horiz-adv-x="540" d="M439 85T393 43T259 0H117V76H269Q306 76 329 98T352 151V255Q352 285 337 303T290 322H260Q186 322 143 365T100 492V530Q100 615 146 657T280 700H423V624H270Q233 624 210 602T187 549V473Q187 442
 207 422T259 401H289Q360 401 399 360T439 236V170Q439 85 393 43Z" />
 <glyph unicode="T" glyph-name="T" horiz-adv-x="540" d="M226 0V624H67V700H472V624H313V0H226Z" />
 <glyph unicode="U" glyph-name="U" horiz-adv-x="540" d="M462 85T416 43T282 0H257Q170 0 124 42T77 170V700H164V151Q164 120 187 98T247 76H292Q329 76 352 98T375 151V700H462V170Q462 85 416 43Z" />
 <glyph unicode="V" glyph-name="V" horiz-adv-x="540" d="M56 700H144L264 88L393 700H479L322 0H203L56 700Z" />
 <glyph unicode="W" glyph-name="W" horiz-adv-x="540" d="M268 284L205 0H85L51 700H125L155 75L238 405H300L385 75L416 700H485L451 0H325L268 284Z" />
 <glyph unicode="X" glyph-name="X" horiz-adv-x="540" d="M145 0H51L225 362L67 700H162L272 463L386 700H479L317 363L489 0H391L271 263L145 0Z" />
 <glyph unicode="Y" glyph-name="Y" horiz-adv-x="540" d="M223 0V325L44 700H140L272 409L404 700H495L313 325V0H223Z" />
 <glyph unicode="Z" glyph-name="Z" horiz-adv-x="540" d="M441 0H87V88L361 626H110V700H451V612L178 74H441V0Z" />
 <glyph unicode="[" glyph-name="bracketleft" horiz-adv-x="540" d="M375 820V745H245V-45H375V-120H165V820H375Z" />
 <glyph unicode="\" glyph-name="backslash" horiz-adv-x="540" d="M490 -110H406L50 810H134L490 -110Z" />
 <glyph unicode="]" glyph-name="bracketright" horiz-adv-x="540" d="M295 -45V745H165V820H375V-120H165V-45H295Z" />
 <glyph unicode="^" glyph-name="asciicircum" horiz-adv-x="540" d="M159 420H71L215 760H329L468 420H377L273 700L159 420Z" />
 <glyph unicode="_" glyph-name="underscore" horiz-adv-x="540" d="M522 -95V-170H18V-95H522Z" />
 <glyph unicode="`" glyph-name="grave" horiz-adv-x="540" d="M267 715L371 580H285L163 715H267Z" />
 <glyph unicode="a" glyph-name="a" horiz-adv-x="540" d="M404 0T389 8T362 30Q339 0 301 0H212Q136 0 102 30T67 135V155Q67 310 213 310H337V360Q337 391 318 408T262 425H107V500H252Q339 500 380 462T422 340V100Q422 85 433 78T472 70V0H417Q404 0 389 8ZM321
 75T329 89T337 125V235H212Q186 235 169 218T152 175V125Q152 99 164 87T202 75H291Q321 75 329 89Z" />
 <glyph unicode="b" glyph-name="b" horiz-adv-x="540" d="M453 76T412 38T283 0H87V700H172V480Q202 500 247 500H283Q371 500 412 463T453 340V160Q453 76 412 38ZM204 425T188 408T172 370V75H293Q330 75 349 92T368 140V360Q368 391 349 408T293 425H237Q204
 425 188 408Z" />
 <glyph unicode="c" glyph-name="c" horiz-adv-x="540" d="M202 0T161 37T120 160V340Q120 424 161 462T290 500H419V425H280Q243 425 224 408T205 360V140Q205 109 224 92T280 75H419V0H290Q202 0 161 37Z" />
 <glyph unicode="d" glyph-name="d" horiz-adv-x="540" d="M342 0T295 0H254Q166 0 125 37T84 160V340Q84 424 125 462T254 500H370V700H455V0H375V23Q342 0 295 0ZM338 75T354 92T370 130V425H244Q207 425 188 408T169 360V140Q169 109 188 92T244 75H305Q338 75 354 92Z" />
 <glyph unicode="e" glyph-name="e" horiz-adv-x="540" d="M176 0T135 37T94 160V340Q94 426 131 463T254 500H301Q372 500 408 461T445 345V215H179V140Q179 109 198 92T254 75H413V0H264Q176 0 135 37ZM362 365Q362 391 345 408T302 425H244Q208 425 194 409T179
 360V290H362V365Z" />
 <glyph unicode="f" glyph-name="f" horiz-adv-x="540" d="M288 625T279 617T269 595V500H430V425H269V75H390V0H99V75H184V425H99V500H184V590Q184 641 213 670T288 700H440V625H304Q288 625 279 617Z" />
 <glyph unicode="g" glyph-name="g" horiz-adv-x="540" d="M467 -103T427 -136T300 -170H92V-95H310Q346 -95 364 -81T382 -45V-13Q382 10 364 23T310 37H137V175Q104 193 88 227T72 315V340Q72 424 113 462T242 500H452V315Q452 240 411 198T302 155H222V112H300Q386
 112 426 79T467 -23V-35Q467 -103 427 -136ZM333 230T349 250T367 292V425H232Q195 425 176 408T157 360V295Q157 264 176 247T232 230H302Q333 230 349 250Z" />
 <glyph unicode="h" glyph-name="h" horiz-adv-x="540" d="M172 700V480Q202 500 247 500H293Q374 500 413 462T453 340V0H368V360Q368 390 351 407T303 425H237Q205 425 189 409T172 373V0H87V700H172Z" />
 <glyph unicode="i" glyph-name="i" horiz-adv-x="540" d="M317 700V610H222V700H317ZM80 425V500H312V75H460V0H227V425H80Z" />
 <glyph unicode="j" glyph-name="j" horiz-adv-x="540" d="M402 700V610H307V700H402ZM294 -95T303 -87T313 -65V425H166V500H398V-60Q398 -111 369 -140T294 -170H137V-95H278Q294 -95 303 -87Z" />
 <glyph unicode="k" glyph-name="k" horiz-adv-x="540" d="M181 214V0H96V700H181V322L338 500H445L271 303L459 0H354L207 244L181 214Z" />
 <glyph unicode="l" glyph-name="l" horiz-adv-x="540" d="M268 0T243 24T217 100V625H70V700H302V105Q302 89 310 82T337 75H470V0H302Q268 0 243 24Z" />
 <glyph unicode="m" glyph-name="m" horiz-adv-x="540" d="M118 500V477Q144 500 180 500H186Q256 500 285 460Q318 500 372 500H378Q439 500 468 469T497 359V0H417V360Q417 401 409 417T370 433H364Q334 433 323 413T310 367V0H230V360Q230 402 220 417T184 433H178Q148
 433 136 416T123 376V0H43V500H118Z" />
 <glyph unicode="n" glyph-name="n" horiz-adv-x="540" d="M167 500V476Q198 500 247 500H293Q374 500 413 462T453 340V0H368V360Q368 390 351 407T303 425H237Q204 425 188 408T172 370V0H87V500H167Z" />
 <glyph unicode="o" glyph-name="o" horiz-adv-x="540" d="M456 76T415 38T286 0H253Q166 0 125 38T83 160V340Q83 424 124 462T253 500H286Q373 500 414 462T456 340V160Q456 76 415 38ZM371 391T352 408T296 425H243Q206 425 187 408T168 360V140Q168 109 187
 92T243 75H296Q333 75 352 92T371 140V360Q371 391 352 408Z" />
 <glyph unicode="p" glyph-name="p" horiz-adv-x="540" d="M167 500V476Q198 500 247 500H283Q371 500 412 463T453 340V160Q453 76 412 38T283 0H172V-170H87V500H167ZM204 425T188 408T172 370V75H293Q330 75 349 92T368 140V360Q368 391 349 408T293 425H237Q204
 425 188 408Z" />
 <glyph unicode="q" glyph-name="q" horiz-adv-x="540" d="M339 0T295 0H254Q166 0 125 37T84 160V340Q84 424 125 462T254 500H455V-170H370V20Q339 0 295 0ZM338 75T354 92T370 130V425H244Q207 425 188 408T169 360V140Q169 109 188 92T244 75H305Q338 75 354 92Z" />
 <glyph unicode="r" glyph-name="r" horiz-adv-x="540" d="M173 75V425H100V500H253V473Q286 500 333 500H436V420H323Q291 420 275 400T258 358V75H367V0H100V75H173Z" />
 <glyph unicode="s" glyph-name="s" horiz-adv-x="540" d="M422 62T384 31T272 0H123V75H282Q309 75 323 86T337 120V173Q337 218 294 218H257Q187 218 153 248T118 345V374Q118 441 156 470T268 500H402V425H258Q233 425 218 414T203 380V344Q203 321 216 310T251
 299H285Q352 299 387 267T422 170V125Q422 62 384 31Z" />
 <glyph unicode="t" glyph-name="t" horiz-adv-x="540" d="M256 0T229 33T202 120V425H107V500H202V620H287V500H433V425H287V115Q287 93 298 84T332 75H433V0H307Q256 0 229 33Z" />
 <glyph unicode="u" glyph-name="u" horiz-adv-x="540" d="M334 0T287 0H253Q172 0 133 38T93 160V500H178V140Q178 110 195 93T243 75H297Q329 75 344 91T362 127V500H447V0H367V23Q334 0 287 0Z" />
 <glyph unicode="v" glyph-name="v" horiz-adv-x="540" d="M64 500H156L273 69L387 500H476L332 0H209L64 500Z" />
 <glyph unicode="w" glyph-name="w" horiz-adv-x="540" d="M272 251L218 0H125L35 500H120L177 103L243 410H308L368 103L425 500H505L416 0H320L272 251Z" />
 <glyph unicode="x" glyph-name="x" horiz-adv-x="540" d="M159 0H65L221 258L77 500H176L271 332L368 500H461L315 262L474 0H374L269 189L159 0Z" />
 <glyph unicode="y" glyph-name="y" horiz-adv-x="540" d="M204 -95T216 -86T234 -55L248 0H228L63 500H155L280 81L389 500H476L321 -54Q308 -105 289 -130T247 -162T186 -170H138V-95H180Q204 -95 216 -86Z" />
 <glyph unicode="z" glyph-name="z" horiz-adv-x="540" d="M424 0H106V80L340 426H126V500H434V411L202 74H424V0Z" />
 <glyph unicode="{" glyph-name="braceleft" horiz-adv-x="540" d="M187 405T202 417T218 469V698Q218 765 243 792T327 820H392V750H341Q317 750 307 743T296 713V469Q296 419 272 387T211 349Q247 345 271 313T296 231V-13Q296 -35 306 -42T341 -50H392V-120H327Q268
 -120 243 -93T218 2V231Q218 270 203 282T147 295V405Q187 405 202 417Z" />
 <glyph unicode="|" glyph-name="bar" horiz-adv-x="540" d="M310 810V-110H230V810H310Z" />
 <glyph unicode="}" glyph-name="braceright" horiz-adv-x="540" d="M352 295T337 283T321 231V2Q321 -65 296 -92T212 -120H147V-50H198Q222 -50 232 -43T243 -13V231Q243 281 267 313T328 349Q292 355 268 387T243 469V713Q243 735 233 742T198 750H147V820H212Q271
 820 296 793T321 698V469Q321 430 336 418T392 405V295Q352 295 337 283Z" />
 <glyph unicode="~" glyph-name="asciitilde" horiz-adv-x="540" d="M112 352T148 366T197 381H212Q225 381 279 361Q331 341 343 341H353Q360 341 394 356T440 377V297Q429 291 396 277T352 262H337Q331 262 284 279Q219 302 207 302H197Q188 302 151 287T100
 266V346Q112 352 148 366Z" />
 <glyph unicode="&#xa0;" glyph-name="uni00A0" horiz-adv-x="540" />
 <glyph unicode="&#xa1;" glyph-name="exclamdown" horiz-adv-x="540" d="M220 400V500H320V400H220ZM228 -200V292H313V-200H228Z" />
 <glyph unicode="&#xa2;" glyph-name="cent" horiz-adv-x="540" d="M188 6T154 43T120 159V339Q120 416 154 453T260 497V600H340V499H419V424H280Q243 424 224 407T205 359V139Q205 108 224 91T280 74H419V-1H340V-110H260V0Q188 6 154 43Z" />
 <glyph unicode="&#xa3;" glyph-name="sterling" horiz-adv-x="540" d="M162 530Q162 615 208 657T342 700H439V624H332Q295 624 272 602T249 549V413H377V340H249V73H447V0H92V73H162V340H92V413H162V530Z" />
 <glyph unicode="&#xa4;" glyph-name="currency" horiz-adv-x="540" d="M73 206T73 252V350Q73 398 85 429L14 501L71 558L139 490Q176 510 243 510H296Q361 510 400 489L469 558L526 501L453 428Q466 398 466 350V252Q466 207 454 175L526 103L469 46L402 113Q362
 92 296 92H243Q174 92 138 113L71 46L14 103L85 174Q73 206 73 252ZM381 401T362 418T306 435H233Q196 435 177 418T158 370V232Q158 201 177 184T233 167H306Q343 167 362 184T381 232V370Q381 401 362 418Z" />
 <glyph unicode="&#xa5;" glyph-name="yen" horiz-adv-x="540" d="M224 0V115H94V190H224V265H94V340H221L55 700H151L273 427L394 700H485L316 340H444V265H314V190H444V115H314V0H224Z" />
 <glyph unicode="&#xa6;" glyph-name="brokenbar" horiz-adv-x="540" d="M310 810V450H230V810H310ZM310 250V-110H230V250H310Z" />
 <glyph unicode="&#xa7;" glyph-name="section" horiz-adv-x="540" d="M113 391T125 419T157 462Q143 477 135 499T127 550V560Q127 633 165 666T277 700H401V625H267Q243 625 228 614T212 580V540Q212 517 225 506T260 495H289Q426 495 426 350V345Q426 277 382
 238Q396 228 404 204T412 150V140Q412 67 374 34T262 0H138V75H272Q296 75 311 86T327 120V160Q327 205 283 205H250Q113 205 113 350V355Q113 391 125 419ZM216 420T207 409T198 375V330Q198 307 211 294T251 280H306Q322 280 331 291T341 325V370Q341 394 330
 407T289 420H233Q216 420 207 409Z" />
 <glyph unicode="&#xa8;" glyph-name="dieresis" horiz-adv-x="540" d="M212 675V595H127V675H212ZM412 675V595H327V675H412Z" />
 <glyph unicode="&#xa9;" glyph-name="copyright" horiz-adv-x="540" d="M515 86T472 43T352 0H188Q111 0 68 43T25 170V530Q25 614 68 657T188 700H352Q429 700 472 657T515 530V170Q515 86 472 43ZM443 585T419 610T352 636H188Q145 636 121 611T97 552V147Q97
 114 121 89T188 63H352Q395 63 419 88T443 147V552Q443 585 419 610ZM231 157T203 180T175 251V449Q175 496 203 519T283 543H358V492H278Q257 492 245 480T232 450V250Q232 233 244 221T278 208H357V157H283Q231 157 203 180Z" />
 <glyph unicode="&#xaa;" glyph-name="ordfeminine" horiz-adv-x="540" d="M359 324T348 329T329 344Q312 324 286 324H234Q177 324 151 347T125 426V441Q125 557 235 557H309V595Q309 618 297 628T256 639H155V700H249Q314 700 345 672T377 580V399Q377 387 385
 382T414 377V324H369Q359 324 348 329ZM297 383T303 393T309 420V499H238Q219 499 206 487T193 454V422Q193 383 230 383H274Q297 383 303 393ZM398 75V0H147V75H398Z" />
 <glyph unicode="&#xab;" glyph-name="guillemotleft" horiz-adv-x="540" d="M201 506H267L204 299L267 92H201L112 299L201 506ZM361 506H427L364 299L427 92H361L272 299L361 506Z" />
 <glyph unicode="&#xac;" glyph-name="logicalnot" horiz-adv-x="540" d="M62 275V350H477V106H392V275H62Z" />
 <glyph unicode="&#xad;" glyph-name="uni00AD" horiz-adv-x="540" d="M432 350V275H107V350H432Z" />
 <glyph unicode="&#xae;" glyph-name="registered" horiz-adv-x="540" d="M515 86T472 43T352 0H188Q111 0 68 43T25 170V530Q25 614 68 657T188 700H352Q429 700 472 657T515 530V170Q515 86 472 43ZM443 585T419 610T352 636H188Q145 636 121 611T97 552V147Q97
 114 121 89T188 63H352Q395 63 419 88T443 147V552Q443 585 419 610ZM225 317V159H169V543H276Q380 543 380 457V404Q380 342 326 326L409 159H348L270 317H225ZM319 478T309 487T276 496H225V363H276Q299 363 309 372T319 403V457Q319 478 309 487Z" />
 <glyph unicode="&#xaf;" glyph-name="overscore" horiz-adv-x="540" d="M397 675V605H142V675H397Z" />
 <glyph unicode="&#xb0;" glyph-name="degree" horiz-adv-x="540" d="M411 458T375 428T284 397H256Q201 397 165 427T129 516V582Q129 640 164 670T256 701H284Q340 701 375 671T411 582V516Q411 458 375 428ZM342 607T326 623T284 639H256Q231 639 215 623T198
 585V513Q198 491 214 475T256 459H284Q309 459 325 475T342 513V585Q342 607 326 623Z" />
 <glyph unicode="&#xb1;" glyph-name="plusminus" horiz-adv-x="540" d="M230 143V275H80V350H230V508H310V350H460V275H310V143H230ZM460 75V0H80V75H460Z" />
 <glyph unicode="&#xb2;" glyph-name="twosuperior" horiz-adv-x="540" d="M262 431Q295 476 303 495T312 551V587Q312 636 251 636H165V700H244Q318 700 351 672T385 581V558Q385 518 380 496T366 458T331 408L228 269H390V205H150V278L262 431Z" />
 <glyph unicode="&#xb3;" glyph-name="threesuperior" horiz-adv-x="540" d="M381 261T352 233T254 205H158V269H251Q279 269 293 280T307 319V374Q307 398 292 412T252 426H181V490H244Q268 490 283 503T299 542V584Q299 613 286 624T244 636H158V700H245Q374
 700 374 583V548Q374 520 362 498T330 461Q381 434 381 369V324Q381 261 352 233Z" />
 <glyph unicode="&#xb4;" glyph-name="acute" horiz-adv-x="540" d="M376 715L254 580H168L272 715H376Z" />
 <glyph unicode="&#xb5;" glyph-name="mu" horiz-adv-x="540" d="M188 500V140Q188 110 205 93T253 75H287Q320 75 336 92T352 130V500H437V0H357V23Q324 0 277 0H263Q218 0 188 10V-170H103V500H188Z" />
 <glyph unicode="&#xb6;" glyph-name="paragraph" horiz-adv-x="540" d="M229 374Q141 374 102 408T62 527V540Q62 625 102 662T229 700H318V630H218Q182 630 163 611T143 560V507Q143 476 162 459T218 442H318V0H235V374H229ZM453 700V0H373V700H453Z" />
 <glyph unicode="&#xb7;" glyph-name="middot" horiz-adv-x="540" d="M320 360V260H220V360H320Z" />
 <glyph unicode="&#xb8;" glyph-name="cedilla" horiz-adv-x="540" d="M250 -136Q283 -136 283 -105Q283 -88 275 -82T248 -76H199V50H269V-21Q315 -21 335 -38T356 -105Q356 -163 331 -181T268 -200H183V-136H250Z" />
 <glyph unicode="&#xb9;" glyph-name="onesuperior" horiz-adv-x="540" d="M245 269V633L146 594V662L237 700H319V269H393V205H154V269H245Z" />
 <glyph unicode="&#xba;" glyph-name="ordmasculine" horiz-adv-x="540" d="M400 383T369 355T273 326H263Q197 326 166 354T135 446V582Q135 645 166 673T263 702H273Q338 702 369 674T400 582V446Q400 383 369 355ZM332 616T318 628T276 641H259Q232 641 218
 629T203 593V435Q203 412 217 400T259 387H276Q304 387 318 399T332 435V593Q332 616 318 628ZM408 75V0H132V75H408Z" />
 <glyph unicode="&#xbb;" glyph-name="guillemotright" horiz-adv-x="540" d="M112 506H178L267 299L178 92H112L175 299L112 506ZM272 506H338L427 299L338 92H272L335 299L272 506Z" />
 <glyph unicode="&#xbc;" glyph-name="onequarter" horiz-adv-x="540" d="M375 810H449L193 -110H119L375 810ZM77 269V630L11 591V662L79 700H151V269H185V205H29V269H77ZM428 0V117H327V191L381 495H450L388 181H424L451 324H498V181H528V117H498V0H428Z" />
 <glyph unicode="&#xbd;" glyph-name="onehalf" horiz-adv-x="540" d="M365 810H453L197 -110H123L365 810ZM77 269V630L11 591V662L79 700H151V269H185V205H29V269H77ZM443 246Q452 266 454 283T457 346V392Q457 431 416 431H380V495H409Q458 495 484 485T520
 451T530 386V353Q530 286 527 262T512 216L441 64H535V0H365V73L443 246Z" />
 <glyph unicode="&#xbe;" glyph-name="threequarters" horiz-adv-x="540" d="M369 810H443L187 -110H113L369 810ZM198 260T171 233T77 205H21V267H74Q101 267 114 278T128 317V376Q128 400 114 414T75 428H44V488H67Q91 488 105 501T120 540V586Q120 615 108 626T67
 638H21V700H68Q131 700 161 672T191 583V548Q191 520 179 498T147 461Q198 434 198 369V324Q198 260 171 233ZM428 0V117H327V191L381 495H450L388 181H424L451 324H498V181H528V117H498V0H428Z" />
 <glyph unicode="&#xbf;" glyph-name="questiondown" horiz-adv-x="540" d="M247 400V500H347V400H247ZM131 24T135 44T153 85T202 142L255 196V292H340V171L282 110Q250 77 237 60T220 29T216 -9V-59Q216 -90 234 -107T289 -124H414V-200H299Q131 -200 131 -50V-18Q131
 24 135 44Z" />
 <glyph unicode="&#xc0;" glyph-name="Agrave" horiz-adv-x="540" d="M253 841L357 726H274L142 841H253ZM173 177L134 0H45L214 700H329L495 0H406L368 177H173ZM352 252L270 634L189 252H352Z" />
 <glyph unicode="&#xc1;" glyph-name="Aacute" horiz-adv-x="540" d="M396 841L264 726H181L285 841H396ZM173 177L134 0H45L214 700H329L495 0H406L368 177H173ZM352 252L270 634L181 252H352Z" />
 <glyph unicode="&#xc2;" glyph-name="Acircumflex" horiz-adv-x="540" d="M209 730H113L223 845H315L426 730H329L269 794L209 730ZM173 177L134 0H45L214 700H329L495 0H406L368 177H173ZM352 252L270 634L189 252H352Z" />
 <glyph unicode="&#xc3;" glyph-name="Atilde" horiz-adv-x="540" d="M144 812T172 826T212 840H227Q235 840 251 834T284 820Q326 800 338 800H348Q356 800 381 815T415 836V764Q407 759 383 745T347 731H332Q327 731 287 748Q235 771 222 771H212Q203 771 174
 756T135 735V807Q144 812 172 826ZM173 177L134 0H45L214 700H329L495 0H406L368 177H173ZM352 252L270 634L189 252H352Z" />
 <glyph unicode="&#xc4;" glyph-name="Adieresis" horiz-adv-x="540" d="M217 815V735H132V815H217ZM406 815L417 735H332V815H406ZM173 177L134 0H45L214 700H329L495 0H406L368 177H173ZM352 252L270 634L189 252H352Z" />
 <glyph unicode="&#xc5;" glyph-name="Aring" horiz-adv-x="540" d="M361 696T335 675L495 0H406L368 177H173L134 0H45L208 674Q179 697 179 741V770Q179 812 203 833T268 855H274Q314 855 338 834T363 770V741Q361 696 335 675ZM306 809T274 809H268Q250 809
 242 799T234 771V740Q234 723 242 713T268 702H274Q306 702 306 740V771Q306 809 274 809ZM352 252L270 634L189 252H352Z" />
 <glyph unicode="&#xc6;" glyph-name="AE" horiz-adv-x="540" d="M141 177L99 0H15L191 700H498V627H325L348 398H493V325H356L381 73H518V0H307L292 177H141ZM247 627L159 252H283L247 627Z" />
 <glyph unicode="&#xc7;" glyph-name="Ccedilla" horiz-adv-x="540" d="M303 -136Q336 -136 336 -105Q336 -88 328 -82T301 -76H252V2Q182 10 146 52T109 170V530Q109 615 155 657T289 700H431V624H279Q242 624 219 602T196 549V151Q196 120 219 98T279 76H431V0H322V-21Q368
 -21 388 -38T409 -105Q409 -163 384 -181T321 -200H236V-136H303Z" />
 <glyph unicode="&#xc8;" glyph-name="Egrave" horiz-adv-x="540" d="M248 841L352 726H269L137 841H248ZM437 700V627H190V398H412V325H190V73H437V0H103V700H437Z" />
 <glyph unicode="&#xc9;" glyph-name="Eacute" horiz-adv-x="540" d="M397 841L265 726H182L286 841H397ZM437 700V627H190V398H412V325H190V73H437V0H103V700H437Z" />
 <glyph unicode="&#xca;" glyph-name="Ecircumflex" horiz-adv-x="540" d="M210 730H114L224 845H316L427 730H330L270 794L210 730ZM437 700V627H190V398H412V325H190V73H437V0H103V700H437Z" />
 <glyph unicode="&#xcb;" glyph-name="Edieresis" horiz-adv-x="540" d="M212 815V735H127V815H212ZM412 815V735H327V815H412ZM437 700V627H190V398H412V325H190V73H437V0H103V700H437Z" />
 <glyph unicode="&#xcc;" glyph-name="Igrave" horiz-adv-x="540" d="M247 841L351 726H268L136 841H247ZM229 73V627H139V700H406V627H316V73H406V0H139V73H229Z" />
 <glyph unicode="&#xcd;" glyph-name="Iacute" horiz-adv-x="540" d="M392 841L260 726H177L281 841H392ZM226 73V627H136V700H403V627H313V73H403V0H136V73H226Z" />
 <glyph unicode="&#xce;" glyph-name="Icircumflex" horiz-adv-x="540" d="M210 730H114L224 845H316L427 730H330L270 794L210 730ZM227 73V627H137V700H404V627H314V73H404V0H137V73H227Z" />
 <glyph unicode="&#xcf;" glyph-name="Idieresis" horiz-adv-x="540" d="M213 815V735H128V815H213ZM413 815V735H328V815H413ZM226 73V627H136V700H403V627H313V73H403V0H136V73H226Z" />
 <glyph unicode="&#xd0;" glyph-name="Eth" horiz-adv-x="540" d="M467 72T428 36T297 0H91V325H34V400H91V700H285Q375 700 421 664T467 544V158Q467 72 428 36ZM380 586T360 605T307 625H178V400H294V325H178V75H306Q344 75 362 92T380 148V553Q380 586 360 605Z" />
 <glyph unicode="&#xd1;" glyph-name="Ntilde" horiz-adv-x="540" d="M142 812T170 826T210 840H225Q233 840 249 834T282 820Q324 800 336 800H346Q354 800 379 815T413 836V764Q405 759 381 745T345 731H330Q325 731 285 748Q233 771 220 771H210Q201 771 172
 756T133 735V807Q142 812 170 826ZM160 0H79V700H221L379 74V700H460V0H317L160 626V0Z" />
 <glyph unicode="&#xd2;" glyph-name="Ograve" horiz-adv-x="540" d="M247 841L351 726H268L136 841H247ZM470 85T424 43T290 0H250Q163 0 117 42T70 170V530Q70 615 116 657T250 700H290Q377 700 423 658T470 530V170Q470 85 424 43ZM383 580T360 602T300 624H240Q203
 624 180 602T157 549V151Q157 120 180 98T240 76H300Q337 76 360 98T383 151V549Q383 580 360 602Z" />
 <glyph unicode="&#xd3;" glyph-name="Oacute" horiz-adv-x="540" d="M399 841L267 726H184L288 841H399ZM470 85T424 43T290 0H250Q163 0 117 42T70 170V530Q70 615 116 657T250 700H290Q377 700 423 658T470 530V170Q470 85 424 43ZM383 580T360 602T300 624H240Q203
 624 180 602T157 549V151Q157 120 180 98T240 76H300Q337 76 360 98T383 151V549Q383 580 360 602Z" />
 <glyph unicode="&#xd4;" glyph-name="Ocircumflex" horiz-adv-x="540" d="M209 730H113L223 845H315L426 730H329L269 794L209 730ZM470 85T424 43T290 0H250Q163 0 117 42T70 170V530Q70 615 116 657T250 700H290Q377 700 423 658T470 530V170Q470 85 424 43ZM383
 580T360 602T300 624H240Q203 624 180 602T157 549V151Q157 120 180 98T240 76H300Q337 76 360 98T383 151V549Q383 580 360 602Z" />
 <glyph unicode="&#xd5;" glyph-name="Otilde" horiz-adv-x="540" d="M141 812T169 826T209 840H224Q232 840 248 834T281 820Q323 800 335 800H345Q352 800 377 815T412 836V764Q404 759 380 745T344 731H329Q324 731 284 748Q232 771 219 771H209Q200 771 171
 756T132 735V807Q141 812 169 826ZM470 85T424 43T290 0H250Q163 0 117 42T70 170V530Q70 615 116 657T250 700H290Q377 700 423 658T470 530V170Q470 85 424 43ZM383 580T360 602T300 624H240Q203 624 180 602T157 549V151Q157 120 180 98T240 76H300Q337 76 360
 98T383 151V549Q383 580 360 602Z" />
 <glyph unicode="&#xd6;" glyph-name="Odieresis" horiz-adv-x="540" d="M216 815V735H131V815H216ZM416 815V735H331V815H416ZM470 85T424 43T290 0H250Q163 0 117 42T70 170V530Q70 615 116 657T250 700H290Q377 700 423 658T470 530V170Q470 85 424 43ZM383
 580T360 602T300 624H240Q203 624 180 602T157 549V151Q157 120 180 98T240 76H300Q337 76 360 98T383 151V549Q383 580 360 602Z" />
 <glyph unicode="&#xd7;" glyph-name="multiply" horiz-adv-x="540" d="M97 193L213 310L97 427L153 483L270 367L387 483L443 427L327 310L443 193L387 137L270 253L153 137L97 193Z" />
 <glyph unicode="&#xd8;" glyph-name="Oslash" horiz-adv-x="540" d="M470 85T424 43T290 0H250Q223 0 211 2L185 -91H109L141 24Q70 66 70 170V530Q70 615 116 657T250 700H290Q303 700 327 698L353 791H429L397 676Q470 636 470 530V170Q470 85 424 43ZM157 131T166
 116L306 624H240Q203 624 180 602T157 549V151Q157 131 166 116ZM383 569T372 586L231 76H300Q337 76 360 98T383 151V549Q383 569 372 586Z" />
 <glyph unicode="&#xd9;" glyph-name="Ugrave" horiz-adv-x="540" d="M227 841L331 726H248L116 841H227ZM462 85T416 43T282 0H257Q170 0 124 42T77 170V700H164V151Q164 120 187 98T247 76H292Q329 76 352 98T375 151V700H462V170Q462 85 416 43Z" />
 <glyph unicode="&#xda;" glyph-name="Uacute" horiz-adv-x="540" d="M426 841L294 726H211L315 841H426ZM462 85T416 43T282 0H257Q170 0 124 42T77 170V700H164V151Q164 120 187 98T247 76H292Q329 76 352 98T375 151V700H462V170Q462 85 416 43Z" />
 <glyph unicode="&#xdb;" glyph-name="Ucircumflex" horiz-adv-x="540" d="M214 730H118L228 845H320L431 730H334L274 794L214 730ZM462 85T416 43T282 0H257Q170 0 124 42T77 170V700H164V151Q164 120 187 98T247 76H292Q329 76 352 98T375 151V700H462V170Q462
 85 416 43Z" />
 <glyph unicode="&#xdc;" glyph-name="Udieresis" horiz-adv-x="540" d="M214 815V735H129V815H214ZM414 815V735H329V815H414ZM462 85T416 43T282 0H257Q170 0 124 42T77 170V700H164V151Q164 120 187 98T247 76H292Q329 76 352 98T375 151V700H462V170Q462 85 416 43Z" />
 <glyph unicode="&#xdd;" glyph-name="Yacute" horiz-adv-x="540" d="M401 841L269 726H186L290 841H401ZM223 0V325L44 700H140L272 409L404 700H495L313 325V0H223Z" />
 <glyph unicode="&#xde;" glyph-name="Thorn" horiz-adv-x="540" d="M455 219T412 181T285 142H181V0H94V700H181V570H283Q368 570 411 533T455 414V300Q455 219 412 181ZM368 461T351 478T295 495H181V217H295Q333 217 350 234T368 290V423Q368 461 351 478Z" />
 <glyph unicode="&#xdf;" glyph-name="germandbls" horiz-adv-x="540" d="M78 630T121 665T228 700H267Q355 700 396 663T437 540V415H359Q329 415 317 404T304 370V355Q304 332 315 321T347 310Q402 310 434 278T466 190V125Q466 69 431 35T328 0H216V75H334Q381
 75 381 120V190Q381 212 371 223T335 235Q284 235 252 268T219 356V366Q219 430 253 456T352 486V560Q352 591 333 608T277 625H223Q190 625 177 608T163 570V0H78V560Q78 630 121 665Z" />
 <glyph unicode="&#xe0;" glyph-name="agrave" horiz-adv-x="540" d="M238 715L342 580H256L134 715H238ZM404 0T389 8T362 30Q339 0 301 0H212Q136 0 102 30T67 135V155Q67 310 213 310H337V360Q337 391 318 408T262 425H107V500H252Q339 500 380 462T422 340V100Q422
 85 433 78T472 70V0H417Q404 0 389 8ZM321 75T329 89T337 125V235H212Q186 235 169 218T152 175V125Q152 99 164 87T202 75H291Q321 75 329 89Z" />
 <glyph unicode="&#xe1;" glyph-name="aacute" horiz-adv-x="540" d="M410 715L288 580H202L306 715H410ZM404 0T389 8T362 30Q339 0 301 0H212Q136 0 102 30T67 135V155Q67 310 213 310H337V360Q337 391 318 408T262 425H107V500H252Q339 500 380 462T422 340V100Q422
 85 433 78T472 70V0H417Q404 0 389 8ZM321 75T329 89T337 125V235H212Q186 235 169 218T152 175V125Q152 99 164 87T202 75H291Q321 75 329 89Z" />
 <glyph unicode="&#xe2;" glyph-name="acircumflex" horiz-adv-x="540" d="M194 580H98L210 715H298L411 580H314L254 655L194 580ZM404 0T389 8T362 30Q339 0 301 0H212Q136 0 102 30T67 135V155Q67 310 213 310H337V360Q337 391 318 408T262 425H107V500H252Q339
 500 380 462T422 340V100Q422 85 433 78T472 70V0H417Q404 0 389 8ZM321 75T329 89T337 125V235H212Q186 235 169 218T152 175V125Q152 99 164 87T202 75H291Q321 75 329 89Z" />
 <glyph unicode="&#xe3;" glyph-name="atilde" horiz-adv-x="540" d="M115 672T143 686T183 700H198Q206 700 222 694T255 680Q297 660 309 660H319Q327 660 352 675T386 696V624Q378 619 354 605T318 591H303Q298 591 258 608Q206 631 193 631H183Q174 631 145
 616T106 595V667Q115 672 143 686ZM404 0T389 8T362 30Q339 0 301 0H212Q136 0 102 30T67 135V155Q67 310 213 310H337V360Q337 391 318 408T262 425H107V500H252Q339 500 380 462T422 340V100Q422 85 433 78T472 70V0H417Q404 0 389 8ZM321 75T329 89T337 125V235H212Q186
 235 169 218T152 175V125Q152 99 164 87T202 75H291Q321 75 329 89Z" />
 <glyph unicode="&#xe4;" glyph-name="adieresis" horiz-adv-x="540" d="M191 675V595H106V675H191ZM391 675V595H306V675H391ZM404 0T389 8T362 30Q339 0 301 0H212Q136 0 102 30T67 135V155Q67 310 213 310H337V360Q337 391 318 408T262 425H107V500H252Q339
 500 380 462T422 340V100Q422 85 433 78T472 70V0H417Q404 0 389 8ZM321 75T329 89T337 125V235H212Q186 235 169 218T152 175V125Q152 99 164 87T202 75H291Q321 75 329 89Z" />
 <glyph unicode="&#xe5;" glyph-name="aring" horiz-adv-x="540" d="M344 592T319 570T255 548H249Q210 548 185 570T160 633V662Q160 704 184 725T249 747H255Q295 747 319 726T344 662V633Q344 592 319 570ZM287 701T255 701H249Q231 701 223 691T215 663V632Q215
 615 223 605T249 594H255Q287 594 287 632V663Q287 701 255 701ZM404 0T389 8T362 30Q339 0 301 0H212Q136 0 102 30T67 135V155Q67 310 213 310H337V360Q337 391 318 408T262 425H107V500H252Q339 500 380 462T422 340V100Q422 85 433 78T472 70V0H417Q404 0 389
 8ZM321 75T329 89T337 125V235H212Q186 235 169 218T152 175V125Q152 99 164 87T202 75H291Q321 75 329 89Z" />
 <glyph unicode="&#xe6;" glyph-name="ae" horiz-adv-x="540" d="M346 0T317 11T273 47Q262 27 237 14T174 0H160Q93 0 59 31T25 135V147Q25 224 59 263T166 302H232V360Q232 392 217 408T165 425H60V500H155Q200 500 226 491T275 463Q296 483 316 491T375 500H382Q452
 500 484 461T516 345V229H315V132Q318 73 385 73H484V0H395Q346 0 317 11ZM435 367Q435 394 422 410T383 427H375Q340 427 328 411T315 362V302H435V367ZM137 229T123 212T108 167V123Q108 97 120 85T158 73H184Q214 73 223 87T232 123V229H163Q137 229 123 212Z"
 />
 <glyph unicode="&#xe7;" glyph-name="ccedilla" horiz-adv-x="540" d="M293 -136Q326 -136 326 -105Q326 -88 318 -82T291 -76H242V3Q180 12 150 49T120 160V340Q120 424 161 462T290 500H419V425H280Q243 425 224 408T205 360V140Q205 109 224 92T280 75H419V0H312V-21Q358
 -21 378 -38T399 -105Q399 -163 374 -181T311 -200H226V-136H293Z" />
 <glyph unicode="&#xe8;" glyph-name="egrave" horiz-adv-x="540" d="M261 715L365 580H279L157 715H261ZM176 0T135 37T94 160V340Q94 426 131 463T254 500H301Q372 500 408 461T445 345V215H179V140Q179 109 198 92T254 75H413V0H264Q176 0 135 37ZM362 365Q362
 391 345 408T302 425H244Q208 425 194 409T179 360V290H362V365Z" />
 <glyph unicode="&#xe9;" glyph-name="eacute" horiz-adv-x="540" d="M426 715L304 580H218L322 715H426ZM176 0T135 37T94 160V340Q94 426 131 463T254 500H301Q372 500 408 461T445 345V215H179V140Q179 109 198 92T254 75H413V0H264Q176 0 135 37ZM362 365Q362
 391 345 408T302 425H244Q208 425 194 409T179 360V290H362V365Z" />
 <glyph unicode="&#xea;" glyph-name="ecircumflex" horiz-adv-x="540" d="M211 580H115L227 715H315L428 580H331L271 655L211 580ZM176 0T135 37T94 160V340Q94 426 131 463T254 500H301Q372 500 408 461T445 345V215H179V140Q179 109 198 92T254 75H413V0H264Q176
 0 135 37ZM362 365Q362 391 345 408T302 425H244Q208 425 194 409T179 360V290H362V365Z" />
 <glyph unicode="&#xeb;" glyph-name="edieresis" horiz-adv-x="540" d="M218 675V595H133V675H218ZM418 675V595H333V675H418ZM176 0T135 37T94 160V340Q94 426 131 463T254 500H301Q372 500 408 461T445 345V215H179V140Q179 109 198 92T254 75H413V0H264Q176
 0 135 37ZM362 365Q362 391 345 408T302 425H244Q208 425 194 409T179 360V290H362V365Z" />
 <glyph unicode="&#xec;" glyph-name="igrave" horiz-adv-x="540" d="M253 715L357 580H271L149 715H253ZM80 425V500H312V75H460V0H227V425H80Z" />
 <glyph unicode="&#xed;" glyph-name="iacute" horiz-adv-x="540" d="M413 715L291 580H205L309 715H413ZM80 425V500H312V75H460V0H227V425H80Z" />
 <glyph unicode="&#xee;" glyph-name="icircumflex" horiz-adv-x="540" d="M213 580H117L229 715H317L430 580H333L273 655L213 580ZM80 425V500H312V75H460V0H227V425H80Z" />
 <glyph unicode="&#xef;" glyph-name="idieresis" horiz-adv-x="540" d="M213 675V595H128V675H213ZM413 675V595H328V675H413ZM80 425V500H312V75H460V0H227V425H80Z" />
 <glyph unicode="&#xf0;" glyph-name="eth" horiz-adv-x="540" d="M223 626H147V700H266L296 750H378L342 690Q445 658 445 530V170Q445 88 400 44T287 0H252Q184 0 139 44T94 170V300Q94 384 135 422T262 460H360V549Q360 574 345 594T303 622L270 566H188L223
 626ZM216 385T198 368T179 319V151Q179 119 200 97T257 75H282Q318 75 339 97T360 151V385H252Q216 385 198 368Z" />
 <glyph unicode="&#xf1;" glyph-name="ntilde" horiz-adv-x="540" d="M146 672T174 686T214 700H229Q237 700 253 694T286 680Q328 660 340 660H350Q357 660 382 675T417 696V624Q409 619 385 605T349 591H334Q329 591 289 608Q237 631 224 631H214Q205 631 176
 616T137 595V667Q146 672 174 686ZM167 500V476Q198 500 247 500H293Q374 500 413 462T453 340V0H368V360Q368 390 351 407T303 425H237Q204 425 188 408T172 370V0H87V500H167Z" />
 <glyph unicode="&#xf2;" glyph-name="ograve" horiz-adv-x="540" d="M261 715L365 580H279L157 715H261ZM452 76T411 38T282 0H249Q162 0 121 38T79 160V340Q79 424 120 462T249 500H282Q369 500 410 462T452 340V160Q452 76 411 38ZM367 391T348 408T292 425H239Q202
 425 183 408T164 360V140Q164 109 183 92T239 75H292Q329 75 348 92T367 140V360Q367 391 348 408Z" />
 <glyph unicode="&#xf3;" glyph-name="oacute" horiz-adv-x="540" d="M377 715L255 580H169L273 715H377ZM456 76T415 38T286 0H253Q166 0 125 38T83 160V340Q83 424 124 462T253 500H286Q373 500 414 462T456 340V160Q456 76 415 38ZM371 391T352 408T296 425H243Q206
 425 187 408T168 360V140Q168 109 187 92T243 75H296Q333 75 352 92T371 140V360Q371 391 352 408Z" />
 <glyph unicode="&#xf4;" glyph-name="ocircumflex" horiz-adv-x="540" d="M210 580H114L226 715H314L427 580H330L270 655L210 580ZM456 76T415 38T286 0H253Q166 0 125 38T83 160V340Q83 424 124 462T253 500H286Q373 500 414 462T456 340V160Q456 76 415 38ZM371
 391T352 408T296 425H243Q206 425 187 408T168 360V140Q168 109 187 92T243 75H296Q333 75 352 92T371 140V360Q371 391 352 408Z" />
 <glyph unicode="&#xf5;" glyph-name="otilde" horiz-adv-x="540" d="M139 672T167 686T207 700H222Q230 700 246 694T279 680Q321 660 333 660H343Q351 660 376 675T410 696V624Q402 619 378 605T342 591H327Q322 591 282 608Q230 631 217 631H207Q198 631 169
 616T130 595V667Q139 672 167 686ZM456 76T415 38T286 0H253Q166 0 125 38T83 160V340Q83 424 124 462T253 500H286Q373 500 414 462T456 340V160Q456 76 415 38ZM371 391T352 408T296 425H243Q206 425 187 408T168 360V140Q168 109 187 92T243 75H296Q333 75 352
 92T371 140V360Q371 391 352 408Z" />
 <glyph unicode="&#xf6;" glyph-name="odieresis" horiz-adv-x="540" d="M213 675V595H128V675H213ZM413 675V595H328V675H413ZM456 76T415 38T286 0H253Q166 0 125 38T83 160V340Q83 424 124 462T253 500H286Q373 500 414 462T456 340V160Q456 76 415 38ZM371
 391T352 408T296 425H243Q206 425 187 408T168 360V140Q168 109 187 92T243 75H296Q333 75 352 92T371 140V360Q371 391 352 408Z" />
 <glyph unicode="&#xf7;" glyph-name="divide" horiz-adv-x="540" d="M320 560V460H220V560H320ZM460 350V275H80V350H460ZM320 165V65H220V165H320Z" />
 <glyph unicode="&#xf8;" glyph-name="oslash" horiz-adv-x="540" d="M456 76T415 38T286 0H233L206 -89H128L159 15Q121 32 102 67T83 160V340Q83 424 124 462T253 500H286Q300 500 306 499L334 589H411L379 484Q418 467 437 432T456 340V160Q456 76 415 38ZM168
 112T183 95L284 425H243Q206 425 187 408T168 360V140Q168 112 183 95ZM371 388T355 404L255 75H296Q333 75 352 92T371 140V360Q371 388 355 404Z" />
 <glyph unicode="&#xf9;" glyph-name="ugrave" horiz-adv-x="540" d="M239 715L343 580H257L135 715H239ZM334 0T287 0H253Q172 0 133 38T93 160V500H178V140Q178 110 195 93T243 75H297Q329 75 344 91T362 127V500H447V0H367V23Q334 0 287 0Z" />
 <glyph unicode="&#xfa;" glyph-name="uacute" horiz-adv-x="540" d="M425 715L303 580H217L321 715H425ZM334 0T287 0H253Q172 0 133 38T93 160V500H178V140Q178 110 195 93T243 75H297Q329 75 344 91T362 127V500H447V0H367V23Q334 0 287 0Z" />
 <glyph unicode="&#xfb;" glyph-name="ucircumflex" horiz-adv-x="540" d="M209 580H113L225 715H313L426 580H329L269 655L209 580ZM334 0T287 0H253Q172 0 133 38T93 160V500H178V140Q178 110 195 93T243 75H297Q329 75 344 91T362 127V500H447V0H367V23Q334 0 287 0Z" />
 <glyph unicode="&#xfc;" glyph-name="udieresis" horiz-adv-x="540" d="M210 675V595H125V675H210ZM410 675V595H325V675H410ZM334 0T287 0H253Q172 0 133 38T93 160V500H178V140Q178 110 195 93T243 75H297Q329 75 344 91T362 127V500H447V0H367V23Q334 0 287 0Z" />
 <glyph unicode="&#xfd;" glyph-name="yacute" horiz-adv-x="540" d="M403 715L281 580H195L299 715H403ZM204 -95T216 -86T234 -55L248 0H228L63 500H155L280 81L389 500H476L321 -54Q308 -105 289 -130T247 -162T186 -170H138V-95H180Q204 -95 216 -86Z" />
 <glyph unicode="&#xfe;" glyph-name="thorn" horiz-adv-x="540" d="M371 500T412 463T453 340V160Q453 76 412 38T283 0H182V-170H97V700H182V480Q213 500 257 500H283Q371 500 412 463ZM368 391T349 408T293 425H247Q214 425 198 408T182 370V75H293Q330 75 349
 92T368 140V360Q368 391 349 408Z" />
 <glyph unicode="&#xff;" glyph-name="ydieresis" horiz-adv-x="540" d="M212 675V595H127V675H212ZM412 675V595H327V675H412ZM204 -95T216 -86T234 -55L248 0H228L63 500H155L280 81L389 500H476L321 -54Q308 -105 289 -130T247 -162T186 -170H138V-95H180Q204
 -95 216 -86Z" />
 <glyph unicode="&#x2013;" glyph-name="endash" horiz-adv-x="540" d="M460 350V275H80V350H460Z" />
 <glyph unicode="&#x2014;" glyph-name="emdash" horiz-adv-x="540" d="M507 350V275H32V350H507Z" />
 <glyph unicode="&#x2018;" glyph-name="quoteleft" horiz-adv-x="540" d="M302 542V452H207V542L262 699H332L302 542Z" />
 <glyph unicode="&#x2019;" glyph-name="quoteright" horiz-adv-x="540" d="M237 610V700H332V610L277 453H207L237 610Z" />
 <glyph unicode="&#x201a;" glyph-name="quotesinglbase" horiz-adv-x="540" d="M237 0V90H332V0L277 -157H207L237 0Z" />
 <glyph unicode="&#x201c;" glyph-name="quotedblleft" horiz-adv-x="540" d="M225 542V452H130V542L185 699H255L225 542ZM380 542V452H285V542L340 699H410L380 542Z" />
 <glyph unicode="&#x201d;" glyph-name="quotedblright" horiz-adv-x="540" d="M160 610V700H255V610L200 453H130L160 610ZM315 610V700H410V610L355 453H285L315 610Z" />
 <glyph unicode="&#x201e;" glyph-name="quotedblbase" horiz-adv-x="540" d="M160 0V90H255V0L200 -157H130L160 0ZM315 0V90H410V0L355 -157H285L315 0Z" />
 <glyph unicode="&#x2022;" glyph-name="bullet" horiz-adv-x="540" d="M345 390V235H195V390H345Z" />
 <glyph unicode="&#x2039;" glyph-name="guilsinglleft" horiz-adv-x="540" d="M281 506H347L284 299L347 92H281L192 299L281 506Z" />
 <glyph unicode="&#x203a;" glyph-name="guilsinglright" horiz-adv-x="540" d="M192 506H258L347 299L258 92H192L255 299L192 506Z" />
 </font>
 </defs>
 </svg>
@@ -0,0 +1 @@
 <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 192 512"><!--! Font Awesome Pro 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license (Commercial License) Copyright 2022 Fonticons, Inc. --><path d="M144 80c0 26.5-21.5 48-48 48s-48-21.5-48-48s21.5-48 48-48s48 21.5 48 48zM0 224c0-17.7 14.3-32 32-32H96c17.7 0 32 14.3 32 32V448h32c17.7 0 32 14.3 32 32s-14.3 32-32 32H32c-17.7 0-32-14.3-32-32s14.3-32 32-32H64V256H32c-17.7 0-32-14.3-32-32z"/></svg>
@@ -0,0 +1,91 @@
 <!DOCTYPE html>
 <html lang="en">
 <head>
    <meta charset="UTF-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
    <link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
    <link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">
    <link rel="manifest" href="/site.webmanifest">
    <link rel="mask-icon" href="/safari-pinned-tab.svg" color="#5bbad5">
    <meta name="msapplication-TileColor" content="#2d89ef">
    <meta name="theme-color" content="#ffffff">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <link rel="stylesheet" href="/mdn-style.min.css">
    <link rel="stylesheet" href="/foo-style.min.css">
    <title>Document</title>
    <script src="/redirect.js"></script>
    <script src="https://kit.fontawesome.com/7a57741988.js" crossorigin="anonymous"></script>
 </head>
 <body>
    <div id="app"></div>
    <script src="/app.js"></script>
    <script src="https://cdn.jsdelivr.net/npm/marked/marked.min.js"></script>
    <script src="/prism.js"></script>
    <script src="https://cdn.jsdelivr.net/npm/prismjs@1.29.0/plugins/autoloader/prism-autoloader.min.js"></script>
    <script>
        var app = Elm.Main.init({ node: document.getElementById("app") });
        var renderSuccess = false;
        app.ports.sendString.subscribe(function (markdowndata) {
            var numberOfHeadings = 0;
            // let toc = '';
            const renderer = new marked.Renderer();
            const sections = [];
            renderer.heading = (text, level) => {
                if (level === 1) {
                    return `<h${level}>${text}</h${level}>`
                }
                const escapedText = text.trim().toLowerCase().replace(/[^\w]+/g, '-');
                const endSection = `</div></section>`;
                const sectionContent = `
            <section aria-labelledby="${escapedText}">
            <h${level} id="${escapedText}">
              <a title="Permalink to ${text}" href="#${escapedText}">
                ${text}
              </a>
            </h${level}>
            <div class="section-content">`;
                // toc += `<li class="document-toc-item"><a class="document-toc-link" href="#${escapedText}">${text}</a></li>`;
                if (numberOfHeadings === 0) {
                    numberOfHeadings++;
                    return sectionContent;
                } else {
                    return endSection + sectionContent;
                }
            };
            renderer.blockquote = (text) => {
                return `<div id="sect3" class="notecard note">${text}</div>`;
            };
            marked.setOptions({
                renderer: renderer,
                highlight: function (code, lang) {
                    const grammar = Prism.languages[lang];
                    if (!grammar) {
                        console.warn(
                            `Unable to find a Prism grammar for '${lang}'`
                        );
                        return; // bail!
                    }
                    return Prism.highlight(code, grammar, lang);
                }
            })
            document.getElementById("insert-here").innerHTML = marked.parse(markdowndata);
            // document.getElementById("toc-entries").innerHTML = toc;
        });
        // app.ports.isRenderComplete.send(renderSuccess);
    </script>
 </body>
 </html>
@@ -0,0 +1,96 @@
 <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="65" height="60"
 shape-rendering="crispEdges"><style type="text/css">
 .color {
    -webkit-animation: col 300s linear infinite;
    -moz-animation: col 300s linear infinite;
    -o-animation: col 300s linear infinite;
    animation: col 300s linear infinite;
 }
@keyframes col {
    0% {
        fill: #EE67A4;
    }
    12.5% {
        fill: violet;
    }
    25% {
        fill: indigo;
    }
    37.5% {
        fill: blue;
    }
    50% {
        fill: #35BEB8
    }
    62.5% {
        fill: green;
    }
    75% {
        fill: yellow;
    }
    87.5% {
        fill: orange;
    }
    100% {
        fill: red;
    }
 }
 .rcolor {
    -webkit-animation: rcol 300s linear infinite;
    -moz-animation: rcol 300s linear infinite;
    -o-animation: rcol 300s linear infinite;
    animation: rcol 300s linear infinite;
 }
@keyframes rcol {
    0% {
        fill: #35BEB8;
    }
    12.5% {
        fill: blue;
    }
    25% {
        fill: indigo;
    }
    37.5% {
        fill: violet;
    }
    50% {
        fill: #EE67A4;
    }
    62.5% {
        fill: red;
    }
    75% {
        fill: orange;
    }
    87.5% {
        fill: yellow;
    }
    100% {
        fill: green;
    }
 }
 </style><symbol id="logo" viewBox="0 -60 65 60"><path class="st0 color" d="M60-60H0V0h60z" /><path class="st1" d="M60-41h-5v10h5z" /><path class="st2 rcolor" d="M65-41h-5v10h5z" /></symbol><use xlink:href="#logo" width="65" height="60" id="XMLID_14_" y="-60" transform="scale(1 -1)" overflow="visible" /></svg>
@@ -0,0 +1,5 @@
 <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="65" height="60" shape-rendering="crispEdges"><style type="text/css"><![CDATA[
 	.st0{fill:#EE67A4;}
 	.st1{fill:#231F20;}
 	.st2{fill:#35BEB8;}
 ]]></style><symbol id="logo" viewBox="0 -60 65 60"><path class="st0" d="M60-60H0V0h60z"/><path class="st1" d="M60-41h-5v10h5z"/><path class="st2" d="M65-41h-5v10h5z"/></symbol><use xlink:href="#logo" width="65" height="60" id="XMLID_14_" y="-60" transform="scale(1 -1)" overflow="visible"/></svg>
@@ -0,0 +1,30 @@
 // Single Page Apps for GitHub Pages
 // https://github.com/rafrex/spa-github-pages
 // Copyright (c) 2016 Rafael Pedicini, licensed under the MIT License
 // ----------------------------------------------------------------------
 // This script checks to see if a redirect is present in the query string
 // and converts it back into the correct url and adds it to the
 // browser's history using window.history.replaceState(...),
 // which won't cause the browser to attempt to load the new url.
 // When the single page app is loaded further down in this file,
 // the correct url will be waiting in the browser's history for
 // the single page app to route accordingly.
 (function(l) {
    if (l.search) {
      var q = {};
      l.search
        .slice(1)
        .split("&")
        .forEach(function(v) {
          var a = v.split("=");
          q[a[0]] = a
            .slice(1)
            .join("=")
            .replace(/~and~/g, "&");
        });
      if (q.p !== undefined) {
        window.history.replaceState(null, null, l.pathname.slice(0, -1) + (q.p || "") + (q.q ? "?" + q.q : "") + l.hash);
      }
    }
  })(window.location);
@@ -0,0 +1,80 @@
 <?xml version="1.0" standalone="no"?>
 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 20010904//EN"
 "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
 <svg version="1.0" xmlns="http://www.w3.org/2000/svg"
 width="1040.000000pt" height="1040.000000pt" viewBox="0 0 1040.000000 1040.000000"
 preserveAspectRatio="xMidYMid meet">
 <metadata>
 Created by potrace 1.14, written by Peter Selinger 2001-2017
 </metadata>
 <g transform="translate(0.000000,1040.000000) scale(0.100000,-0.100000)"
 fill="#000000" stroke="none">
 <path d="M0 5200 l0 -4800 4799 0 c4790 0 4799 0 4804 20 3 11 1 20 -4 20 -5
 0 -4 11 1 25 6 16 6 25 0 25 -6 0 -6 9 0 25 6 16 6 25 0 25 -6 0 -6 9 0 25 6
 15 6 25 0 25 -5 0 -5 12 0 30 5 18 5 30 0 30 -6 0 -6 10 0 25 6 17 6 25 -1 25
 -6 0 -7 5 -4 11 9 14 10 113 1 128 -4 6 -3 11 3 11 7 0 7 8 1 25 -6 15 -6 27
 0 30 6 3 6 15 0 30 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 15 -6 26 0 30 7 4 6 13
 0 25 -6 12 -7 21 0 25 6 4 6 15 0 30 -6 16 -6 25 0 25 6 0 6 9 0 25 -5 14 -6
 25 -2 25 8 0 6 74 -2 97 -3 7 -1 13 4 13 6 0 6 9 0 25 -6 16 -6 25 0 25 6 0 6
 9 1 23 -5 13 -5 30 -1 37 5 8 4 22 -1 32 -7 12 -6 18 1 18 7 0 8 6 0 19 -7 13
 -7 22 0 26 6 4 7 13 1 24 -6 10 -6 23 -1 31 5 8 5 19 0 25 -5 6 -5 17 0 25 4
 7 4 24 0 36 -6 14 -5 26 0 29 7 4 6 13 0 25 -6 12 -7 21 0 25 6 4 6 15 0 30
 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 15 -6 25 0
 25 5 0 5 12 0 30 -5 18 -5 30 0 30 6 0 6 10 0 25 -6 15 -6 25 0 25 5 0 5 12 0
 30 -5 18 -5 30 0 30 6 0 6 10 0 25 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 16 -6 25
 0 25 6 0 6 9 0 25 -6 15 -6 27 0 30 6 3 6 15 0 30 -6 16 -6 25 0 25 6 0 6 9 0
 25 -6 15 -6 26 0 30 7 4 6 13 0 25 -6 12 -7 21 0 25 6 4 6 15 0 30 -6 16 -6
 25 0 25 6 0 6 9 0 25 -5 14 -6 25 -2 25 8 0 6 74 -2 97 -3 7 -1 13 4 13 6 0 6
 9 0 25 -6 16 -6 25 0 25 6 0 6 9 1 23 -5 13 -5 30 -1 37 5 8 4 22 -1 32 -7 12
 -6 18 1 18 7 0 8 6 0 19 -7 13 -7 22 0 26 6 4 7 13 1 24 -6 10 -6 23 -1 31 5
 8 5 19 0 25 -5 6 -5 17 0 25 4 7 4 24 0 36 -6 14 -5 26 0 29 7 4 6 13 0 25 -6
 12 -7 21 0 25 6 4 6 15 0 30 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 16 -6 25 0 25
 6 0 6 9 0 25 -6 15 -6 25 0 25 5 0 5 12 0 30 -5 18 -5 30 0 30 6 0 6 10 0 25
 -6 15 -6 25 0 25 5 0 5 12 0 30 -5 18 -5 32 1 35 5 4 5 14 -1 25 -7 13 -7 21
 0 25 7 4 7 13 1 24 -13 23 15 67 32 53 7 -5 23 -6 37 -2 14 4 35 3 47 -1 13
 -5 25 -4 28 1 4 7 13 6 25 0 13 -7 21 -7 25 0 4 7 12 7 25 0 13 -7 21 -7 25 0
 5 8 11 8 19 1 7 -6 16 -8 19 -5 8 9 85 9 93 1 4 -3 14 -2 23 3 10 5 22 5 28 2
 14 -9 82 -7 90 2 4 3 12 1 19 -5 8 -7 14 -7 19 1 4 7 12 7 25 0 11 -6 21 -6
 25 -1 3 6 17 6 35 1 18 -5 32 -5 35 1 4 5 14 5 25 -1 13 -7 21 -7 25 0 5 7 11
 8 19 1 7 -6 17 -6 26 -1 8 5 18 6 22 4 4 -3 8 355 8 795 0 756 -1 801 -17 802
 -10 1 -21 1 -24 1 -7 -1 -110 -2 -141 -1 -10 0 -67 0 -128 0 -60 0 -116 0
 -122 0 -7 0 -44 0 -83 0 -38 0 -77 0 -85 0 -8 1 -51 1 -95 0 -114 -1 -115 -1
 -105 19 6 11 5 21 -2 28 -9 9 -9 12 -1 12 8 0 9 9 3 30 -5 17 -5 30 0 30 5 0
 5 13 0 30 -5 18 -5 30 0 30 6 0 6 10 0 25 -6 15 -6 26 0 30 7 4 6 13 0 25 -7
 13 -7 21 0 25 6 4 7 13 1 24 -6 10 -6 23 -1 31 5 8 5 19 0 25 -5 6 -5 17 0 25
 4 7 4 24 0 36 -6 14 -5 26 0 29 7 4 6 13 0 25 -6 12 -7 21 0 25 6 4 6 15 0 30
 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 15 -6 25 0
 25 5 0 5 12 0 30 -5 18 -5 30 0 30 6 0 6 10 0 25 -6 15 -6 25 0 25 5 0 5 12 0
 30 -5 18 -5 30 0 30 6 0 6 10 0 25 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 16 -6 25
 0 25 6 0 6 9 0 25 -6 15 -6 27 0 30 6 3 6 15 0 30 -6 16 -6 25 0 25 6 0 6 9 0
 25 -6 15 -6 26 0 30 7 4 6 13 0 25 -6 12 -7 21 0 25 6 4 6 15 0 30 -6 16 -6
 25 0 25 6 0 6 9 0 25 -5 14 -6 25 -2 25 8 0 6 74 -2 97 -3 7 -1 13 4 13 6 0 6
 9 0 25 -6 16 -6 25 0 25 6 0 6 9 1 23 -5 13 -5 30 -1 37 5 8 4 22 -1 32 -7 12
 -6 18 1 18 7 0 8 6 0 19 -7 13 -7 22 0 26 6 4 7 13 1 24 -6 10 -6 23 -1 31 5
 8 5 19 0 25 -5 6 -5 17 0 25 4 7 4 24 0 36 -6 14 -5 26 0 29 7 4 6 13 0 25 -6
 12 -7 21 0 25 6 4 6 15 0 30 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 16 -6 25 0 25
 6 0 6 9 0 25 -6 15 -6 25 0 25 5 0 5 12 0 30 -5 18 -5 30 0 30 6 0 6 10 0 25
 -6 15 -6 25 0 25 5 0 5 12 0 30 -5 18 -5 30 0 30 6 0 6 10 0 25 -6 16 -6 25 0
 25 6 0 6 9 0 25 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 15 -6 27 0 30 6 3 6 15 0
 30 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 15 -6 26 0 30 7 4 6 13 0 25 -6 12 -7 21
 0 25 6 4 6 15 0 30 -6 16 -6 25 0 25 6 0 6 9 0 25 -5 14 -6 25 -2 25 8 0 6 74
 -2 97 -3 7 -1 13 4 13 6 0 6 9 0 25 -6 16 -6 25 0 25 6 0 6 9 1 23 -5 13 -5
 30 -1 37 5 8 4 22 -1 32 -7 12 -6 18 1 18 7 0 8 6 0 19 -7 13 -7 22 0 26 6 4
 7 13 1 24 -6 10 -6 23 -1 31 5 8 5 19 0 25 -5 6 -5 17 0 25 4 7 4 24 0 36 -6
 14 -5 26 0 29 7 4 6 13 0 25 -6 12 -7 21 0 25 6 4 6 15 0 30 -6 16 -6 25 0 25
 6 0 6 9 0 25 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 15 -6 25 0 25 5 0 5 12 0 30
 -5 18 -5 30 0 30 6 0 6 10 0 25 -6 15 -6 25 0 25 5 0 5 12 0 30 -5 18 -5 30 0
 30 6 0 6 10 0 25 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 16 -6 25 0 25 6 0 6 9 0
 25 -6 15 -6 27 0 30 6 3 6 15 0 30 -6 16 -6 25 0 25 6 0 6 9 0 25 -6 15 -6 26
 0 30 7 4 6 13 0 25 -6 12 -7 21 0 25 6 4 6 15 0 30 -6 16 -6 25 0 25 6 0 6 9
 0 25 -5 14 -6 25 -2 25 8 0 6 74 -2 97 -3 7 -1 13 4 13 6 0 6 9 0 25 -6 16 -6
 25 0 25 6 0 6 9 1 23 -5 13 -5 30 -1 37 5 8 4 22 -1 32 -7 12 -6 18 1 18 7 0
 8 6 0 19 -7 13 -7 22 0 26 6 4 7 13 1 24 -6 10 -6 23 -1 31 5 8 5 19 0 25 -5
 6 -5 17 0 25 4 7 4 24 0 36 -6 14 -5 26 0 29 7 4 6 13 0 25 -6 12 -7 21 0 25
 5 3 6 15 1 28 -5 12 -5 32 0 45 5 13 5 22 -1 22 -6 0 -6 9 0 25 6 15 6 25 0
 25 -5 0 -5 12 0 30 5 18 5 30 0 30 -6 0 -6 10 0 25 6 15 6 25 0 25 -5 0 -5 12
 0 30 5 18 5 30 0 30 -6 0 -6 10 0 25 6 16 6 25 0 25 -6 0 -6 9 0 25 6 16 6 25
 0 25 -5 0 -7 6 -4 13 8 23 10 97 2 97 -4 0 -3 11 2 25 5 14 6 25 1 25 -5 0 -7
 9 -4 20 5 20 0 20 -4796 20 l-4801 0 0 -4800z"/>
 </g>
 </svg>
@@ -1,6 +1,6 @@
 {
-    "name": "Avinal",
+    "name": "Be My SpaceTime",
-    "short_name": "Avinal",
+    "short_name": "SpaceTime",
    "icons": [
        {
            "src": "/android-chrome-192x192.png",
@@ -13,7 +13,7 @@
            "type": "image/png"
        }
    ],
-    "theme_color": "#00aba9",
+    "theme_color": "#ffffff",
-    "background_color": "#00aba9",
+    "background_color": "#ffffff",
    "display": "standalone"
 }
@@ -1,21 +0,0 @@
 #!/usr/bin/env python
 # -*- coding: utf-8 -*- #
 # This file is only used if you use `make publish` or
 # explicitly specify it as your config file.
 import os
 import sys
 sys.path.append(os.curdir)
 from pelicanconf import *
 # If your site is available via HTTPS, make sure SITEURL begins with https://
 SITEURL = 'https://avinal.space'
 RELATIVE_URLS = False
 FEED_ALL_ATOM = 'feeds/all.atom.xml'
 CATEGORY_FEED_ATOM = 'feeds/{slug}.atom.xml'
 DELETE_OUTPUT_DIRECTORY = True
 # Following items are often useful when publishing
@@ -1,3 +0,0 @@
 pelican
 ghp-import
 wheel
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
avinal	de9debbb5d	sorted json file Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 01:38:55 +05:30
avinal	4882b60bde	move static files to ghpages Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-01 12:18:57 +05:30
avinal	9b27f45e00	Fix blog posting Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-16 19:20:48 +05:30
avinal	eb0f825244	Fix blog posting Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-16 18:49:40 +05:30
avinal	398a09d301	add blog listing fucntions Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-16 17:42:47 +05:30
avinal	fe325ca25a	add favicon and html page handling Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-16 02:35:40 +05:30
avinal	3840e00bec	fix text size and colors Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-15 21:56:35 +05:30
avinal	e46f0dfbbe	fix styling issue Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-15 21:27:32 +05:30
avinal	0a97668317	add font page design Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-15 21:16:02 +05:30
avinal	cda5e8288d	add font page design Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-15 20:59:16 +05:30
avinal	c64a15fef5	add support for article image Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-15 02:04:33 +05:30
avinal	770e809bd2	remove unused Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-15 02:04:03 +05:30
avinal	a68c0354d4	fix styling errors	2022-09-14 21:56:38 +05:30
avinal	2a66c43f5e	fix markdown error and 404	2022-09-14 21:38:20 +05:30
avinal	f15f4b825f	add blogs	2022-09-14 19:51:10 +05:30
avinal	a6e6a4a3ba	for production	2022-09-14 19:50:47 +05:30
avinal	c1570d2b7f	modify workflow	2022-09-14 19:50:01 +05:30
avinal	c954347451	fix some bugs	2022-09-14 17:33:27 +05:30
avinal	f325dafde1	disable scrollonfragmnt	2022-09-14 17:03:22 +05:30
avinal	6e8570edb2	test prism highlighting	2022-09-14 16:50:05 +05:30
avinal	38febf8727	test without callback	2022-09-14 16:31:46 +05:30
avinal	9baef63a2e	fix error reporting Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-14 16:15:36 +05:30
avinal	b0bcd5794e	fix parsing and add scroll Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-14 15:41:45 +05:30
avinal	e6e5a939f3	reduce unused styling Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-14 15:34:45 +05:30
avinal	2ba5689a76	fix yaml parsing error Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-14 00:16:32 +05:30
avinal	e41f2e4520	remove slug Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-13 23:26:19 +05:30
avinal	abe8d6ee20	add metadata parsing Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-13 23:26:04 +05:30
avinal	d71d020d85	fix url resolution error Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-13 02:59:39 +05:30
avinal	5fd42929ae	add example pages Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-13 02:53:29 +05:30
avinal	65fe4eb7a1	update public pages Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-13 02:40:06 +05:30
avinal	0e331cd41f	add blog parser Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-13 02:39:09 +05:30
avinal	d30b69bac0	add markdown loader Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-10 20:01:45 +05:30
avinal	8ac581d3a0	fix some style issue Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 22:38:55 +05:30
avinal	914ec4c0b6	fix some style issue Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 22:25:20 +05:30
avinal	f52ca5f7e4	fix some style issue Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 19:50:34 +05:30
avinal	d949aab083	fix some style issue Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 19:46:02 +05:30
avinal	bab11c32bd	fix some style issue Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 19:37:53 +05:30
avinal	5e539dadaf	fix some style issue Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 19:07:00 +05:30
avinal	80a054c8c0	fix some style issue Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 18:25:10 +05:30
avinal	291a44de09	try merging css Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 16:48:43 +05:30
avinal	68cbbdee1f	add html parser and test blog Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 15:26:33 +05:30
avinal	f19dba4ef8	add post styles and increase animation time Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 15:25:46 +05:30
avinal	038cc78441	add better error page Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 11:44:01 +05:30
avinal	42d6fed355	add background to blogs Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 11:33:18 +05:30
avinal	e21a03d871	fix fonts Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 11:32:25 +05:30
avinal	7d6693ffbd	fix links Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 00:26:14 +05:30
avinal	9b550b4eb9	Update build-deploy.yaml	2022-09-08 00:20:40 +05:30
avinal	47f946dde7	add workflow Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 00:19:11 +05:30
avinal	48f7b5907f	add redirection mechanism Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 00:18:48 +05:30
avinal	00effc7c33	add html and styles Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 00:18:18 +05:30
avinal	5e2c452665	add basic project Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2022-09-08 00:16:39 +05:30
avinal	faa6d37ad9	Initial commit	2022-09-04 20:42:32 +05:30
		`@@ -0,0 +1 @@`
							[{"title":"Developing Minimal Tekton Server","date":"2022-02-27 20:47","category":"development","description":"This blog is a descreptive account of the development of Minimal Tekton Server. This is highly technical in nature, so please make sure that you have sufficient knowledge about Golang, Docker, Kubernetes and TektonCD. You can refer to my [previous blog](\"https://avinal.space/posts/development/i-am-loving-it-redhat.html\") to know about these topics.","slug":"lovely-dangerous-things-redhat"},{"title":"I am loving it! RedHat","date":"2022-02-25 20:47","category":"development","description":"I made it to the Red Hat as a DevTools intern. This post is about onboarding and how I prepared myself for working on the actual project.","slug":"i-am-loving-it-redhat"},{"title":"Google Summer of Code 2021","date":"2021-08-19 23:07","category":"development","description":"This is the final report of my Google Summer of Code 2021 at The FOSSology Project. One of the major improvements over the previous build system is faster build times. CMake generates parallel build-enabled configurations for all generators.","slug":"final-evaluation"},{"title":"How I implemented WakaTime embeddable Coding Graph GHA?","date":"2021-02-02 21:47","category":"development","description":"If you use WakaTime to track your coding activity. You can add that to your README as a bar graph or embed it in your blog/portfolio. Just add this action to any of your repositories and there you have it.","slug":"wakatime"},{"title":"HRT (Hudson River Trading) Systems Internship Interview Experience","date":"2021-01-04 21:47","category":"blogs","slug":"hrt-interview-1","description":"uestions were clear and of medium level. But they were designed in such a way that you must know the basics before you could attempt. Also, they expected a clear and concise approach."},{"title":"Move WSL 2 Safely to another Drive","date":"2020-12-31 19:07","category":"development","description":"It is real pain when you have small SSD and Windows Subsystem for Linux (WSL) is growing exponentially in size. There is no easy way to move the WSL installation to another drive. Here in this blog I will discuss how to tackle this problem with bite size steps.","slug":"wsl2-move"},{"title":"Create the VLC User Documentation for one Mobile Port(Android)","date":"2020-12-01 23:47","category":"blogs","description":"The project was to Create the VLC User Documentation for Android Mobile Port which was previously hosted on VLC wiki pages. The major portion of this was to start everything from scratch including chapter separation, section organization.","slug":"gsod2020-report"},{"title":"प्रेम रतन धन पायो","date":"2019-09-21 15:47","category":"articles","slug":"for-sunshine","description":"प्रकृति की सुंदरता और कलाकारी हिमालय की कण-कण में झलकती है। प्रकृति ने प्रेम को भी हिमालय के जितना ही विशाल और अलौकिक बनाया है । ये एक अलग चर्चा का विषय है कि हिमालय पहले आया या प्रेम। मैं तो प्रेम के पक्ष में हूँ । वो हर अणु-परमाणु जिन्होंने इतने बड़ा पहाड़ खड़ा किया वो सब आपस में प्रेम से बंधे हुए हैं। ये पृथ्वी, सूर्य, चंद्रमा, आकाश-गंगा इत्यादि सब प्रेम से बंधे हुए हैं"},{"title":"The Big Red Ants","date":"2012-02-27 22:47","category":"articles","description":"As I observed them making and reparing their nests, I concluded that they are laborious and intellectual. They create their nests bybinding two or more leaves (maybe up to 500) together. They stich the leaves using a stinky white substance either excreted by themselves or from trees.","slug":"big-red-ants"}]
		`@@ -0,0 +1 @@`
							`<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 192 512"><!--! Font Awesome Pro 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license (Commercial License) Copyright 2022 Fonticons, Inc. --><path d="M144 80c0 26.5-21.5 48-48 48s-48-21.5-48-48s21.5-48 48-48s48 21.5 48 48zM0 224c0-17.7 14.3-32 32-32H96c17.7 0 32 14.3 32 32V448h32c17.7 0 32 14.3 32 32s-14.3 32-32 32H32c-17.7 0-32-14.3-32-32s14.3-32 32-32H64V256H32c-17.7 0-32-14.3-32-32z"/></svg>`