Dirk-Willem van Gulik wrote:
Within the ASF we have a number of projects which deal with formats
and standards close to OASIS.
random examples: docbook, uddi, relax ng.
We've been approached by OASIS to see if it makes sense to join them. This
is a call out to Community to see if that makes sense.
On linux:
http://www.jroller.com/comments/lsd?anchor=howto_install_subversion_and_the
On Mac OS X:
http://kasparov.skife.org/blog/2004/05/20
Man is that a pain to figure out!
cheers,
- Leo
-
To unsubscribe, e-mail: [EMAIL
, and the rest of the open source community stating our shared
position on the subject. Like Havoc Pennington writes
(http://ometer.com/desktop-language.html), the Community Should Decide
and It's time to start the discussion.
WDYT?
--
cheers,
- Leo Simons
Thom May wrote:
malicious users
huh? Who would that be?
--
cheers,
- Leo Simons
---
Weblog -- http://leosimons.com/
IoC Component Glue -- http://jicarilla.org/
Articles Opinions -- http://articles.leosimons.com
Leo Simons wrote:
comments? Good idea?
FWIW, I decided there was not enough interest to make me want to do the
work :D
--
cheers,
- Leo Simons
---
Weblog -- http://leosimons.com/
IoC Component Glue -- http
snip/
Thom and Ted, IIRC. I agreed with the decision. Several others did as
well, apparently. I think if gump's postings were limited to a
1-or-2-paragraph message once a day, it might've been different.
OTOH...reading a build failure just isn't as much fun as reading about
someone's holiday.
a timely reminder?
I'll volunteer to set it up if such a thing is desireable. I just need
the report schedule and some time.
Or maybe we could (mis)use Jira?
comments? Good idea?
--
cheers,
- Leo Simons
---
Weblog
that the network admins will cut me some slack. Given
the half a dozen tomcat instances and several dozen httpd instances that
run here at the university, I'll just go and thumb on some heads with a
big club if they don't :D
--
cheers,
- Leo Simons
Andrew C. Oliver wrote:
That¹s fine, but the results aren't very useful see this:
http://wiki.apache.org/general/FindPage?action=titlesearchvalue=FAQ
This is what I mean (across wikis):
http://nagoya.apache.org/wiki/apachewiki.cgi?search=FAQdosearch=1
The main issue I have with splitting things up
Hi Conor, Brendan, everyone,
Conor MacNeill wrote:
On Tue, 11 Nov 2003 05:40 am, Leo Simons wrote:
Hi gang,
Has anyone requested an ASF-wide clover license yet, or
discussed it with the clover people? Would that be a good
idea to do? Does anyone have any contacts over at Cortex?
i Leo,
I work
Hi gang,
Clover is a cool tool for calculating unit test coverage
of java software (http://www.thecortex.net/clover/). They
make free copies available to open source projects
(http://www.thecortex.net/clover/freelicense.jsp); some
ASF projects already have received such licenses
Ceki Gülcü wrote:
Avalon
http://avalon.apache.org/
done. cheers!
- Leo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Tim,
you missed my point. Sander asked whether commit access is, or is seen
as, a barrier.
The answer is: yes. It is one of many barriers that we have. You're
pointing out that
those are in place for a reason. Well, yeah.
For example, commit priviledge is something which is earned by
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
Costin Manolache wrote:
On Tue, 25 Feb 2003, Leo Simons wrote:
files in /dist/java-repository besides perhaps HEADER.html and
README.htmls...
Few simple questions:
Should we use 2 different dirs for src and binary distribution ? Or maybe
3 dirs ( src, bin, doc ) ?
based on current
Costin Manolache wrote:
I see no problem if Ant, Gump, Centipede cooperate on the jar repository -
and maven doesn't.
uhm, I would like to see all of the above and the rest of us cooperate
on this thing. The value
of everyone's work on setting up and maintaining such a repo decreases
rapidly
Costin Manolache wrote:
What policy should we use for removing older versions ( or we just keep
everything ) ?
my take: keep everything. Again, policy should be the same as for the
contents of /dist/. I dunno
if there is an asf-wide policy for that...looking at
Greg Stein wrote:
The Board exists to help projects in their work. We exist to protect the ASF
to ensure that it will continue to exist, to help projects. Our intent is to
let projects do whatever they feel is right and correct, subject to the
constraints of the operation of the ASF and to what we
Noel J. Bergman wrote:
As you have seen from some of our exchange and Costin's comments, there are
differing views on how to make use of the repository. Costin and I seem to
be of the option that a significant portion of the value of the repository
comes from sharing and centralizing the
on this topic held on the community@apache.org,
general@jakarta.apache.org and dev@avalon.apache.org mailing lists
as well as on other mailing lists, for the context in which these
questions arose.
thanks for your time and best regards,
- Leo Simons
Leo Simons wrote:
you get an ok on that from the board and/or the infrastructure team,
and consensus across the
community, and I'll be absolutely 100% behind any such plan.
scratch that, I'm in a Just Do It mood today. Just sent a message to
the board (who are
reading already anyway, but hey
Sam Ruby wrote:
- Leo (avalon pmc member acting sort-of on behalf of the java peeps
using the
lazy consensus model and the Just-Do-It-in-the-event-of-consensus
mindset :D)
I like that mindset. Note: the essence of lazy consensus is that such
actions are immeditely rolled back if an issue is
Noel J. Bergman wrote:
Which PMC is going to oversee the repository?
all PMCs whose committers 'commit' to the repository should maintain
some oversight. I
don't think there's an official precedent wrt how this works @ apache.
It might be possible
to get the infrastructure peeps to take on the
Noel J. Bergman wrote:
all PMCs whose committers 'commit' to the repository should maintain
some oversight.
Infrastructure hasn't considered that a good model for the Wiki, and I don't
know that it would work any better for the repository. Someone needs to
take responsibility for the
Hi all,
(sorry for the massive crosspost up front, as this is a proposal that
should in the end come from the various PMCs towards the infrastructure
team I'm doing lots of CCing, just once)
I've been giving this some thought. It has been pointed out that the
primary distribution location for
Noel J. Bergman wrote:
David,
I agree that there should be an e-mail. But it should be short, and consist
of little more than a reference to the web site. All of this information
should be available on the web site for review and update. As that content
is enhanced, e-mail can go out to [EMAIL
Hi all,
I've just updated the setup mentioned below to do handle the licensing
issue just a tiny bit better, up to the point
where I think (IANAL!) it is no longer in violation of any license.
http://cvs.apache.org/viewcvs.cgi/avalon/check-targets.ent
Sam Ruby wrote:
Leo Simons wrote:
recent board decree (saw it first on the infrastructure list)
(paraphrasing): the ASF must not distribute software packages (in any
form) licensed under LGPL, GPL or Sun Binary Code License in any way.
Sun's Binary Code license permits bundling as part of your
VOTE 1: would you like to make it possible for non-committers to read
this mail list thru a web archive?
[X] +1 yes, let's make it readable
[ ] 0 don't know/don't care
[ ] -1 no, let's keep it private
VOTE 2: would you like to make it possible for non-committers to fully
such as MARC, etc.
View 3: Close the list to all except members and committers.
View 1: +1 Sam, Steven Noles
+0
View 2: +1 Andy
+1
View 3: +1 Ken
-0
Please state your view and vote your conscience.
- Leo Simons
30 matches
Mail list logo
