[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: http://incubator.apache.org/river/RIVER/downloads.html Apache River (Incubating) is focused on furthering the development and advancement of Jini technology. Jini is an open source service oriented architecture that defines a programming model built on Java which can be used to build secure, adaptive, network (distributed) systems that are scalable, evolvable, and flexible as typically required in dynamic computing environments. This is the first release from Apache River Incubating, and is based on the contributions of Sun's Jini Technology Starter Kit (Starter Kit) v2.1 and the Service UI (attaching user interfaces to Jini services) contribution from Artima. The release focuses on merging the two contributions together, structuring src and bin releases, amending the source and documentation naming and versioning to Apache River Incubating, and making some small modifications. We're in the midst of working on more substantive changes in a second release. If you have feedback or questions, please join the river-dev mailing list and let us know your thoughts. We are actively seeking developers to get involved, so check out the release and join in! The Apache Incubator River Community http://incubator.apache.org/river/index.html - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Vote Result] Apache River 2.1.1 Incubating Release
Thanks to all who examined the release candidate and provided comments and asked questions. The Incubator vote passed with 5 yes votes (* - 4 binding): Craig Russell* Matthieu Riou* Vincent Siveton Niclas Hedhman* Kevan Millar* The [EMAIL PROTECTED] vote thread starts here: http://mail-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 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 Wednesday, January 16th. Thanks! -Jim [EMAIL PROTECTED] Release Proposal: http://people.apache.org/~fbarnaby/river/2.1.1/ RAT output: http://people.apache.org/~fbarnaby/river/2.1.1/rat_output.txt Vote result: http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200801.mbox/[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Wednesday, January 16th. Thanks! -Jim [EMAIL PROTECTED] Release Proposal: http://people.apache.org/~fbarnaby/river/2.1.1/ RAT output: http://people.apache.org/~fbarnaby/river/2.1.1/rat_output.txt Vote result: http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200801.mbox/[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
'Handling Crypto..' - River project
We're (River incubator project) trying to comply with: Handling Cryptography within an ASF Release http://www.apache.org/dev/crypto.html This process talks only about software that has been self classified as 5D002 (has strong crypto classification). Parts of the Sun Jini Technology Starter Kit (the base contribution for the River project) were classified as 5D992.b.1, which is a different classification. From the ASF perspective, should we treat this (5D992) classification as effectively no crypto? Need some guidance and insight to help us understand what we need to do to comply. thanks -Jim [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 'Handling Crypto..' - River project
Thanks Bill -- I'll copy over to legal-discuss. Just to be clear, the Sun release was not a product, but rather an open source (Apache 2 license) release. I could be wrong, but I don't think it was handled as a commercial product. -Jim On Oct 24, 2007, at 1:21 PM, William A. Rowe, Jr. wrote: Keep in mind, Sun stuff wasn't necessarily handled under generally available open source TSU (exception) classifications, but as commercial product. This is, in part, why distributors may have issues using our exceptions and our classifications (their 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/crypto.html This process talks only about software that has been self classified as 5D002 (has strong crypto classification). Parts of the Sun Jini Technology Starter Kit (the base contribution for the River project) were classified as 5D992.b.1, which is a different classification. From the ASF perspective, should we treat this (5D992) classification as effectively no crypto? Need some guidance and insight to help us understand what we need to do to comply. thanks -Jim [EMAIL PROTECTED] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 http://wiki.apache.org/incubator/PigProposal. We would like to ask that the ASF consider forming a podling according to the proposal. Thanks, Olga Natkovich mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -- -- - = Pig Open Source Proposal = == Abstract == Pig is a platform for analyzing large data sets. == Proposal == The Pig project consists of high-level languages for expressing data analysis programs, coupled with infrastructure for evaluating these : : : - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
(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 accomplish that. thanks -Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 filed a Software Grant to contribute the code to the Foundation. does the grant cover trademarks? - robert IANAL, so I can't definitively say if things are covered. My assumption is that the Software Grant (for the Foundation accepting code contributions) would be sufficient legally to allow Apache projects to use and advance the code contributed. If it's not, someone will need to explicitly articulate the issue. Thanks to all that responded to this thread. Otherwise, I think we (River project) have the guidance we need to define our roadmap forward. -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)
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: JiniProposal - BraintreeProposal
Based on all the emails in this thread (and also some negative reactions from the Jini Community)... it doesn't look like this name is going to stick. I'll start another (sigh) effort to come up with a workable name. In the meantime, Geir - does it make sense to have a vote, or wait 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 address the name issue again during incubation. thanks -Jim On Oct 25, 2006, at 3:44 PM, Noel J. Bergman wrote: In any event, let's get this thing going. *IF* the name has to change again, it can change again. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 than the one selected? What is the criteria? This topic comes up quite often. --- Noel Does this same criteria apply to any name? I'm questioning whether I understand the rules, so some clarification would really help. thanks -Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 Oct 25, 2006, at 3:44 PM, Noel J. Bergman wrote: In any event, let's get this thing going. *IF* the name has to change again, it can change again. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 associated with that name that were uncovered (after the survey). From people far more knowledgeable on trademark policy, different spelling virtually never makes enough difference in trademark circumstances. There is already trademark around aladdin, and therefore, we don't feel like we should choose this name. Going to the next preference (djinn) also uncovered some potential trademark issues. I also looked at variations, including djinni which had similar issues. Given this, it doesn't seem like a good choice for us as well. The third preference (braintree) seems fairly clean, so we are going to go with this name for our project proposal. I will update the wiki today. If we are successful in getting approved as an incubator project, and this name is not resonating, we can always change it during incubation. Thanks, everyone, for your patience and support during this somewhat trying naming period... once we get the Proposal on the wiki updated, I hope we can move forward to an incubator vote. If you have any questions, please let me know. thanks -Jim -- Results of the 134 votes cast, along with percentage numbers for the first 4 preferences. 1) aladin( 28.80%) 2) djinn (18.40%) 3) braintree(16.00%) 4) river(9.60%) 5) bodega 6) codeinmotion 7) kuiper 8) constellation, freejack, jackalope 9) biere, peace, red99, cloudscape 10) jazmin, jinius, jane, genio, particles, jiniache, djs, hydra, ubi, swami, iguana -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [JiniProposal] Choosing a new name...
Thanks Geir. It's certainly a viable alternative plan, but we're trying to match up with the history and culture we've created in the Jini Community of open involvement, so it seems like goodness to engage more broadly and give people a say. We've had a number of good names submitted -- but I'm guessing the winner is still out there... so please consider submitting a name. Thanks. Many of the names submitted so far have played off the Jini name or space (e.g., the Eden example below). An alternate direction is to just propose something different and fun (which might just be a cool name and not tied at all to the technology). We'll welcome all ideas through today and then start the vetting process. Thanks again -Jim On Sep 24, 2006, at 7:48 PM, Geir Magnusson Jr wrote: While we all appreciate you inviting the community 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 communication on our Proposal. Following my summary post: http://mail-archives.apache.org/mod_mbox/incubator-general/ 200608.mbox/[EMAIL PROTECTED] and list discussion, I believe choosing a new name for the project and then updating our Proposal are the last bits before we can ask for an incubator vote. We've been fairly consumed by our Jini Community Meeting event last week in Brussels (see the Jini.org front page for links to info from the event), so again, I'm sorry for not getting this closed sooner so we can move on and (hopefully) get going. As we're all too familiar with :-o -- picking a name (that everyone likes) is hard. In order to get as many creative ideas as possible, and have a defined process (so that it doesn't drag out) for making a decision... we'd like to: * Gather Name Ideas -- through Tuesday, Sept 26 Ask both the Apache incubator and Jini Community for name ideas. In order to not consume the lists with name mail, if you could send me, [EMAIL PROTECTED] your name ideas, and optionally your reasoning/meaning behind the name. I'd really appreciate it. For example: name: Eden -- reminds me of Barbara Eden from I Dream of Genie! ;-) * Choose the New Name (voting) -- Thursday, Sept 28 through Monday, Oct 2 We'll take the list of ideas, make sure they pass TM, etc and select a top ten choices that we'll put up for an open vote. Whatever name is supported the most by the vote is the one we'll choose for the project. If these dates feel too tight we can be a little pliable, but we are hoping to update our Proposal and have the voting (start) before the upcoming ApacheCon if possible. There's obviously an endless amount of ways to go about picking a name... this might not be the best, but we wanted to engage the Apache incubator and our existing Community in contributing. We're betting that with everyone's creative juices flowing - we're going to collectively come up with a cool name that represents the project well and that most people like. I hope you'll give us your support. thanks -Jim
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.java.net project - which utilitzes Jini). Van has a nice way of explaining things, and so if you like podcasts, this may be of interest to you: Interview with Van Simmons about Jini and ComputeCycles * Part 1 (Sep 17): http://javaposse.com/index.php?post_id=131159 * Part 2 (Sep 24): http://javaposse.com/index.php?post_id=133510 * Part 3 (coming...) He also touches on our Jini Apache incubator Proposal, but is not intimate with the details of where we are in the process... so primarily just comments on how it's a good thing :-) -Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[JiniProposal] Choosing a new name...
Hi all- I apologize for the gap in communication on our Proposal. Following my summary post: http://mail-archives.apache.org/mod_mbox/incubator-general/ 200608.mbox/[EMAIL PROTECTED] and list discussion, I believe choosing a new name for the project and then updating our Proposal are the last bits before we can ask for an incubator vote. We've been fairly consumed by our Jini Community Meeting event last week in Brussels (see the Jini.org front page for links to info from the event), so again, I'm sorry for not getting this closed sooner so we can move on and (hopefully) get going. As we're all too familiar with :-o -- picking a name (that everyone likes) is hard. In order to get as many creative ideas as possible, and have a defined process (so that it doesn't drag out) for making a decision... we'd like to: * Gather Name Ideas -- through Tuesday, Sept 26 Ask both the Apache incubator and Jini Community for name ideas. In order to not consume the lists with name mail, if you could send me, [EMAIL PROTECTED] your name ideas, and optionally your reasoning/meaning behind the name. I'd really appreciate it. For example: name: Eden -- reminds me of Barbara Eden from I Dream of Genie! ;-) * Choose the New Name (voting) -- Thursday, Sept 28 through Monday, Oct 2 We'll take the list of ideas, make sure they pass TM, etc and select a top ten choices that we'll put up for an open vote. Whatever name is supported the most by the vote is the one we'll choose for the project. If these dates feel too tight we can be a little pliable, but we are hoping to update our Proposal and have the voting (start) before the upcoming ApacheCon if possible. There's obviously an endless amount of ways to go about picking a name... this might not be the best, but we wanted to engage the Apache incubator and our existing Community in contributing. We're betting that with everyone's creative juices flowing - we're going to collectively come up with a cool name that represents the project well and that most people like. I hope you'll give us your support. thanks -Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIni Proposal
While we continue to look forward to your review and response ;-) thought I'd mention a Jini event coming up next month: * Tenth Jini Community Meeting Brussels, Belgium September 13-14, 2006 * * Session Abstracts: http://www.jini.org/wiki/10th_JCM_Sessions * Schedule: http://www.jini.org/wiki/10th_JCM_Agenda_Day_1 http://www.jini.org/wiki/10th_JCM_Agenda_Day_2 It would be great to have Apache members there. The meeting is open and free, and all interested developers are welcome. We are hoping to provide an update on our Jini Proposal at the meeting (the Update on the 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. 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 try and propose a path forward and we'll see where we go from there. Thanks again, and we look forward to your review and response. -Jim -- 1) specifications / API docs It appears that there are many (valid) lenses in which to view the specifications question. I'd rather not reintroduce all of the different perspectives and proposals, but rather focus on one that we believe is acceptable to the Jini Community, and hopefully will be to Apache. We would like to include the API docs (specifications seems to be a loaded term, with many different definitions and assumptions tied up in it) in the project. Many of the API docs are generated directly from the code (Javadoc), but would be made available as a separate download within the project. These would not be called standards. They would be called Jini API documents. They are intended to clearly define the APIs and semantics that are implemented as part of the project. Outside parties certainly have the right, and are welcome to use those docs to create alternative implementations - but that is not the predominant reason for producing the docs. The process used for introducing a change to the API docs would be developed by the project PMC and committers. We'd expect it to follow a similar process to proposed code mods, with the added responsibilities of making them visible to the overall Jini Community through the project email lists, and having open discussion and debate. We'd expect that the Community feedback would heavily influence the work performed on the API docs. The (perfectly reasonable) suggestion on creating a separate project for the governance of the specifications is not viable as we do not have the volunteers to run another project, nor was the intention of defining a specifications process within Apache something that the initial committers of our Proposal wanted or can satisfy. ------------ ------ 2) Java package names (namespace) There are two namespaces that are part of the Proposal that have been discussed: * net.jini.* -- this is the primary Jini namespace defined in the API docs, and chiefly for compatibility reasons with existing implementations and applications, we can not change this. * com.sun.jini.* -- there are also some compatibility issues associated with changing this namespace in the implementation, but we understand the reasons for wanting to change this to org.apache.projectname, and would do this as part of the incubation phase of the project. ------------ ------ 3) project name There is some pretty strong sentiment within the Jini Community for keeping the Jini name as part of the Apache Proposal. Our overall reading, however, is that given the scope of the project proposed and other technology sites (jini.dev.java.net, Jini.org) on the web, that the name would not be acceptable to Apache. We, therefore, are open to discussing a name change to something else within the Jini Community. If there's agreement on the positions stated in 1 and 2 above, we'll assume there's general support for our Proposal to Apache and begin the name discussion in the Jini Community. -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
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 try and propose a path forward and we'll see where we go from there. Thanks again, and we look forward to your review and response. -Jim -- 1) specifications / API docs It appears that there are many (valid) lenses in which to view the specifications question. I'd rather not reintroduce all of the different perspectives and proposals, but rather focus on one that we believe is acceptable to the Jini Community, and hopefully will be to Apache. We would like to include the API docs (specifications seems to be a loaded term, with many different definitions and assumptions tied up in it) in the project. Many of the API docs are generated directly from the code (Javadoc), but would be made available as a separate download within the project. These would not be called standards. They would be called Jini API documents. They are intended to clearly define the APIs and semantics that are implemented as part of the project. Outside parties certainly have the right, and are welcome to use those docs to create alternative implementations - but that is not the predominant reason for producing the docs. The process used for introducing a change to the API docs would be developed by the project PMC and committers. We'd expect it to follow a similar process to proposed code mods, with the added responsibilities of making them visible to the overall Jini Community through the project email lists, and having open discussion and debate. We'd expect that the Community feedback would heavily influence the work performed on the API docs. The (perfectly reasonable) suggestion on creating a separate project for the governance of the specifications is not viable as we do not have the volunteers to run another project, nor was the intention of defining a specifications process within Apache something that the initial committers of our Proposal wanted or can satisfy. -------------- ---- 2) Java package names (namespace) There are two namespaces that are part of the Proposal that have been discussed: * net.jini.* -- this is the primary Jini namespace defined in the API docs, and chiefly for compatibility reasons with existing implementations and applications, we can not change this. * com.sun.jini.* -- there are also some compatibility issues associated with changing this namespace in the implementation, but we understand the reasons for wanting to change this to org.apache.projectname, and would do this as part of the incubation phase of the project. -------------- ---- 3) project name There is some pretty strong sentiment within the Jini Community for keeping the Jini name as part of the Apache Proposal. Our overall reading, however, is that given the scope of the project proposed and other technology sites (jini.dev.java.net, Jini.org) on the web, that the name would not be acceptable to Apache. We, therefore, are open to discussing a name change to something else within the Jini Community. If there's agreement on the positions stated in 1 and 2 above, we'll assume there's general support for our Proposal to Apache and begin the name discussion in the Jini Community. -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 are. Hope that will help. thanks -Jim On Aug 18, 2006, at 7:21 AM, Jukka Zitting wrote: Hi, On 8/15/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote: I think that we should consider the Jini standard separately - we have a community and a codebase, and should proceed with that now. Because it still is a standard we can work on that in parallel if all parties are willing. +1 I believe therefore that we have now returned to the original question... what should the name of the new podling be called? :) I think Apache Jinn and Apache Genie have already been proposed. Other alternatives could be Apache Jafar or Apache Jasmine based on characters from the Disney film featuring the famous genie. (Though I'm quite sure that Jafar and Jasmine are trademarked by Disney. Is that a problem for us?) Apache Aladdin would also be nice, but Aladdin is already heavily used. Would the Jini community be happy with bringing the project in under a different name? At some point it was mentioned that keeping the Jini name would be the preferred choice. I'd like to advocate using a different name also from the point of view that there is currently no exact definition of Jini, and starting Apache Jini would just add to that confusion. Are there any other open issues regarding the proposal? BR, Jukka Zitting -- Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED] Software craftsmanship, JCR consulting, and Java development - 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: 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 starter? And if we have them both under a single podling to start, and we see how it goes, does that work for you? Separate mailing lists for source code development and API/spec discussions seems reasonable. Some developers in the Community might be interested in the details on how the impl work is going, and others might be only interested in API -related proposed changes. I think that would work fine for us. thanks -Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 the project being proposed as *the* Jini implementation or as *a* Jini implementation? Hi Jukka- I'm not going to try and pull a Bill Clinton with it depends what the definition of is is but I'd answer that I believe the Jini Community views the project as *the* Jini implementation. But *the* as in: the main, the original, the most prominent, (what will be) the Community's implementation, and the one you'd recommend a developer go grab to get going with Jini. But not *the* as in the only. I view it as being/becoming *the* Jini Community's touchstone (or main commons). Don't know if that helps. -Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 Jini by other community sites, etc would be acceptable? We're anxious to get going, but the path we must take is unclear to us. Thanks for any help. -Jim On Aug 8, 2006, at 6:29 AM, Mark Brouwer wrote: Sanjiva Weerawarana wrote: I know changing the name is a *really* tough thing for Jini. However, is Jini a *technology* or an *implementation*? If its the prior I'm afraid our current guidelines are not to do technology names. I understand for those not very involved with the Jini Technology it is hard to pinpoint what Jini exactly is and why some of us are willing to go through great lengths to take this name with us, so let me try. First Jini is a Technology, but with an extra handicap as the borders where Jini begins and ends are not very well defined, even while in 1999/2000 there was already a document that described the Jini Architecture and the Jini Technology Core Platform. It just lacks a clear definition, when you ask 10 people to describe Jini chances are high that you will get 10 different answers; some that will make you happy or smile, and some that make you foam with rage ... Many consider the implementation of Sun JTSK (Jini Technology Starter Kit) as being 'Jini' but this is not correct (if you would ask me) and while the proposal mainly centers around their code the proposal also includes another Jini Community Approved Standard, namely ServiceUI (the other trademark involved). What is part of this proposal are most of the Jini Community Approved Standards and the IMHO 'sad' thing is that the Jini Decision Process that ratified these specifications as community approved standards ceased to exist. Sun is no longer willing to provide the Executive to run the process and there are not enough people in the community that want to take it over (read don't want to spend time on it). The current owner of the Standards also doesn't believe they can get accepted as JSR in the JCP based on experience with some of the specifications that ended up as Jini Standard while they should have become J2SE specifications in the first place. The net result is that some really important Jini Community aspects [1] (the Standards) we all circle around are part of this proposal, and if we can stay clear of forks it should be seen as the foundation on top of which the rest of the Jini community will build their own stuff. [1] as Jim mentioned the new http://jini.org/ is another aspect of the community and is there for everything one could see as Jini related (really open ended), http://jini.dev.java.net/ should be seen as the yellow pages with regard to Jini related development projects and news around that. Renaming the Technology itself would be suicidal in my opinion as there are dozens of people/companies that develop products/specifications on top of 'Jini' so it would be harming them too. Of course it would be possible to give the TLP a different name, but then again almost every sentence would have a reference to the Jini Technology for which I guess nobody could say where the 'Jini Technology' itself lives. Given the fact the ASF project would be closest to defining the 'Jini Technology' I think it is good to emphasize this by the name of the TLP. IANAL and have no idea what the impact would be of handing over the Jini trademark to the ASF, how the ASF will deal with other communities that have Jini in their name, or other specifications that have Jini in their name. I'm reluctant to say this given the fact that Sun has to protect its trademarks, but I have the feeling that Jini has become rather generic in the past years. People say I wrote a Jini service, I developed a Jini Service Container, I do Jini, it is the Jini way, etc. I also don't understand the implications of abandoning the trademark itself, but I would like to see that Jini can be used in the future as it is today, even when it makes your mouth foam. To summarize as *I* see it at this very moment: - Jini is not a product. - Jini can't be used as a noun. - Jini in combination with another noun could serve as a specification name for which one can have multiple implementations, such as 'Jini Helper and Utility Classes', 'Jini Platform', 'Jini Service Container', etc. - the deliverables of an Apache Jini TLP should get their own distinct name without Jini in it, except when it represent a 'Jini ... Specification'. - Jini itself only represents the magic of doing distributed computing in a proper way and comes in a lamp, these are already hard to find these days so please don't make it even harder :-) I would like to know whether people object against
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: http://mail-archives.apache.org/mod_mbox/incubator-general/ 200606.mbox/[EMAIL PROTECTED] I've also placed it in the wiki at: http://wiki.apache.org/incubator/JiniProposal which I'll update as we go along. thanks -jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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, integrations with other technologies, etc. For the most part they are led and developed by individuals or companies looking to share and leverage work within the Jini Community. Most of these projects were on our CollabNet -based Jini.org site prior to it being decommissioned on June 30, 2006. An overview of the overall Jini direction was outlined in a mail to the Community in April. See the note and full thread at: http://archives.java.sun.com/cgi-bin/wa?A1=ind0604L=jini-users#2 thanks -Jim On Aug 7, 2006, at 12:22 PM, Matthias Wessendorf wrote: I think they ended up at java.net (see [1]). Last week or so I saw that and was wondering myself, b/c of the proposal here. -Matthias [1] https://jini.dev.java.net/ On 8/7/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: So whatever happened to the Jini proposal?? I just remembered that there was a lot of discussion but don't recall the conclusion. Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 Hurley to chime in.) I agree with Bob's reasoning, and a different or qualified name might be a better choice after reflection. As Geir had mentioned... Sun's original intent (with the proposed Jini name of the project) was to donate the TM to the ASF. I'm not sure how that would work now (TM use -wise) with other Jini -related work and sites (for example, the jini.dev.java.net Community project area (for work around the Apache Jini project core), and the new informational Jini.org project site being worked). -Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 http://archives.java.sun.com/cgi-bin/wa?A2=ind0604L=jini- usersF=S=P=4029, I assume that the scope of the project will just be the core infrastructure. But you also mention related utilities and tools. Can you clarify a little more how the scope is defined? Phil Thanks Phil. :-) The related utilities and tools abstract the core infrastructure to make it easier for developers to build Jini clients and services. The ones we are specifically referring to are currently provided in the Jini Technology Starter Kit, which contains contributed implementations of Jini technology infrastructure services, as well as supporting helper classes, and other services including JavaSpaces technology. An example of a helper utility is JoinManager, which is a utility class that performs all of the functions related to discovery, joining, service lease renewal, and attribute management that the Jini programming model requires of a well-behaved service. See: http://java.sun.com/products/jini/2.1/doc/specs/html/joinutil- spec.html Therefore, we are trying to define the scope of the project as Jini technology core infrastructure software, including the implementation of Jini specs, related utilities and tools. HTH. -Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 includes core developers from Sun Microsystems (original developer of the technology) as well as Community technical leaders. This is very cool. Who controls the Jini spec, out of curiosity? -Brian Thanks Brian. Currently the specs are controlled by our community process, The Jini Community Decision Process (JDP). Details can be found at http://jini.org/jdp/. Right now we're leaning towards moving the specs into the Apache project (if accepted), and having them controlled by the PMC/committers of the project. This would replace the JDP's role in controlling changes to the specs. The whole of the Jini Community would still have a strong influence in what happens with the specs (through the Apache project aliases, etc), and for those in the Community wanting to get involved in a more substantive way, they have the opportunity to become a committer/be on the PMC. It's still somewhat of an open issue and is being discussed right now in the Jini Community. -Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Proposal] Jini project
to choose this as our best option. As a Java-based infrastructure for building systems, Jini fits in well with the other projects at Apache, and the Community we've built shares many philosophies (open communication, fairness, diversity, etc). We believe there are strong synergies here. (1) scope of the project The scope of the Jini project would be the continued development of Jini technology core infrastructure software, including the implementation of Jini specifications, related utilities and tools. The development would include adding new features and improving performance, scalability, quality, and extensibility. (2) identify the initial source from which the project is to be populated The initial resources would be garnered from: * Jini Technology Starter Kit http://starterkit.jini.org/downloads/2.1/ project on Jini.org, * Service UI implementation http://www.artima.com/jini/serviceui/CodeAccess.html from Artima.com, * QATests http://qatests.jini.org project on Jini.org (3) identify the ASF resources to be created (3.1) mailing list(s) * jini-ppmc (with moderated subscriptions) * jini-dev * jini-commits * jini-user (3.2) Subversion or CVS repositories Jini would like to use a Subversion repository. (3.3) Jira (issue tracking) Since Jini would have its own release cycle, it should have its own JIRA project * Project Name: Jini * Project Key: Jini (4) identify the initial set of committers * Dan Creswell ([EMAIL PROTECTED]) * Bill Venners ([EMAIL PROTECTED]) * Mark Brouwer ([EMAIL PROTECTED]) * 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 Barnaby ([EMAIL PROTECTED]) * Nigel Daley ([EMAIL PROTECTED]) * Fred Oliver ([EMAIL PROTECTED]) * Robert Resendes ([EMAIL PROTECTED] * Vinod Johnson ([EMAIL PROTECTED]) * Ron Mann ([EMAIL PROTECTED]) * Jim Hurley ([EMAIL PROTECTED]) (5) identify apache sponsoring individual * Champion - Geir Magnusson Jr. * Mentors - Geir Magnusson Jr. --- /last edited 2006-06-19 9:27:33 by Jim Hurley/ --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Proposal] Jini Project
communication, fairness, diversity, etc). We believe there are strong synergies here. (1) scope of the project The scope of the Jini project would be the continued development of Jini technology core infrastructure software, including the implementation of Jini specifications, related utilities and tools. The development would include adding new features and improving performance, scalability, quality, and extensibility. (2) identify the initial source from which the project is to be populated The initial resources would be garnered from: * Jini Technology Starter Kit http://starterkit.jini.org/downloads/2.1/ project on Jini.org, * Service UI implementation http://www.artima.com/jini/serviceui/CodeAccess.html from Artima.com, * QATests http://qatests.jini.org project on Jini.org (3) identify the ASF resources to be created (3.1) mailing list(s) * jini-ppmc (with moderated subscriptions) * jini-dev * jini-commits * jini-user (3.2) Subversion or CVS repositories Jini would like to use a Subversion repository. (3.3) Jira (issue tracking) Since Jini would have its own release cycle, it should have its own JIRA project * Project Name: Jini * Project Key: Jini (4) identify the initial set of committers * Dan Creswell ([EMAIL PROTECTED]) * Bill Venners ([EMAIL PROTECTED]) * Mark Brouwer ([EMAIL PROTECTED]) * 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 Barnaby ([EMAIL PROTECTED]) * Nigel Daley ([EMAIL PROTECTED]) * Fred Oliver ([EMAIL PROTECTED]) * Robert Resendes ([EMAIL PROTECTED] * Vinod Johnson ([EMAIL PROTECTED]) * Ron Mann ([EMAIL PROTECTED]) * Jim Hurley ([EMAIL PROTECTED]) (5) identify apache sponsoring individual * Champion - Geir Magnusson Jr. * Mentor - Geir Magnusson Jr. --- /last edited 2006-06-19 9:27:33 by Jim Hurley/ --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
