OK, let's summarize :-) There *is* some interest in Hivemind left, at least there were 4 or 5 people giving answers to the board report. >From my point of view we need somebody to take the lead :-) In most posts (this was true for the last board report in February, too) there is a "maybe", "we should" and so on, but no one who actually decides something and put it on the road ... As I mentioned now for two or three times I know not much about the structures of an open source project inside Apache, so I can be terribly wrong, but: It seems like there should be a group of people that is responsible for each project. In case of Hivemind there are not much people left from that group, even not enough to put some other peoples in charge. For example, there is no one who says: OK, Johan, go on, apply the patches and prepare a release!
All what is said is a bit vague without concrete plan ... For me, (based on my observations in this mailing list, don't want to offend someone) there are only two (perhaps three) persons at the moment, who could fill that gap: James, Johan (and perhaps Achim, but he seems to be very busy, too). Whoever takes the lead should make a concrete, but perhaps very small plan for the very near future and ask the people who showed interest to follow this plan and assign tasks to them. Then we can see if the interest is really big enough to start some bigger efforts and if it is really worth to start a discussion about the future of HiveMind ... To come to that discussion: If the Hivemind-vs-Spring - Philosophy article from Howard is still true now, 4 years later, there *is* some difference in the philosophy of both packages. And, if this differences still exists, this implies that you do things in a slightly different way - even if it is possible to achieve the almost same result in Spring. Without knowing Spring much it sounds like you end up with a different application design ... A different application design would be a good reason to choose one or another package, so this alone would justify the existence of HiveMind as a standalone project. Or is this difference to small? What are the things we can do with Hivemind we can't do with Spring? Cheers, Jochen -----Ursprüngliche Nachricht----- Von: Johan Lindquist [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 14. Mai 2008 11:12 An: [email protected] Betreff: Re: AW: HiveMind for Applications -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As a start, maybe we should call for all interested parties to have a look at issues (focusing on bugs primarily) and use the JIRA voting system. This would give us a good hint as to what is immediately wanted/needed. I can in parallel take a look to try to summarize outstanding issues as well ... It would also be nice perhaps to add a couple of new versions to JIRA (1.2, 1.2.1 or even 1.3) and re-assign pending maintenance and enhancements for 1.X - giving us small roadmap to work against. Emphasis on 'maintenance updates' at the moment, to see where the wind takes it ... Jochen, a couple of Howards posts relating to Spring/Hivemind differences below - somewhat outdated, but a start ... http://tapestryjava.blogspot.com/2004/02/comparing-hivemind-to-spring.html http://tapestryjava.blogspot.com/2004/06/hivemind-vs-spring-philosophy.html Cheers, Johan [EMAIL PROTECTED] wrote: | Yesterday evening I scanned all the JIRA Issues. | I found quite a few bugs where patches already exists. As I see it there are 78 issues, but only 13 bugs without a patch. All other issues do have patches or are improvements, wishes or new feature requests (and there are also some with patches already included). |>From that 13 open bugs are some with comments that suggests that these "bugs" could be solved with a different approach or aren't bugs at all, some are for Hivemind 2.0 only, so I believe there are less than 10 real bugs left for Hivemind 1.1.1 ... | | Perhaps someone (Johan? :-) should scan the issues (and patches) and mark the ones (including feature requests) we need solved (or refactored) for a 1.2 release. I made an Excel sheet where I marked the issues that have patches supplied and the ones that are open, but I can only send this in the evening, because I'm at work now :-) | | To start a discussion for "give Hivemind a new reason of existence": | Could someone emphasise differences to Spring that exists at the moment? | There must be some differences, I think Howard did something like this in the past already, but I was not able to find the web page again where I read this ... this could be a good start for a discussion ... what do you think?? | | Cheers, | Jochen | | -----Ursprüngliche Nachricht----- | Von: Johan Lindquist [mailto:[EMAIL PROTECTED] | Gesendet: Mittwoch, 14. Mai 2008 08:44 | An: [email protected] | Betreff: Re: HiveMind for Applications | | Agree, but we should not forget the few faithfuls out there ;) And | there has been interest out there for a 1.2 from quite a few ... | | Would an option be to trickle out a 1.2 release while putting more | effort into re-defining Hivemind's reasons for not dying? | | Cheers, | | Johan | | Raffael Herzog wrote: | | Am Dienstag, 13. Mai 2008 15.04:43 schrieb James Carman: | |> On Tue, May 13, 2008 at 7:57 AM, <[EMAIL PROTECTED]> wrote: | |>> James - do you think that there is any chance that there will be any | |>> work on Hivemind in the future? Or is it really at its end? | |> I really don't know at this point. Spring is very pervasive and even | |> Howard stopped using HiveMind on Tapestry (our biggest source of | |> customers by far) in version 5. I actually use Spring myself now. | | | | I think, this is exactly HiveMind's problem: In that moment, when | Tapestry | | stopped using HiveMind, HiveMind basically lost it's reason of existence. | | There are now two options: | | a) we let it die | | b) we give it a new reason of existence | | | | This might also include throwing away some existing efforts for 1.2 or | 2.0, | | no replacement planned. *might*, not *must*! | | | | I think, if we want to get HiveMind back to life, we should be open to | take | | some drastic measures. | | Cheers, | | Raffi | | | - -- you too? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIKqzZpHYnED7evioRAjt/AJ9IXtMbFztUPE7ddNZfojYZOG2w/gCfUv2F XwQlhX9kjoncfz0QLuuTD5E= =SG3x -----END PGP SIGNATURE-----
