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 it on
I want the acronym-list, acronym often used
in Apache.Org, to be put on wikipage, committers
module or somewhere appropriate.
e.g.
---
* AFAIK As Far As I Know
* ASAP As Soon As Possible
* BTW By The Way
* FAQ Frequently
On Fri, 11 Jul 2003 01:24:23 +0100
Rob Oxspring [EMAIL PROTECTED] wrote:
One point I would like to make though, and not wanting to detract
from this fantastic issue (thanks Tetsuya!), is that keeping the up
the momentum has proved difficult at times over the last year and
that not every
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
IMO there are enough acronym finders on the web already, I can't see any
need to have one here too.
Most acronyms used in english conversational prose are correctly identified
in listings like this, including the bizzare ROTFLMAO.
I use www.acronymfinder.com, and FYI this is what it says about NIH
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 that if there is
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 and
Noel,
However, in the interests of compromise between those who want just a
summary with link and those who want the full content, perhaps it would be
best to post a summary e-mail,
Don't you think annouce@ is the place for that?
If you're worried that subscribers to community@ won't be
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.
on 7/11/03 6:07 AM Thom May wrote:
Why the obsession with email?
push vs. pull
example: we are having this conversation and the information I'm sending
its pushed into your mailbox. I could post this information on a weblog
and then point you to it, but, in my experience, the chance that you
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) the
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 is
* 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
Danny,
As I said to you in the broader context, I wasn't saying that community@ is
the right place; just that I think it is hard to call it off-topic if it
covers the whole community.
Actually, announce@ was one of the places I'd suggested in an earlier
message. announce@ has almost no traffic,
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
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 that an
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. :-) And
23 matches
Mail list logo
