[ANNOUNCE] Apache River 2.1.1-incubating

The Apache River community is pleased to announce the release of Apache River v2.1.1-incubating. This release has actually been out for a little bit, we just didn't do an announcement (we apologize - still learning). The source and binary downloads are available here:

[Vote Result] Apache River 2.1.1 Incubating Release

ail-archives.apache.org/mod_mbox/incubator-general/200801.mbox/[EMAIL PROTECTED] > We'll be publishing Apache River 2.1.1 Incubating, and then moving on to our next release. :-) Thanks again. -Jim On Jan 14, 2008, at 12:38 AM, Jim Hurley wrote: Incubator PMC: The River community voted

[Vote] Apache River 2.1.1 Incubating Release

Incubator PMC: The River community voted on and has approved a proposal to release River 2.1.1 incubating. This is the first release from our project. We would like to request permission of the Incubator PMC to publish the release on the River Download page. The vote will be open through W

Re: 'Handling Crypto..' - River project

r export legal advisors know better). For these questions, always kick them across to [EMAIL PROTECTED] please :) Bill Jim Hurley wrote: We're (River incubator project) trying to comply with: "Handling Cryptography within an ASF Release" <http://www.apache.org/dev/cry

'Handling Crypto..' - River project

We're (River incubator project) trying to comply with: "Handling Cryptography within an ASF Release" This process talks only about software that has been self classified as 5D002 (has strong crypto classification). Parts of the Sun Jini Technology S

Re: Incubator Proposal: Pig

+1 -Jim On Sep 18, 2007, at 3:52 PM, Olga Natkovich wrote: Hi, Yahoo! research and development teams have developed a proposal below. The proposal is also available on wiki at http://wiki.apache.org/incubator/PigProposal. We would like to ask t

(confluence) wiki site ?

The River project is considering changing its project area from a velocity site which was originally setup to a confluence wiki site (or maybe now that JSPWiki is going to be an incubating project, that would be a better wiki choice?). Looking for advice/pointers/help on specifically how we could

Re: Discuss: Package Naming for Incubator Release of River

On Jul 23, 2007, at 12:30 PM, Robert Burrell Donkin wrote: On 7/23/07, Jim Hurley <[EMAIL PROTECTED]> wrote: On Jul 22, 2007, at 2:15 PM, Ted Husted wrote: > IMHO, unless there are trademark or licensing issues involved, : I don't believe there are issues involved - Sun fi

Re: Discuss: Package Naming for Incubator Release of River

On Jul 22, 2007, at 2:15 PM, Ted Husted wrote: IMHO, unless there are trademark or licensing issues involved, : I don't believe there are issues involved - Sun filed a Software Grant to contribute the code to the Foundation. -Jim ---

Re: [VOTE] Incubate new podling, "River" (nee Braintree, nee..., nee Jini)

