I'd like to suggest a thread on general@ for each of those projects who believe they are close to graduation, but not sure what to do next. To kick off such a thread, email *me* with a summary (like you do for status reports) of where your project is now in terms of community, code, releases and functionality. Don't forget to tell everyone *what* the code does, the language it's coded in, etc :)
Most importantly, point out what help *you* think it needs. (Once launch the discussion your fellow podling members can offer their perceptions and opinion about what's needed, so we'll get a balanced view.) Here are the rules to keep this fun... Reply to *me*, not the list, so I can put one podling up for help at a time. Keep this subject so I can keep them in their own folder. If I see something missing, I'll help with editing the appeal so that everyone has enough information to jump in if they want to help. This also lets you remain anonymous, if you prefer - just tell me upfront. Only one of these at a time, let's give each podling our undivided attention on [EMAIL PROTECTED] I'll post the first appeal just as soon as I get it. Exactly one week of general@ discussion to help solicit the advise, help needed, advise, and possibly attract some other helpers reading general@ to your podling-dev@ list. Then let another have their turn. After a week, I'll kick off the second podling based on whichever appeal is next in my email queue, then the third, etc etc. Betting we can discuss and help out four podlings before we take a break for the holidays, and pick back up in January. Anyone want to give this a try? Bill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
