What is Taiga?

On the first view Taiga (taiga.io) is a open source Trello replacement. On the second it is way more than that. Taiga does offer a lot more integration into Scrum and Kanban Workflow than Trello could ever do (even if you would pay for all those neat power-ups). Taiga is offered as hosted and self-hosted (as it is completely open source) and does offer all features in payed and free accounts on the hosted solution. Unlike tools like Gitlab where there are premium features that are held back for the enterprise offering this tool is developed in the open (https://github.com/taigaio).

Taiga does offer proper Backlogs and Sprints that are connected with each other. In Trello you loose the connection between your Backlog and Sprintboard at some point and tracking does get harder.

On top of that Taiga offers importers for Trello, Github Issues, Jira and Asana. These would be very helpful for teams to migrate away from current tools and organize everything in one place that was developed with Scrum and Kanban in mind.

Why do we need a FATE Sync?

Automatic downsyncing of FATE features into Taiga would ease the job of POs, TPMs and SMs. You won't have to enter FATE features in your teams Scrum Board anymore as you would do now in Trello. To make it easier, it would be a good idea to support downsyncing first as this doesn't harm the FATE database.

How could it work?

A user creates a custom search query on FATE which results in a list of features that are relevant for the Backlog of the Scrum Team. This list will be checked against the current backlog and updated in Taiga (minimum including the title, FATE number, features description including customer and business case). It should also check against current sprints to make sure that it is not added as a duplicate to the backlog.

Taiga does offer some APIs to achieve that. On FATE side I am not sure, but as there is a desktop client for it I assume there also is an API for it.

Looking for hackers with the skills:

python django angular angularjs angular.js fate taiga

This project is part of:

Hack Week 17

Activity

  • over 7 years ago: kbaikov liked this project.
  • over 7 years ago: SLindoMansilla liked this project.
  • over 7 years ago: aspiers liked this project.
  • over 7 years ago: suntorytimed disliked this project.
  • over 7 years ago: suntorytimed left this project.
  • over 7 years ago: suntorytimed liked this project.
  • over 7 years ago: suntorytimed disliked this project.
  • over 7 years ago: suntorytimed liked this project.
  • over 7 years ago: suntorytimed liked this project.
  • over 7 years ago: suntorytimed liked this project.
  • over 7 years ago: suntorytimed added keyword "taiga" to this project.
  • over 7 years ago: suntorytimed added keyword "fate" to this project.
  • over 7 years ago: suntorytimed added keyword "python" to this project.
  • over 7 years ago: suntorytimed added keyword "django" to this project.
  • over 7 years ago: suntorytimed added keyword "angular" to this project.
  • over 7 years ago: suntorytimed added keyword "angularjs" to this project.
  • over 7 years ago: suntorytimed added keyword "angular.js" to this project.
  • over 7 years ago: suntorytimed started this project.
  • over 7 years ago: suntorytimed originated this project.

  • Comments

    Be the first to comment!

    Similar Projects

    Song Search with CLAP by gcolangiuli

    Description

    Contrastive Language-Audio Pretraining (CLAP) is an open-source library that enables the training of a neural network on both Audio and Text descriptions, making it possible to search for Audio using a Text input. Several pre-trained models for song search are already available on huggingface

    SUSE Hackweek AI Song Search

    Goals

    Evaluate how CLAP can be used for song searching and determine which types of queries yield the best results by developing a Minimum Viable Product (MVP) in Python. Based on the results of this MVP, future steps could include:

    • Music Tagging;
    • Free text search;
    • Integration with an LLM (for example, with MCP or the OpenAI API) for music suggestions based on your own library.

    The code for this project will be entirely written using AI to better explore and demonstrate AI capabilities.

    Result

    In this MVP we implemented:

    • Async Song Analysis with Clap model
    • Free Text Search of the songs
    • Similar song search based on vector representation
    • Containerised version with web interface

    We also documented what went well and what can be improved in the use of AI.

    You can have a look at the result here:

    Future implementation can be related to performance improvement and stability of the analysis.

    References


    Liz - Prompt autocomplete by ftorchia

    Description

    Liz is the Rancher AI assistant for cluster operations.

    Goals

    We want to help users when sending new messages to Liz, by adding an autocomplete feature to complete their requests based on the context.

    Example:

    • User prompt: "Can you show me the list of p"
    • Autocomplete suggestion: "Can you show me the list of p...od in local cluster?"

    Example:

    • User prompt: "Show me the logs of #rancher-"
    • Chat console: It shows a drop-down widget, next to the # character, with the list of available pod names starting with "rancher-".

    Technical Overview

    1. The AI agent should expose a new ws/autocomplete endpoint to proxy autocomplete messages to the LLM.
    2. The UI extension should be able to display prompt suggestions and allow users to apply the autocomplete to the Prompt via keyboard shortcuts.

    Resources

    GitHub repository


    Improvements to osc (especially with regards to the Git workflow) by mcepl

    Description

    There is plenty of hacking on osc, where we could spent some fun time. I would like to see a solution for https://github.com/openSUSE/osc/issues/2006 (which is sufficiently non-serious, that it could be part of HackWeek project).


    Improve/rework household chore tracker `chorazon` by gniebler

    Description

    I wrote a household chore tracker named chorazon, which is meant to be deployed as a web application in the household's local network.

    It features the ability to set up different (so far only weekly) schedules per task and per person, where tasks may span several days.

    There are "tokens", which can be collected by users. Tasks can (and usually will) have rewards configured where they yield a certain amount of tokens. The idea is that they can later be redeemed for (surprise) gifts, but this is not implemented yet. (So right now one needs to edit the DB manually to subtract tokens when they're redeemed.)

    Days are not rolled over automatically, to allow for task completion control.

    We used it in my household for several months, with mixed success. There are many limitations in the system that would warrant a revisit.

    It's written using the Pyramid Python framework with URL traversal, ZODB as the data store and Web Components for the frontend.

    Goals

    • Add admin screens for users, tasks and schedules
    • Add models, pages etc. to allow redeeming tokens for gifts/surprises
    • …?

    Resources

    tbd (Gitlab repo)


    Update M2Crypto by mcepl

    There are couple of projects I work on, which need my attention and putting them to shape:

    Goal for this Hackweek

    • Put M2Crypto into better shape (most issues closed, all pull requests processed)
    • More fun to learn jujutsu
    • Play more with Gemini, how much it help (or not).
    • Perhaps, also (just slightly related), help to fix vis to work with LuaJIT, particularly to make vis-lspc working.


    OpenPlatform Self-Service Portal by tmuntan1

    Description

    In SUSE IT, we developed an internal developer platform for our engineers using SUSE technologies such as RKE2, SUSE Virtualization, and Rancher. While it works well for our existing users, the onboarding process could be better.

    To improve our customer experience, I would like to build a self-service portal to make it easy for people to accomplish common actions. To get started, I would have the portal create Jira SD tickets for our customers to have better information in our tickets, but eventually I want to add automation to reduce our workload.

    Goals

    • Build a frontend website (Angular) that helps customers create Jira SD tickets.
    • Build a backend (Rust with Axum) for the backend, which would do all the hard work for the frontend.

    Resources (SUSE VPN only)

    • development site: https://ui-dev.openplatform.suse.com/login?returnUrl=%2Fopenplatform%2Fforms
    • https://gitlab.suse.de/itpe/core/open-platform/op-portal/backend
    • https://gitlab.suse.de/itpe/core/open-platform/op-portal/frontend