Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: ModPerl: Advocacy

making the Press Release

 

 

ModPerl advocacy RSS feed   Index | Next | Previous | View Threaded


stas at stason

Dec 16, 2004, 2:30 PM

Post #1 of 21 (20820 views)
Permalink
making the Press Release

OK, I've contacted the group responsible for Press Releases at ASF and
they gave us the guidelines which you can find below.

Now, I really have to concentrate on finishing the remaining bits of mp2,
unless we want this to drag for another few months. It's been a few days
already that I manage to write not a single line of code, and just
answering emails all day long. So if someone could volunteer to lead the
effort of satisfying the listed below requirements and prepare the press
release, that would be really helpful.

Thank you.

------------------

From: susie [at] apache
To: pmcs [at] apache
Cc: prc [at] apache
Subject: How to work with the PRC to issue Press Releases
Date: Mon, 27 Sep 2004 09:13:37 -0700 (PDT)

How to work with the PRC to issue a press release. We are here to
help the PMCs, but in order for us to help you effectively, we would
like you to follow these general guidelines.

Audience: Any PMC who wants to issue a press release or generate media
coverage of a newsworthy event.

Overall Steps / Timeline:

1. In order to maximize the impact and effectiveness of press
announcements (also called "return on investment") the PRC normally
requires a MINIMUM of 2 weeks notice prior to each announcement. This
time is used to carry out all of the groundwork required to achieve as
large an impact as possible from a release. This means that from the
date you begin working with us, the PRC, to the date that you want
your release to hit the wire, we need a 2 week window. If the release
addresses urgent information (e.g a security problem and related patch
or release) then the PRC can arrange such releases on a much quicker
schedule. Also, if your PMC decides to independently complete any of
the steps on its own (such as Step 5, the most time consuming step),
then our PRC turnaround time will be correlatively shorter.

2. For a successful release, try to think of your announcement in
terms of telling a story (also called "a pitch"). Like any truly
compelling story, it should have certain key elements to grab and keep
your audience's attention. To help you order your thoughts and allow
the PRC to help in this process, the Press Release Questionnaire has
been created. This should be filled out and emailed to prc [at] apache
<mailto:prc [at] apache> . You can solicit the PRC's assistance in
devising the overall "pitch" or story for your release. Just let us
know how much help you will need and we can brainstorm story ideas
with you.

3. The PRC can work with you to create a press release, to whatever
extent necessary. For example, the PRC is happy to help you write the
first draft, structure your ideas, or just edit your drafts. The PRC
can also contact people and garner quotes suitable for inclusion if
this is required. Draft versions of releases can be submitted with
the Press Release Questionnaire.

4. The PRC will promote your release to the media by initiating
dialogue with contacts in the media, whether supplied by your group,
known to the PRC, or both. The intent is to allow the contacts to
prepare stories (also called "seeding stories"), talk to the release
contacts (typically ASF representatives) and carry out any background
research so that when the release hits the wire it will prompt a
number of fast, knowledgeable responses and/or stories. This is the
longest stage of the entire process and can be omitted if the release
is urgent. However, this is the most valuable stage of the process, as
it allows us to generate interest in your story prior to the issue of
a release. The more time we can spend on generating pre-release
interest, the more media impact and coverage your story will have on
the actual date of the release. Also, this step plays an important
role in building better relationships with media and analyst contacts,
a step that is critical in strengthening the ASF brand.

