Got a URL for one?
--- Noel
-Original Message-
From: Dirk-Willem van Gulik [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 04, 2003 16:36
To: community@apache.org
Subject: RE: Where we are.. continued..
On Tue, 4 Feb 2003, Noel J. Bergman wrote:
http://mapper.acme.com/?lat
Are the *.apache.org sites ever scanned for broken links?
I noticed to day that Eric Raymond moved his personal web site from
tuxedo.org to catb.org, invalidating all links to tuxedo.org. See
http://hurkle.thyrsus.com/~esr, which says My site has moved to
http://www.catb.org/~esr/. Please fix
,
commons-* and found only 3 incorrect links.
In any event, I'm wondering about the systematic issue.
Do you think about a general link-checker installed on daedalus? Hmmm, is
this really needed? IMHO this should be the responsibility of the
content-producing group.
cheers,
Erik
Noel J. Bergman
setup,
a cron job could kick it off at the desired schedule.
--- Noel
-Original Message-
From: Erik Abele [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 02, 2003 15:35
To: community@apache.org
Subject: Re: Verifying links
Noel J. Bergman wrote:
Erik,
You are most welcome
Oversight of content relating to a specific PMC should be the
repsonsibility
of said PMC.
That is one view. There may be others. I believe that there is interest in
having a consensus on policy first, and then a solution. Not too many
people have spoken up one way or another on that issue.
Costin,
I see several differences between mailing list and Wiki content:
1. posting policy
If you manage your Wiki with Wiki pages in conversation mode, shouldn't you
want similar control over Wiki posting as e-mail posting?
2. representation
I do see wiki as a transcript of opinions
Dirk-Willem van Gulik:
Noel J. Bergman wrote:
The three WikiAdmins are neither official nor representatives of a
proper
oversight body. The most logical group would be those who are
responsible
for the site module, and I don't believe that they want it.
Well - the PMC's could each
Now that it appears that a consensus is brewing, I'm finally posting this
message in public
---
There appears to be a consensus for a Wiki per-PMC approach until some other
Wiki technology might provide some other segmentation schema for oversight.
The purpose is to
: Saturday, February 01, 2003 16:46
To: community@apache.org
Subject: Re: Wiki - we have a problem :)
On Saturday, February 1, 2003, at 02:10 PM, Noel J. Bergman wrote:
a solution using the current Wiki code, I imagine that it would look
something like:
http://james.apache.org/wiki/
http
I hope we don't tear down the current one for a bit, make sure the PMC
owned ones are a functional replacement.
I understand your concern about data loss, and share it. See my comment
about starting the new ones as clones of the current one. And no need to
take down the old one (maybe make it
Thinking about it some more. I guess my concern is less about the data
and more about the people. I'm most concerned about pulling the rug
out from under people having fun before their a place they can move
their fun to.
I'm sure we can make the migration work. :-)
We wouldn't remove any
What I mean here is -not- the ASF cultural thing of having things
validated by your peers; but the oversight of the type that the
ASF as a US incorperated is supposed to maintain.
specificaly of the type which gets us in real-live(tm) trouble;
warez, child-porn, list of license keys, etc.
Justin,
The wikidiffs@ list received 77 emails yesterday. That's a *lot* of
traffic for a small group to handle reliably. I certainly can't keep
up with that.
Understood. One problem is that changes aren't merged. I probably do a
half dozen minor Wiki updates before I finish with an edit.
I wonder how this ended up on wikidiffs@
Looks like
http://nagoya.apache.org/wiki/apachewiki.cgi?TheStudentResearchPage was
something that Andy started. My guess is that Master Townhill e-mailed
wikidiffs because of Andy's comments on
http://nagoya.apache.org/wiki/apachewiki.cgi?WikiAdmin.
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]
rg
Do you still need to do something to enable searching? Doesn't seem to be
available.
--- Noel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
In the community@ archives you can find the vote on whether this list
should be open or closed.
WHAT archives? As I have commented on before, eyebrowse has none for
community@ (http://nagoya.apache.org/eyebrowse/SummarizeList?listId=108).
Are they elsewhere? If so, where?
--- Noel
We're not really trying to hide anything. What you might
be able to attribute to malice, attribute to, umm,
absentmindedness.
For the record, malice never occured to me as an option. I'd asked about
archives previously, without a response. So when the comment was ever so
casually made that
The life of a dyslexic is full of surprises. That should have read
This is a bad-thing(tm)..
I had figured as much from the earlier part of the paragraph. :-)
I assume that as soon as we create per PMC Wiki those PMC would
discover that they have pride of craft in the content of that Wiki.
People can do the same with patches on mailing list; and seem less likely
to abuse that. Perhaps the simple validation (and display) of a valid
email address may do the trick.
You are concerned about abuse. I don't disagree, but the mailing lists are
also capable of being abused. I would not
Is there a uniform release policy for the ASF? For example, here are two
documents:
http://httpd.apache.org/dev/release.html
Technically, any one can make a release of the source code due to the
Apache Software License. However, only members of the Apache HTTP Server
Project (committers) to
a friend of the court brief for the Board vs. Wiki.
Board vs. Wiki? That's somewhat amusing in its timing, considering that the
Chairman of the Board, as a private individual not in an official capacity,
(a) is the author of SubWiki, (b) posted a message to community@ in support
for Wiki use
In my book Andy (Oliver, not Clark) is the master of Wiki...
Andy gave myself and Ben Hyde admin access. From what Andy is saying, his
plan is to give that to anyone (within reason) who asks. I don't
particularly have a care, other than that people ought to know that such
things as deleting
Costin,
Consensus or at least a majority :-)
I believe he was using the common dictionary definition, not refering to
unanimity.
[agregating blogs ( or subsets ) from the apache community]
is a very different and IMO more important issue.
Putting this information togheter and making it
Justin, Sander, and I just chatted on IRC.
This reminds me. Many of us recognize the benefits of instant messaging,
via whatever method. However, when I first started contributing to James,
one of the things that came out from one longer time Community member was a
great deal of ...
Yup. Python people *and* Subversion people. :)
Well *that* much I knew. :-) The association between Collab.Net and the
ASF isn't obscured.
I keep wondering if some of the tigris.org projects will migrate to the ASF.
There appears to be a lot in common, including people. ASF uses (or will
Jeff,
Unless I missed a discussion elsewhere (I'm only on community@ and
infrastructure@, as well as project lists), Andy appeared to be complaining
about (a) people asking for changes to the Wiki without contributing
patches, and (b) the current lack of consensus on how to integrate
push-model
Because wiki's tend to fill with content rapdily, once you
use them for a little while you are pretty much locked in.
Counterpoint?
Personally, I'm getting mileage out of UseModWiki, despite its issues. I
wouldn't want to have to move every page in the Wiki, but I could cut
paste the
Greg Stein wrote (technical details omitted):
*if* we migrate to SubWiki or some other Wiki, then we can get the
data out of UseModWiki.
Sounds like your approach follows the truism that in the worst case any open
source code that can read its own data can be instrumented to become its own
Its too bad we don't have any decent perl programmers. I'm apparently
the master PERL programmer here. The rest of you are all talk.
I'm getting quite sick of your you're all talk attitude.
Chill the hell out.
damn. I was joking around. sheesh.
That was not at all clear from
For those of you who are humor-impaired, or not aware of the Perl Acme
meme, the Acme::* line of modules on CPAN are jokes.
Aha! :-) I knew there was a joke in there somewhere, but that little
tidbit does help to illuminate the punchline.
--- Noel
19:12
To: community@apache.org
Subject: Re: email notification done...sorta
Noel J. Bergman [EMAIL PROTECTED] writes:
[...]
I was going to reply that perhaps the choice of usemodwiki was a good
one as a turnkey thing, but perhaps not the best choice for the long
term due to the lack
Justin,
I don't particularly care which Wiki we use, so if one has benefits over the
other, great. But I would like to see the content migrated from usemodwiki
to Subwiki if that's what is going to be used. How viable is it to machine
migrate the content?
--- Noel
Bah. Use SubWiki, check out the Wiki pages into a working copy, make all
your changes, then commit them. Regular commit email sends the full bunch
of
changes.
grin Does this mean that Subversion is coming soon to replace a CVS
repository near us?
Not that updating a Wiki that way is in the
I'll bite ... what is Tapestry?
--- Noel
-Original Message-
From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 04, 2003 17:54
To: community@apache.org; Jakarta General List;
general@incubator.apache.org
Subject: Tapestry incubation
no-connotation
I am interested in content quality. I would probably subscribe
to the 'wiki-changes' list, since that would push the content under
my nose instead of having me actively reading each changed page online.
Right, that has been my point about push model communication. But do you
really want to
Yeah its still on my radar Noel, but as you say, I have to bond with my
kids...
If I were you, I know where my priority would be. :-) Happy Holidays.
--- Noel
no idea what nagoya is but Steven has a pretty fat server behind
cocoondev
According to the machines page, Nagoya is a Sun E4500. I don't have any
more clue than that (would be curious to know the actual configuration), but
E4500s tend to be pretty powerful beasts.
--- Noel
My personal suggestion would be to find a way to partition the wiki
pages per project and send those diffs to the various project mail
lists.
But I have no idea on how difficult/feasible that is with the current
software.
How good a PERL coder are you? [Actually, Danny Angus had mentioned
I'd much prefer mailing list notifications over RSS feeds. These types of
notifications shouldn't be pull.
Is there an engine that can pull from RSS on one side, and e-mail on
another? [Something to add to the nice-to-have list for James]
--- Noel
Andrew,
Around HotJava, the browser application? I suspect relatively little.
Around the component? I know several projects that would love to see it
resurrected.
--- Noel
Andrew,
Hallalujah! I have been asking about a Wiki on and off for months, and was
told as recently as a week ago that there were security reasons for not yet
having one. Kudos for just getting this done!
I am not familar with the code of this particular Wiki engine. What would
it take to
We transfered all of our domains from NSI to BulkRegister, and we have been
very happy with BulkRegister, so far.
--- Noel
Andrew,
There is already some sort of e-mail notification capability built into the
Wiki, although there seems to be some question over its usefulness on the
UseMod wiki site. But that at least provides us with a starting point.
I've downloaded the source code, and will have a look see next
Andrew,
With respect to the proposal that Sun be approached to turn over HotJava to
the ASF, do you have a suitable person at Sun to fulfill your
ContactAtSun - We'll need a contact at Sun in order to make this happen
role? Is Sun aware of the interest?
--- Noel
-Original
you might want to include Maven/Jelly in the section on
bulding, which currently has only Ant.
I've invited Mavenites to contribute, I've not recieved anything.
Ask Dion Gillard specifically. He's doing a lot on documenting Maven.
Other topics for your list: What is GUMP (just an example,
Sam Ruby wrote:
The ASF has supportted .forward files for e-mail for quite some time.
Would the mere act of putting a one line .forward file into your
~/public_html directory with your favorite URL be OK?
A bit more work for httpd than your ~name/public_html/community or some
such proposal,
Justin, if you would like to put forward a set of rules,
guidelines, and suggest an enforcement mechanism, I would be
inclined to endorse it if it would further consensus.
It occurs to me that if people want to guide the content of the ASF hosted
personal page, there could be a DTD, and the
ROUS wrote:
uniform education of (new) committers is one of the purposes of the
incubator
project. documenting these things for all, including existing committers,
is as well.
As a new committer, I not only appreciate that view, I want to know where to
find the info! :-)
--- Noel
201 - 248 of 248 matches
Mail list logo
