>> ...
>> 3. I'm interested in hearing what you have to say about the design of a
>> new SMServer, even if you're hysterical about. But I would appreciate it if
>> you would allow me to respond in my own time.

As you may know, I put a lot of time and thought and work into
SqueakMap.  The goal has always been for the community to have one
single source for information about all or most Squeak-based software,
to the extent that, anyone who wants published software to be noticed
by Squeaker's will want it to be "in Squeak's app store" too.

When you first said replace the server, I thought you meant replace
the implementation and look-and-feel of the web-UI per your
discretion.  That would be great.  Not only would the community end up
with a new SM server running on 4.5/Cog, it'd also be a
signature-example of a web-app to learn from that has browse, search,
user-accounts and a callout API.

Then when I saw your revamp of the requirements and that something
about the "closet" and, remembering past events, I wondered while I
was reading it whether all my work had already gone "poof".  Had to
check.  Whew!  Downloaded a backup of entire SqueakMap.

We don't have to be friends to do good for the SqueakMap server
(though it would be preferable, of course).  I've had this on my own
to-do list to replace because I want to learn web and it's a good
example-app.  I don't think it'll be a "quick-and-done" at all,
because all the requirements serve a needed purpose and integrate into
a overall process.  If you're willing to retain "SqueakMap" as we know
it today, with the domain model and all the critical functionality
intact, I'd welcome that.