Idées de projets
Cette page présente diverses idées de projets liés à GNU Taler sur lesquels la bonne personne pourrait travailler, éventuellement dans le cadre d’un NLnet NGI Open Call. Pour chaque idée, nous donnons une estimation approximative du temps qu'elle devrait prendre et de la difficulté qu'elle présente.
Idées ouvertes pour les projets
- Update Pretix integration to latest Taler APIs, making use of the newly added support for WebHooks and using refunds, possibly via the rewards API (120h, moderate difficulty)
- Extend the Point-of-Sale App with multi-currency support. The configuration should specify multiple currencies and their conversion rate. During payment, the user should be given the choice of currency to pay with. (30h, easy)
- Extend the Point-of-Sale App with the ability to enter a table number (for restaurants), and include the table in the contract terms. Implement a second app that shows active orders to kitchen staff and allows them to mark orders as completed. (300h, moderate difficulty)
- Add self-service Web frontend to the merchant backend that allows non-admin visitors to order (and pay for) the creation of merchant instances hosted by a (trusted) merchant backend provider. This should make it trivial for non-technical users to sign up at a merchant backend hoster to obtain an instance at that hoster. The Web frontend should collect contact information, warn the user if their service agreement is about to expire, and delete (and eventually purge) instances for which the payment has expired. (600h, moderate difficulty)
- Implement a currency conversion service by enhancing the merchant backend to allow a wallet to pay with one currency for signatures on blindly signed tokens in another currency. (300h, hard)
- Add the merchant backend database plugin that supports sqlite3. (600h, tedious)
- Add sales analytics (how many products are sold when) to the merchant backend (120h, easy)
- Add merchant backend inventory alerts (Webhooks that fire when inventory falls below certain thresholds) to the merchant backend (60h, easy).
- Add exchange command-line tool to re-encrypt exchange KYC attributes to a different symmetric key to enable changing the encryption key (for example, when it was accidentally disclosed). (60h, easy)
- Implement improved coin-selection algorithm in wallet-core that is better at minimizing state size and customer fees, and spends coins before they would require a refresh (to prevent expiration). (300h, hard)
- A wallet should have a way to export its reserve public key (for P2P payments) as a QR code and users should be able to scan this QR code to trigger arbitrary payments into that wallet. Wallets should periodically fetch the reserve history of their reserve to observe such payments. This would be like the merchant backend templating mechanism (buyer enters amount and subject, or they might also be pre-set in the QR code) but work without a merchant backend or bank account (transfers go wallet-to-wallet). (600h, moderate difficulty)
- See our bugtracker for further ideas.