You are viewing a plain text version of this content. The canonical link for it is here.
Posted to community@apache.org by Leo Simons <le...@apache.org> on 2003/04/05 17:05:02 UTC
news.apache.org (was: apache.org vs. mozilla.org)
Stefano Mazzocchi wrote:
>Now, I'm asking: what if the ASF provides its own news server that wraps
>around all our current mail lists setup and make them available to all
>news-archiving services and news-reading clients?
>
+1
NNTP makes more sense than SMTP for group discussions.
I read allmost all OSS mailing lists I participate in through gmane. It
kicks major ass.
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org
RE: news.apache.org (was: apache.org vs. mozilla.org)
Posted by "Noel J. Bergman" <no...@devtech.com>.
> Two problems I'd have with switching to NNTP exclusively:
Why would anyone switch exclusively? Looks like Pier has done as nice job
integrating the news and mail feeds. If adopted officially, that would be a
good thing to keep in mind down the road.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org
Re: news.apache.org (was: apache.org vs. mozilla.org)
Posted by Rich Bowen <rb...@rcbowen.com>.
On Sun, 6 Apr 2003, Stefano Mazzocchi wrote:
> news.apache.org
>
> which *wraps* (NOT REPLACE!) the current SMTP-based infrastructure?
+1
Yes, this would be very nice, and would save me the trouble of
struggling to get my internal NNTP mirror of the list to actually work.
--
Rich Bowen - rbowen@rcbowen.com
Author - Apache Administrator's Guide
http://www.ApacheAdmin.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org
RE: news.apache.org (was: apache.org vs. mozilla.org)
Posted by "Noel J. Bergman" <no...@devtech.com>.
> So, summing up, is anybody against running
> news.apache.org
> which *wraps* (NOT REPLACE!) the current SMTP-based infrastructure?
+1 to do it, assuming my prior concerns about NNTP connectivity aren't an
issue.
> This will also work as a permanent archive and will probably be picked
> up by google groups to provide nice mail searching
Given the problems with eyebrowse that have recently become a constant, this
would be a good thing. I would assume that at least for the time being that
only public lists would be accessible via the public news server.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org
Re: news.apache.org (was: apache.org vs. mozilla.org)
Posted by Stefano Mazzocchi <st...@apache.org>.
on 4/6/03 12:17 AM Danny Angus wrote:
>>Two problems I'd have with switching to NNTP exclusively:
>
>
> I would hope that this discussion is about augmenting the listservers by providing NNTP as an alternative means of access, not a replacement.
Yes, people, do not worry: the discussion is about *augmenting*, not
about replacing anything.
In fact, ezmlm *WILL* remain as it is. I never even thought about
changing it for a second!
NNTP can provide a *wrapper* on top of our SMTP-based infrastructure so
that people can choose their favorite use to access the meat and
messages are *NEVER* removed.
Personally, I would probably keep using email for the mail list I mostly
follow, but then use news for the lists I just lurk sometimes. So that i
don't have to keep myself subscribed to them *AND* I get a nicer client
than a web interface to browse them (an awesome web-based mail archive
browsing SUCK ASS compared to any decent news client!)
If there is consensus about this, we can move it over to infrastructure.
So, summing up, is anybody against running
news.apache.org
which *wraps* (NOT REPLACE!) the current SMTP-based infrastructure?
This will also work as a permanent archive and will probably be picked
up by google groups to provide nice mail searching (that we could also
hook into our project web pages directly!)
Thoughts?
--
Stefano.
---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org
RE: news.apache.org (was: apache.org vs. mozilla.org)
Posted by Danny Angus <da...@apache.org>.
> Two problems I'd have with switching to NNTP exclusively:
I would hope that this discussion is about augmenting the listservers by providing NNTP as an alternative means of access, not a replacement.
---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org
Re: news.apache.org (was: apache.org vs. mozilla.org)
Posted by Tom Copeland <to...@infoether.com>.
> We had stumbled on the discovery that by normalizing the work so it all
> happened in one place intermediated by the machine we were more
> thoughtful, more efficient, more convivial, effective due to the
> orthogonal skills, able to tap into bits of serendipity, able to work
> with people who could be prickly in person, etc. etc. etc.
I've had this sort of experience around a Wiki. People started to refer
to "the DevConfig page" where we posted host names and such... everyone
knew where to go to get the current info.
> One thing that would happen in that context was that NNTP threads would
> often lie idle for months only to suddenly come back to life. That is
> one reason it could be used for working on individual
> bugs/enhancements/ports/etc.
Yup, very Wiki-ish.
Fun stuff!
Yours,
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org
Re: news.apache.org (was: apache.org vs. mozilla.org)
Posted by Ben Hyde <bh...@pobox.com>.
A note were in Ben has post Vietnam flashback...
Justin Erenkrantz wrote:
> Leo Simons <le...@apache.org> wrote:
>
>> NNTP makes more sense than SMTP for group discussions.
>
> No, it doesn't necessarily.
I was in a room yesterday with a lot of people who have been spending
way too much time attempting to 'understand open source'. I am always
greatly amused by these gathering because you have a group of extremely
smart people attempting to tease apart the mystery of what we do.
That's fascinating to listen too. But they are always attempting to
do so with out getting the hands dirty. At one point during the day
they spent a good two hours discussing one thread in the Linux kernel
mailing list. They looked at the first four messages and then were
given a summary of the other 175 messages. I was the only person in
the room that had the least clue what the topic of the thread was.
What I often say in these gathering is that Open Source is both a very
old process, i.e. people cooperating to solve problems, and a very new
one, i.e. manufacturing of a document intermediated by computers. We
are a long way from having searched the space of all possible schemes
for doing it effectively. That even the simplest things, like what
affordances on the tools might help are just beginning to get some
experimentation.
For example would open source projects work better if CVS was more
enthusiastic about forking? Would a cooperative drawing tools help?
Is there a right size for a repository, or a community, or an
appropriate way to manage the boundaries around these? Nobody knows,
but we have lots of intuitions that may or may not just be cargo cult
experiences.
I have a lot of nostalgic affection for using NNTP rather than SMTP for
this stuff. The first project I ever worked on that was effectively
intermediated using computers and networks used NNTP. 1980-85 I worked
on a very complex compiler project and we used NNTP to organize the
narrative around the work. For example we used individual threads for
each bug. We never discarded any messages. The entire message store
was in flat files on the file system so we could use unix tools to
search for lost bits of info - like "did heather say something about
stack chunks a few weeks back". I vividly recall noticing about half
way thru that project that we all stopped talking about the work in the
halls, that we only talked about life in the halls. That struck some
of the management as very odd.
We had stumbled on the discovery that by normalizing the work so it all
happened in one place intermediated by the machine we were more
thoughtful, more efficient, more convivial, effective due to the
orthogonal skills, able to tap into bits of serendipity, able to work
with people who could be prickly in person, etc. etc. etc.
This was also the first time I saw automated builds and testing used to
help developers avoid embarrassment. The first time I saw builds and
testing triggered by commits so we could shorten the interval between
break and fix - and hence increase the chance that the guy that broke
it could remember what he thought he was doing. It was also the first
time I got the commits posted to netnews so many eyes could casually
proof read them.
One thing that would happen in that context was that NNTP threads would
often lie idle for months only to suddenly come back to life. That is
one reason it could be used for working on individual
bugs/enhancements/ports/etc. The threading seemed more robust then it
it ever seems to in dev@httpd.apache.org. I assume that was because we
were all using the exact same client software then.
These days I have a lot of trouble seeing the difference between a good
news setup and a good mail setup. But both need archive, threading,
search etc. etc. I run all the dev@apr.apache.org email into my
in-house news server, for example.
Of course the major user list for httpd is netnews based.
- ben
---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org
Re: news.apache.org (was: apache.org vs. mozilla.org)
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Saturday, April 5, 2003 5:05 PM +0200 Leo Simons <le...@apache.org>
wrote:
> NNTP makes more sense than SMTP for group discussions.
No, it doesn't necessarily. NNTP was based for transient discussions rather
than discussions that have lasting impact.
> I read allmost all OSS mailing lists I participate in through gmane. It
> kicks major ass.
Two problems I'd have with switching to NNTP exclusively:
- NNTP server admins tend to be very aggressive about deleting messages.
We could take the policy of never deleting messages off *our* news server, but
that doesn't allow us to synchronize/use other NNTP hosts. That'd be the
major benefit of using NNTP exclusively - people could read the lists on their
local NNTP server rather than our private server.
But, if I go away for a week and come back, I could have missed messages that
my local Usenet server harvested. That's not acceptable.
- Disconnected support and filtering would be non-existant
There would be no way to read the lists offline unless I install my own NNTP
server locally that synchronizes. Uh, no. And, I have to rely on the
filtering scheme of the news server rather than my own custom scheme. I have
some lists that go to the same mailbox (namely related CVS commits) - not
everyone would agree with this filtering scheme. But, it's the way I prefer
it.
So, I don't really care if we offer NNTP as well as keeping ezmlm, but if you
remove email access, you'll hear my loud screams. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org