# SVN -> Git transition checklist

1. doc.php.net
    1. Update the `revcheck.php` script (includes internal conjobs/shell scripts etc)
        - do we want to switch from *distance* computing to e.g. commits count?
        - providing diff for the files
            1. GitHub - displays complete comparision between two commits, which cannot
               be limited to the single file view. We can of course create a link to the
               specific file on such page but that page can be very big and sometimes file
               diff will not be loaded without confirming
            2. git.php.net - `gitweb` can display a comparision for the single file
            3. custom solution - we can build simple script on the `doc.php.net` (which
               already needs Git repos in place anyways) in case git.php.net's design
               will be limiting; I think translators could benefit even from that simple
               changes like dropping actual `+`/`-` on the beginning of each line (personally
               I very often wanted to just copy-paste something from such diff and work
               on that in the editor)
    2. Update the tutorial
1. doc-base repository
    1. Review all the scripts, one by one, and either migrate to Git where needed or drop
       where keeping does not make sense anymore
1. PhD
    1. Review the code to make sure it has no dependencies on the SVN, update if needed
    2. Update the documentation
1. edit.php.net
    1. Decision: do we want to have edit.php.net ported before the migrations happens?
1. rsync box/systems repository
    1. Switch fetching documentation sources from Git
1. web-php
    1. Switch "edit" links in the documentation to GitHub edits or add it besides edit.php.net
       links - depends on the decision regards the editor
1. PHP Manual
    1. Look for pages mentioning SVN and update accordingly
1. Windows CHM box
    1. Probably needs an update to fetch files from Git
1. Mailing lists
    1. Probably `php.doc.cvs` needs some switch to deliver emails based on Git repository
    2. Same for all `php.doc.LANG` lists
    3. Setting up pull request notifications[?]
1. Announcements
    1. PHP.net homepage -  I know we rarely post such internal upgrades there but I think
       it is worth sharing; can also engage some new contributors
    2. Announcement on `php.doc` and each of `php.doc.LANG` mailing lists
1. more?

## Side notes
- adding Travis CI with `configure.php` to each of documentation repos
  seems like a natural and benefical future scope