Re: Competing projects was Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Davanum Srinivas wrote: Is this about competing podlings? or existing projects/new podlings? The Competing Projects thread is a general umbrella of how the incubator should approach any two proposed podlings that overlap in scope, or a proposed podling that overlaps in scope with an existing podling/project. Niclas said it well, let the code speak for itself. It would add an extra burden on the incoming project; Project Foo intersects the functionality of project Bar. We take a different design approach by using ... which will accomplish (It's not necessary, and probably in poor taste to add project Foo will trump project Bar by ) And the reviewers approving incubation would need to be comfortable that there is a technical reason for two implementations. If there is, great, let it incubate :) Healthy competition of code is always good. We shouldn't treat two of the competing code bases within the ASF any differently than one implementation at the ASF, and one outside at codehaus, sourceforge, or in the commercial sector. Let code speak for itself. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Competing projects was Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Is this about competing podlings? or existing projects/new podlings? -- dims On 12/26/06, William A. Rowe, Jr. [EMAIL PROTECTED] wrote: Jim Jagielski wrote: On Dec 23, 2006, at 11:16 AM, Justin Erenkrantz wrote: I think it's a concern because the precedent puts the podling on the defensive and in the mind set of oh, if there's a competing project, we won't accept you. The fact that there's a project already here that 'competes' is irrelevant to us and I don't want to confuse the podlings into thinking that's a criteria when it's certainly not. -- Ah, I see your point. My PoV is that it's better to nip any such things in the bud first. This places those who would complain on the defensive ;) But competition is a fact of the real world, and for some podlings its a prime factor *for* its inclusion. But it should never be a factor for its rejection. Depends. We shouldn't reject a podling with overlapping scope that differs from another podling in engineering / design paradigms. We bloody well should think twice before accepting a competing podling that differs mostly in personalities. Been there, done that, archived the bloodshed in apmail. When we have two competing communities because folks can't accept the simplest ASF meritocracy and let code speak for itself, one, the other, or both are broken :) ASF projects are unique. People can truly dislike others in the same project, and yet collaborate towards a common goal. Not that this is healthy for the people, but the projects and communities should survive personality conflicts when they are operating properly. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT] Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
I gave it a few more days because of the Christmas holiday and preparations. The results : +1 from Geir, Niclas, Phil, Henri, Bertrand, Jukka, Craig, David W, Richard, Craig, Gianugo, Mark, Robert, Brian, Nigel, Dan C, Bob, Noel, Juan, Justin, Jim H, Bill, Dan R, Jim Jagielski +0 from Yoav No other votes cast. (I hope I didn't miss anyone). As we received an adequate number of +1 votes from Incubator PMC members, this vote passes :) I'll get the necessary infrastructure machinery going, staring with the mail lists. geir On Dec 20, 2006, at 10:46 PM, Geir Magnusson Jr. wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. Therefore, please vote on the proposal that follows : [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) The proposal can be found here : http://wiki.apache.org/incubator/RiverProposal and is included below for archival purposes : RiverProposal *Proposal for new project River* 8 December 2006 (0) rationale Jini technology is a service oriented architecture that defines a programming model which both exploits and extends Java technology to enable the construction of secure, distributed systems consisting of federations of services and clients. Jini technology can be used to build adaptive network systems that are scalable, evolvable and flexible as typically required in dynamic computing environments. Quoting from The Jini Specifications (http://java.sun.com/docs/ books/jini/spec/) book: Jini technology is a simple infrastructure for providing services in a network, and for creating spontaneous interactions between programs that use these services. Services can join or leave the network in a robust fashion, and clients can rely upon the availability of visible services, or at least upon clear failure conditions. When you interact with a service, you do so through a Java object provided by that service. This object is downloaded into your program so that you can talk to the service even if you have never seen its kind before - the downloaded object knows how to do the talking. That's the whole system in a nutshell. Sun Microsystems originally introduced the technology in January, 1999 by providing a Jini Technology Starter Kit (http:// starterkit.dev.java.net/). This includes a contributed implementation of all of the specifications, as well as helpful utilities and tools. The source code was made available through the Sun Community Source License (SCSL) as an attempt to make the code widely available and accessible to both individuals and companies. Sun has continued to innovate throughout the years, releasing many versions of the starter kit. The license associated with the starter kit was changed (http://archives.java.sun.com/cgi-bin/wa? A2=ind0503L=jini-usersO=AP=36217) in March, 2005 to the Apache License, Version 2.0. Since its beginning, there was desire and effort to form a developer community around the technology. This has helped to create an interesting, active, and passionate community - the Jini Community. This global Community has engaged on technology projects, discussions and debates, events, and a decision making process. It has contributed to, and helped influence the direction of the starter kit. Some of the collaborative technology projects have led to key contributions being used by other technology projects as well as commercial products. One example is the Service UI API (http://www.artima.com/jini/serviceui/), which is a way to attach user interfaces to Jini services. Despite the obvious successes of the technology and Community, some changes are in store as outlined in a recent note to the Community: A New Day (http://archives.java.sun.com/cgi-bin/wa? A2=ind0604L=jini-usersF=S=P=4029). The most critical part of the new plan is to find the right place for the future development and advancement of the core Jini technology. We wanted an environment that was synergistic with our exisiting Community culture -- so one that is active, with open communication and collaboration, and a reputation for producing high quality software. We think we've found that place with the Apache Software Foundation. (0.1) criteria /Meritocracy:/ The River project will be meritocractic. The project will follow the guidelines (http://apache.org/foundation/how-it- works.html#meritocracy) of the Apache Software Foundation. In order to achieve this, we plan on proactively recruiting
Re: Competing projects was Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Tuesday 26 December 2006 14:24, William A. Rowe, Jr. wrote: People can truly dislike others in the same project, and yet collaborate towards a common goal. If we take another heated example, Avalon, which was heavily criticized for its unhealthy community; IMHO, it was the different 'common' goals that created the flamefest and the so called personal conflicts and dislikes. Overlapping in Scope is IMHO not enough reason to disallow a new community. That would be like IETF saying, Hey, we don't want IMAP. Go to the POP guys and work it out with them. We should allow different approaches to the same problem domain, and as you say Let the Code Speak for itself. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Competing projects was Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Jim Jagielski wrote: On Dec 23, 2006, at 11:16 AM, Justin Erenkrantz wrote: I think it's a concern because the precedent puts the podling on the defensive and in the mind set of oh, if there's a competing project, we won't accept you. The fact that there's a project already here that 'competes' is irrelevant to us and I don't want to confuse the podlings into thinking that's a criteria when it's certainly not. -- Ah, I see your point. My PoV is that it's better to nip any such things in the bud first. This places those who would complain on the defensive ;) But competition is a fact of the real world, and for some podlings its a prime factor *for* its inclusion. But it should never be a factor for its rejection. Depends. We shouldn't reject a podling with overlapping scope that differs from another podling in engineering / design paradigms. We bloody well should think twice before accepting a competing podling that differs mostly in personalities. Been there, done that, archived the bloodshed in apmail. When we have two competing communities because folks can't accept the simplest ASF meritocracy and let code speak for itself, one, the other, or both are broken :) ASF projects are unique. People can truly dislike others in the same project, and yet collaborate towards a common goal. Not that this is healthy for the people, but the projects and communities should survive personality conflicts when they are operating properly. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Jim, I've updated the proposal in the wiki, hopefully addressing your two concerns - noting that there are no other implementations of Jini technology at the ASF, and noting that committership for the initial committers will be granted upon engagement with the project, as determined by the mentors. I hope this addresses your concerns, and that with your vote on this, we will conclude the vote today. geir On Dec 23, 2006, at 9:28 PM, Jim Jagielski wrote: Noel J. Bergman wrote: Jim, Keep in mind that JINI significantly predates all of the current Web Services efforts, not just here but anywhere. Technically, SOAP at Microsoft *might* predate JINI, but JINI was out and about (in so far as it has ever gained much marketshare) before Web Services as we know them. Thanks for the info, but I didn't need it. Asking that something be addressed/mentioned/explained in a proposal doesn't imply the asker is clueless :) -- == = Jim Jagielski [|] [EMAIL PROTECTED] [|] http:// www.jaguNET.com/ If you can dodge a wrench, you can dodge a ball. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Dec 24, 2006, at 9:06 AM, Geir Magnusson Jr. wrote: Jim, I've updated the proposal in the wiki, hopefully addressing your two concerns - noting that there are no other implementations of Jini technology at the ASF, and noting that committership for the initial committers will be granted upon engagement with the project, as determined by the mentors. I hope this addresses your concerns, and that with your vote on this, we will conclude the vote today. ++1 on the proposal! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Competing projects was Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Dec 22, 2006, at 11:18 AM, Justin Erenkrantz wrote: On 12/22/06, Jim Jagielski [EMAIL PROTECTED] wrote: A simple one-liner similar to Geir's No other ASF project or podling in the architecture space is based on Jini is enough I think... This is getting off-topic, but really why do we care? We don't. As I've said many times, having competing projects IS good. All I've said is that when proposals come in they should simply acknowledge it and mention how/why they are different. We have lots of competing proposals and projects all across the ASF. And, many of them don't communicate for extremely petty and personal reasons; some don't communicate because they disagree on the technical direction. If there's a community around *this* proposal, that's all that I care about. -- justin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Competing projects was Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Dec 22, 2006, at 11:18 AM, Justin Erenkrantz wrote: We have lots of competing proposals and projects all across the ASF. And, many of them don't communicate for extremely petty and personal reasons; IMO, that is a shame... competition is good. Territorialism (if that's even a word :) ) isn't. some don't communicate because they disagree on the technical direction. That, of course, is a whole different matter... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Competing projects was Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Dec 23, 2006, at 10:41 AM, Jim Jagielski wrote: On Dec 22, 2006, at 11:18 AM, Justin Erenkrantz wrote: On 12/22/06, Jim Jagielski [EMAIL PROTECTED] wrote: A simple one-liner similar to Geir's No other ASF project or podling in the architecture space is based on Jini is enough I think... This is getting off-topic, but really why do we care? We don't. As I've said many times, having competing projects IS good. All I've said is that when proposals come in they should simply acknowledge it and mention how/why they are different. And, for what it's worth, what is the sense of going through issues and learning lessons (I'm thinking CeltixFire/CXF primarily at this point) if not to make adjustments to avoid them in the future. 2 things we learned from that: 1. Podlings that appear to compete with other podlings or projects create friction, either rightly or wrongly (I say wrongly, of course). So efforts should be made to reduce that. Simple acknowledge is a nice easy way to do that. 2. The relationship between the initial committer list and initial PPMC is vague, or, at least, not clear enough that we had different people (one of which was a Mentor) have differing views and who was actually part of the PPMC. Again, why not simply avoid this potential by making it explicit. I really fail to see how all that is such a big deal. We're talking an additional 2 sentences - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Competing projects was Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On 12/23/06, Jim Jagielski [EMAIL PROTECTED] wrote: I really fail to see how all that is such a big deal. We're talking an additional 2 sentences I think it's a concern because the precedent puts the podling on the defensive and in the mind set of oh, if there's a competing project, we won't accept you. The fact that there's a project already here that 'competes' is irrelevant to us and I don't want to confuse the podlings into thinking that's a criteria when it's certainly not. -- justin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Competing projects was Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Dec 23, 2006, at 11:16 AM, Justin Erenkrantz wrote: On 12/23/06, Jim Jagielski [EMAIL PROTECTED] wrote: I really fail to see how all that is such a big deal. We're talking an additional 2 sentences I think it's a concern because the precedent puts the podling on the defensive and in the mind set of oh, if there's a competing project, we won't accept you. The fact that there's a project already here that 'competes' is irrelevant to us and I don't want to confuse the podlings into thinking that's a criteria when it's certainly not. -- Ah, I see your point. My PoV is that it's better to nip any such things in the bud first. This places those who would complain on the defensive ;) But competition is a fact of the real world, and for some podlings its a prime factor *for* its inclusion. But it should never be a factor for its rejection. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Jim, Keep in mind that JINI significantly predates all of the current Web Services efforts, not just here but anywhere. Technically, SOAP at Microsoft *might* predate JINI, but JINI was out and about (in so far as it has ever gained much marketshare) before Web Services as we know them. In any event, I think that overlap could be considered in terms of potential synergies (technical and community). Those are things that I'd like to see more from Synapse (WSDL focused ESB), Tuscany (SCA focused ESB) and ServiceMix (JBI focused ESB), for example. I am quite interested to see what JINI will bring to the table in terms of inter-operability and added value at a time when most people are focused on models based on BPEL and WSDL-described services. And I do believe that it has such to offer. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Competing projects was Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Justin Erenkrantz wrote: We have lots of competing proposals and projects all across the ASF. And, many of them don't communicate for extremely petty and personal reasons; some don't communicate because they disagree on the technical direction. While they are within the Incubator, I'd prefer to see the extremely petty reasons reduced. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Competing projects was Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On 12/23/06, Noel J. Bergman [EMAIL PROTECTED] wrote: While they are within the Incubator, I'd prefer to see the extremely petty reasons reduced. And, I'd like a pony, too. =P -- justin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Competing projects was Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Justin Erenkrantz wrote: On 12/23/06, Noel J. Bergman [EMAIL PROTECTED] wrote: While they are within the Incubator, I'd prefer to see the extremely petty reasons reduced. And, I'd like a pony, too. =P -- justin Did you ask Santa? :) -- === Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ If you can dodge a wrench, you can dodge a ball. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Noel J. Bergman wrote: Jim, Keep in mind that JINI significantly predates all of the current Web Services efforts, not just here but anywhere. Technically, SOAP at Microsoft *might* predate JINI, but JINI was out and about (in so far as it has ever gained much marketshare) before Web Services as we know them. Thanks for the info, but I didn't need it. Asking that something be addressed/mentioned/explained in a proposal doesn't imply the asker is clueless :) -- === Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ If you can dodge a wrench, you can dodge a ball. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Dec 21, 2006, at 5:37 PM, Dan Creswell wrote: From experience of evangelizing Jini I find each person's SOA definition to be different from another's and I have to argue/discuss on a case by case basis. So I kind of agree it's a valid item for discussion but given the above experience I really am not sure exactly how one provides an exhaustive/useful explanation to handle this discussion (in it's myriad of forms) in the proposal. A simple one-liner similar to Geir's No other ASF project or podling in the architecture space is based on Jini is enough I think... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Competing projects was Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On 12/22/06, Jim Jagielski [EMAIL PROTECTED] wrote: A simple one-liner similar to Geir's No other ASF project or podling in the architecture space is based on Jini is enough I think... This is getting off-topic, but really why do we care? We have lots of competing proposals and projects all across the ASF. And, many of them don't communicate for extremely petty and personal reasons; some don't communicate because they disagree on the technical direction. If there's a community around *this* proposal, that's all that I care about. -- justin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
+1 from me too Bill Bill Venners President Artima, Inc. http://www.artima.com Geir Magnusson Jr. wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. Therefore, please vote on the proposal that follows : [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) The proposal can be found here : http://wiki.apache.org/incubator/RiverProposal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
[ ] +1 Accept River as a new podling as described below +1 Dan Rollo (cloutless vote) -- This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
+1 BR, Jukka Zitting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On 12/20/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote: [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) +1 Craig
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
[ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) +1 -- David N. Welton - http://www.dedasys.com/davidw/ Linux, Open Source Consulting - http://www.dedasys.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Dec 21, 2006, at 1:47 AM, Henri Yandell wrote: On Thursday 21 December 2006 11:46, Geir Magnusson Jr. wrote: [x] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) Good name too. I've always hoped that someone would wish to call an ASF project Fog Think about it :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Dec 20, 2006, at 10:46 PM, Geir Magnusson Jr. wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. Therefore, please vote on the proposal that follows : [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) Could you address the overlap with other ASF projects and podlings which are in similar technology space? Why a new and distinct podling and not joining/helping them? Also, I'm assuming graduation to TLP (I may have missed that in the proposal)? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Dec 21, 2006, at 9:01 AM, Jim Jagielski wrote: On Dec 20, 2006, at 10:46 PM, Geir Magnusson Jr. wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. Therefore, please vote on the proposal that follows : [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) Could you address the overlap with other ASF projects and podlings which are in similar technology space? There are none doing Jini at this time. Why a new and distinct podling and not joining/helping them? See above :) Also, I'm assuming graduation to TLP (I may have missed that in the proposal)? Oh - whoops. Yes, because we're asking for Incubator PMC as sponsor (rather than another PMC), my expectation is that this will be a TLP. geir - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Good name too. 'Apache River' is very close to 'Apache Rivet', but they are in different areas, so hopefully won't get mixed up much. -- David N. Welton - http://www.dedasys.com/davidw/ Linux, Open Source Consulting - http://www.dedasys.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Jim Jagielski wrote: On Dec 20, 2006, at 10:46 PM, Geir Magnusson Jr. wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. Therefore, please vote on the proposal that follows : [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) Could you address the overlap with other ASF projects and podlings which are in similar technology space? Why a new and distinct podling and not joining/helping them? Can you provide an indication as to which projects and podlings you think this overlaps with? Thanks, Dan. Also, I'm assuming graduation to TLP (I may have missed that in the proposal)? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
+1 - richard Geir Magnusson Jr. wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. Therefore, please vote on the proposal that follows : [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) The proposal can be found here : http://wiki.apache.org/incubator/RiverProposal and is included below for archival purposes : RiverProposal *Proposal for new project River* 8 December 2006 (0) rationale Jini technology is a service oriented architecture that defines a programming model which both exploits and extends Java technology to enable the construction of secure, distributed systems consisting of federations of services and clients. Jini technology can be used to build adaptive network systems that are scalable, evolvable and flexible as typically required in dynamic computing environments. Quoting from The Jini Specifications (http://java.sun.com/docs/books/jini/spec/) book: Jini technology is a simple infrastructure for providing services in a network, and for creating spontaneous interactions between programs that use these services. Services can join or leave the network in a robust fashion, and clients can rely upon the availability of visible services, or at least upon clear failure conditions. When you interact with a service, you do so through a Java object provided by that service. This object is downloaded into your program so that you can talk to the service even if you have never seen its kind before - the downloaded object knows how to do the talking. That's the whole system in a nutshell. Sun Microsystems originally introduced the technology in January, 1999 by providing a Jini Technology Starter Kit (http://starterkit.dev.java.net/). This includes a contributed implementation of all of the specifications, as well as helpful utilities and tools. The source code was made available through the Sun Community Source License (SCSL) as an attempt to make the code widely available and accessible to both individuals and companies. Sun has continued to innovate throughout the years, releasing many versions of the starter kit. The license associated with the starter kit was changed (http://archives.java.sun.com/cgi-bin/wa?A2=ind0503L=jini-usersO=AP=36217) in March, 2005 to the Apache License, Version 2.0. Since its beginning, there was desire and effort to form a developer community around the technology. This has helped to create an interesting, active, and passionate community - the Jini Community. This global Community has engaged on technology projects, discussions and debates, events, and a decision making process. It has contributed to, and helped influence the direction of the starter kit. Some of the collaborative technology projects have led to key contributions being used by other technology projects as well as commercial products. One example is the Service UI API (http://www.artima.com/jini/serviceui/), which is a way to attach user interfaces to Jini services. Despite the obvious successes of the technology and Community, some changes are in store as outlined in a recent note to the Community: A New Day (http://archives.java.sun.com/cgi-bin/wa?A2=ind0604L=jini-usersF=S=P=4029). The most critical part of the new plan is to find the right place for the future development and advancement of the core Jini technology. We wanted an environment that was synergistic with our exisiting Community culture -- so one that is active, with open communication and collaboration, and a reputation for producing high quality software. We think we've found that place with the Apache Software Foundation. (0.1) criteria /Meritocracy:/ The River project will be meritocractic. The project will follow the guidelines (http://apache.org/foundation/how-it-works.html#meritocracy) of the Apache Software Foundation. In order to achieve this, we plan on proactively recruiting individuals in the Community to get involved in the project: specifying work that needs to be done, encouraging bug fixes, enhancements, and advancements, and engaging in discussion on how the code works and is structured. In the end, we are committed to creating an environment to foster a meritocracy. /Community:/ There has been a diverse and active Community built around Jini technology since it was first introduced in January, 1999. The Jini Community consists of a global set of individuals, companies, non-profit organizations, and universities. The Community communicates primarily through various email
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Hi, On Thursday 21 December 2006 11:46, Geir Magnusson Jr. wrote: [x] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) +0 on the River proposal. On 12/21/06, Jim Jagielski [EMAIL PROTECTED] wrote: I've always hoped that someone would wish to call an ASF project Fog I liked Braintree way better than River ;) Too bad, but I'll live. As to Fog: Apache Nebbia (fog in Italian) is a pretty cool name! There's a saying in Italian that Stefano, Gianugo, Ugo, David W, or others hanging out on this list might appreciate (and that I'm probably mispelling): Al inizio, Dio creo la Padana (in the beginning, God created la Padana, the region in northern Italy) Poi ci ripenso, e creo la nebbia (and then He thought better of it, and created the fog) Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Dec 21, 2006, at 9:15 AM, Geir Magnusson Jr. wrote: On Dec 21, 2006, at 9:01 AM, Jim Jagielski wrote: On Dec 20, 2006, at 10:46 PM, Geir Magnusson Jr. wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. Therefore, please vote on the proposal that follows : [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) Could you address the overlap with other ASF projects and podlings which are in similar technology space? There are none doing Jini at this time. Why a new and distinct podling and not joining/helping them? See above :) I think that the proposal should at least address that... People see hey another SOA project, architecture for services and need to know how River is different and unique by anticipating the question :) Also, one thing that had been discussed is better clarification in proposals regarding the Initial List of Committers and the Initial List of PPMC Members... To avoid the issues that popped up with CXF. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Dec 21, 2006, at 11:09 AM, Jim Jagielski wrote: On Dec 21, 2006, at 9:15 AM, Geir Magnusson Jr. wrote: On Dec 21, 2006, at 9:01 AM, Jim Jagielski wrote: On Dec 20, 2006, at 10:46 PM, Geir Magnusson Jr. wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. Therefore, please vote on the proposal that follows : [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) Could you address the overlap with other ASF projects and podlings which are in similar technology space? There are none doing Jini at this time. Why a new and distinct podling and not joining/helping them? See above :) I think that the proposal should at least address that... People see hey another SOA project, architecture for services it's a little different. Jini is an old and I would say fundamental technology for service infrastructure in the java platform, very different from today's SOA. I'll let someone else argue my point, as I have to go christmas shopping. If no one does, I'll do it when I get back. They are fundamentally different (and we always allow competing impls anyway...) and need to know how River is different and unique by anticipating the question :) Yeah. Well, I have a basic understanding of what Jini is, and I never confuse the two. I certainly can understand how someone unfamiliar with it would be confused. Also, one thing that had been discussed is better clarification in proposals regarding the Initial List of Committers and the Initial List of PPMC Members... To avoid the issues that popped up with CXF. We'll argue it out once/if the podling starts, but I was going to suggest that we run it in the fashion of Harmony - that we wait until those that are listed engage and participate, and then give them commit, and have the mentors build the PPMC in parallel based on engagement and participation. geir - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
+1 (non-binding) I think it's great that Apache will adopt this great technology... Craig On Dec 20, 2006, at 7:46 PM, Geir Magnusson Jr. wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. Therefore, please vote on the proposal that follows : [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) The proposal can be found here : http://wiki.apache.org/incubator/RiverProposal and is included below for archival purposes : RiverProposal *Proposal for new project River* 8 December 2006 (0) rationale Jini technology is a service oriented architecture that defines a programming model which both exploits and extends Java technology to enable the construction of secure, distributed systems consisting of federations of services and clients. Jini technology can be used to build adaptive network systems that are scalable, evolvable and flexible as typically required in dynamic computing environments. Quoting from The Jini Specifications (http://java.sun.com/docs/ books/jini/spec/) book: Jini technology is a simple infrastructure for providing services in a network, and for creating spontaneous interactions between programs that use these services. Services can join or leave the network in a robust fashion, and clients can rely upon the availability of visible services, or at least upon clear failure conditions. When you interact with a service, you do so through a Java object provided by that service. This object is downloaded into your program so that you can talk to the service even if you have never seen its kind before - the downloaded object knows how to do the talking. That's the whole system in a nutshell. Sun Microsystems originally introduced the technology in January, 1999 by providing a Jini Technology Starter Kit (http:// starterkit.dev.java.net/). This includes a contributed implementation of all of the specifications, as well as helpful utilities and tools. The source code was made available through the Sun Community Source License (SCSL) as an attempt to make the code widely available and accessible to both individuals and companies. Sun has continued to innovate throughout the years, releasing many versions of the starter kit. The license associated with the starter kit was changed (http://archives.java.sun.com/cgi-bin/wa? A2=ind0503L=jini-usersO=AP=36217) in March, 2005 to the Apache License, Version 2.0. Since its beginning, there was desire and effort to form a developer community around the technology. This has helped to create an interesting, active, and passionate community - the Jini Community. This global Community has engaged on technology projects, discussions and debates, events, and a decision making process. It has contributed to, and helped influence the direction of the starter kit. Some of the collaborative technology projects have led to key contributions being used by other technology projects as well as commercial products. One example is the Service UI API (http://www.artima.com/jini/serviceui/), which is a way to attach user interfaces to Jini services. Despite the obvious successes of the technology and Community, some changes are in store as outlined in a recent note to the Community: A New Day (http://archives.java.sun.com/cgi-bin/wa? A2=ind0604L=jini-usersF=S=P=4029). The most critical part of the new plan is to find the right place for the future development and advancement of the core Jini technology. We wanted an environment that was synergistic with our exisiting Community culture -- so one that is active, with open communication and collaboration, and a reputation for producing high quality software. We think we've found that place with the Apache Software Foundation. (0.1) criteria /Meritocracy:/ The River project will be meritocractic. The project will follow the guidelines (http://apache.org/foundation/how-it- works.html#meritocracy) of the Apache Software Foundation. In order to achieve this, we plan on proactively recruiting individuals in the Community to get involved in the project: specifying work that needs to be done, encouraging bug fixes, enhancements, and advancements, and engaging in discussion on how the code works and is structured. In the end, we are committed to creating an environment to foster a meritocracy. /Community:/ There has been a diverse and active Community built around Jini technology since it was first introduced in January, 1999. The Jini
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Dec 21, 2006, at 1:19 PM, Geir Magnusson Jr. wrote: it's a little different. Jini is an old and I would say fundamental technology for service infrastructure in the java platform, very different from today's SOA. I'll let someone else argue my point, as I have to go christmas shopping. If no one does, I'll do it when I get back. They are fundamentally different (and we always allow competing impls anyway...) I know and agree, but when the proposal starts off with: Jini technology is a service oriented architecture that defines a programming model which both exploits and extends Java technology to enable the construction of secure, distributed systems then it's valid item, I think :) Also, one thing that had been discussed is better clarification in proposals regarding the Initial List of Committers and the Initial List of PPMC Members... To avoid the issues that popped up with CXF. We'll argue it out once/if the podling starts, but I was going to suggest that we run it in the fashion of Harmony - that we wait until those that are listed engage and participate, and then give them commit, and have the mentors build the PPMC in parallel based on engagement and participation. IIRC, the thinking within the Incubator after all the discussions was that it needed to be more clear before the podling started, to ensure everyone was on the same page. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
+1 , glad we have come to this point. -- Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On 12/21/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. 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) - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Geir Magnusson Jr. wrote: Therefore, please vote on the proposal that follows : +1 Accept River as a new podling as described below Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
+1 Accept River as a new podling - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On 12/21/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote: [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) +1 -- Gianugo Rabellino Sourcesense, making sense of Open Source: http://www.sourcesense.com Orixo, the XML business alliance: http://www.orixo.com (blogging at http://www.rabellino.it/blog/) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Geir Magnusson Jr. wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. 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 Dan. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 - Bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Geir Magnusson Jr. wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate [the project formerly known as Jini] No kidding! And it's about time! :-) You may be familiar with this project as it has been discussed under other names, including [Jini]. Yes, and I have been quite looking forward to its arrival at the ASF, thank you very much. :-) please vote on the proposal +1 --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
[X] +1 Accept River as a new podling as described below - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On 12/20/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. 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) Thanks! -- justin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. Therefore, please vote on the proposal that follows : [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) The proposal can be found here : http://wiki.apache.org/incubator/RiverProposal and is included below for archival purposes : RiverProposal *Proposal for new project River* 8 December 2006 (0) rationale Jini technology is a service oriented architecture that defines a programming model which both exploits and extends Java technology to enable the construction of secure, distributed systems consisting of federations of services and clients. Jini technology can be used to build adaptive network systems that are scalable, evolvable and flexible as typically required in dynamic computing environments. Quoting from The Jini Specifications (http://java.sun.com/docs/books/jini/spec/) book: Jini technology is a simple infrastructure for providing services in a network, and for creating spontaneous interactions between programs that use these services. Services can join or leave the network in a robust fashion, and clients can rely upon the availability of visible services, or at least upon clear failure conditions. When you interact with a service, you do so through a Java object provided by that service. This object is downloaded into your program so that you can talk to the service even if you have never seen its kind before - the downloaded object knows how to do the talking. That's the whole system in a nutshell. Sun Microsystems originally introduced the technology in January, 1999 by providing a Jini Technology Starter Kit (http://starterkit.dev.java.net/). This includes a contributed implementation of all of the specifications, as well as helpful utilities and tools. The source code was made available through the Sun Community Source License (SCSL) as an attempt to make the code widely available and accessible to both individuals and companies. Sun has continued to innovate throughout the years, releasing many versions of the starter kit. The license associated with the starter kit was changed (http://archives.java.sun.com/cgi-bin/wa?A2=ind0503L=jini-usersO=AP=36217) in March, 2005 to the Apache License, Version 2.0. Since its beginning, there was desire and effort to form a developer community around the technology. This has helped to create an interesting, active, and passionate community - the Jini Community. This global Community has engaged on technology projects, discussions and debates, events, and a decision making process. It has contributed to, and helped influence the direction of the starter kit. Some of the collaborative technology projects have led to key contributions being used by other technology projects as well as commercial products. One example is the Service UI API (http://www.artima.com/jini/serviceui/), which is a way to attach user interfaces to Jini services. Despite the obvious successes of the technology and Community, some changes are in store as outlined in a recent note to the Community: A New Day (http://archives.java.sun.com/cgi-bin/wa?A2=ind0604L=jini-usersF=S=P=4029). The most critical part of the new plan is to find the right place for the future development and advancement of the core Jini technology. We wanted an environment that was synergistic with our exisiting Community culture -- so one that is active, with open communication and collaboration, and a reputation for producing high quality software. We think we've found that place with the Apache Software Foundation. (0.1) criteria /Meritocracy:/ The River project will be meritocractic. The project will follow the guidelines (http://apache.org/foundation/how-it-works.html#meritocracy) of the Apache Software Foundation. In order to achieve this, we plan on proactively recruiting individuals in the Community to get involved in the project: specifying work that needs to be done, encouraging bug fixes, enhancements, and advancements, and engaging in discussion on how the code works and is structured. In the end, we are committed to creating an environment to foster a meritocracy. /Community:/ There has been a diverse and active Community built around Jini technology since it was first introduced in January, 1999. The Jini Community consists of a global set of individuals, companies, non-profit organizations, and universities. The Community communicates primarily through various email lists: jini-users
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
+1 from me Geir Magnusson Jr. wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. Therefore, please vote on the proposal that follows : [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) The proposal can be found here : http://wiki.apache.org/incubator/RiverProposal and is included below for archival purposes : RiverProposal *Proposal for new project River* 8 December 2006 (0) rationale Jini technology is a service oriented architecture that defines a programming model which both exploits and extends Java technology to enable the construction of secure, distributed systems consisting of federations of services and clients. Jini technology can be used to build adaptive network systems that are scalable, evolvable and flexible as typically required in dynamic computing environments. Quoting from The Jini Specifications (http://java.sun.com/docs/books/jini/spec/) book: Jini technology is a simple infrastructure for providing services in a network, and for creating spontaneous interactions between programs that use these services. Services can join or leave the network in a robust fashion, and clients can rely upon the availability of visible services, or at least upon clear failure conditions. When you interact with a service, you do so through a Java object provided by that service. This object is downloaded into your program so that you can talk to the service even if you have never seen its kind before - the downloaded object knows how to do the talking. That's the whole system in a nutshell. Sun Microsystems originally introduced the technology in January, 1999 by providing a Jini Technology Starter Kit (http://starterkit.dev.java.net/). This includes a contributed implementation of all of the specifications, as well as helpful utilities and tools. The source code was made available through the Sun Community Source License (SCSL) as an attempt to make the code widely available and accessible to both individuals and companies. Sun has continued to innovate throughout the years, releasing many versions of the starter kit. The license associated with the starter kit was changed (http://archives.java.sun.com/cgi-bin/wa?A2=ind0503L=jini-usersO=AP=36217) in March, 2005 to the Apache License, Version 2.0. Since its beginning, there was desire and effort to form a developer community around the technology. This has helped to create an interesting, active, and passionate community - the Jini Community. This global Community has engaged on technology projects, discussions and debates, events, and a decision making process. It has contributed to, and helped influence the direction of the starter kit. Some of the collaborative technology projects have led to key contributions being used by other technology projects as well as commercial products. One example is the Service UI API (http://www.artima.com/jini/serviceui/), which is a way to attach user interfaces to Jini services. Despite the obvious successes of the technology and Community, some changes are in store as outlined in a recent note to the Community: A New Day (http://archives.java.sun.com/cgi-bin/wa?A2=ind0604L=jini-usersF=S=P=4029). The most critical part of the new plan is to find the right place for the future development and advancement of the core Jini technology. We wanted an environment that was synergistic with our exisiting Community culture -- so one that is active, with open communication and collaboration, and a reputation for producing high quality software. We think we've found that place with the Apache Software Foundation. (0.1) criteria /Meritocracy:/ The River project will be meritocractic. The project will follow the guidelines (http://apache.org/foundation/how-it-works.html#meritocracy) of the Apache Software Foundation. In order to achieve this, we plan on proactively recruiting individuals in the Community to get involved in the project: specifying work that needs to be done, encouraging bug fixes, enhancements, and advancements, and engaging in discussion on how the code works and is structured. In the end, we are committed to creating an environment to foster a meritocracy. /Community:/ There has been a diverse and active Community built around Jini technology since it was first introduced in January, 1999. The Jini Community consists of a global set of individuals, companies, non-profit organizations, and universities. The Community communicates primarily through various email lists:
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
Note - this vote will be for 3 days, ending midnight, saturday december 23rd, 2006. Geir Magnusson Jr. wrote: It is with great relief and hope that I propose that the Apache Incubator PMC vote to incubate a new podling, to be known as River. You may be familiar with this project as it has been discussed under other names, including Braintree and Jini. I've actually lost track of the Quest for a Name, and actually feel very responsible for this naming mess, for which I apologize. Therefore, please vote on the proposal that follows : [ ] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) The proposal can be found here : http://wiki.apache.org/incubator/RiverProposal and is included below for archival purposes : RiverProposal *Proposal for new project River* 8 December 2006 (0) rationale Jini technology is a service oriented architecture that defines a programming model which both exploits and extends Java technology to enable the construction of secure, distributed systems consisting of federations of services and clients. Jini technology can be used to build adaptive network systems that are scalable, evolvable and flexible as typically required in dynamic computing environments. Quoting from The Jini Specifications (http://java.sun.com/docs/books/jini/spec/) book: Jini technology is a simple infrastructure for providing services in a network, and for creating spontaneous interactions between programs that use these services. Services can join or leave the network in a robust fashion, and clients can rely upon the availability of visible services, or at least upon clear failure conditions. When you interact with a service, you do so through a Java object provided by that service. This object is downloaded into your program so that you can talk to the service even if you have never seen its kind before - the downloaded object knows how to do the talking. That's the whole system in a nutshell. Sun Microsystems originally introduced the technology in January, 1999 by providing a Jini Technology Starter Kit (http://starterkit.dev.java.net/). This includes a contributed implementation of all of the specifications, as well as helpful utilities and tools. The source code was made available through the Sun Community Source License (SCSL) as an attempt to make the code widely available and accessible to both individuals and companies. Sun has continued to innovate throughout the years, releasing many versions of the starter kit. The license associated with the starter kit was changed (http://archives.java.sun.com/cgi-bin/wa?A2=ind0503L=jini-usersO=AP=36217) in March, 2005 to the Apache License, Version 2.0. Since its beginning, there was desire and effort to form a developer community around the technology. This has helped to create an interesting, active, and passionate community - the Jini Community. This global Community has engaged on technology projects, discussions and debates, events, and a decision making process. It has contributed to, and helped influence the direction of the starter kit. Some of the collaborative technology projects have led to key contributions being used by other technology projects as well as commercial products. One example is the Service UI API (http://www.artima.com/jini/serviceui/), which is a way to attach user interfaces to Jini services. Despite the obvious successes of the technology and Community, some changes are in store as outlined in a recent note to the Community: A New Day (http://archives.java.sun.com/cgi-bin/wa?A2=ind0604L=jini-usersF=S=P=4029). The most critical part of the new plan is to find the right place for the future development and advancement of the core Jini technology. We wanted an environment that was synergistic with our exisiting Community culture -- so one that is active, with open communication and collaboration, and a reputation for producing high quality software. We think we've found that place with the Apache Software Foundation. (0.1) criteria /Meritocracy:/ The River project will be meritocractic. The project will follow the guidelines (http://apache.org/foundation/how-it-works.html#meritocracy) of the Apache Software Foundation. In order to achieve this, we plan on proactively recruiting individuals in the Community to get involved in the project: specifying work that needs to be done, encouraging bug fixes, enhancements, and advancements, and engaging in discussion on how the code works and is structured. In the end, we are committed to creating an environment to foster a meritocracy. /Community:/ There has been a diverse and active Community built around Jini technology since it was first introduced in January, 1999. The Jini Community consists of a global set of individuals, companies, non-profit organizations, and
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Thursday 21 December 2006 11:46, Geir Magnusson Jr. wrote: [x] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) non-binding. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
+1 Phil On 12/20/06, Niclas Hedhman [EMAIL PROTECTED] wrote: On Thursday 21 December 2006 11:46, Geir Magnusson Jr. wrote: [x] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) non-binding. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate new podling, River (nee Braintree, nee..., nee Jini)
On Thursday 21 December 2006 11:46, Geir Magnusson Jr. wrote: [x] +1 Accept River as a new podling as described below [ ] -1 Do not accept the new podling (provide reason, please) Good name too. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
