[ann] HiveMind retirement

A heads up for the HiveMind user community that the HiveMind project
has been 'moved to the Attic'. This means that the HiveMind developers
(more formally its Project Management Committee) have voted to retire
HiveMind and move the responsibility for its oversight over to the
Attic project.

You can read more about the Apache Attic at http://attic.apache.org.

HiveMind is the first project to move into the Attic, so the process
will be identified as we go along. You can follow this at
https://issues.apache.org/jira/browse/ATTIC-1 if you so wish.

Thanks,

Henri Yandell
on behalf of HiveMind + the Attic.

Re: [ann] HiveMind retirement

On Thu, Apr 16, 2009 at 5:20 AM, Henri Yandell <flamefew <at> gmail.com> wrote:

> HiveMind is the first project to move into the Attic, so the process
> will be identified as we go along. You can follow this at
> https://issues.apache.org/jira/browse/ATTIC-1 if you so wish.

It's somehow sad and nice at the same time for HiveMind to be the
first one to be moved into the Attic.

HiveMind has been a nice project to work with plus it has settled the
base for future concepts in IoC containers.

Thanks to all developers

Cheers
--

-- 
Massimo
http://meridio.blogspot.com

Re: [ann] HiveMind retirement

Re: [ann] HiveMind retirement

Nothing that I know of (beyond the usual suspects in the IoC world).

That's a very good point though and something for the Attic to
document if any of the HiveMind community identify an obvious
candidate.

On Thu, Apr 16, 2009 at 7:33 AM, Kevin Gilpin <kevin.gilpin <at> praxeon.com> wrote:
> Is there a recommendation to switch to an alternative framework?
>
> On Wed, Apr 15, 2009 at 11:20 PM, Henri Yandell <flamefew <at> gmail.com> wrote:
>>
>> A heads up for the HiveMind user community that the HiveMind project
>> has been 'moved to the Attic'. This means that the HiveMind developers
>> (more formally its Project Management Committee) have voted to retire
>> HiveMind and move the responsibility for its oversight over to the
>> Attic project.
>>
>> You can read more about the Apache Attic at http://attic.apache.org.
>>
>> HiveMind is the first project to move into the Attic, so the process
>> will be identified as we go along. You can follow this at
>> https://issues.apache.org/jira/browse/ATTIC-1 if you so wish.
>>
>> Thanks,
>>
>> Henri Yandell
>> on behalf of HiveMind + the Attic.
>
>
>
> --
> CTO
> Praxeon Inc
> kevin.gilpin <at> praxeon.com
>

The Attic and Beyond

Hi all

So, now it's official: HiveMind's development at Apache has stopped. Time to 
move on and start over. ;)

For me, one thing is clear: I will branch HiveMind, one way or the other. 
The question for me is: Which way?

