On Wed, 24 Dec 2003 14:26:30 -0600
William A. Rowe, Jr. wrote:
The entire suggestion? I was really surprised that you proposed spaming
the announce list again with the full body of the newsletter, but the rest of
your proposals seemed on target.
Yes, the entire suggestion. Withdrawal. Sorry
Hello,
I will take back my remarks upon this issue.
Sorry for the annoyance.
Thank you,
I wish you a merry Christmas.
Sincerely,
-- Tetsuya. ([EMAIL PROTECTED])
On Tue, 23 Dec 2003 19:53:45 +0900
(Subject: Plan of the future Newsletter)
Tetsuya Kitahata wrote:
Hello folks,
I talked
suggestion? I was really surprised that you proposed spaming
the announce list again with the full body of the newsletter, but the rest of
your proposals seemed on target.
Of course the creation of a newsletter list didn't seem off target, nor did
announcing that list with an invitation to subscribe sent
Hello folks,
I talked with Rob (Rob Oxspring) about the Apache Newsletter.
Rob seemed to have been very busy because of the job change.
I had felt it that The Apache Newsletter was one of my children.
... Really worried about the future of my child. Therefore,
for the time being, I do want
message for the
first newsletter and I'm sure there are others who got a whole lot
more copies than I did. And to top it all off, it was the same
message being sent repeatedly, so it beat msg-id duplicate filters.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
On Tue, 2 Dec 2003 09:22:11 +0100
Mads Toftum wrote:
This is personal opinion: posting to all the -dev lists is very hard
(burden) for him (Rob?) to do.
I recommend him to post a note to committers@
and write please copy this mail to -dev lists to which you are
subscribing, instead. I
On Sun, 30 Nov 2003, Noel J. Bergman wrote:
Do people want the newsletter to continue? If so then I'm happy
to edit the Oct/Nov issue with no promises to tackle subsequent
issues - aiming to publish in a week or so.
+1 and much thanks.
As much as voting with +1s would be appreciated
On Tue, 2003-12-02 at 18:26, Martin Cooper wrote:
On Sun, 30 Nov 2003, Noel J. Bergman wrote:
Do people want the newsletter to continue? If so then I'm happy
to edit the Oct/Nov issue with no promises to tackle subsequent
issues - aiming to publish in a week or so.
+1 and much
welcomed if short and to the point.
I think the discussion was more focussed on how to garner articles and text
for the newsletter rather than how to advertise it once written, but +1 on
the above sentiments :)
david
-
To unsubscribe
Do people want the newsletter to continue? If so then I'm happy
to edit the Oct/Nov issue with no promises to tackle subsequent
issues - aiming to publish in a week or so.
+1 and much thanks.
As much as voting with +1s would be appreciated, voting with content would
be better
Tetsuya
Right then, I don't really want to start another round of endless
discussions so I'll try to keep this short and to the point. Do people want
the newsletter to continue? If so then I'm happy to edit the Oct/Nov issue
with no promises to tackle subsequent issues - aiming to publish in a week
On Sun, 30 Nov 2003, Rob Oxspring wrote:
Right then, I don't really want to start another round of endless
discussions so I'll try to keep this short and to the point. Do people want
the newsletter to continue? If so then I'm happy to edit the Oct/Nov issue
with no promises to tackle
On Sun, 30 Nov 2003 17:53:42 -0500 (Eastern Standard Time)
Joshua Slive wrote:
As much as voting with +1s would be appreciated, voting with content would
be better as would someone setting up the dedicated newsletter@ mailing
list. To vote with content just use the wiki:
http
3. Apache Newsletter is one of the News from the ASF material,
which people who do not have much time to read all the websites in
the Apache.org have been eager to get in the past,
so it fit to the original usage of [EMAIL PROTECTED] mailing list
and I will publish this newsletter
At 03:39 AM 8/26/2003, David Reid wrote:
3. Apache Newsletter is one of the News from the ASF material,
which people who do not have much time to read all the websites in
the Apache.org have been eager to get in the past,
so it fit to the original usage of [EMAIL PROTECTED] mailing list
and I
Peoples,
After the conversation concering the matter of our The
Apache Newsletter, I have come to tentative conclusion:
1. I will not publish the second newsletter (Issue #2) in
the middle of September 2003. I will release in the middle
of October as The Apache Newsletter Issue #2
2
On Mon, 18 Aug 2003, Noel J. Bergman wrote:
(b) subscribe each [EMAIL PROTECTED] to announce@apache.org
Whoa whoa whoa. b) is backwards - from the other discussions on this, you
wanted to subscribe announce@apache.org to each [EMAIL PROTECTED],
not the other way around.
I think
On Mon, 18 Aug 2003 16:26:18 -0700 (PDT)
Brian Behlendorf [EMAIL PROTECTED] wrote:
OK. My concerns about one list trying to deliver to another remain.
I still am not sure it's wise to automate that. For example, just
today I found that the announce@ws.apache.org list was configured to
Someone said:
Ah! It sounds as if other people aren't aware of the background and
original intent. From what you are saying, announce@apache.org should
be
subscribed to announce@tlp.apache.org. That way announcements would
automatically funnel to [EMAIL PROTECTED]
+1 to the general idea.
* Noel J. Bergman ([EMAIL PROTECTED]) wrote :
So then it sounds as if two action items are to:
(a) ensure that each TLP has an announce@
(b) subscribe each [EMAIL PROTECTED] to announce@apache.org
Works for me.
Sounds good, unless anyone has any reservations I'll look at doing this
On Mon, 18 Aug 2003, Thom May wrote:
* Noel J. Bergman ([EMAIL PROTECTED]) wrote :
So then it sounds as if two action items are to:
(a) ensure that each TLP has an announce@
(b) subscribe each [EMAIL PROTECTED] to announce@apache.org
Works for me.
Sounds good, unless anyone has
(b) subscribe each [EMAIL PROTECTED] to announce@apache.org
Whoa whoa whoa. b) is backwards - from the other discussions on this, you
wanted to subscribe announce@apache.org to each [EMAIL PROTECTED],
not the other way around.
I think you're saying what I meant. announce@apache.org is
On 16/08/2003, at 11:58, Noel J. Bergman wrote:
Joshua Slive wrote:
When I originally proposed the announce@apache.org list, the purpose
was
this: Each project would send their announcements to their own list
(eg.
announce@httpd.apache.org) AND send a copy to [EMAIL PROTECTED]
That
way people
Ah! It sounds as if other people aren't aware of the background and
original intent. From what you are saying, announce@apache.org should
be
subscribed to announce@tlp.apache.org. That way announcements would
automatically funnel to [EMAIL PROTECTED]
Is that right?
I'm not suggesting we reopen
On Sat, 16 Aug 2003 17:58:05 -0400, Noel J. Bergman [EMAIL PROTECTED]
said:
Ah! It sounds as if other people aren't aware of the background and
original intent. From what you are saying, announce@apache.org should be
subscribed to announce@tlp.apache.org. That way announcements would
Of course, I never really clarified this, which might have been part
of the problem. I just hoped people would figure out by example.
Uh huh ... LOL
--- Noel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
that nobody ever sends anything to
announce@apache.org other than the HTTP project. Why? Who knows.
Personally, I think the announce@apache.org list is the perfect place for
the newsletter. People subscribe there because they want news about
events in the foundation and its projects
On Fri, 15 Aug 2003 20:02:09 +0100
Thom May [EMAIL PROTECTED] wrote:
* Noel J. Bergman ([EMAIL PROTECTED]) wrote :
Personally, I think that announce@apache.org is the correct place for a
monthly ASF newsletter.
I'm vaguely ambivalent, but I really think that we should keep
announce
Soliciting amusing war stories from the larger community would be fun.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Sat, 16 Aug 2003 10:48:43 +0900, Tetsuya Kitahata
[EMAIL PROTECTED] said:
I'm vaguely ambivalent, but I really think that we should keep
announce for announcements, and have something else for sitewide of
interest stuff.
I am still not sure the difference between
hello!
Now, I published the first newsletter and I felt as if a load had
been taken off my shoulders. So, I can write what I wanted to say.
(If I jumped into the conversation occurred here in the early
this month, this first newsletter would *never* be published,
my character taken
other than the HTTP project. Why? Who knows.
Personally, I think the announce@apache.org list is the perfect place for
the newsletter. People subscribe there because they want news about
events in the foundation and its projects. This is what the newsletter
provides.
Overall, I liked
Personally, I think that announce@apache.org is the correct place for a
monthly ASF newsletter. However, I do agree with your comments related to
the terra-intl.com references. The following ought to have been removed:
My main job is marketing, business development and IT consulting [4
* Noel J. Bergman ([EMAIL PROTECTED]) wrote :
Personally, I think that announce@apache.org is the correct place for a
monthly ASF newsletter.
I'm vaguely ambivalent, but I really think that we should keep announce for
announcements, and have something else for sitewide of interest stuff
Joshua Slive wrote:
A couple suggestions:
- Perhaps a monthly newsletter is asking a little too much. Many projects
don't have much going on in a month. Quarterly might get more results.
Empathic +1 on quarterly. I'm scared to death already for next month's
nagging. ;-)
- I'd tone down
the finished
results. Regrettable? Certainly.
Why not add a newsletter@ mailing list and those that feel they have
literary bones can join there and contribute towards the newsletters
production, then once it's ready and available it can be announced on
announce@ (and possibly here as well).
Life is too
. Regrettable? Certainly.
Why not add a newsletter@ mailing list and those that feel they have
literary bones can join there and contribute towards the newsletters
production, then once it's ready and available it can be announced on
announce@ (and possibly here as well).
Life is too full of emails that can
Can we move discussions about newsletters to another mailing list?
I know I'm not alone in finding that while some here will be interested,
many aren't interested in assisting though will happily read the finished
results. Regrettable? Certainly.
Why not add a newsletter@ mailing list and those
the finished
results. Regrettable? Certainly.
Why not add a newsletter@ mailing list and those that feel they have
literary bones can join there and contribute towards the newsletters
production, then once it's ready and available it can be announced on
announce@ (and possibly here as well).
Life
Hello, All (community@ members!)
I am now preparing the 'The Apache Newsletter Issue 1',
the first ASF-wide-newsletter of July 2003, which will be published
in the middle of August 2003.
-- http://www.apache.org/newsletter/ --
This Apache Newsletter will be published as a result
Mads Toftum wrote, On 11/07/2003 18.53:
...
I like the idea of a (bi-)monthly newsletter, but I'd hate to see it
being forced on people who didn't want it.
Are there a lot of people here on community@apache.org that not want to
know, or even care, of what is happening in Apache-land?
Oh well
On Mon, Jul 14, 2003 at 11:01:16AM +0200, Nicola Ken Barozzi wrote:
Mads Toftum wrote, On 11/07/2003 18.53:
...
I like the idea of a (bi-)monthly newsletter, but I'd hate to see it
being forced on people who didn't want it.
Are there a lot of people here on community@apache.org
http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaNewsletterDrafts/Issue10
Please feel free to write the comments on the last (jakarta) newsletter
;-) ... (@ Readers' Voice Section)
... even if the Jakarta Newsletter will be sublimated as the Apache
Newsletter, your opinions/voices might
Santiago Gala [EMAIL PROTECTED] wrote:
It looks amazingly similar to RSS or necho
(http://www.intertwingly.net/wiki/pie/) if we want a more experimental
format :-)
Necho? Echo?
Necho reminds me of the word Neko, which is used by
Andy Clark's piece of works... CyberNeko Parser etc.
it the-format-that-should-not-be-named-echo or something.
It is/will be a format similar to RSS, with API to edit or archive news
items. Of potential interest for things like the FAN (Future Apache
Newsletter) ;-)
Necho reminds me of the word Neko, which is used by
Andy Clark's piece of works
On Fri, 11 Jul 2003 02:57:13 -0400
(Subject: RE: Jakarta Newsletter Issue 9 -- May-June 2003)
Noel J. Bergman [EMAIL PROTECTED] wrote:
you can't know who are the new committers without taking
snapshots of /etc/passwd or /home/cvs/CVSROOT/avail
AFAICS, committer uids in /etc/passwd started
On Fri, 11 Jul 2003 10:33:14 -0500
Stefano Mazzocchi [EMAIL PROTECTED] wrote:
This is what I would like to see:
1) the ASF publishes a newsletter (following the very nice style used
in the recent Jakarta one) that covers all the ASF endevours. Including
infrastructure, licensing, security
Noel J. Bergman escribió:
Something like:
article name=... url=... title=
summary
/summary
body
/body
/article
would handle multiple forms, e.g., brief e-mail, full e-mail, web site
edition. Cocoon could handle the entire publishing process, even producing
a downloadable
Stefano Mazzocchi wrote:
1) the ASF publishes a newsletter (following the very nice style used
in the recent Jakarta one) that covers all the ASF endevours. Including
infrastructure, licensing, security, incubation and all the
non-so-project stuff.
2) the newsletter is sent to announce@apache.org
Stefano Mazzocchi applauded:
on 7/10/03 4:21 PM Dirk-Willem van Gulik wrote:
clip/
So an apache-wide newsletter would be great. And posting it to apache
wide
announce, or even xposting it to all announce mailing list - sure. I'd
love that. Having it on the web is nice for archival too
- Original Message -
From: Stefano Mazzocchi [EMAIL PROTECTED]
on 7/10/03 4:21 PM Dirk-Willem van Gulik wrote:
So an apache-wide newsletter would be great. And posting it to apache wide
announce, or even xposting it to all announce mailing list - sure. I'd
love that. Having
project has something useful to say every month.
Building the newsletter via the wiki makes it easier to contribute
but I suspect that the normal size of a monthly apache newsletter
still wouldn't be much bigger than this one. I guess what I'm saying
is that I think we should let the newsletter
you can't know who are the new committers without taking
snapshots of /etc/passwd or /home/cvs/CVSROOT/avail
AFAICS, committer uids in /etc/passwd started at a particular value, and
monotonically increment for each new user, so couldn't he use that as an
indicator?
--- Noel
- Original Message -
From: Noel J. Bergman [EMAIL PROTECTED]
Stefano Mazzocchi applauded:
on 7/10/03 4:21 PM Dirk-Willem van Gulik wrote:
I think we should have an apache-wide newsletter and deliver it thru
announce@apache.org once a month.
+1 except for the frequency, which I
Ceki Gülcü [EMAIL PROTECTED] writes:
If I understand correctly, you are unwilling to receive one
Jakarta-related email per month, on say, announce@apache.org mailing
list. Is that the mailing list being considered?
With more than 15 projects, each one of which would presumably have
the right
I don't think community@ is a valid place for news of a newsletter anyway.
Perhaps announce@ for those who are interested.
david
- Original Message -
From: Thom May [EMAIL PROTECTED]
To: community@apache.org
Sent: Friday, July 11, 2003 10:55 AM
Subject: Re: Jakarta Newsletter Issue 9
* David N. Welton ([EMAIL PROTECTED]) wrote :
Ceki G?lc? [EMAIL PROTECTED] writes:
Sending a Java related email on announce@apache.org may breach the
possibly implicit contract between the list and its subscribers.
However, that seems more like a moral question rather than a
technical
David Reid wrote:
I don't think community@ is a valid place for news of a newsletter anyway.
Perhaps announce@ for those who are interested.
I agree, cross posting sucks in general and annoucements and the jakarta
newsletter are verging on OT for community@ as well.
I'd think
I don't think community@ is a valid place for news of a newsletter
anyway.
Perhaps announce@ for those who are interested.
the jakarta newsletter are verging on OT for community@ as well.
Perhaps, but it seems to me that this discussion has been about taking the
Jakarta Newsletter
be subscribed to
announce@ (and that the newsletter will miss some of its target audience)
then I still feel quite strongly that the solution isn't to cross post, but
to encourage people to subscribe to the correct list.
If cross posting becomes an acceptable solution to the problem of people not
being
On Fri, 11 Jul 2003 12:07:12 +0100
(Subject: Re: Jakarta Newsletter Issue 9 -- May-June 2003)
Thom May [EMAIL PROTECTED] wrote:
Why the obsession with email?
We have a (pretty good ;-) ) webserver. Why don't we have a web page?
www.apache.org/news/monthly or something.
http://www.debian.org
it is much lower.
This is what I would like to see:
1) the ASF publishes a newsletter (following the very nice style used
in the recent Jakarta one) that covers all the ASF endevours. Including
infrastructure, licensing, security, incubation and all the
non-so-project stuff.
2) the newsletter
On Fri, 2003-07-11 at 11:33, Stefano Mazzocchi wrote:
on 7/11/03 6:07 AM Thom May wrote:
This is what I would like to see:
1) the ASF publishes a newsletter (following the very nice style used
in the recent Jakarta one) that covers all the ASF endevours. Including
infrastructure
Stefano Mazzocchi wrote:
This is what I would like to see:
1) the ASF publishes a newsletter (following the very nice style used
in the recent Jakarta one) that covers all the ASF endevours. Including
infrastructure, licensing, security, incubation and all the
non-so-project stuff.
2
On 11/07/2003, at 05:33, Stefano Mazzocchi wrote:
1) the ASF publishes a newsletter (following the very nice style used
in the recent Jakarta one) that covers all the ASF endevours. Including
infrastructure, licensing, security, incubation and all the
non-so-project stuff.
2) the newsletter
* Stefano Mazzocchi ([EMAIL PROTECTED]) wrote :
This is what I would like to see:
1) the ASF publishes a newsletter (following the very nice style used
in the recent Jakarta one) that covers all the ASF endevours. Including
infrastructure, licensing, security, incubation and all the
non-so
to
announce@ (and that the newsletter will miss some of its target audience)
In fact it will reach more of the target audience, not less. As you say,
the solution is to encourage people to subscribe to the right list. Also,
the newsletter would be available on the web.
and provide a separate
Jeff Trawick escribió:
Stefano Mazzocchi wrote:
This is what I would like to see:
1) the ASF publishes a newsletter (following the very nice style used
in the recent Jakarta one) that covers all the ASF endevours. Including
infrastructure, licensing, security, incubation and all the
non-so
Noel,
Personally, I agree with those who feel that the text should be available
via e-mail, and considering the roughly 1 message per month traffic on
announce@, it is hard to argue that it is too much volume.
Agreed, I like the jakarta newsletter a lot.
But with the obvious caveat
But with the obvious caveat that an ASF wide newsletter might become quite
big if people write major dissertations, I'd rather see nice concise
precis
of recent activity, and links to more detail text where relevant, I'm more
likely to read it all that way.
Let's see what happens
am afraid it will be annoying for the subscribers.
Probably, I need more *inquiry* and collaborators.
(There's no problem creating new wikipages for xml-newsletter and
I can make the most use of the know-hows on the jakarta-newsletter)
Sincerely,
-- Tetsuya ([EMAIL PROTECTED
it???
We have different lists for different purposes. This content does not belong
on this list. Neither would an XML newsletter, an APR one or an HTTPD one.
david
- Original Message -
From: André Malo [EMAIL PROTECTED]
To: community@apache.org
Sent: Thursday, July 10, 2003 3:04 PM
Why not simply make it the Apache Newsletter, add the projects that
are
not there yet, and publish it here on [EMAIL PROTECTED]
+1
If we list up all the projects in ASF and make Apache-newsletter,
I am (very) afraid it will be too big for ezmlm :-)
I don't believe that the newsletter
is not a big deal in any case.
straw. camel's back.
there's no reason for the newsletter to be coming here that i can see.
one of the consequences of encouraging the breaking up of jakarta is that
there are a lot more apache projects (whether they started in jakarta or
not) who are feel interested
on 7/10/03 4:21 PM Dirk-Willem van Gulik wrote:
...
one of the consequences of encouraging the breaking up of jakarta is
that there are a lot more apache projects (whether they started in
...
if we do manage to get some momentum for an apache-wide newsletter, would
Please please
On Wed, 9 Jul 2003, Tetsuya Kitahata wrote:
... cut ... most wonderful newletter ...
Wow -you guys rocks ! Keep up the good work.
And I really do hope that this will keep its 'all things java and xml'
scope; despite ant and avalong becoming a PMC of their own!
Thanks!
Dw
Thank you for the comment!!
Well, I think Jakarta-Newsletter will keep in touch with the
'jakarta-related-projects'.. projects graduated from jakarta.
'XML Project' and 'WS-Project' are different from jakarta, I think.
However, in my mind, it might be wonderful if we can prepare
the 'XML
hi Tetsuya
thanks again for all the hard work in the limited time available for
newsletter 9. i'd you like to volunteer to create an xml newsletter as
well as a jakarta one then i'm sure it'd be a great success.
- robert
On Wednesday, July 9, 2003, at 05:41 PM, Tetsuya Kitahata wrote:
Thank you
Hello, All
We are now preparing the 'Jakarta Newsletter Issue 9',
news from May to June 2003, which would be published
in the middle of July 2003.
The 'Jakarta Newsletter Issue 9' will be appeared at
http://jakarta.apache.org/site/news/200305.html
and the editorial deadline would be 00:00 GMT
Hi,
For those of you that don't know I'm behind the effort for a monthly(ish)
newsletter from the folks at jakarta. The original aim was to help
developers stay informed of whats going on in the rest of Jakarta without
them having to monitor every list, each subproject would send in tidbits
Andrew C. Oliver wrote:
It would be nice if other people gave Rob a hand and maybe we expanded
this to a wider scope..
Just so people can see examples of what the finished product looks like
each month: http://jakarta.apache.org/site/news/
- Sam Ruby
Andrew C. Oliver wrote:
It would be nice if other people gave Rob a hand and maybe we expanded
this to a wider scope..
I was thinking of this and am going to contact Rob to offer my
services to be the Jakarta Commons *representitive* for the
newsletter, i.e. I will try to round up one
82 matches
Mail list logo
