Re: ApacheCon logo: a little less busy
--- B. W. Fitzpatrick [EMAIL PROTECTED] wrote: Sander Temme [EMAIL PROTECTED] writes: http://www.red-bean.com/fitz/acpoker.jpg Very cute. :-) One thing though: the file is named acpoker.jpg, but the picture is black jack... Doh! I changed my mind after I started the file but forgot to change the filename. Hehe. -Fitz A great bad blackjack hand, but those would be even more promising as hole cards in Texas Hold-em. I'm sure that's what Fitz was thinking. ;) - Morgan = Morgan Delagrange http://jakarta.apache.org/commons http://axion.tigris.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [proposal] daedalus jar repository (was: primary distribution location)
--- Costin Manolache [EMAIL PROTECTED] wrote: On Fri, 28 Feb 2003 [EMAIL PROTECTED] wrote: In other words - as long as maven decisions affect only maven - I don't care. But if it affects other projects, and the repository certainly does - then the PMCs of those projects or the apache community are the ones that decide. Sure, but please take into account the work we've already done. Of course. The maven word comes up quite frequently on this thread :-) The issue is that the repository on daedalus will affect all apache projects that choose to use it ( to download and upload files ). Certainly a daedalus repository could be of use to many projects. One feature I would LOVE to see is a repository that contained the HEAD versions of every JAR in addition to snapshots, releases, etc. If I could flip a switch in my Maven, Ant, Centipede, etc. script and compile my project against the absolute latest and greatest, that would be an extremely useful sanity check. Whether those HEAD jars are built by Maven, GUMP, Centipede or Tool X makes no difference to me. However since GUMP is one of the only tools (perhaps the only tool?) that currently does the job, I find the statement that GUMP sucks disingenuous. Is GUMP easy to deploy for your own environment? Not really. Is it useful for building individualy projects a la Maven? No. Does it provide an effective continuous integration environment for Apache? Yes indeed. Does it suck? Hardly. If parts of GUMP are awkward, it's only because continuous integration is a thankless job. Thanks, GUMP. :) - Morgan = Morgan Delagrange http://jakarta.apache.org/taglibs http://jakarta.apache.org/commons http://axion.tigris.org http://jakarta.apache.org/watchdog __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [fyi] apache ego massage
One thing the article doesn't mention is that Britannica has three Apache committers and some contributors too. Committed to open source since 1768 (or thereabouts). Top that! ;) - Morgan --- Stefano Mazzocchi [EMAIL PROTECTED] wrote: http://java.sun.com/features/2003/02/britannica.html -- Stefano Mazzocchi [EMAIL PROTECTED] Pluralitas non est ponenda sine necessitate [William of Ockham] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = Morgan Delagrange http://jakarta.apache.org/taglibs http://jakarta.apache.org/commons http://axion.tigris.org http://jakarta.apache.org/watchdog __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Open this list
While I agree that this list should be opened up, I don't think this is the right time. While you were away, this issue was opened up again, and it seemed apparent that few opinions have changed since this issue was voted upon. I suggest tabling the issue for at least a few months, while working on some convincing arguments for allowing a wider audience. If we talk about it now, I'm pretty sure people will feel that it's been done to death and be fairly intransigent. - Morgan --- Andrew C. Oliver [EMAIL PROTECTED] wrote: I would like to propose that after seeing the way that this list functions up until now, that it the issue be reconsidered and that it be re-opened to the public. Main considerations: * there is already a private list *committers* which important issues like gee the server was attacked, please don't leave publically executable/writable files in your home director expecially you, you and you * The quality of the conversation will increase * The dumb user who stumbles in factor is pretty low. Since [EMAIL PROTECTED] was moved to the bottom of the mail2.html page under everything else, the moron flamewars have settled. Now all the flamewars are started and run by primarily committers. * promotes community and discourages the perception that we're arrogant snobs Minor considerations: * I will rejoin and stop whining about it. -Andy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = Morgan Delagrange http://jakarta.apache.org/taglibs http://jakarta.apache.org/commons http://axion.tigris.org http://jakarta.apache.org/watchdog __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Open this list
--- David Reid [EMAIL PROTECTED] wrote: If we talk about it now, I'm pretty sure people will feel that it's been done to death and be fairly intransigent. Very well put - even if a little down in tone... Only when it's put on a line all by its lonesome, I think. :) Anyway, I'm not picking on one side or the other; I think both camps will be stubborn at this point. I'd like to open up the list, but even I am getting tired of talking about it. - Morgan = Morgan Delagrange http://jakarta.apache.org/taglibs http://jakarta.apache.org/commons http://axion.tigris.org http://jakarta.apache.org/watchdog __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Hashing it out [was: Re: Clear the air Re: ATTN: Maven developers ...]
OK, Java-specific question. It seems likely that altering or inlining LGPL code pollutes the Apache license. Are you of the opinion that IMPORTING but not altering or distributing LGPL classes pollutes the Apache licecnse? And if so, can that be stated on the Wiki page? If LGPL code cannot be imported, it's pretty much useless in any capacity for Java projects. - Morgan --- Rodent of Unusual Size [EMAIL PROTECTED] wrote: [snip] i'm not even going to touch the infection issue at this point; it always makes my cephalic nodule hurt horribly. let's just say that we can't do anything that will trigger an infection of the asf's assets -- or those of someone using asf packages. if a licence permits *linking* against a library, there's no prohibition on our packages requiring the library in order to run properly. if a licence allows us to include the library, as a general rule we can package it with our stuff. if by linking with it or including it in our distributions we trigger a clause in its licence that either overrides the asf licence on our stuff, or forces the user to comply with rules more restrictive than the asf licence.. then we mustn't do that. [snip] = Morgan Delagrange http://jakarta.apache.org/taglibs http://jakarta.apache.org/commons http://axion.tigris.org http://jakarta.apache.org/watchdog __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Open community (was ... secret discussions ...)
Welcome to the minority, Joshua. :) - Morgan --- Joshua Slive [EMAIL PROTECTED] wrote: On Tue, 28 Jan 2003, Sander Striker wrote: community@ is the only ASF wide list that is opt-in and not bound to a certain topic (like infrastructure@ for example). committers@ always reaches _all_ committers if they want to participate or not. So that list is not an option. The fact that it is the only ASF-wide list for discussion seems to be an argument for opening it, not closing it. Anyway, there are arguments for and against, a bunch of them are in the reorg@ archives. In the community@ archives you can find the vote on whether this list should be open or closed. Yah. Right. And where would I find those archives? One good reason for opening a list is it allows us to have public archives. Sorry for rehashing an old issue, but I just can't imagine a topic I would want to discuss on here that I wouldn't want to be public. Apache is an open organization. All discussion should be open unless there is a very specific reason otherwise. And the only reasons I can think of are security, legal, and making decisions on trust (which I always put in quotes). None of that should be happening here. If I were to write a set of Apache principles, Open discussion and debate would certainly be one of them. We aren't following that here. Joshua. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = Morgan Delagrange http://jakarta.apache.org/taglibs http://jakarta.apache.org/commons http://axion.tigris.org http://jakarta.apache.org/watchdog __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
Re: [VOTE] Openness
Hey all, --- Vadim Gritsenko [EMAIL PROTECTED] wrote: Torsten Curdt wrote: [snip] VOTE 2: would you like to make it possible for non-committers to fully subscribe to this mail list? [ ] +1 yes, let's open it to everyone [ ] 0 don't know/don't care [X] -1 no, let's keep it for committers only ...OR THOSE INVITED Ditto. Actually, specifying invitees as a qualification to the -1 may not be necessary, if each invitee will need to be voted in individually anyway. Only if invitees may be added without a vote do we need to resolve the matter, and that's probably worthy of a specific second vote if -1 proves the majority opinion. Just pointing out that you probably needn't worry about this detail. IMO we should wait for the -1 result, and then determine the terms by which we will add invitees. - Morgan = Morgan Delagrange http://jakarta.apache.org/taglibs http://jakarta.apache.org/commons http://axion.tigris.org http://jakarta.apache.org/watchdog __ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/
RE: [VOTE] Openness
--- James Cox [EMAIL PROTECTED] wrote: Why are you changing the vote here? I would like to vote but you have changed the direction of this vote, in a way that's really wierd. Currently, as i understand it, the last vote favored opening the list to invited experts, with a public archive. How would I vote that here? -- james I think you want to vote +1 on the first issue and -1 on the second issue, with a subsequent vote later (if it's even necessary) to extend access to invited guests. The last vote was essentially a free-for-all write-in with no clear result IMO. You interpreted the last vote as allowing a public archive, but one could easily assert that the option 3, no public archive, won because it received the most votes. The contrary interpretation is that the public archive opinion won because options 1 and 2 both allow an archive and received more combined votes than option 3. It was an unclear format. - Morgan = Morgan Delagrange http://jakarta.apache.org/taglibs http://jakarta.apache.org/commons http://axion.tigris.org http://jakarta.apache.org/watchdog __ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/
