| | 1 | = Move, Copy and/or Synchronize Parts or all of Trac Instance = |
| | 2 | |
| | 3 | There are some use cases where moving, copying, synchronizing trac instances (or part of trac instances) might be benefitial: |
| | 4 | * single persons working disconnected: |
| | 5 | * they would need to get the latest information they have access right to onto a laptop. |
| | 6 | * when reconnecting to the network they need to merge their changes into the central trac instance |
| | 7 | * InterTrac: |
| | 8 | * information is entered into the wrong instance and should be moved to another one. |
| | 9 | * information should be moved to a newly created trac instance |
| | 10 | |
| | 11 | related tickets are: #1465, #1465 |
| | 12 | |
| | 13 | == some solution ideas grabbed from the mailing list and the tickets == |
| | 14 | |
| | 15 | * use import/export with csv |
| | 16 | * use (implement) versioning backenends as trac storage backend |
| | 17 | * use (implement) synchronisation based on the xml-rpc based on timeline information |
| | 18 | |
