[Fwd: [PROPOSAL] Newsletter Submissions]

[Ted Husted <hu...@apache.org>]

In case anyone is interested in handling this ...

-------- Original Message --------
Subject: [PROPOSAL] Newsletter Submissions
Date: Tue, 25 Jun 2002 11:46:57 +0100
From: "Rob Oxspring" <ro...@imapmail.org>
Reply-To: "Jakarta General List" <ge...@jakarta.apache.org>
To: <ge...@jakarta.apache.org>

Id like to propose the following time scale for the June newsletter and
similar setup for subsequent ones.

1)    Content submissions in by end of sunday (midnight)

2)    I'll pull together whats there and post a draft copy to general@
on
the Monday (1st July)

3)    Then await edits and a lazy consensus and post final copy to
announcements@ on the Wednesday (3rd July)

Content should aim to summerise what's been going on in the various
groups
throughout June, I used the most active threads for issue #0
(http://nagoya.apache.org/eyebrowse/ReadMsg?listName=general@jakarta.apache.
org&msgNo=12130) but this may miss out the occasional worthy decision /
change / vote, YMMV.  It would also be good to all be using the same
reference source so nagoya.apache.org/eyebrowse for links to mail
archives
where possible?

I guess submissions might as well go directly to me so that the draft
has
something new for people to read.  Although as Ted Husted suggested -
discussion of content in the respective -dev lists would probably be a
good
step prior to submission, and some sort of [news] subject prefix would
be
appreciated for filtering.  If projects want to further subdivide (e.g.
commons / avalon) then they should organise it amongst themselves.

Could I have volunteers to organise / edit / submit on behalf of each
-dev
list for June? I'd like to avoid a cross-post invitation to all -dev@ if
at
all possible.

Rob


--
To unsubscribe, e-mail:  
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>