river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Calum Shaw-Mackay" <calum.shawmac...@gmail.com>
Subject Re: Split JavaSpaces and JINI
Date Thu, 11 Dec 2008 09:44:52 GMT
I think shouting Fork is a little premature.... I think before we
think that the project is in limbo.... perhaps we should think more
that the committers are in limbo...

We need a common set of goals... bugfixes and little tweaks to support
your own wants and nullify your own niggles with the tech is all well
and good but it does not progress anything in any direction but that
of a small group of interested parties.... I believe we have to stop
thinking about what is right for 'abc' and start looking at the bigger
picture and what is right for the project as a whole

We need to qualify and quantify these goals against cost, speed and
quality and start getting some of them our the door. For instance to
my mind, a small bigfix may be easy to do but may pale into
insignificance when say putting XA support into the transaction
manager, or starting a spec for qualifiable entry matching (the old
less than X more than Y argument). I think what Niclas is alluding to
is that we do not have much time in which to further stagnate this
technology.... 1.4 is now out of support for normal end users although
business support continues to 2018, we can't use the same excuses any
more... and with not having the full resources of the sun team we have
to take this on our selves and actually get on with it.


2008/12/11 Niclas Hedhman <niclas@hedhman.org>:
> On Thu, Dec 11, 2008 at 5:26 PM, Jools <joolski@gmail.com> wrote:
> Thanks for the feedback. Fork comes to mind, and there seems to be
> enough willing people to take big steps in all kinds of directions. I
> hope we can grow a common base to move forward. It will be interesting
> days for me for the remaining days of the year. Stay tuned.
>> So I guess it comes to this. Is river just a place where Sun has parked
>> jini, so legacy codebases can get access to the old code, or is it a place
>> where we can start to build the tools for the next generation of distributed
>> systems ?
> <hat type="Mentor/PMC Member">
> If this is the case, then River will fail incubation and either be
> dangling in limbo or have to be moved elsewhere. Incubator will not
> graduate a community dormant project.
> </hat>
> Cheers
> Niclas

View raw message