Update another comment about MongoDB and AGPL

dosp-survey.ltx

@@ -730,8 +730,19 @@ collapse down to a dual-licensing scheme with proprietary and A/GPL options.
  Did any BUSL adopters seriously consider adopting AGPL? If not, why not?
  If so, why did they end up preferring BUSL's approach?
 
-% TODO I thought I saw something about MongoDB considering AGPL but
-% deciding that its (non-DOSP) noncompete license model was preferable.
+% MongoDB was previously licensed under AGPL and then switched to SSPL,
+% which it has maintained should be considered an Open Source license.
+% The OSI review process didn't agree, although it was controversial.
+% Apparently from MongoDB's point of view, it was just trying to shift
+% from one Open Source license to another (that would disincentivize
+% some competitive behavior that the developers found unfair or
+% undesirable).  But from the outside world's perspective, since SSPL
+% isn't uniformly accepted as Open Source, this was a switch from Open
+% Source to proprietary (and also not DOSP because there is no time
+% period after which the code reverts to a conventional license).
+%
+% I haven't managed to find out whether it's correct that AWS was
+% offering MongoDB-as-a-service before the relicensing in 2018.
 
 	\item Taxonomy of BUSL Additional Use Grants.