2015:archipelagos_in_git
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| 2015:archipelagos_in_git [2015/04/01 10:08] – created jonjagger | 2015:archipelagos_in_git [2016/06/11 14:05] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| **Duration**: | **Duration**: | ||
| **Description**: | **Description**: | ||
| - | Island: Any piece of subcontinental | + | Island: Any piece of subcontinental |
| Archipelago: | Archipelago: | ||
| \\ | \\ | ||
| Assumptions: | Assumptions: | ||
| - | * Reviewing | + | |
| - | * No one wants to review and/or merge code as their fulltime | + | * No one wants to review and/or merge code as their fulltime |
| - | * No one person should bear all that responsibility anyway | + | * No one person should bear all that responsibility anyway |
| - | | + | * Existing, nonconceptual |
| - | * Communication is always required and goes a long way to solving many of our problems, but we can't all communicate with everyone all the time on a medium | + | * Communication is always required and goes a long way to solving many of our problems, but we can't all communicate with everyone all the time on a medium |
| - | * Metaphors help understand intent | + | * Metaphors help understand intent |
| - | * Sometimes code will need to be shared between teams; it isn't always possible to divide up work by features (although appropriate interfaces help with this) | + | * Sometimes code will need to be shared between teams; it isn't always possible to divide up work by features (although appropriate interfaces help with this) |
| Basics:\\ | Basics:\\ | ||
| - | 1. An ' | + | - An ' |
| - | 2. An archipelago is identifiable as a number of islands which are " | + | |
| - | * Created as a concept to help medium to large teams manage sharing of code between areas of related work and to ease merge pain | + | |
| - | * Merging is always difficult; it's a difficult job. Archipelagos don't solve merge problems, but they do simplify them and provide conceptual assistance | + | * Merging is always difficult; it's a difficult job. Archipelagos don't solve merge problems, but they do simplify them and provide conceptual assistance |
| - | * Islands in an archipelago are related to one another purely by virtue of their proximity to one an another. If a fork/branch is close to another, it makes sense to consider it part of the same archipelago | + | * Islands in an archipelago are related to one another purely by virtue of their proximity to one an another. If a fork/branch is close to another, it makes sense to consider it part of the same archipelago |
| - | * Pull requesting to the owner of the archipelago simplifies the merge you're dealing with and still allows everyone interested in that archipelago to be party to what's going into it | + | * Pull requesting to the owner of the archipelago simplifies the merge you're dealing with and still allows everyone interested in that archipelago to be party to what's going into it |
| - | * Pull requesting the entire archipelago to " | + | * Pull requesting the entire archipelago to " |
| Advanced\\ | Advanced\\ | ||
| - | * Archipelagos can be near or far away from each other sometimes they will want to merge between each other, but this is not particularly desirable unless you combine | + | |
| - | * How do we know when to create an archipelago? | + | * How do we know when to create an archipelago? |
| - | * Feature files / executable specification.... where does it fit in? | + | * Feature files / executable specification, where does it fit in? |
| - | * Realisations from actual use with several teams totalling 20+ developers\\ | + | * Realisations from actual use with several teams totalling 20+ developers\\ |
| \\ | \\ | ||
| \\ | \\ | ||
2015/archipelagos_in_git.1427882889.txt.gz · Last modified: 2016/06/11 14:05 (external edit)