Re: draft of press release
Philippe M. Chiasson wrote: Apache Software Foundation Releases mod_perl 2.0, Bringing Full Apache 2 API to Perl Developers Should we call this mod_perl 2.0 or more precisely mod_perl 2.0.0 ? 2.0 is perfect. I'd try and mention something about APR as well in there. Not too much, but some. Hmm, yes, but that might be confusing. It allows you to run apps outside Apache :) This release has received extensive testing, both from automated tests built with the new Apache::Test framework and from users. mod_perl's test suite now includes over more than 2500 individual functionnal tests, compared to mod_perl 1's modest 400 ... drop the mp1 comparison. just keep the first half One thing I'd like to see too is is? end of transmission? -- __ Stas BekmanJAm_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]
Re: draft of press release
Perrin, one more thing you may want to mention. Quoting Robert Spier: qpsmtpd (qmail-perl-smtpd, which really doesn't have much to do with qmail anymore) http://qpsmtpd.develooper.com/ contains a mod_perl 2 backend -- not for HTTP -- but to do SMTP. Apache 2 was re-architected to be more protocol agnostic - so you can use it for almost any connection based protocol. -- __ Stas BekmanJAm_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]
Re: draft of press release
Perrin Harkins wrote: On Monday 23 May 2005 2:49 am, Stas Bekman wrote: should mention that input can be filtered as well. What's a good example application for that? I'm not aware of one in perl, but ssl is implemented as an input filter. But may be just mentioning will be fine. * Extensible high-speed HTTP request parsing library, libapreq2, already in use by other Apache 2 modules. does it really belong here? I only included it because I had an old e-mail from you asking me to. I'll take it out. Hmm, I'm very inconsistent, am I? :) Let's ask Joe. Joe, what do you think, should we announce libapreq as a part of mod_perl 2.0 press release? To me the main obstacle is that it is not released yet. May be add a long list of companies using mod_perl? some names from our site and more from http://www.masonhq.com/?MasonPoweredSites ? I don't want to make a long list out of it because it could start to sound desperate, but a few more might fit. +1 -- __ Stas BekmanJAm_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]
Re: draft of press release
Philip M. Gollucci wrote: Perrin Harkins wrote: Are you talking about separate pools of interpreters perl vhost? Is that really working? I donn't think is works yet as this need will use the perlchild MPM which isn't finished and isn't currently being actively developed by httpd. Not quite. It does work even with the prefork mpm. But there are issues. -- __ Stas BekmanJAm_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]
Re: draft of press release
Joe Schaefer wrote: Stas Bekman [EMAIL PROTECTED] writes: Let's ask Joe. Joe, what do you think, should we announce libapreq as a part of mod_perl 2.0 press release? To me the main obstacle is that it is not released yet. I don't see the harm in including it. libapreq2 is beta-quality now, people are already using it, and I expect an official 2.06 release to emerge sometime in (early) June. In which case go for it Perrin. -- __ Stas BekmanJAm_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]
Re: About putting the blame on other shoulders
Andreas J Koenig wrote: On Tue, 28 Dec 2004 00:09:07 -0500, Stas Bekman [EMAIL PROTECTED] said: Will it not also affect us who build mod_perl applications and want an easy-to-use installer to just work for people who download our software? Frankly, I don't think that it should be fine for just the dedicated mod_perl developer. This is one place where PHP is kicking the crap out of us. us == perl, once PAUSE is fixed, and CPAN clients are adjusted, it will just work. Stas, please stop propagating this fairy tale. The danger is, that people will believe you. This I call unfair propaganda as it tries to put the blame on somebody else's shoulders. That's not a very promising strategy to solve problems. Listen carefully: it is very unlikely that PAUSE and CPAN get fixed as you call it. There is no solution at hand and 4 people who you know well and who in turn know the problem domain very well have agreed and have told you so. So please stop telling untruth. Andreas, what exactly do you call untruth? My attempt to make PAUSE/CPAN better and accomodate the growing community needs? Why is that untruth? It's not a danger that people will believe me, it's a hope. If enough people believe in that may be things will change. Things shouldn't be cast in stone and they should evolve as the world evolve. I truly don't understand why you refuse to believe that CPAN/PAUSE needs to grow. Re: About putting the blame on other shoulders It's not putting blame on other shoulders. It's an attempt to actually solve things. You know very well, that I didn't just say it's PAUSE/CPAN problem. I've spent hours trying to find a solution. I've even found a person who have agreed to implement the required changes. And all you can say: put the blame on other shoulders? thanks so much for giving me so much credit. -- __ Stas BekmanJAm_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]
Re: About putting the blame on other shoulders
Cure wrote: Everybody needs to STEP BACK and realize how much work and soul Stas has put into mod_perl. He deserves A LOT OF CREDIT. Keep up the Good work Stas. Thanks Cure, for the kind words... but we are talking about a different kind of credit here. Andreas has put just as much work and soul if not more into PAUSE/CPAN. I was talking about the credits of actually trying to resolve the current conflict, rather than just trying to make someone else do the work. -- __ Stas BekmanJAm_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]
Slashdot | Help Test mod_perl 2 Release Candidates
My submission to /.org made it to the Apache section: http://apache.slashdot.org/apache/04/12/25/1414211.shtml?tid=145tid=2 It's about asking to help testing the mp2-RCs. -- __ Stas BekmanJAm_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]
Re: slashdot php article
allan juul wrote: Perrin Harkins wrote: On Wed, 2004-12-22 at 07:56 +0100, allan juul wrote: it would be cool if it somehow somehwhere were more visible for everybody. for instance, if ASF on the menu on http://apache.org/ had a big fat checked mark and the words Apache2 compatible next to Perl, Jakarta or which ever was compatible with Apache2 (obviously many of these menuitems are not httpd- related) PHP is just as compatible with apache 2 as mod_perl 2 is. The threading problems are in the libraries, which is where Perl's threading problems are as well. aha - hmm, if that's the case why aren't *we* worried about people upgrading to Apache2 like the PHP folks apparently are, as seen in the slashdot article ? IOW, whats the big difference in the mod_perl community making an upgrade suggestion versus PHP making a non-upgrade suggestion if PHP is just as compatible with apache 2 as mod_perl 2 is ? [sorry for getting a bit off topic here, but i'm just getting a little bit worried that the PHP folks actually are right here] They are right. But there is not much to worry about. Those problems aren't modperl ones, but mostly CPAN modules' ones. Once people will discover problems they will fix those. mod_perl2 is probably the first real product that will give a real test to CPAN modules under threads. That's said I think there are a few problems to solve in modperl, but we will get there and fix those as soon as they are discovered, so again nothing to worry about. -- __ Stas BekmanJAm_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]
Re: slashdot php article
also, i don't know if this true, but i like the idea of mod_perl being an Apache module more than a perl module. And i like the idea of mod_perl versions following Apache versions. So when Apache releases Apache 3.0 [which surely will be a major release], mod_perl3 will follow in the footsteps. it sort of gives the impression that mod_perl is a official professional partner I don't think we will have another choice. though if Apache 2.2 will be made possible to work with the current mp2, there is no reason to release mp2.2, unless it'll require Apache 2.2 to work. -- __ Stas BekmanJAm_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]
Re: misc advocacy ideas
allan juul wrote: Quoting Stas Bekman [EMAIL PROTECTED]: Most of the things in the docs, at least mod_perl 1.0 guide are FAQ. It was originally written based on frequently asked questions on the list. yes, i understand that now. in a nutshell i see a FAQ as a short full stop page where one can quickly view commonly asked questions. let's take perl itself as an example. sometimes i forget how to do a directly search replace in a file (in old perls you had to create tmp files and unlink them afterwards). this is not something i do very often so i tend to forget the syntax. but i also know that this would be a pretty common thing for people to do hence i look first in the perl FAQ. the infamous Sometimes it Works, Sometimes it Doesn't problem. i personally consider it a FAQ. if you were a mod_perl beginner but knew about this problem already (but couldn't remember how to solve it) how would you go about ? i see three approaches 1) look on perl.apache.org (how to find this answer is not that easy or is it ? what would you search for - how would you hyperlinnk-navigate ?) 2) ask the question on the mailing list 3) search elsewhere like google.com. horror! Right, I've posted a link to http://perl.apache.org/docs/1.0/guide/frequent.html in the other post. Allan, may I suggest that may be you don't realize how much information there is in our docs and how hard it's going to be to decide what should be in the FAQ and what not? i certainly know there's a lot of information. i even think you know i know :) I do :) would you go along if i (if i can fine the time) took the task of simply compiling a small list a bit like the one i sent as an example in an earlier mail, the faq answers would then point to the real doc ? sure, but in pod of course :) and I'd suggest to start with mp1 specific ones, since mp2 docs aren't there yet. If you really want to help with docs, the best thing you can do now is start porting mod_perl 1 docs to mod_perl 2 docs, since that's the biggest hole now. mod_perl 1 is going to phase out, and 99.9% of the questions in the next year are going to be about mp2. We can't write a FAQ for that since things are still not there. But filling the gaps in the normal docs is what's the most important thing at the moment, if you ask me. i don't think a FAQ should be mod_perl2 og mod_perl1 specific. but i agree that getting the actual documentation right is much more important than a FAQ. but unfortuantely , im not in a position to help on that No problem. -- __ Stas BekmanJAm_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]
Re: posting news on perl.apache.org
Perrin Harkins wrote: On Mon, 2004-12-13 at 16:29 -0500, Stas Bekman wrote: No news is better than stale news. So I'm really -0 on starting any news sections. We tried this before, it never worked. Really? I don't remember that. On the old site? Updates were kind of difficult back then. Correct, the old site. The only way I can see this working if someone volunteers to keep it up2date and really does the work, and not for the first week. I volunteered for this, and I will keep it going. perrin++. I guess in the worst case if things stale down, we can always remove it later. perl.apache.org is really a documentation site, it's not a news site. Perhaps someone could start /.org style modperl news site, in which case it should be much easier to keep it alive, by just letting others post stories. perl.apache.org could link to it and have RSS feed to it. I will work on providing an RSS feed later, but I think it's important to have news on the front page, like php.net and most others do. But RSS feed to what? Or do you mean RSS feed of perl.apache.org to other sites? I was thinking to have something like modperl.use.perl.org or elsewhere where there will be news posted and just have perl.apache.org include RSS to that site. So one doesn't change anything on perl.apache.org. -- __ Stas BekmanJAm_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]
Re: mod_perl usage stats continue to decline
Frank Wiles wrote: On Mon, 01 Nov 2004 19:18:47 -0500 Stas Bekman [EMAIL PROTECTED] wrote: You mean the decline is because more and more people move to the front-/back-end setup, and people aren't just moving to php? Oh I'm sure some of the decline is people moving to PHP, Python, Java, etc... but I don't think that we're losing as many people as that survey says. The reason I say that is because doing a default install of Apache2/mp2 via the instructions on perl.apache.org, my server at home doesn't report that it is using mod_perl. I'm sure other people are in similar situations where they don't even realize their server isn't claiming to be mod_perl powered. I'm not saying that we shouldn't do that. But I think that no matter how things are configured by default now, both stats counters give a good indication that the user base is going down. Maybe we should put together a quick howto on fixing that and suggest it on the mailing list? Do you think it'll have any impact when we talk about hundreds of thousands of users who aren't on the list and will never reach our site? What technique to help the scanners were you thinking about? I wasn't really thinking about a scanner technique, but you're I wasn't talking about the scanning technique. But the approach that will tell the scanners that mod_perl is there :) If user sets ServerToken to Off, you can't do much. And you can't enable it by default since some believe it's a security issue. right we wouldn't reach everyone via the mailing list. However, if we could put the howto up on the website, mention it on the list, etc it couldn't hurt to help boost those numbers. It wouldn't be anything drastic, but shouldn't be much work for us and/or the users. Sure, but I still want to hear first, what do you have on your mind, that you want to propose to users? While I think the NetCraft survey is important, maybe we should attack this another way. Create our own registered users page, like the Linux Counter site, where mod_perl users could list their sites. This still wouldn't catch everyone, but every little bit helps. Personally, I doubt we really want to do that. But if others are interested, by all means go for it. I just think noone will really care, and we will have the efforts wasted, which otherwise could be directed at better venues. But what do I know :) Please don't consider that as a discouraging note :) -- __ Stas BekmanJAm_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]
Re: Open Source Web Book | Content | mod_perl
Frank Wiles wrote: On Thu, 16 Sep 2004 16:59:53 -0400 Stas Bekman [EMAIL PROTECTED] wrote: Frank Wiles wrote: On Thu, 16 Sep 2004 16:44:16 -0400 Stas Bekman [EMAIL PROTECTED] wrote: So, are there any volunteers to take over those articles/resource maintenance? It shouldn't be to hard to get a cvs commit access, oncethe patches start flowing in. Is that everything under /docs/offsite/ ? That's correct. I'll take it over. It'll probably be a week or so before I have time to start on it, but it shouldn't be much work to clean it up and keep my eyes open for new stuff from here on out. Thanks Frank. BTW, I've found those while trying a9.com, the new search engine. http://a9.com/mod_perl -- __ Stas BekmanJAm_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]
Debugging mod_perl with a symbol audit - Builder.com
Found this article: http://builder.com.com/5100-6371-1058784.html Debugging mod_perl with a symbol audit November 4, 2002 Not sure who wrote it. Should we link to it? -- __ Stas BekmanJAm_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]
Open Source Web Book | Content | mod_perl
And I've found this too: http://www.opensourcewebbook.com/contents/mod_perl/ -- __ Stas BekmanJAm_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]
Re: Content Management with Bricolage on Perl.com
David Wheeler wrote: The first in a series of articles on Bricolage that I'm writing for O'Reilly and Associates, Content Management with Bricolage, has been published on Perl.com. http://www.perl.com/pub/a/2004/08/27/bricolage.html This article targets organizational decision makers by offering a high-level overview of the content management ecosystem and how Bricolage compares to other approaches to content management. It also highlights some of the more important features of Bricolage, as well as a number of the Websites currently powered by Bricolage. Future articles in the series will cover installation, document modeling, templating, and customization. David++! -- __ Stas BekmanJAm_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]
Re: ping!
And there are also the Apache Software Foundation resources. I'm not sure what they can do for us, but I know ASF java projects do get PRs released. Not sure if it's through ASF or not. -- __ Stas BekmanJAm_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]
Re: mod_perl Public Relations
Philippe M. Chiasson wrote: Perrin Harkins wrote: On Sat, 2004-08-07 at 06:13, Uwe Voelker wrote: I would like to help. What needs to be done? Is it more html or perl coding? It's both. What I had in mind was a file that we would add news items to, probably in XML or some other format with a handy parser already written. How about POD or YAML for a simple format like that one ? Keeping the pool of possible authors/reporters as high as possible. +1 to stand clear of XXXml ;) -- __ Stas BekmanJAm_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]
Re: mod_perl Public Relations
Perrin Harkins wrote: On Sat, 2004-08-07 at 06:13, Uwe Voelker wrote: I would like to help. What needs to be done? Is it more html or perl coding? It's both. What I had in mind was a file that we would add news items to, probably in XML or some other format with a handy parser already written. Then we need to hook into the site generation script to read this file, put the first 3 items on the home page if they are newer than 60 days, generate an archive page for the rest up to a year old, and generate an RSS file for the latest 10 items. Check out the site code by following the instructions here: http://perl.apache.org/download/docs.html May be it's the simplest to setup wiki? it can live in the checkout directory w/o having anything to do with the site generation. just an idea. -- __ Stas BekmanJAm_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]
Re: mod_perl Public Relations
Perrin Harkins wrote: On Mon, 2004-08-09 at 05:25, Stas Bekman wrote: Philippe M. Chiasson wrote: How about POD or YAML for a simple format like that one ? Keeping the pool of possible authors/reporters as high as possible. +1 to stand clear of XXXml ;) I can't imagine that more people know YAML than basic XML. I know I've avoided YAML so far, since it seems pretty pointless to me. I don't think POD or a wiki would provide enough structure for this use (we need a headline, body, date, poster, etc.), although I suppose we could make POD work by requiring a strict structure for news items. One way to do it would be to simply write into a large RSS file by hand, and let a script grab the last 10 of those for the real RSS feed and for generating the pages. Yuck. The front-end doesn't have to be anything format specific. Just have a simple form for content management. I really liked the Bricolage presentation at OSCon, it's so easy to create and manipulate data. Can you please take a look at how jobs.perl.org works. I'm not sure what they are using behind the scenes, but it seems to work great. -- __ Stas BekmanJAm_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]
Re: mod_perl Public Relations
Perrin Harkins wrote: On Mon, 2004-08-09 at 14:59, Stas Bekman wrote: That's the whole point. In order to make things simple, it shouldn't require commit access or anything list that. We could even use a simplified version of slashdot, so people can submit stories, people can comment on them, making it much more efficient and not creating any bottlenecks. Yes, we could set up a blog for news. It seems a bit redundant to have comments when we already have the mailing list(s), so I would skip that. We also can't put things on the site without an approval process, so it would need users and permissions. If we are able to host web apps on perl.apache.org and someone out there feels like playing with some simple blog software (Blosxom? Bryar?), that would be fine with me. Just throwing ideas, really. If the overhead of managing news is too big, it will be too easy to stop doing that. So I'm just wondering what's the simplest approach for more people being able to contibute w/o as little overhead as possible. -- __ Stas BekmanJAm_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]
Re: Introduction
Philippe M. Chiasson wrote: [...] What do you think? We put these files under cvs modperl-docs and we sync the discussions here with these files. Would we want those files to be publicly visible on the perl.apache.org site as well (I wouldn't mind). sure, since this list is public, there should be no reason why the concolusions should be secret. it should be easy to have them in plain pod, or text or whatever in the source and autogenerate files as all other files on perl.apache.org. Or if people think that some sort of kiki-miki is more efficient and creates less barriers (but potentially bigger admin) overhead, that will work just as well. It's hard to understand what's happening from emails, it's easier to track that via files. Yup, wether we decide to simply use a few text files or POD files that end up on the site as well, I'd like to volounter as maintainer of that stuff once we agree what/where we put the 'stuff'. It's possible to start maintaining things right away, and move later to whatever format we decide upon. I think a plain text files (keep .txt to DocSet will know to automatically convert those to html) is a good start. So, unless anybody strongly objects, I'll prepare an overview of what has been said this week and split it up in some sort of documents. gozer++ -- __ Stas BekmanJAm_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]
Re: Introduction
Randal L. Schwartz wrote: Stas == Stas Bekman [EMAIL PROTECTED] writes: Stas o SysAdmin Stas - Frank Wiles [EMAIL PROTECTED] sent a proposal I write a bi-monthly column there. Stas o The Perl Magazine Stas - geoff is working on the Oct article If this is The Perl Journal, I write a monthly column there. And, Linux Magazine - monthly column. Ah, OK, I guess I shouldn't have used real names to mock up the proposals format :) So, Randal, what it'll take for you to start writing mod_perl columns? -- __ Stas BekmanJAm_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]
Re: Introduction
Stas Bekman wrote: I try to get it in where I can. If anyone, and I mean *anyone* has an idea, I have 2.5 colums to write every month. I'm there. I'll do it. Just feed me the core idea. Philippe, please write down to send core files to Randal :) I mean 'core ideas' ;-) -- __ Stas BekmanJAm_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]
Re: reply-to header test
Randal L. Schwartz wrote: Stas == Stas Bekman [EMAIL PROTECTED] writes: Stas Sorry, Randal, but No to your No. I spend a way too much time asking Stas people to reply to the list. And I predict within four weeks, someone will post a mailing here that says oops, I didn't mean that for the list. It happens. Best to err toward privacy, not public disclosure. It happens both ways, there is no perfect approach. I prefer people watching their To headers, than us active posters handling tons of misdirected emails ending up in my private inbox, breaking threads, having information disappear, etc. -- __ Stas BekmanJAm_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]
