wiki:Moving to Git

Version 3 (modified by, 15 years ago) (diff)


Proposal for moving WebKit development to Git

Benefits of moving to Git

  • A large number of WebKit devs are already using git-svn
  • All major organizations involved with WebKit development have significant sub-sets of devs already using git-svn
  • Would make code review easier
  • Would allow us to do away with manually editing/resolving ChangeLog files
    • git diff already includes ChangeLog entry
    • bugzilla could be modified to point to a private branch for code review, making code review easier and more thorough.
    • no more pastebin, just a simple git push
  • Distributed nature of git allows to commit even when server goes down
  • Those who are working far away / a slow connection can have local git mirrors rather then going through the one svn server (A real issue today)
  • Branching is cheap with git which would encourage the practice of developing unstable features in smaller chunks
  • We have a significant amount of git knowledge amongst various WebKit devs for training the remaining devs
  • WebKitTools/Scripts already contains lots of git coverage
  • Using GitHub or setting up our own gitorious server for WebKit would allow others to more easily see the different projects that are going on.
  • Please fill in here...

Costs of moving to Git

  • X number of WebKit developers do not know git and would have to learn a new tool
  • Git itself can be hard to learn and hard to use
  • Please fill in here...

Problems to be solved

  • Bugzilla integration
  • A common suggested workflow would need to be worked out
  • An option for contributing for those who are unwilling/unable to learn git?
  • Please fill in here...


  • Unsure of the current status of Git on Windows and how many Windows developers we have.
  • Find out just how many git users we have who actively contribute to WebKit
  • Find out how many svn users we have and there feelings on moving to git
  • Please fill in here...