community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave <snoopd...@gmail.com>
Subject Re: Boosting participation and community in Apache Labs?
Date Wed, 01 Sep 2010 02:37:52 GMT
I now have a Roller task that runs periodically, gathers up to 30 blog
entries from the last 30 days and then sends out an email that lists
each entry with a link and a short excerpt. It can be configured to
send out this email once a month and to only include blog entries with
one specific tag, e.g. 'newsletter'

So, now the questions are about format, process and who does what.

First, what format should the newsletter take, what title and content
should be shown in addition to the blog entry summaries? Doe we need
special signature, links, disclaimers?

Next, what should the process be? Does somebody get the email, add
some cheerful chat at the start and then send it out or does the email
just go out automatically? I think the best approach might be for the
email to come to this mail list (dev@community.apache.org), then
somebody on the list steps up to draft a short snappy intro, tweaks
the format, maybe adds some special messages from the ASF and sends it
out to a wide audience.

Thoughts?

Thanks,
- Dave


On Fri, Jul 23, 2010 at 9:20 AM, Ross Gardler <rgardler@apache.org> wrote:
> On 23/07/2010 13:37, Dave wrote:
>>>
>>> On 23/07/2010 12:45, Dave wrote:
>>>>
>>>> I've written a bunch of utilities like the one you describe. It's
>>>> pretty easy to implement a Roller scheduled task that fires
>>>> periodically, reads the most recent X entries in a tag, forms an email
>>>> and sends it out. Are those really the complete requirements.
>>
>> On Fri, Jul 23, 2010 at 8:31 AM, Ross Gardler<rgardler@apache.org>  wrote:
>>>
>>> Pretty much, yes. I think it would be better to be teaser content rather
>>> than the complete content (there are RSS feeds for that). The idea is to
>>> provide a cross foundation summary of activities without requiring people
>>> to
>>> sift through all the project specific stuff.
>>
>> If you use Roller for the blog, you'd put teaser comment would go in
>> the "Summary" field and full content would go in the Content field.
>
> OK, sounds good and I can see what you mean in the system.
>
>>> On 23/07/2010 12:45, Dave wrote:
>
>> Either way should be easy with a Roller task we could pull from one
>> blog or the whole site.
>
> I really like the sound of that. I've sent a mail to run it past press@
> (mostly out of courtesy).
>
> Ross
>
>
> --
> rgardler@apache.org
> @rgardler
>

Mime
View raw message