Sourceforge Diaspora: Slide 3

index.html

@@ -84,14 +84,23 @@
 </section>
 
 
-
-
 <!-- Denver: you can edit above all you want -->
 <!-- bkuhn promises to not work above here -->
 <!-- bkuhn is still working on the below: -->
 
 <!-- NO ONE BUT BKUHN EDIT BELOW YET: -->
 
+<section>
+  <h3>Post-Sourceforge Diaspora</h3>
+  <ul><li>Berlios</li>
+    <li>Gna!</li>
+    <li>Savannah</li>
+  </ul>
+    <p>There have even
+        been <a href="https://www.igi-global.com/article/fork-not-fork/68147">academic
+        whitepapers</a> written about this situation as late as 2011.</p>
+      
+</section>
 
 
 

what-bkuhn-was-going-to-say.md

@@ -134,5 +134,15 @@ project spent *years* well into the 2010s trying to fully divorce from
 Sourceforge, and ironically, the successor in interest, Sourceforce, Inc.,
 realized Inkscape downloads were one of their largest downloaded projects,
 and constantly pitched us toxic revenue-sharing schemes until Inkscape
-finally escaped Sourceforge.
+finally escaped Sourceforge. [ next slide ]
+
+## Sourceforge Diaspora: Slide 3
+
+The reason some projects had such trouble with getting away from Sourceforge
+was because there wasn't a primary fork, but dozens.  Here's a list of the
+ones that Bradley could remember, but he recalls at the time there were at
+least four or five more that split the attention of the community so badly
+that, by the time AJAX and Web 2.0 came along, there was not enough
+leadership to move an old PHP+HTML application to the more interactive and
+modern looks that users were demanding by the late 2000s. [ switch slides ]