OK, well since Maurice bowed out, and Matt has been MIA (I know you're out there Matt, you can't hide forever!), we need a new owner/maintainer for WebWork. I'd volunteer to do it myself, but being that I'm the current owner for OSCore, OSUser, PropertySet, Clickstream, and OSWorkflow -- and that I don't have nearly enough time for even one of those right now, I shouldn't take on WebWork. I'd be fine handling OSWF and WebWork, though. But no more than two for me.
So that means... I'd like to start shuffling around ownership of these modules. None of this can happen overnight, since we need to see dedication before handing over the reigns, otherwise we don't get anywhere. If anyone would like to volunteer for OSCore, OSUser, PropertySet, Clickstream, or WebWork, please write back to the mailing list. We need some good, dedicated people. Only reply back if you really feel you can do a good job. This isn't a huge job -- maybe a few hours a week at the most, but it's important that you be consistent (you can't disappear for weeks on end). I know I'll be keeping a hold of OSWorkflow for now. I've got a lot of ideas and familiarity with WebWork as well, but I can't take it unless others offer to lighten my other loads. Alternatively, if there is anyone else out there qualified and has the time, please start talking about who can take on managing WebWork. Either way, I'd like for anyone interested in OSCore, OSUser, PropertySet, or Clickstream to get back to me (cc the list) as well. OK, that's it. -Pat ------------------------------------------------------- This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at: http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
