Here's what I have: The HiveMind PMC has voted to move HiveMind into the "Attic." Henri Yandell has graciously offered to take care of presenting HiveMind to the Attic PMC and the board for inclusion in the Attic. James Carman
On Wed, Mar 4, 2009 at 10:26 PM, James Carman <james <at> carmanconsulting.com> wrote: > Here's what I have: > > The HiveMind PMC has voted to move HiveMind into the "Attic." Henri > Yandell has graciously offered to take care of presenting HiveMind to > the Attic PMC and the board for inclusion in the Attic. > > James Carman It has been a good library/framework to work with and served as a launch pad for next generation IoC but this seems the right decision. Thanks to all HiveMind developers! Regards -- -- Massimo http://meridio.blogspot.com
I don't get it ... could some one explain this decision? There were some discussions on this list about HiveMind. There was even the effort to do a maintenance release. I grant you that there was not much reaction to it, but at least the HiveMind PMC should have reacted in some way ... no one cared to answer to even direct questions about help on this topic ... If you planned this anyway for some reasons you could have explained this in the past instead of encourage further work and then simply stop answering questions ... that's sort of weird, I think(Continue reading)Cheers, Jochen -------- Original-Nachricht -------- > Datum: Thu, 5 Mar 2009 09:31:38 +0100 > Von: Massimo Lusetti <mlusetti <at> gmail.com> > An: dev <at> hivemind.apache.org > Betreff: Re: [DRAFT] HiveMind Board Report - March 2009 > On Wed, Mar 4, 2009 at 10:26 PM, James Carman > <james <at> carmanconsulting.com> wrote: > > > Here's what I have: > > > > The HiveMind PMC has voted to move HiveMind into the "Attic." Henri > > Yandell has graciously offered to take care of presenting HiveMind to > > the Attic PMC and the board for inclusion in the Attic. > > > > James Carman > > It has been a good library/framework to work with and served as a
Am Mittwoch, 4. März 2009 22.26:27 schrieb James Carman: > Here's what I have: > > The HiveMind PMC has voted to move HiveMind into the "Attic." Henri > Yandell has graciously offered to take care of presenting HiveMind to > the Attic PMC and the board for inclusion in the Attic. > > James Carman That's a pity ... but no surprise, it was only a question of time ... :( To explain myself, as I am one who at least talked about contributing to HiveMind, but never did: What I am using and developing is an extension to HiveMind, a thing, that would always be a separate project. HiveApp, is I uninspiredly call it, is in production about 20 times, and that number is growing and will continue to grow. I needed some things to be done differently, but those were things that the majority of "plain HiveMind" users wouldn't care about. This fact makes it very difficult for me to start contributing to HiveMind itself, because I'm often looking at things from a different perspective. Where some people wanted new features, my focus would rather be to open HiveMind to provide hooks at implementation-level, where I and possibly other people working at low-level could hook into and extend HiveMind. As an example: HiveMind is largely designed to run within a web application server. The way I'm using it, I reverse things: Jetty is running within the HiveMind container. Therefore, it's very difficult for me to contribute "my(Continue reading)
It's a direct reaction to the effort. Users are trying to put together the release. There is no one in the project committers to support them. Therefore the project needs to be moved to the Attic which will have clear instructions and support for others to fork the project with Apache's blessing. Ideally it's not a fork but rather a closing down at Apache and a starting up elsewhere with a new group. So now that the HiveMind committers have voted for that, the Attic group will be able to use it as a first use case to put together those instructions/blessing/steps. Hope that helps - this is specifically to try to help the situation where a project has an active user base but no developer base, as with HiveMind. Hen On Thu, Mar 5, 2009 at 1:29 AM, Jochen Zimmermann <zet4080 <at> gmx.de> wrote: > I don't get it ... could some one explain this decision? > There were some discussions on this list about HiveMind. > There was even the effort to do a maintenance release. > I grant you that there was not much reaction to it, but at least the HiveMind PMC should have reacted in some way ... no one cared to answer to even direct questions about help on this topic ... > > If you planned this anyway for some reasons you could have explained this in the past instead of encourage further work and then simply stop answering questions ... that's sort of weird, I think(Continue reading)
Thanks for that explanation - it makes the intention clear now(Continue reading)-------- Original-Nachricht -------- > Datum: Thu, 5 Mar 2009 19:26:13 -0800 > Von: Henri Yandell <flamefew <at> gmail.com> > An: dev <at> hivemind.apache.org > Betreff: Re: [DRAFT] HiveMind Board Report - March 2009 > It's a direct reaction to the effort. > > Users are trying to put together the release. There is no one in the > project committers to support them. Therefore the project needs to be > moved to the Attic which will have clear instructions and support for > others to fork the project with Apache's blessing. Ideally it's not a > fork but rather a closing down at Apache and a starting up elsewhere > with a new group. > > So now that the HiveMind committers have voted for that, the Attic > group will be able to use it as a first use case to put together those > instructions/blessing/steps. > > Hope that helps - this is specifically to try to help the situation > where a project has an active user base but no developer base, as with > HiveMind. > > Hen > > On Thu, Mar 5, 2009 at 1:29 AM, Jochen Zimmermann <zet4080 <at> gmx.de> wrote: > > I don't get it ... could some one explain this decision? > > There were some discussions on this list about HiveMind.
Hi Henry, So while the Attic group picks the project up, would you actively be looking for a group to pick it up, or does a group have to 'announce' itself to be considered? Also, for practical things such as patches etc supplied, would these be available after a closure? Cheers, Johan Henri Yandell wrote: > It's a direct reaction to the effort. > > Users are trying to put together the release. There is no one in the > project committers to support them. Therefore the project needs to be > moved to the Attic which will have clear instructions and support for > others to fork the project with Apache's blessing. Ideally it's not a > fork but rather a closing down at Apache and a starting up elsewhere > with a new group. > > So now that the HiveMind committers have voted for that, the Attic > group will be able to use it as a first use case to put together those > instructions/blessing/steps. > > Hope that helps - this is specifically to try to help the situation > where a project has an active user base but no developer base, as with(Continue reading)
RSS Feed8 | |
|---|---|
7 | |
8 | |
5 | |
22 | |
1 | |
11 | |
68 | |
26 | |
3 | |
9 | |
6 | |
4 | |
2 | |
3 | |
4 | |
8 | |
35 | |
5 | |
68 | |
67 | |
7 | |
49 | |
19 | |
21 | |
61 | |
86 | |
86 | |
94 | |
66 | |
74 | |
36 | |
68 | |
57 | |
17 | |
63 | |
65 | |
86 | |
83 | |
108 | |
220 | |
105 | |
102 | |
160 | |
76 | |
36 | |
70 | |
94 | |
142 | |
185 | |
160 | |
122 | |
31 | |
45 |
