| 1 | | Coming Soon |
| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | = Proposal for moving WebKit development to Git = |
| | 4 | |
| | 5 | == Benefits of moving to Git == |
| | 6 | * A large number of WebKit devs are already using git-svn |
| | 7 | * All major organizations involved with WebKit development have significant sub-sets of devs already using git-svn |
| | 8 | * Would make code review easier |
| | 9 | * Would allow us to do away with manually editing/resolving ChangeLog files |
| | 10 | * git diff already includes ChangeLog entry |
| | 11 | * bugzilla could be modified to point to a private branch for code review |
| | 12 | * no more pastebin, just a simple git push |
| | 13 | * Distributed nature of git allows to commit even when server goes down |
| | 14 | * Branching is cheap with git which would encourage the practice of developing unstable features in smaller chunks |
| | 15 | * WebKitTools/Scripts already contains lots of git coverage |
| | 16 | * We have a significant amount of git knowledge amongst various WebKit devs for training the remaining devs |
| | 17 | * GitHub for WebKit would be cool :) |
| | 18 | * Please fill in here... |
| | 19 | |
| | 20 | == Costs of moving to Git == |
| | 21 | * Git is still very slow and flaky under windows |
| | 22 | * The majority of WebKit devs are used to using svn and would need to learn this new tool |
| | 23 | * Git itself can be hard to learn and hard to use |
| | 24 | * Please fill in here... |
| | 25 | |
| | 26 | == Problems to be solved == |
| | 27 | * Bugzilla integration |
| | 28 | * Workflow would need to be worked out |
| | 29 | * An option for contributing for those who are unwilling/unable to learn git? |
| | 30 | * Please fill in here... |
| | 31 | |
| | 32 | == TODO == |
| | 33 | * Find out just how many git users we have who actively contribute to WebKit |
| | 34 | * Find out how many svn users we have and there feelings on moving to git |
| | 35 | * Please fill in here... |
