The consensus (mainly private mails) seems to be to stick to the monthly scheme and 
accept September as a blip.

So business as usual - I'll call for contributions covering Sep + Oct sometime next 
week and post drafts from the 4th.

Cheers,

Rob

----- Original Message -----
From: "Brian Ewins" <[EMAIL PROTECTED]>
To: "Jakarta General List" <[EMAIL PROTECTED]>
Sent: Thursday, October 17, 2002 5:33 PM
Subject: Re: Newsletter


> As a reader, monthly is a good frequency.  Maybe I'm expecting something
> different from the newsletter than you're looking to include?
>
> I look at the newsletter as being something like kernel traffic[1], the
> kernel cousins[2], or the 'eclectic' weblog[3]. It lets me keep up with
> the direction the community is heading in without reading all the lists.
> Announcements of new releases are actually the least interesting parts
> of the newsletter, since these get flagged up on the main news page
> anyway, and as you say arent all that frequent; feature-freezes and
> banches are more interesting.  The most interesting things though are
> when something new appears on the horizon, a major new feature becomes
> usable (even if unstable), or there is a statement of the future
> direction of the project on the list. This kind of nugget is exactly
> what you need to keep abreast of the projects.
>
> Stuff like that did appear on struts dev in September - and it does
> every month! -, even though Sept was a light month for messages:
> http://nagoya.apache.org/eyebrowse/ReadMsg?listId=41&msgNo=10612 - the
> Struts-EL package was checked in
> 
>http://nagoya.apache.org/eyebrowse/ReadMsg?listName=struts-dev@;jakarta.apache.org&msgNo=10550
> - which led to David Karr becoming a committer
> 
>http://nagoya.apache.org/eyebrowse/ReadMsg?listName=struts-dev@;jakarta.apache.org&msgNo=10547
> - Craig clarified whats going on with struts and JSF (you could make the
> whole months struts entry just by editing down this email!)
>
> If the editorial was going to the depth of kernel traffic, rather than
> the paragraph or two each list gets in the newsletter, I'd also have
> included some of the thread voting on validator behaviour, the responses
> to Craigs email about JSF, and possibly some of the discussion on
> browser caching[4].
>
> eh, this isnt me volunteering as editor or anything ;) - I'm just giving
> my perspective on what I get out of reading the newsletter.
>
> Cheers,
> Baz
>
> [1] http://kt.zork.net/kernel-traffic/latest.html (summarizes the
> linux-kernel list)
> [2] http://kt.zork.net/wine/latest.html - for example, this is the wine
> kernel cousin
> [3] http://weblogs.userland.com/eclectic/ - eclectic covers the xml-dev
> list (by the former author of xml-deviant
> http://www.xml.com/pub/q/xmldeviant)
> [4] surprised noone mentioned that because ActionServlet doesn't
> override lastModified()  conditional GETs on struts actions arent
> supported - but thats by the by.
>
> Joe Germuska wrote:
>
> > As the volunteer editor for Struts for the first few newsletters, I'm
> > wondering if monthly is the right frequency for these?  Maybe it's
> > because Struts is pretty focused on killing bugs for a 1.1 release,
> > but that doesn't make for a lot of interesting news.
> >
> > Of course, the fact that various projects can participate or not
> > according to their wishes may mean that circulating the newsletter
> > every month is sensible, but that projects shouldn't feel obliged to
> > conjure up news every month if there isn't much to say?
> >
> > We could probably survive with newsletters every 2 or 3 months instead
> > of monthly.
> >
> > Joe
> >
>
>
>
> Privacy and Confidentiality Notice
>
> ------------------------------------------------
>
> The information contained in this E-Mail message is intended only for the person or 
>persons to whom it is addressed.  Such
information is confidential and privileged and no mistake in transmission is intended 
to waive or compromise such privilege.  If you
have received it in error, please destroy it and notify us on the telephone number 
printed above.  If you do not receive complete
and legible copies, please telephone us immediately. Any opinions expressed herein 
including attachments are those of the author
only. i-documentsystems Ltd. does not accept responsibility for the accuracy or 
completeness of the information provided or for any
changes to this Email, however made, after it was sent. (Please note that it is your 
responsibility to scan this message for
viruses).
>
>
> --
> To unsubscribe, e-mail:   <mailto:general-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail: <mailto:general-help@;jakarta.apache.org>
>
>
>


--
To unsubscribe, e-mail:   <mailto:general-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:general-help@;jakarta.apache.org>

Reply via email to