What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
| Date | Action | Decided by |
|---|---|---|
| 2006-04-26 | Appointed James Carman | the board, by resolution |
| Date | Decision | Item | Outcome |
|---|---|---|---|
| 2009-03-18 | Termination of the HiveMind PMC | special order | approved |
| 2006-04-26 | Establish the Apache HiveMind Project | special order | approved |
The HiveMind project has remained quite inactive during the last 3 months. There are currently no active developers on the project.
The HiveMind project has remained quite inactive during the last 3 months. There are currently no active developers on the project.
The HiveMind project has remained quite inactive during the last 3 months. There are currently no active developers on the project.
The HiveMind project has remained quite inactive during the last 3 months. There are currently no active developers on the project. However, some of the users have expressed interest in becoming contributors. They have been asked to begin providing patches to JIRA issues. After I sent this out to the development list for review (Feb 9th), the JIRA issues started to get some attention. In particular, Johan Lindquist and Jochen Zimmerman started commenting and attaching patches.
The HiveMind project has remained quite inactive during the past three months. Howard removed his name from the HiveMind JIRA issues assigned to him. A few new JIRA issues have been entered, but no work has been done on them, since we really have no active developers. There has been some interest from Tapestry users in some of the HiveMind-based libraries (hibernate, acegi, etc.) that I've written in the past.
There is really not much to report. The HiveMind project has remained almost completely inactive during the last 3 months. There have been a few questions asked/answered on the mailing lists and maybe some JIRA issues filed (mainly because of a release of Tapestry 4.x which uses HiveMind). As for development, I do not believe there are currently any active committers.
NEWS
- A HiveMind-2.0-apha-1 release was cut.
- I have requested that someone else take over the reigns as chair of the
HiveMind project. My work schedule has left me with little time. As of
yet, none of the committers has taken me up on the offer. They all
seem to be just as busy as me.
SVN ACTIVITY (02/14/2007 - 03/15/2007)
HiveMind2: There were 236 commits with the last one occurring on 02/19.
Achim performed all commits.
HiveMind1: There were no commits.
NOTES
The HiveMind development community struggles to maintain itself. All of
our active committers are busy with other endeavors (work, other projects
like Tapestry5, etc.). What happens to a top-level project if its
development community dwindles away?
- The HiveMind team is actively working on the HiveMind 2.0 API. - We're trying to migrate the HiveMind 1.x branch(es) over to use Maven for releases since we've had requests from our users that the jars in the maven2 repositories need a real POM with dependencies and all. - We've replaced the website with a maven-based one.
The HiveMind team is working on the architecture for HiveMind 2.0. The HiveMind TLP move is finally finished. Thanks to all who helped us (actually me; I'm still learning) in the process. We are also in the process of cutting a 1.1.2 release. I believe we are going to switch to a new release strategy, much like what Tapestry is doing. Basically, we cut a release, but don't declare it "official" until we have a vote on it. That's my understanding at least. Does this go along with what the rest of Apache does?
The HiveMind team is working on the architecture for HiveMind 2.0. The HiveMind TLP move is still in progress. The website content has been moved, but we still need to get the containing websites (Apache main and Jakarta) updated to reflect the move. We are also in the process of cutting a 1.1.2 release.
The HiveMind team is working on the architecture for HiveMind 2.0. The HiveMind TLP move is still in progress. We still need the websites directory and the hivemind unix group created. We are also in the process of cutting a 1.1.2 release.