5. The PRC has access to a range of news bureaus (also called "wire
services") and will choose the most appropriate venues for your
release. If your group has specific requests or resources available
then details should be provided to the PRC so these can be
used. Additionally the announcement will be sent to all relevant
announcement mailing lists known to the PRC and your PR will be linked
to from the PRC or ASF home page. If there is extraordinary (national,
international, or otherwise significant) news coverage of your PR
event, the PRC would also like to link to those news articles from our
(home) page.

Press Release Questionnaire:

1. What do you need from the PRC? Be specific. Do you need help
coming up with ideas for a story? Do you need help drafting the
release? Help with generating pre-release interest from the media?
Help putting the release on the wire?

2. What are you trying to accomplish with this release? Announce a
new product? Make a position statement? Why will the public care about
what you have to say? Think about this carefully - because this will
impact what content we present and how we present it. Answer the
following for us (as clearly and without jargon as possible).

a. My release is important because:

i. X
ii. Y
iii. Z

b. Reasons why people will care about this release:

i. A
ii. B
iii. C

3. Who is the audience? Who are you trying to communicate with?
After all, a press release is a codified method of communicating with
a large audience. Are you targeting business media? Business decision
makers? End Users? Tech Developers? Answering this question as
thoroughly as you can is important because it will help us tailor the
appropriate message for your target audience. What are your metrics
for judging the success of this release? (I.e. If 3 major tech
websites pick this up, it will be successful. If 2 major business
papers pick this up it will be successful. If our web page hits go up
by 50%, etc.)

4. What timeframe are you looking at? Is there an absolutely rigid
date? (I.e. Coinciding with a conference, or a release date) If so,
please let us know. If your timeframe is more flexible, inform us of
that as well. In fact, if you have a release idea that is very
'general' and not tied to any fixed event (i.e. A general position
statement on the state of your industry/category), we're still happy
to work with you.

5. Are there quotes you would like to have represented in the
release? We can help you contact the people you would want to have
quoted, and work on drafting these quotes.

6. Has your PMC talked with press in the past that were interested
in your project? Give us a list of these names, if available, and we
will contact them for you.

7. Finally, who do you want to be the primary contacts for this
release? There may be media who want to ask follow up
questions. Please provide us with name, title, short bio, email, and
phone number.

--
Susan Wu
PRC Committee
susie [at] apache


--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas [at] stason http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


perrin at elem

Dec 17, 2004, 10:45 AM

Post #2 of 21 (20232 views)
Permalink
Re: making the Press Release [In reply to]

On Thu, 2004-12-16 at 17:30 -0500, Stas Bekman wrote:
> So if someone could volunteer to lead the
> effort of satisfying the listed below requirements and prepare the press
> release, that would be really helpful.

I'll take care of it.

I'm assuming we won't be doing the release until January. Has anyone
thought about whether we should do it on the actual release date or a
day or two later? I would vote for doing it the next day, to make sure
there are no problems with CPAN propagation, etc.

- Perrin




---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


frank at wiles

Dec 17, 2004, 12:16 PM

Post #3 of 21 (20255 views)
Permalink
Re: making the Press Release [In reply to]

On Fri, 17 Dec 2004 13:45:13 -0500
Perrin Harkins <perrin [at] elem> wrote:

> On Thu, 2004-12-16 at 17:30 -0500, Stas Bekman wrote:
> > So if someone could volunteer to lead the
> > effort of satisfying the listed below requirements and prepare the
> > press release, that would be really helpful.
>
> I'll take care of it.
>
> I'm assuming we won't be doing the release until January. Has anyone
> thought about whether we should do it on the actual release date or a
> day or two later? I would vote for doing it the next day, to make
> sure there are no problems with CPAN propagation, etc.

I second that! Should we use one of the press release blasting
services to send it out? I'd be willing to chip in some $$$ for it
if everyone agrees that it would be useful.

---------------------------------
Frank Wiles <frank [at] wiles>
http://www.wiles.org
---------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


larryl at emailplus

Dec 17, 2004, 12:37 PM

Post #4 of 21 (20260 views)
Permalink
Re: making the Press Release [In reply to]

On Fri, 17 Dec 2004, Frank Wiles wrote:

> I second that! Should we use one of the press release blasting
> services to send it out? I'd be willing to chip in some $$$ for it
> if everyone agrees that it would be useful.

I'd be willing to make a contribution too. Shouldn't we be able to use
some Perl Foundation monies for that? If so, then people could make
donations to the Perl Foundation earmarked for promotion of mod_perl.


Larry



---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


perrin at elem

Dec 17, 2004, 12:42 PM

Post #5 of 21 (20250 views)
Permalink
Re: making the Press Release [In reply to]

On Fri, 2004-12-17 at 14:16 -0600, Frank Wiles wrote:
> Should we use one of the press release blasting
> services to send it out?

I think that the ASF is going to handle that part for us. Thanks for
the offer though, Frank.

- Perrin


---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


stas at stason

Dec 17, 2004, 2:15 PM

Post #6 of 21 (20215 views)
Permalink
Re: making the Press Release [In reply to]

Perrin Harkins wrote:
> On Thu, 2004-12-16 at 17:30 -0500, Stas Bekman wrote:
>
>>So if someone could volunteer to lead the
>>effort of satisfying the listed below requirements and prepare the press
>>release, that would be really helpful.
>
>
> I'll take care of it.

yay, perrin++

> I'm assuming we won't be doing the release until January.

I believe so. but you never know.

> Has anyone
> thought about whether we should do it on the actual release date or a
> day or two later? I would vote for doing it the next day, to make sure
> there are no problems with CPAN propagation, etc.

Will there be a problem if the press release is done a week or 2 weeks
after the release? what difference does it make?

--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas [at] stason http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


stas at stason

Dec 17, 2004, 2:16 PM

Post #7 of 21 (20249 views)
Permalink
Re: making the Press Release [In reply to]

Frank Wiles wrote:
> On Fri, 17 Dec 2004 13:45:13 -0500
> Perrin Harkins <perrin [at] elem> wrote:
>
>
>>On Thu, 2004-12-16 at 17:30 -0500, Stas Bekman wrote:
>>
>>>So if someone could volunteer to lead the
>>>effort of satisfying the listed below requirements and prepare the
>>>press release, that would be really helpful.
>>
>>I'll take care of it.
>>
>>I'm assuming we won't be doing the release until January. Has anyone
>>thought about whether we should do it on the actual release date or a
>>day or two later? I would vote for doing it the next day, to make
>>sure there are no problems with CPAN propagation, etc.
>
>
> I second that! Should we use one of the press release blasting
> services to send it out? I'd be willing to chip in some $$$ for it
> if everyone agrees that it would be useful.

Can we collect enough for a NY Times ad? :)
http://www.mozillazine.org/talkback.html?article=5781

