There are important considerations governing the Mozilla Public License in use by Taiga. Please be sure you are familiar with your rights and obligations before starting to work on the Taiga code.
Since the open source license covering Taiga is MPL 2.0, you can freely clone/fork the repo and make any modifications you want. Just remember the basic condition that the MPL brings to the table: any Taiga instance must easily provide to all users a link to the source code that is running that particular Taiga service. See related MPLS FAQs Q8 and Q9.
If you don’t make any changes to the code, the link is pretty simple, it’s just a link to Taiga’s github page. But if you intend to make adaptations or changes, you must provide a (de-facto) zero-cost way to obtain the complete modified source code. The easiest way would be to fork the repo on github and point your users to that forked repo (you can place that link in the documentation somewhere).
Our repo is quickly evolving so we suggest you keep careful track of our changes, that way you can easily benefit from our own improvements “for free”. Some users have decided to use our Taiga cloud instance together with our public API and only develop a separate integration layer that effectively lives outside the Taiga source code. By doing this you can “forget” about changes taking place at the Taiga source code.
Your needs will dictate which option suits you better.
Please read the Mozilla Public License covering Taiga.
If you would like to discuss specific dual-licensing with us, contact us a firstname.lastname@example.org. Note: we moved from AGPL 3.0 to MPL 2.0 because it gave us more control over the Taiga trademark and lessened the restrictions to redistribute modified code while still making sure people get informed about Taiga code’s presence in any derivative work.