The ideal situation for me right now would be if someone would pay me to develop Scoop. That's my biggest concern-- I could and would continue to finance kuro5hin.org out of pocket if necessary, or perhaps whoever wanted to pay for Scoop development would agree to make kuro5hin.org financing part of the deal, as a sort of "testbed" and with a little "sponsored by" notice.
"Why would someone want to do this?" you might ask. Well, I can think of several ways Scoop might be profitable for some enterprising company. Selling the application on CD, and providing service and support, a la RedHat is one. Providing preinstalled servers running Scoop for clients, a la cobalt (sort of) is another. With some more development, Scoop could be a nifty corporate intranet news server, and with some other applications bundled in, it'd probably be the heart of a nice little intranet/extranet application. Not to mention the potential ad revenue that could come from a "news" section being added to some existing websites.
Like I said, that situation would be ideal. Less than ideal would be if I had to somehow leverage kuro5hin.org to fund further scoop development. I really, really don't want to do that, so let's pretend that's not an option for now.
Of course the final option, and the default one if nothing else changes, is maintain the status quo. I work on Scoop in my free time, maybe some other perl hackers get a hold of the code and figure out how it works (currently no easy task!) and help me out. I will keep working on it, regardless, but development is likely to be stop-and-go as other pressures come and go. This is workable, but not ideal.
But never fear. Scoop will always remain GPL. I will not agree to any deal which requires that that change (unless they want me to "Artistic" or "BSD" license it :-). And there might be some terrific option that I'm completely overlooking. It's the era of new business models-- anyone have one that would work here?