--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas [at] stason http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


perrin at elem

Dec 17, 2004, 2:53 PM

Post #8 of 21 (20235 views)
Permalink
Re: making the Press Release [In reply to]

On Fri, 2004-12-17 at 17:15 -0500, Stas Bekman wrote:
> Will there be a problem if the press release is done a week or 2 weeks
> after the release? what difference does it make?

No difference at all, as far as I'm concerned.

- Perrin


---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


stas at stason

Dec 17, 2004, 2:59 PM

Post #9 of 21 (20227 views)
Permalink
Re: making the Press Release [In reply to]

Perrin Harkins wrote:
> On Fri, 2004-12-17 at 17:15 -0500, Stas Bekman wrote:
>
>>Will there be a problem if the press release is done a week or 2 weeks
>>after the release? what difference does it make?
>
>
> No difference at all, as far as I'm concerned.

Same here, in fact I think it's even better to make it later to make two
waves (the first wave coming from the usual announcement).

--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas [at] stason http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


frank at wiles

Dec 17, 2004, 3:00 PM

Post #10 of 21 (20241 views)
Permalink
Re: making the Press Release [In reply to]

On Fri, 17 Dec 2004 17:15:14 -0500
Stas Bekman <stas [at] stason> wrote:

> Will there be a problem if the press release is done a week or 2 weeks
> after the release? what difference does it make?

I would say we want the press release to be as close to the real
release date as possible. I would be afraid of /. picking up on
the release via the list or the website and it getting around the
Internet and then having a press release about it 2 weeks later.

If other sites get the word out in too much of advance of the
press release then their words are what spread and not ours. It
would also water down the effect, if a news organization slightly
covered the release after reading about it somewhere online they
aren't likely to cover it again when they receive the release.

---------------------------------
Frank Wiles <frank [at] wiles>
http://www.wiles.org
---------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


stas at stason

Dec 17, 2004, 3:03 PM

Post #11 of 21 (20238 views)
Permalink
Re: making the Press Release [In reply to]

Frank Wiles wrote:
> On Fri, 17 Dec 2004 17:15:14 -0500
> Stas Bekman <stas [at] stason> wrote:
>
>
>>Will there be a problem if the press release is done a week or 2 weeks
>>after the release? what difference does it make?
>
>
> I would say we want the press release to be as close to the real
> release date as possible. I would be afraid of /. picking up on
> the release via the list or the website and it getting around the
> Internet and then having a press release about it 2 weeks later.
>
> If other sites get the word out in too much of advance of the
> press release then their words are what spread and not ours. It
> would also water down the effect, if a news organization slightly
> covered the release after reading about it somewhere online they
> aren't likely to cover it again when they receive the release.

OK, that makes sense to me. Thanks Frank.

--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas [at] stason http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


tomg at barzakh

Dec 17, 2004, 3:25 PM

