Tatsuhiko Miyagawa wrote: > At Tue, 28 May 2002 23:24:56 +0800, > Stas Bekman wrote: > > >>>Any pointers (including suggestions for the article) are welcome. >> >>When do you need to publish it? > > > I've been told that July 10th will be the deadline ;)
Great, so we have time! >>I'm working on my OSC paper (intro to >>mod_perl 2.0) partially based on the docs that Doug originally wrote >>with the new stuff I'm adding on top of it. When it's done I'm also >>planning to publish it as an article (probably a few articles). If you >>are interested we can work together on it and end up with an English and >>Japanese versions :) My work covers the new things in Apache 2.0/ >>mod_perl 2.0 / Perl 5.6-5.8 (relevant to mod_perl). > > > Sounds exciting! I'm very interested in co-working with you. I'll keep you posted then, hopefully I'll have something to show till the end of this week. >>However, I was actually holding off on publishing the articles, since I >>believe it's still early to bring a big attention to modperl 2.0. The >>docs aren't there yet and it's better to announce things in media when >>we get more prepared. Please correct me if I'm wrong. > > > I guess you mean "Early announce with sparse documents" is worse than > "Later announce with enough documents", which seems cleverer strategy. > I vote +1 for that. I'm not sure, if it's clever, I just think we better spend time finishing up things now, then answering gazillions of questions. Luckily we don't need to use marketing strategies used by commercial bodies, where marketers sell projects that are still only planned. __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
