Git is the strongest contender (vs Mercurial, Bazaar or Fossil) for the next generation of Tiki development using a distributed revision control system. This page collects the resources regarding that topic and explains the current status.
- There has been a lot of discussion about Distributed revision control, which led to Git being the best option
- There's a significant effort in migrating to Git, since whole workflow and release scripts have to be updated. The roadmap is under construction at What ToDo When Migrating To Git. And it would force changes on community members who are perfectly happy with current workflow.
- There's a discussion on an ideal Git Workflow, which will be possible once everything has been moved to Git and SVN is abandoned. And abandoning SVN would disrupt the workflow of some community members.
- A Git and SVN combined workflow will allow to add an "official" Git workflow while maintaing current SVN workflow. This offers new benefits (ex.: managing pull requests) with the least changes to the current system and it avoids forcing a change of workflow on community members. This will permit a gradual change to Git for those who are interested. If and when there is critical mass of the community that uses Git, it will be natural to implement a Git Workflow and work on What ToDo When Migrating To Git.
- A git repository is working at git.tiki.org, synced with SVN, according to Git and SVN combined workflow. It's currently being evaluated before it can be adopted by community. See Using Git with Tiki for details on how to join the evaluation team.