Post #12 of 21 (20246 views)
Permalink
RE: making the Press Release [In reply to]

> Can we collect enough for a NY Times ad? :)
> http://www.mozillazine.org/talkback.html?article=5781

Making the NY Times is one thing. However, I think that one thing you guys
should keep your eyes on whilst doing this press release is search engine
penetration - how high up will the article get when someone types in the
most common keywords (mod_perl, perl apache, perl, apache, php or perl,
etc).

The reason I say this is that, when I first started researching mod_perl,
about 1.5 short years ago, search engines often led me to very helpful
articles on how to install/configure mod_perl, but these were frequently
emblazoned with the alarming qualifier "DO NOT USE MOD_PERL 2 IN A
PRODUCTION ENVIRONMENT" or words to that effect.

and lest you've forgotten:
http://web.archive.org/web/20030604112031/http://beaucox.com/mason/mason-wit
h-apmp2-mini-HOWTO.htm

The problem is that these articles are all still around, and in particular
they are associated with otherwise otherwise highly marketable software like
Mason and Embperl.

IMHO, these qualifiers play a fairly significant role in the decline in
mod_perl usage stats we've been seeing in the last few months.

Tom.




---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


stas at stason

Dec 17, 2004, 3:33 PM

Post #13 of 21 (20249 views)
Permalink
Re: making the Press Release [In reply to]

Tom Gazzini wrote:
>>Can we collect enough for a NY Times ad? :)
>>http://www.mozillazine.org/talkback.html?article=5781
>
>
> Making the NY Times is one thing. However, I think that one thing you guys
> should keep your eyes on whilst doing this press release is search engine
> penetration - how high up will the article get when someone types in the
> most common keywords (mod_perl, perl apache, perl, apache, php or perl,
> etc).
>
> The reason I say this is that, when I first started researching mod_perl,
> about 1.5 short years ago, search engines often led me to very helpful
> articles on how to install/configure mod_perl, but these were frequently
> emblazoned with the alarming qualifier "DO NOT USE MOD_PERL 2 IN A
> PRODUCTION ENVIRONMENT" or words to that effect.
>
> and lest you've forgotten:
> http://web.archive.org/web/20030604112031/http://beaucox.com/mason/mason-wit
> h-apmp2-mini-HOWTO.htm
>
> The problem is that these articles are all still around, and in particular
> they are associated with otherwise otherwise highly marketable software like
> Mason and Embperl.
>
> IMHO, these qualifiers play a fairly significant role in the decline in
> mod_perl usage stats we've been seeing in the last few months.

Any ideas how to fix that situation? go after the old articles and ask to
change them?

--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas [at] stason http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


tomg at barzakh

Dec 18, 2004, 5:45 AM

Post #14 of 21 (20251 views)
Permalink
RE: making the Press Release [In reply to]

> -----Original Message-----
> From: Stas Bekman [mailto:stas [at] stason]
> Sent: 17 December 2004 23:34
> To: advocacy [at] perl
> Subject: Re: making the Press Release
>
> Tom Gazzini wrote:
> >>Can we collect enough for a NY Times ad? :)
> >>http://www.mozillazine.org/talkback.html?article=5781
> >
> >
> > Making the NY Times is one thing. However, I think that one thing you
> guys
> > should keep your eyes on whilst doing this press release is search
> engine
> > penetration - how high up will the article get when someone types in the
> > most common keywords (mod_perl, perl apache, perl, apache, php or perl,
> > etc).
> >
> > The reason I say this is that, when I first started researching
> mod_perl,
> > about 1.5 short years ago, search engines often led me to very helpful
> > articles on how to install/configure mod_perl, but these were frequently
> > emblazoned with the alarming qualifier "DO NOT USE MOD_PERL 2 IN A
> > PRODUCTION ENVIRONMENT" or words to that effect.
> >
> > and lest you've forgotten:
> >
> http://web.archive.org/web/20030604112031/http://beaucox.com/mason/mason-
> wit
> > h-apmp2-mini-HOWTO.htm
> >
> > The problem is that these articles are all still around, and in
> particular
> > they are associated with otherwise otherwise highly marketable software
> like
> > Mason and Embperl.
> >
> > IMHO, these qualifiers play a fairly significant role in the decline in
> > mod_perl usage stats we've been seeing in the last few months.
>
> Any ideas how to fix that situation? go after the old articles and ask to
> change them?

