It is great to hear that HiveMind does have a small, but devoted following
still! :)  I still believe in HiveMind.  It does some things that the others
just don't do.  I couldn't use HiveMind on our current project because the
team members were afraid of the lack of documentation (the "book factor").
I'm happy with our current spring-based architecture, but there are
definitely times that I wish we have HiveMind around for stuff like
overriding service implementations.
I would encourage some of you devoted HiveMinders to submit some patches to
anything you want to see in the 1.1.2 release and I'll do my best to get
them in there (provided they have test cases and don't break anything else
of course).  I'm sure I can get the other PMC members to vote for new
members quite easily (I need 3 +1s I think), so maybe we can get some "new
blood" in here and let them revive the project, but we can't do that without
a "track record" which means community involvement and code patches.  Also,
if you can't provide code patches, it might be helpful to put some votes out
there in JIRA so that we know what folks are really wanting and we can
concentrate our efforts.

On Wed, Nov 26, 2008 at 6:24 AM, Jochen Zimmermann <zet4080@gmx....> wrote:

> Sorry, hit the enter button accidentially :-)
>
> I agree too, we use Hivemind for company internal projects for some time
> now and have no complaints and will use it for other projects in the future.
>
> But sometimes I have problems to convince team members to stick to Hivemind
> because there is no active development anymore ... so I can understand the
> question if the project is dead or not because I had some discussions
> because of that question in my team :-)
>
> Regards,
> Jochen
>
> -------- Original-Nachricht --------
> > Datum: Wed, 26 Nov 2008 09:10:57 -0200
> > Von: Juliano Viana <juliano@logi...>
> > An: dev@hive...
> > Betreff: Re: [DISCUSS] [REPORT] HiveMind November 2008
>
> > Hello,
> >
> > Couldn't agree more.
> > After using Hivemind over the last 4 years in many projects, I can say I
> > have no wish list for feature improvements at the moment. It could use
> > better documentation but once you start using it , it simply works.
> > I really don't believe using annotations as was planned for Hivemind 2.0
> > would be a big improvement in the way it works, maybe quite the
> > opposite. So I believe this project, while no longer in active
> > development, is far from dead.
> >
> > Regards,
> >   - Juliano
> > Johan Maasing wrote:
> > > We use hivemind in our web portal, serving a lot of customers. So I
> > > would say that our organization is pretty dependent on hivemind and we
> > > are slowly increasing the use of hivemind to wire together frameworks,
> > > both web-portals, plain java applications and webservice frameworks.
> > > So why are we not involved in developing hivemind further?
> > > Because "it just works". We have no big problems with hivemind, it has
> > > all the features we need. The configuration and contribution-trick in
> > > hivemind is a killer feature, I know no way to do the same thing as
> > > easily in spring, guice or the others. Perhaps there is but I don't
> > > know how. So for us hivemind is a very nice tool that just works.
> > > So the hivemind project on apache might be slow and appear dead but
> > > that shouldn't stop you from using it. It is mature, tested in battle
> > > and works.
> > >
> > > Cheers,
> > > Johan
> > >
> > > 2008/11/18 James Carman <james@carm...>:
> > >
> > >> HiveMind hasn't been in active development for quite some time.
> > >>
> > >> On Tue, Nov 18, 2008 at 10:19 AM, fan_42 <frank.bommeli@nose...>
> > wrote:
> > >>
> > >>> I just stumbled up HiveMind.
> > >>>
> > >>> it sound interesting to me, but is it dead or is it on hold?
> > >>>
> > >>> --
> > >>> View this message in context:
> >
> http://www.nabble.com/-DISCUSS---REPORT--HiveMind-November-2008-tp20437346p20561587.html
> > >>> Sent from the HiveMind - Dev mailing list archive at Nabble.com.
> > >>>
> > >>>
> > >>>
>