As some of you may know, I'm developing and using HiveApp, an extension to 
HiveMind which adds a VFS, ClassLoader management, built-in JMX support and 
some useful services. There are many applications based on it in production 
(and there will be many more) and its development continues, although it's 
currently a one-man-show (everything's open though, and anyone is free to 
join: http://hiveapp.raffael.ch/).

So, from this point of view, the obvious thing to do is to take HiveMind's 
source code, integrate it into HiveApp's source tree, and just continue 
like that.

However, now's the time to look further. ;) HiveMind, as it is now, is good, 
but it's gotten a bit outdated, and development as officially stalled. I've 
got many ideas what to do with HiveMind (you can find some of them in 
HiveApp) and I'm sure, there are more people with ideas. This is the time 
to progressively move forward, because there won't be any HiveMind 1.2 or 
2.0 anymore. But there may be a HiveSomethingElse 0.1.

The question is: If you had commit rights for HiveMind's source code 
tomorrow, would you start contributing?

The idea is to branch HiveMind at OPS4J (http://www.ops4j.org/). OPS4J 
stands for "Open Participation Software for Java", a relatively young and 
active FOSS community. "Open Participation" means basically Wiki brought to 
coding. Anyone can start contributing: Just register yourself, and you've 
immediately got commit access to all of OPS4J's SVN. At OPS4J, if you find 
a bug, you don't submit a patch which fixes it and wait for a committer to 
apply your patch. At OPS4J, you commit the fix yourself. OPS4J provides all 
the infrastructure one needs: Version control (SVN), bug tracking (JIRA), 
Wiki (Confluence), CI (Bamboo), mailing lists, web space ...

Introduction to OPS4J: http://wiki.ops4j.org/display/ops4j/Introduction

I think, this community might be just the right thing to kickstart 
HiveMind's development. I've already talked to some people at OPS4J about 
it, they'd happily welcome the HiveMind community.

However, the question remains: Are there people who would actually 
contribute?

What do you think?

Cheers,
   Raffi

--

-- 
The difference between theory and practice is that in theory, there is
no difference, but in practice, there is.

herzog <at> raffael.ch · Jabber: herzog <at> raffael.ch
PGP Key 0x5FFDB5DB5D1FF5F4 · http://keyserver.pgp.com

Re: The Attic and Beyond

Hi Raffael,

I am all for this idea - not very familiar with OPS4J, but their
intentions sounds good.  Definitely would allow more contributions to
trickle in.

So, count me in.

Cheers,

Johan

Raffael Herzog wrote:
> Hi all
> 
> So, now it's official: HiveMind's development at Apache has stopped. Time to 
> move on and start over. ;)
> 
> For me, one thing is clear: I will branch HiveMind, one way or the other. 
> The question for me is: Which way?
> 
> As some of you may know, I'm developing and using HiveApp, an extension to 
> HiveMind which adds a VFS, ClassLoader management, built-in JMX support and 
> some useful services. There are many applications based on it in production 
> (and there will be many more) and its development continues, although it's 
> currently a one-man-show (everything's open though, and anyone is free to 
> join: http://hiveapp.raffael.ch/).
> 
> So, from this point of view, the obvious thing to do is to take HiveMind's 
> source code, integrate it into HiveApp's source tree, and just continue 
> like that.
> 
> However, now's the time to look further. ;) HiveMind, as it is now, is good, 
> but it's gotten a bit outdated, and development as officially stalled. I've 
> got many ideas what to do with HiveMind (you can find some of them in 
> HiveApp) and I'm sure, there are more people with ideas. This is the time 
> to progressively move forward, because there won't be any HiveMind 1.2 or 
> 2.0 anymore. But there may be a HiveSomethingElse 0.1.
> 
> The question is: If you had commit rights for HiveMind's source code 
> tomorrow, would you start contributing?
> 
> The idea is to branch HiveMind at OPS4J (http://www.ops4j.org/). OPS4J 
> stands for "Open Participation Software for Java", a relatively young and 
> active FOSS community. "Open Participation" means basically Wiki brought to 
> coding. Anyone can start contributing: Just register yourself, and you've 
> immediately got commit access to all of OPS4J's SVN. At OPS4J, if you find 
> a bug, you don't submit a patch which fixes it and wait for a committer to 
> apply your patch. At OPS4J, you commit the fix yourself. OPS4J provides all 
> the infrastructure one needs: Version control (SVN), bug tracking (JIRA), 
> Wiki (Confluence), CI (Bamboo), mailing lists, web space ...
> 
> Introduction to OPS4J: http://wiki.ops4j.org/display/ops4j/Introduction
> 
> I think, this community might be just the right thing to kickstart 
> HiveMind's development. I've already talked to some people at OPS4J about 
> it, they'd happily welcome the HiveMind community.
> 
> However, the question remains: Are there people who would actually 
> contribute?
> 
> What do you think?
> 
> Cheers,
>    Raffi
> 

--
you too?

Re: The Attic and Beyond

On Fri, Apr 17, 2009 at 1:55 PM, Raffael Herzog <herzog <at> raffael.ch> wrote:

> However, the question remains: Are there people who would actually
> contribute?
>
> What do you think?

I won't contribute directly to it but it's sure i will do a
chenillekit module (http://tapestry.formos.com/nightly/chenille-kit/)
for the new project to bridge it to T5 IoC.
So after all a very nice idea.

--

-- 
Massimo
http://meridio.blogspot.com

Shutting down the dev list

Notice of intent that I'm going to ask the infra team to close up the
dev list for HiveMind, while keeping the user list open.

Hen