I wouldn't recommend that method (sorry, can't tell if you're being
sarcastic on email). I was involved in a similar media push a while ago, and
trying to get webmasters to update article content is like trying to cut off
a hydra's heads. There's so many mirrored and cached site abounding they
just keep cropping up everywhere. If you do it this way, expect it to take
about a year before you come close to cleaning everything up.

An alternative way would be to push out articles on the internet that
promote the READINESS of mod_perl2 for production envs. (If indeed, it is
ready - is it?). By judicious use of keywords in these articles, you can try
and ensure that they get to the top of search engine listings. So make sure
that any press releases you do get links to high profile sites, and contain
good keywords.

Otherwise, I fear that as more people move to apache2, the "mod_perl2 is not
ready" articles will increasingly push people towards the competition.

Tom.







---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


perrin at elem

Dec 18, 2004, 7:17 AM

Post #15 of 21 (20258 views)
Permalink
RE: making the Press Release [In reply to]

On Fri, 2004-12-17 at 23:25 +0000, Tom Gazzini wrote:
> The reason I say this is that, when I first started researching mod_perl,
> about 1.5 short years ago, search engines often led me to very helpful
> articles on how to install/configure mod_perl, but these were frequently
> emblazoned with the alarming qualifier "DO NOT USE MOD_PERL 2 IN A
> PRODUCTION ENVIRONMENT" or words to that effect.

Those were necessary warnings, in my opinion, since Red Hat was shipping
alpha code as their only mod_perl offering.

They also all say that it's not released yet, so all we have to do is
make sure people hear that it's released.

> IMHO, these qualifiers play a fairly significant role in the decline in
> mod_perl usage stats we've been seeing in the last few months.

I don't really think so. PHP has all the same qualifiers about use with
Apache 2.

- Perrin


---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


stas at stason

Dec 18, 2004, 8:33 AM

Post #16 of 21 (20249 views)
Permalink
Re: making the Press Release [In reply to]

Tom Gazzini wrote:
[...]
>>Any ideas how to fix that situation? go after the old articles and ask to
>>change them?
>
>
> I wouldn't recommend that method (sorry, can't tell if you're being
> sarcastic on email).

I'm not sure myself. But every time I say/hear 'rewrite the history' I
think "1984". So I prefer to think that it was a sarcastic suggestion.

> I was involved in a similar media push a while ago, and
> trying to get webmasters to update article content is like trying to cut off
> a hydra's heads. There's so many mirrored and cached site abounding they
> just keep cropping up everywhere. If you do it this way, expect it to take
> about a year before you come close to cleaning everything up.
>
> An alternative way would be to push out articles on the internet that
> promote the READINESS of mod_perl2 for production envs. (If indeed, it is
> ready - is it?).

I'm not using it myself in production, since I don't have one at the
moment. But based on other people's comments on the users list it
definitely is.

> By judicious use of keywords in these articles, you can try
> and ensure that they get to the top of search engine listings. So make sure
> that any press releases you do get links to high profile sites, and contain
> good keywords.
>
> Otherwise, I fear that as more people move to apache2, the "mod_perl2 is not
> ready" articles will increasingly push people towards the competition.

Sure, writing new articles is a good idea.

--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas [at] stason http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


yining at ectoplasm

Dec 21, 2004, 5:53 AM

Post #17 of 21 (20248 views)
Permalink
Re: making the Press Release [In reply to]

Stas Bekman wrote:

> Tom Gazzini wrote:
>
>> By judicious use of keywords in these articles, you can try
>> and ensure that they get to the top of search engine listings. So
>> make sure
>> that any press releases you do get links to high profile sites, and
>> contain
>> good keywords.
>>
>> Otherwise, I fear that as more people move to apache2, the "mod_perl2
>> is not
>> ready" articles will increasingly push people towards the competition.
>
>
> Sure, writing new articles is a good idea.
>

Blogs is the effective way to boost web pages search ranks, due to its
highly cross-hyperlinking nature and like contents. RSS feeds have also
been the most efficient means to spread the meme[1] across the online
communities.

Not only that, regularly updated blogs will definitely move those
related but static outdated articles on the web down and off the google
search result pages.

I would suggest that, if possible, guys here start writing blogs,
talking about modperl once a while, and have your RSS feeds registered
to sites like pubsub, artima.com, technorati, etc. The result will very
sure be apparent before long.

[1] http://en.wikipedia.org/wiki/Meme

