From 77508a6b77b1947b8654a16501ae77beaf85e3fa Mon Sep 17 00:00:00 2001 From: "Bradley M. Kuhn" Date: Sun, 2 Feb 2025 12:49:14 +0100 Subject: [PATCH] Sourceforge Diaspora: Slide 3 --- index.html | 13 +++++++++++-- what-bkuhn-was-going-to-say.md | 12 +++++++++++- 2 files changed, 22 insertions(+), 3 deletions(-) diff --git a/index.html b/index.html index 97a13c5..27fc5a6 100644 --- a/index.html +++ b/index.html @@ -84,14 +84,23 @@ - - +
+

Post-Sourceforge Diaspora

+ +

There have even + been academic + whitepapers written about this situation as late as 2011.

+ +
diff --git a/what-bkuhn-was-going-to-say.md b/what-bkuhn-was-going-to-say.md index 921ed9a..654567e 100644 --- a/what-bkuhn-was-going-to-say.md +++ b/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 ]