taler-www

Main taler.net website
Log | Files | Refs | Submodules | README | LICENSE

ngi-taler.html.j2 (18484B)


      1 {% extends "common/consortium.j2" %}
      2 {% block subtitle %}{{ _("NGI TALER") }}{% endblock subtitle %}
      3 {% block body_content %}
      4   <main id="maincontent">
      5     <div class="container consortium dark-grey-text">
      6       <article>
      7         <div class="row">
      8           <div class="col-lg-6">
      9             <img class="img-fluid" src="{{ url_static('images/logo-NGI_TALER_Bold.svg') }}" alt="NGI Taler logo"
     10               width="500px">
     11           </div>
     12           <h4 class="font-weight-bold pb-2 mb-4">NGI TALER</h4>
     13           <!-- {# <div class="col col-md-auto"></div> #} project intro -->
     14           <div class="col-md-11 col-md-4 mb-4 px-md-4">
     15             <p class="w-responsive mx-auto mb-3">
     16               GNU Taler (<em>Taxable Anonymous Libre Electronic Resources</em>) is a new secure
     17               electronic payment system based on open standards, free software, and advanced cryptography.
     18               GNU Taler provides privacy guarantees to the buyer while offering the possibility
     19               to audit merchants, making sale incomes transparent and fraud difficult.
     20               To online merchants and retailers, GNU Taler offers instant transaction clearance
     21               without risks of fake payment methods. Computations needed to clear the payments
     22               are efficient and scalable so that banks can pass on lower transaction costs to
     23               consumers and merchants. Consumers can withdraw money from their existing bank account
     24               into their GNU Taler wallet, detaching their spending habits from scrutiny, in the way cash does.
     25             </p>
     26             <p class="w-responsive mx-auto mb-3">
     27               The NGI TALER project is funded under Horizon Europe (Pilots for the Next Generation Internet) with the aim
     28               of bringing GNU Taler to market across Europe.
     29             </p>
     30             <p class="w-responsive mx-auto mb-3">
     31               To make GNU Taler accessible to European citizens, we need a commercially viable use of
     32               the GNU Taler technology. We will achieve this through the four key project objectives.
     33             </p>
     34             <div class="accordion" id="accordionObjectives">
     35               {% for objective in conf['objectives'] %}
     36                 <div class="accordion-item">
     37                   <h2 class="accordion-header" id="heading_{{ loop.index }}">
     38                     <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse"
     39                       data-bs-target="#collapse_{{ loop.index }}" aria-expanded="false"
     40                       aria-controls="collapse_{{ loop.index }}">
     41                       Objective {{ loop.index }}: {{ objective.title }}
     42                     </button>
     43                   </h2>
     44                   <div id="collapse_{{ loop.index }}" class="accordion-collapse collapse"
     45                     aria-labelledby="heading_{{ loop.index }}" data-bs-parent="#accordionObjectives">
     46                     <p class="accordion-body text-muted w-responsive">
     47                       {{ objective.text }}
     48                     </p>
     49                   </div>
     50                 </div>
     51               {% endfor %}
     52             </div>
     53           </div>
     54         </div>
     55       </article>
     56 
     57       <article>
     58         <div class="row">
     59           <h4 class="font-weight-bold pb-2 mb-4">Open Calls</h4>
     60           <div class="col-md-11 col-md-4 mb-4 px-md-4">
     61             <p class="w-responsive mx-auto mb-3">
     62               NGI TALER has frequent open calls for funding to third parties.
     63               The deadlines were April 1<sup>st</sup> 2024, June 1<sup>st</sup>, October 1<sup>st</sup>, December
     64               1<sup>st</sup>, February 1<sup>st</sup> 2025, April 1<sup>st</sup>, June 1<sup>st</sup>, August
     65               1<sup>st</sup>, October 1<sup>st</sup>, December 1<sup>st</sup>, February 1<sup>st</sup> 2026, April 1<sup>st</sup>, June 1<sup>st</sup>,
     66               and August 1<sup>st</sup>.
     67               <b>The 15<sup>th</sup> and last open call of NGI TALER</b> opened up on August 1<sup>st</sup> with a deadline
     68               of <b>October 1<sup>st</sup> 2026 (12:00 CEST)</b>.
     69               You can find more information at the <strong><a href="https://nlnet.nl/taler" target="_blank"
     70                   rel="noopener noreferrer">Open Calls</a></strong> page and
     71               get feedback and support at the <strong><a href="https://ich.taler.net/pub/open-calls-helpdesk"
     72                   target="_blank" rel="noopener noreferrer">
     73                   TALER Integration Community Hub</a></strong>.
     74             </p>
     75             <p class="w-responsive mx-auto mb-3">
     76               In the program's first open call <strong>five teams</strong> have been selected by an external experts
     77               committee:
     78               <ul>
     79                 <li><strong><a href="https://nlnet.nl/project/TALER-LookupService" target="_blank"
     80                       rel="noopener noreferrer">GNU Taler Wallet ID Lookup Service</a>
     81                   </strong> will provide the optional discovery of wallet addresses linked to digital identities</li>
     82                 <li><strong><a href="https://nlnet.nl/project/TALER-OIM" target="_blank" rel="noopener noreferrer">Road
     83                       Signs for Digital Payments</a>
     84                   </strong> will work on an interface for people who cannot read or write</li>
     85                 <li><strong><a href="https://nlnet.nl/project/TALER-Bullion" target="_blank" rel="noopener noreferrer">TALER
     86                       Bullion</a>
     87                   </strong> will add an infrastructure for Taler payments with non-fiat currencies such as gold and silver
     88                 </li>
     89                 <li><strong><a href="https://nlnet.nl/project/MTE" target="_blank" rel="noopener noreferrer">MTE - the
     90                       MirageOS Taler Exchange</a>
     91                   </strong> will implement Taler Exchange functionality in an OCaml-based unikernel</li>
     92                 <li><strong><a href="https://nlnet.nl/project/TALER-Odoo-module" target="_blank"
     93                       rel="noopener noreferrer">Taler-Odoo Payment System</a>
     94                   </strong> will integrate Taler in the <em>Odoo</em> business management software suite</li>
     95               </ul>
     96             </p>
     97             <p class="w-responsive mx-auto mb-3">
     98               In NGI TALER's second open call <strong>two teams</strong> have been selected by the external experts
     99               committee:
    100               <ul>
    101                 <li><strong><a href="https://nlnet.nl/project/TALER-Tryton" target="_blank" rel="noopener noreferrer">GNU
    102                       Taler Tryton/GNUHealth Integration</a>
    103                   </strong> will develop a <em>Tryton</em> module which would
    104                   allow users to integrate payments with GNU Taler into their web shops and businesses, going
    105                   hand in hand with <em>GNU Health</em>, which is built on <em>Tryton</em> and provides a suite of libre
    106                   alternatives for hospital management software, health information systems and electronic health records
    107                 </li>
    108                 <li><strong><a href="https://nlnet.nl/project/TALER-Interledger-study" target="_blank"
    109                       rel="noopener noreferrer">Interledger Interoperability Inquiry</a>
    110                   </strong> will investigate the technical feasibility of using
    111                   Taler as a payment method on the <em>Interledger payment network</em> to support web monetization</li>
    112               </ul>
    113             </p>
    114             <p class="w-responsive mx-auto mb-3">
    115               In NGI TALER's third open call <strong>three teams</strong> have been selected by the external experts
    116               committee:
    117               <ul>
    118                 <li><strong><a href="https://nlnet.nl/project/TALER-OpenBankingGateway" target="_blank"
    119                       rel="noopener noreferrer">
    120                       Taler Open Banking Gateway</a></strong> will provide the technology to top-up a Taler wallet in a
    121                   regulatory-compliant, instant and user-friendly way</li>
    122                 <li><strong><a href="https://nlnet.nl/project/TALER-flohmarkt" target="_blank" rel="noopener noreferrer">
    123                       Flohmarkt</a></strong> will integrate Taler payments into <em>Flohmarkt</em>, a decentralized federated
    124                   small advertisement platform,
    125                   and allows individuals to informally sell goods to each other in a privacy-preserving manner</li>
    126                 <li><strong><a href="https://nlnet.nl/project/TALER-integration-Nuxt" target="_blank"
    127                       rel="noopener noreferrer">
    128                       Payment Module for Nuxt/Vue.js</a></strong> will create a dedicated GNU Taler module for <em>Nuxt</em>
    129                   including Vue.js components for donation and order payment, documentation and examples such as a
    130                   file-based webshop</li>
    131               </ul>
    132             </p>
    133             <p class="w-responsive mx-auto mb-3">
    134               In NGI TALER's fourth and fifth open call <strong>four teams</strong> have been selected by the external
    135               experts committee:
    136               <ul>
    137                 <li><strong><a href="https://nlnet.nl/project/Taler-Dolibarr" target="_blank" rel="noopener noreferrer">
    138                       Taler-Dolibarr Integration</a></strong> will provide a comprehensive module to integrate the
    139                   privacy-preserving payment system GNU Taler
    140                   with Dolibarr, an open-source Enterprise Resource Planning used by many small businesses around the world
    141                 </li>
    142                 <li><strong><a href="https://nlnet.nl/project/Contributron" target="_blank" rel="noopener noreferrer">
    143                       Contributron</a></strong>, a privacy-aware donation portal with Taler-based payments, delivers a
    144                   self-hostable personal website to collect donations
    145                   and track crowd-funding efforts on various external platforms, including one-time and recurring donations
    146                 </li>
    147                 <li><strong><a href="https://nlnet.nl/project/Taler-on-BSD" target="_blank" rel="noopener noreferrer">
    148                       xBSD</a></strong>, porting and packaging of Taler components for xBSD systems, will make sure that the
    149                   entire Taler software stack
    150                   is natively available on a number of operating systems beyond the already available (and obviously
    151                   popular) Linux operating system
    152                   — NetBSD, OpenBSD, FreeBSD and Apple's MacOS X</li>
    153                 <li><strong><a href="https://nlnet.nl/project/TalerPHP" target="_blank" rel="noopener noreferrer">
    154                       TalerPHP</a></strong> will develop an open-source PHP library to interact with GNU Taler’s REST APIs,
    155                   enabling PHP-based applications to more easily support privacy-preserving payments</li>
    156               </ul>
    157             </p>
    158             <p class="w-responsive mx-auto mb-3">
    159               In the sixth and seventh open call <strong>three teams</strong> have been selected by the external experts
    160               committee:
    161               <ul>
    162                 <li><strong><a href="https://nlnet.nl/project/TALER-Ruby-OFN" target="_blank" rel="noopener noreferrer">
    163                       Libre Payments in Ruby</a></strong> integrates GNU Taler into Ruby-based e-commerce applications —
    164                   supporting GNU Taler for ethical trade
    165                   and starting with the Open Food Network (OFN)</li>
    166                 <li><strong><a href="https://nlnet.nl/project/TALER-Liberapay" target="_blank" rel="noopener noreferrer">
    167                       Taler in Liberapay</a></strong> aims at implementing GNU Taler for payments in Liberapay, a recurrent
    168                   donations platform, enabling users with a
    169                   Taler wallet to support projects and creators in a privacy-preserving manner</li>
    170                 <li><strong><a href="https://nlnet.nl/project/TALER-APIs" target="_blank" rel="noopener noreferrer">
    171                       Taler OpenAPI specification</a></strong> adds automatic OpenAPI specification generation to GNU
    172                   Taler's bank APIs and the wallet-core API</li>
    173               </ul>
    174               We congratulate the grantees! More information regarding the grantees' projects can be found at the
    175               <strong><a href="https://nlnet.nl/thema/NGITALERFund.html" target="_blank" rel="noopener noreferrer">NGI TALER
    176                   grants selection page</a></strong>.
    177             </p>
    178           </div>
    179         </div>
    180       </article>
    181 
    182       <article>
    183         <div class="row">
    184           <h4 class="font-weight-bold pb-2 mb-4">Events</h4>
    185         </div>
    186         <div class="row mb-4">
    187           <p>
    188             The consortium participated in different types of events across Europe. <strong>Past events:</strong>
    189           </p>
    190           {# Events will include talks presenting GNU Taler and related technologies, expert panels discussing
    191           financial problems and possible solutions, workshops to jointly work on GNU Taler integrations,
    192           usability studies with interested volunteers, and public consultations to gather ideas and requirements
    193           from the general public. #}
    194         </div>
    195 
    196         {% for year, yitem in eventsdata|groupby('date.year')|reverse %}
    197           <p><b>{{ year }}</b></p>
    198           <ul class="timeline">
    199             {% for item in yitem|sort(attribute='date', reverse=true) %}
    200               <li>
    201                 <section class="item-preview">
    202                   <header>
    203                     <h5>{{ item.date.strftime("%Y-%m-%d") }}: {{ item.title|e }}</h5>
    204                     <p class="item-date">{{ item.teaser }}</p>
    205                   </header>
    206                   <p class="item-abstract">{{ item.location }} - Speaker: {{ item.speaker }}</p>
    207                   {% if item.url_ext %}
    208                     <p class="item-date">
    209                       <a href="{{ item.url_ext }}" target="_blank" rel="noopener noreferrer">
    210                         External link: {{ item.url_ext }}
    211                       </a>
    212                     </p>
    213                   {% endif %}
    214                 </section>
    215               </li>
    216             {% endfor %}
    217           </ul>
    218         {% endfor %}
    219       </article>
    220 
    221       <article>
    222         <div class="row">
    223           <h4 class="font-weight-bold pb-2 mb-4">Deliverables</h4>
    224         </div>
    225         <div class="list-group">
    226           {% for item in conf['deliverables'] %}
    227             {% set ns = namespace(symbol='images/file-cancel.svg') %}
    228 
    229             {% if item.url_pdf is defined and item.url_pdf %}
    230               {% set ns.symbol = 'images/pdf.svg' %}
    231               {% set target_url = url(item.url_pdf) %}
    232             {% else %}
    233               {% set target_url = "#" %}
    234             {% endif %}
    235 
    236             <a href="{{ target_url }}" class="list-group-item list-group-item-action py-3 text-decoration-none">
    237 
    238               <div class="d-flex align-items-center">
    239                 <img src="{{ url_static(ns.symbol) }}" alt="" width="32" height="32" class="me-3 opacity-75">
    240 
    241                 <div class="flex-grow-1">
    242                   <div class="d-flex justify-content-between">
    243                     <h5 class="mb-1 text-dark">{{ item.title }}</h5>
    244                     <small class="text-muted">{{ item.workpackage }}</small>
    245                   </div>
    246 
    247                   {% if item.comment %}
    248                     <p class="mb-1 text-secondary small fst-italic">{{ item.comment }}</p>
    249                   {% endif %}
    250 
    251                 </div>
    252               </div>
    253             </a>
    254 
    255             {% if item.page is defined and item.page and item.page != "" %}
    256               <div class="small text-muted">
    257                 <i class="fa fa-link me-1"></i>
    258                 Further reading:
    259                 <a href="{{ item.page }}" class="text-muted text-decoration-none">{{ item.page }}</a>
    260               </div>
    261             {% endif %}
    262           {% endfor %}
    263 
    264         </div>
    265 
    266       </article>
    267 
    268       <article>
    269         <div class="row">
    270           <h4 class="font-weight-bold pb-2 mb-4">Partners</h4>
    271         </div>
    272 
    273         <div class="row mb-4">
    274           <!-- intro -->
    275           <div class="col-md-11 col-md-4 mb-4 px-md-4">
    276             <p class="w-responsive mx-auto mb-3">
    277               The NGI TALER consortium consists of 11 partners from 8 European countries (the Netherlands, Belgium,
    278               France,
    279               Germany, Greece, Hungary, Luxembourg and Switzerland).
    280             </p>
    281             <p class="w-responsive mx-auto mb-3">
    282               The consortium is diverse in terms of types of institutions, including research (Eindhoven University of
    283               Technology) and
    284               applied science universities (Berner Fachhochschule BFH), small for-profit companies (Code Blau GmbH, Taler
    285               Systems S.A., VisualVest),
    286               a structure (petites singularités), cooperative banks (GLS Bank, MagNet Bank), a foundation (Stichting
    287               NLnet)
    288               and grassroots movements (E-Seniors Association, Homo Digitalis).
    289             </p>
    290           </div>
    291         </div>
    292 
    293         <div class="row row-cols-1 row-cols-md-3 g-4 text-center">
    294           <!-- consortium board -->
    295 
    296           {% for partner in conf['partners'] %}
    297             <div class="col">
    298               <div class="card border-0 h-100">
    299                 <a href="{{ partner.url }}" target="_blank" rel="noopener noreferrer">
    300                   <img src="{{ url(partner.logo) }}" height="100" class="card-header rounded-circle z-depth-3"
    301                     alt="{{ partner.id + ' avatar' }}">
    302                 </a>
    303                 {# <!-- <div class="card-note grey-text text-muted mt-3">{{ partner.contact }}</div> --> #}
    304                 <div class="card-body h-100">
    305                   <h5 class="card-title font-weight-bold grey-text">{{ partner.name }} </h5>
    306                   {# <!-- <p class="card-text grey-text text-muted word-wrap"> {{ partner.role }} </p> --> #}
    307                 </div>
    308                 {# <!-- <div class="card-footer">
    309                 <p><small class="text-body-secondary dark-grey-text text-muted word-wrap">
    310                     <i>{{ partner.statement }}</i>
    311                   </small></p>
    312               </div> --> #}
    313               </div>
    314             </div>
    315           {% endfor %}
    316         </div>
    317       </article>
    318 
    319     </div>
    320   </main>
    321 {% endblock body_content %}