--
---------------------------------------------------------------
Zhang Yining
URL: http://www.zhangyining.net | http://www.yining.org
mailto: yining [at] zhangyining | yining [at] ectoplasm
Fingerprint: 25C8 47AE 30D5 4C0D A4BB 8CF2 3C2D 585F A905 F033


---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


stas at stason

Dec 21, 2004, 8:37 AM

Post #18 of 21 (20279 views)
Permalink
Re: making the Press Release [In reply to]

Perrin,

I think this is a nice summary of libapreq2 Joe just posted that can be
included in the PR as an incentive to upgrade to mp2.



-------- Original Message --------
Subject: Re: libapreq2 upload question
Date: Tue, 21 Dec 2004 11:26:55 -0500
From: Joe Schaefer <joe+gmane [at] sunstarsys>
To: modperl [at] perl
References: <E1Cgf0s-0007Qm-00 [at] relay>

"eps com estem" <ggerard [at] mixmail> writes:


[...]

> One last question, would you use libapreq2 to handle all GET
> and POST data or only the multipart-POST data??

It's designed to be usable for all GET / POST data.
The Content-Types it currently understands are

application/x-www-form-urlencoded
multipart/form-data
multipart/related

The first two are what HTML forms typically use,
but we've also laid enough groundwork within libapreq2
to support newer specs like XForms and WHATWG once
browsers start implementing them. libapreq2 provides
a C API to extend/modify the parser list, so you
can even extend it yourself if apreq-dev@ isn't
extending it fast enough for you.

> I mean, what's the intention of libapreq to be?

libapreq2 is intended to provide a common request
parsing library for all apache2 modules (not just
a "faster CGI.pm"). There are already a few C modules
(mod_spin is a nice example) that use libapreq2. The
upshot is that such modules will all share the *parsed*
POST data, without stealing the *raw* POST data from
other modules.

--
Joe Schaefer



--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas [at] stason http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


tomg at barzakh

Dec 21, 2004, 2:40 PM

Post #19 of 21 (20232 views)
Permalink
RE: making the Press Release [In reply to]

> On Fri, 2004-12-17 at 23:25 +0000, Tom Gazzini wrote:
> > The reason I say this is that, when I first started researching
> mod_perl,
> > about 1.5 short years ago, search engines often led me to very helpful
> > articles on how to install/configure mod_perl, but these were frequently
> > emblazoned with the alarming qualifier "DO NOT USE MOD_PERL 2 IN A
> > PRODUCTION ENVIRONMENT" or words to that effect.
>
> Those were necessary warnings, in my opinion, since Red Hat was shipping
> alpha code as their only mod_perl offering.
>
> They also all say that it's not released yet, so all we have to do is
> make sure people hear that it's released.


Yes that's right. You have to make sure they hear it.


> > IMHO, these qualifiers play a fairly significant role in the decline in
> > mod_perl usage stats we've been seeing in the last few months.
>
> I don't really think so. PHP has all the same qualifiers about use with
> Apache 2.


I know very little about what the PHP crowd do, or how PHP know-how is
propagated.

I was really talking from personal experience. That of recently trying to
convince a team of developers at work (who have been raised mostly on
Microsoft tools) that a particularly large and high profile project would be
better and more quickly accomplished using apache and mod_perl. It didn't
take them long to do a google search and come up with the "Do not use
mod_perl in production" articles (as these seem to come somewhere the top of
the search listings if you start researching Mason or Embperl with
mod_perl). This then became ammo against mod_perl. Mod_perl lost the battle.





---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


perrin at elem

Jan 4, 2005, 3:34 PM

Post #20 of 21 (20220 views)
Permalink
RE: making the Press Release [In reply to]

Hi all,

Just wanted to report that I have been having an easy time gathering
good stories from business users of mp2 to include in the press release.
I will try to get all of them to contribute success stories as well.

- Perrin


---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl


stas at stason

Jan 5, 2005, 6:51 AM

Post #21 of 21 (20240 views)
Permalink
Re: making the Press Release [In reply to]

Perrin Harkins wrote:
> Hi all,
>
> Just wanted to report that I have been having an easy time gathering
> good stories from business users of mp2 to include in the press release.
> I will try to get all of them to contribute success stories as well.

Perrin++

--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas [at] stason http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe [at] perl
For additional commands, e-mail: advocacy-help [at] perl

ModPerl advocacy RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.