Am Donnerstag, 23. April 2009 14.12:12 schrieb Cameron Braid: > What are the reasons for apache retiring it ?
Henri Yandell from the Apache Attic team explained it here: http://mail-archives.apache.org/mod_mbox/hivemind-dev/200903.mbox/%3c31cc37360903051926y28d576b7w70978339abd08...@mail.gmail.com%3e Short version: HiveMind was basically stuck in Apache's system, because there were no active committers anymore who could commit a patch, and without submitting patches, you can't get promoted to a committer. HiveMind would have needed to go through the Incubator again. > What are the reasons for OPS4J continuing its development ? In the above E-Mail, Henri Yandell wrote: "Ideally it's not a fork but rather a closing down at Apache and a starting up elsewhere with a new group." -- That's exactly what we are trying to do. We think, that OPS4J is the right platform to do that, because of it's massively lowered barrier (compared to Apache) trough the concept of Open Participation. Also, with an established platform and community like OPS4J, we've got a better chance to actually succeed, than by just opening a project at CodeHaus or SourceForge or similar. And finally, I'm here at OPS4J since the beginnings, I'm developing and actively using HiveApp, an extension to HiveMind in my lab, so from my perspective, moving HiveMind to OPS4J was an obvious choice. :) We're going to provide legacy support and maintenance for existing users, while working on a modernised NextGen HiveMind. HTH & Cheers, Raffi -- The difference between theory and practice is that in theory, there is no difference, but in practice, there is. her...@raffael.ch · Jabber: her...@raffael.ch PGP Key 0x5FFDB5DB5D1FF5F4 · http://keyserver.pgp.com _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
