>From the TODO file: >---------------------------------------------------- >The POE Community Wants a Bigger Hand in Development >---------------------------------------------------- >The YAPC 2001 POE BOF agreed that its members want a bigger part in >the project's development. This is great! It should reduce my >workload and generally expand POE knowledge across a larger group of >people. If I get hit by a passing blimp, life goes on without me. >For such a group to remain organized, however, I feel the need to >codify the goals and heuristics that guide my own development. >Certainly these would just be guidelines. Evolution happens, and they >may change over time as the project continues to grow up, but it's a >good idea to know going into it what's expected to come out of it. >So, what am I trying to do here? What are the decision priorities >when making trade-offs? Where do I want to go today? I find these remarks interesting - having accidentally been involved in the early days of the SAMBA and KDE development effort, I can tell you that through my own interest I can foresee a very similar and vibrant future for POE. Of all the thousands of projects out there, POE is the only one that has captured my imagination in the last year or so. Guessing from my past good luck/intuition, perhaps it would be wise to start to prepare for the day POE may suddenly becomes another high-visibility project. Totally off the record, I've been clandestinely working on my own POE-based application, which could potentially bring interest from other large and active communities to POE very quickly if/when it's released to the public domain. I'm being paid to work on this project for internal needs, so it's very possible it could lead to a whole new dimension to POE if it's taken up by others as well. Well - having expressed my intentions, I'm going to go back to keeping my mouth shut, and lurking on this list for now. I thought that it was only fair that I give you all some warning, since you asked. I look forward to the CORBA-like abstraction work being down, getting the chance to learn IKC, and the renaming of yield() to something else. ;) - MW -----Original Message----- From: Rocco Caputo [mailto:[EMAIL PROTECTED]] Sent: Sunday, July 15, 2001 2:53 PM To: [EMAIL PROTECTED] Subject: Version 0.15 is on the web and PAUSE [This announcement sounds a little odd because it's also going to be posted to comp.lang.perl.announce.] Good morning. It's my pleasure to announce that POE 0.15 has been uploaded to the PAUSE. It will arrive at your favorite CPAN mirror after the customary propagation delay. It's available from two web sites right now, if you'd rather not wait for it to reach the CPAN site of your choice: POE's main web site: http://poe.perl.org/ SourceForge : http://sf.net/projects/poe/ It's been some 80 days and four development releases since 0.14. Thanks to everyone who sent in feedback and patches. If you would like to receive announcements of POE's development releases, please send a message to <[EMAIL PROTECTED]>. You will receive instructions for subscribing to POE's mailing list. Change highlights since 0.14: * Added a TODO file to the distribution. This is part changes roadmap and mostly a feature wishlist. * A second alarms interface. It's a little more complex than the original one, but it gives programs more control over timers. * XyzState parameters in wheels have been renamed to XyzEvent. This doesn't break existing code yet, but it is expected to in September. See the TODO file for exact breakage dates. * Documentation and installation fixes. POE won't clobber Devel::Trace anymore. * Removed use of features specific to perl 5.6.1. POE should once again be compatible with perl 5.004_05 and possibly older. * Better memory leak checking, and a leak fix in the signals code. * Better dependency checking and more graceful failure in the face of adversity. * Better Win32 support. Instructions for installing POE with ActiveState's PPM. You can read more about this, historical, and future releases on the web: The full CHANGES file: http://poe.perl.org/poedown/CHANGES The full README file : http://poe.perl.org/poedown/README The full TODO file : http://poe.perl.org/poedown/TODO Thanks for reading! -- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sourceforge.net