Therefore, please vote on the proposal that follows : [ X] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) +1 :-) -Jim - To unsubscribe, e-mail: [EMAIL PROTE

Re: JiniProposal -> BraintreeProposal

t on a new name? -Jim Jim Hurley wrote: Thanks, Noel. I'm not sure if the potential trademark conflicts are problems in this case -- it's always a matter of gauging risk, and it's not clear if they'd be a problem or not. I agree that we'd like to get going, and we can

Re: JiniProposal -> BraintreeProposal

On Oct 25, 2006, at 6:35 PM, Noel J. Bergman wrote: Greg Stein wrote: It doesn't matter whatsoever as long as you are VERY consistently calling it "Apache Braintree" as you should be doing _anyways_ Would that apply equally to the two names that were more highly rated by the JINI community

Re: JiniProposal -> BraintreeProposal

Thanks, Noel. I'm not sure if the potential trademark conflicts are problems in this case -- it's always a matter of gauging risk, and it's not clear if they'd be a problem or not. I agree that we'd like to get going, and we can address the name issue again during incubation. thanks -Jim On Oc

JiniProposal -> BraintreeProposal

Hi all- Thank you to the 134 folks who participated in the survey to help us determine a new name for the "Jini" project proposal at Apache. The results are included below. The first preference was for "aladin" (related to the "genie" theme), but unfortunately, there are some potential TM issues

[JiniProposal at Apache] Name options

First off... a *huge* thanks to all the creative minds in the Jini Community and Apache incubator for coming up with over 100 proposed names. I'm sorry if your name doesn't appear on the final list, we had to narrow it (through TM vetting, etc.). We have settled on a final list of 12 option

podcast on Jini

Don't know if this is acceptable to send to this list -- so my apologies if I'm stepping in it here :-obut I know some people on the list may not be that familiar with Jini and so I thought I'd recommend a recent series of podcasts that the JavaPosse is doing on Jini (and the computecycles.dev

Re: [JiniProposal] Choosing a new name...

ty to help, I also encourage the proposers to consider choosing a name among yourselves. There's nothing wrong with that, and as it's the project you are proposing, it's natural that you can choose the name. geir Jim Hurley wrote: Hi all- I apologize for the gap in communicati

[JiniProposal] Choosing a new name...

Hi all- I apologize for the gap in communication on our Proposal. Following my summary post: and list discussion, I believe choosing a new name for the project and then updating our Proposal are the las

Re: JIni Proposal

Community" talk on the first day is a placeholder whilst we get a better understanding on where our Proposal sits with the incubator). thanks -Jim On Aug 22, 2006, at 3:18 PM, Jim Hurley wrote: We've had some good and spirited discussion on the JiniProposal over the last couple weeks. Tha

JIni Proposal

We've had some good and spirited discussion on the JiniProposal over the last couple weeks. Thanks to everyone who chimed in with your thoughts and opinions. In reviewing the discussion again, I think we can focus on three key items which seem to be at the root of some debate. For each item, I'll

Re: Jini : Separate Governance and Implementation Projects

I think we've had good discussion and have furthered the thinking in some areas that were contentious in the Proposal. We're probably aligned in some places and still have differences of opinion in others. I'll try and summarize in an email over the weekend to help (at least me!) sync where we ar

Re: Jini : Separate Governance and Implementation Projects

On Aug 15, 2006, at 12:50 AM, Noel J. Bergman wrote: : For example, what if we created [EMAIL PROTECTED] and jinn- [EMAIL PROTECTED] Forget the question of "how many podlings" --- I am simply talking about a list related to specification work, and a list related to implementation. Is that a

Re: Jini : Separate Governance and Implementation Projects

On Aug 15, 2006, at 4:46 PM, Jukka Zitting wrote: I'm not convinced the goal in the past was to have multiple implementations, vs allowing multiple implementations. I think the interpretation of this goal underlies both the naming and standard issues. In essence, does the Jini community see t

Re: Jini?

Besides the 'name question' -- are there any other questions or issues associated with the JiniProposal that we could be discussing? For reference, the submission from the incubator archives is at: I

Re: Jini?

Thanks, Mark, for following up with some of the thinking. I am unclear on what the process is... can someone shed some light? As far as the naming goes: - how can we determine if the "Jini" name is acceptable to Apache? - whether contributing the TM would be welcomed? - whether use of "Jin

Re: Jini?

Hi Matthias- Just to clarify the Jini area on Java.net (jini.dev.java.net)... the projects there are shared and/or collaborative works that primarily build on the core infrastructure (that would be in the Apache Jini project). Those projects include: tools, containers, abstraction frameworks, int

Re: Jini?

On Aug 7, 2006, at 12:19 PM, Sanjiva Weerawarana wrote: So whatever happened to the Jini proposal?? I just remembered that there was a lot of discussion but don't recall the conclusion. Sorry - we hit a snag around the name, and have been working to try and get untangled. There seemed to be

Re: [Proposal] Jini Project

On Jun 23, 2006, at 4:46 PM, Bob Scheifler wrote: Having written that, I guess I've just explained to myself why the ASF project should not be merely "Jini", and should either have a different name or an additional qualifier. (As for trademark issues, I'll defer to Jim Hurl

Re: [Proposal] Jini Project

On Jun 21, 2006, at 1:56 AM, Phil Steitz wrote: +1 (as in "will help"). From the text below and the comments in , I assume that the scope of the project will just be the core infrastructure. But you also mention "re

Re: [Proposal] Jini Project

On Jun 20, 2006, at 1:01 PM, Brian McCallister wrote: On Jun 19, 2006, at 7:15 AM, Jim Hurley wrote: This proposal seeks to create a project within the Apache Software Foundation to continue the development and advancement of Jini technology. It has broad backing from the Jini Community, and

[Proposal] Jini Project

* Geir Magnusson Jr ([EMAIL PROTECTED]) * Bob Scheifler ([EMAIL PROTECTED]) * Jim Waldo ([EMAIL PROTECTED]) * John McClain ([EMAIL PROTECTED]) * Brian Murphy ([EMAIL PROTECTED]) * Peter Jones ([EMAIL PROTECTED]) * Juan Ramirez ([EMAIL PROTECTED]) * Frank

[Proposal] Jini project

r ([EMAIL PROTECTED]) * Jim Waldo ([EMAIL PROTECTED]) * John McClain ([EMAIL PROTECTED]) * Brian Murphy ([EMAIL PROTECTED]) * Peter Jones ([EMAIL PROTECTED]) * Juan Ramirez ([EMAIL PROTECTED]) * Frank Barnaby ([EMAIL PROTECTED]) * Nigel Daley ([EMAIL PROTECTED]) * Fred Oliver (