Jean-Francois Poilpret wrote:
Hello,
Why go to java.net? Is there something wrong with SourceForge? Actually, I am not really keen on starting a "war" among OSS repositories but I'd like to understand why SF "could not fit"... Hence I would prefer staying with SF (as long as it fulfills my needs and the needs of the community; I will later see if I have problems setting up the CVS when I have time...).
Honestly I have to say that the "administrative" work is not what I enjoy most ;-) So changing from one site to another, having to relearn how to upload files, upload web content... is a bit of a hassle for someone who prefers to spend time on active "code production" (I suppose you all see what I mean;-)) In addition, I am a faithful guy, so I would need a really good reason to change.
Well i have no real opinion on this, from what i've read it's more a question a personal taste and image. So whatever you prefer i think it will be great. The most important thing is not where it's hosted but more the amount of features that is offered to Hivemind Utilities users. As more and more users are likely to come across the project(even more after the link is posted on hivemind site) i think it would be essential to have:
- An issue tracking application.
- A forum.
- CVS access.
- Good documentation.
With all this i think this project would be able to grow much much faster.
Regarding the sourceforge name "hivetranse", after all it is just used in URLs, it is easy to provide a link that hides this "awful" name:
<a href="http://sourceforge.net/hivetranse/";>HiveMind Utilities</a>
If you do a simple search of "HiveMind" in SF, you will find (among other results):
Project Name: HiveMind Utilities Description: HiveMind Utilities is a set of utilities for HiveMind...
So no "official" hivetranse name there. Why bother?
I think it's a matter of image don't you think ? I would prefer if the sourceforge project name would be changed, it's just cleaner.
Cheers
Jean-Francois
-----Original Message-----
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 11, 2005 9:33 PM
To: [email protected]
Subject: Re: Announcement: The HiveTranse family grows again and changes
name!
Perhaps it would be easier to start over on java.net than continue on SourceForge?
On 5/11/05, James Carman <[EMAIL PROTECTED]> wrote:
I think putting a link to the HiveMind Utilities project would be a wonderful idea. Although, I would recommend changing the URL first. Can you create a new SF project named hivemind-utils (actually
hivemind-contrib
might be more suitable, as it follows the usual naming convention that
other
projects use)? Then, we can put a link from the main HM site that says, "Check out the contributions the HiveMind community has made!" or
something.
-----Original Message----- From: Jean-Francois Poilpret [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 11, 2005 9:40 AM To: [email protected] Subject: RE: Announcement: The HiveTranse family grows again and changes name!
Hello Hugo,
Thank you very much for your enthusiastic support to HiveMind Utilities project!
Regarding integrating these modules into HiveMind, it was from the
beginning
of my involvement into HiveTranse (previous name of the HiveMind
Utilities,
which essentially focused on HM-Hibernate integration) that for licensing reasons, HiveTranse could not be integrated into HiveMind distribution. At this time (I think it must be September or October last year), some long discussion occurred to determine that any library that depends on
Hibernate
(LGPL license) could not be hosted on the Apache site. This is also at
that
time that Howard suggested that I create a project on SF or some other OSS repository. That I did a few months later (the time to make the first hivetranse contribution cleaner).
Now I believe that, in the list of all libraries that HiveMind Utilities depend on globally, probably Hibernate must be the only one to have this licensing problem. In HM Utilities, only one module explicitely depends on Hibernate, this is hivetranse.hibernate (plus the example.hibernate module of course). So it would still be possible to consider integration of a
part
of HM Utilities into HM distribution. I am quite open on this point.
One more thing: some time ago (beginning January I believe), Howard had
also
said it seemed to him a good idea to have some external repository of general utility HM modules.
Maybe one simple way to integrate could be as simple as putting a link to the HM Utilities SF project (or the project web home which is more "personalized" than the generic SF web interface) from the HiveMind site.
Cheers
Jean-Francois Poilpret, HiveMind Utilities team
-----Original Message----- From: Hugo Palma [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 11, 2005 4:28 PM To: [email protected] Subject: Re: Announcement: The HiveTranse family grows again and changes name!
First of all, congratulations on the great work you've donne with HiveMind Utilities. If it wasn't for these project i think i wouldn't have made the Spring to Hivemind migration i did.
Having said this, i just couldn't help thinking while i found the classes in this module more and more useful that they should be part of hivemind itself, and not a separate project. I think this would great both for hivemind and utilities. Utilities would have more visibility, therefore more support from the community and hivemind itself would be a more complete and easy to use framework out-of-the-box.
What are your thoughts about this ?
Cheers
Hugo
Jean-Francois Poilpret wrote:
Dear HiveMind users,
I am glad to announce (after a long silent period) the new release 0.4.0
of
HiveTranse on SourceForge.
Now the project has changed name into "HiveMind Utilities" but the URL
have
not changed however. This name change is due to the fact that the project now hosts a bunch of various utilities dedicated to applications built with HiveMind, and is
not
just limited to transaction management.
It must be noted that this release is still working with HiveMind 1.0
only.
It will probably be the last release to work with HM1.0, the next release should be a port to HM1.1 (but lately I did not have much time to play
with
the latest HM1.1 beta however...)
The original SourceForge announcement is at the end of this mail.
Please do not hesitate to give a try to the various modules provided and
to
comment on these.
In 1-2 weeks time, I hope I will release a pre-version of HiveBoard (also
on
SourceForge), a client/server shared whiteboard system based on HiveMind (and HiveMind Utilities of course). This could be a good way to get
quickly
started with the possibilities of HiveMind Utilities modules.
Cheers
Jean-Francois Poilpret
Announcement on SourceForge: The HiveTranse family grows again and changes name!
At the occasion of 0.4.0 release, the HiveTranse project team is glad to announce several modifications into the project.
First, due to its wider scope, the HiveTranse project is now renamed "HiveMind Utilities", however the name code on SourceForge still remains "hivetranse".
In release 0.4.0, the HiveMind Utilities project has had the following modifications: - refactoring of hivetranse.utils module into hiveutils module and
renaming
of packages in this module (net.sourceforge.hivetranse) to net.sourceforge.hiveutils. - removal of web.utils module, which content has been moved to hiveutils module. - new features added to hiveutils module, in particular a new
ObjectBuilder
service that can create and cache any kind of objects, and inject dependencies into them (can be seen as a hivemind.BuilderFactory for a
wide
range of objects (each such object is defined in a configuration point in order to ease usage of this feature). - renaming of hivetranse.transaction module to hivetranse.core. No package has been renamed however. - creation of new hiveevents module. - creation of new hivegui module.
To summarize, HiveMind Utilities project, as of release 0.4.0, contains
the
following modules: - hiveutils: set of useful classes and services for HiveMind-based applications - hivetranse.core: advanced generic transaction management framework - hivetranse.jdbc: support for JDBC persistence layer in your DAOs - hivetranse.hibernate: support for Hibernate persistence layer in your
DAOs
- hivetranse.ibatis: support for iBATIS SqlMaps persistence layer in your DAOs - hivelock.core, hivelock.shared, hivelock.default: support for security management (authentication, authorization, stateful services) - hiveremoting.caucho: "Web Services" support for your HiveMind services, through Caucho's hessian and burlap protocols (over http). - hiveevents: event notification service
For more information on HiveMind Utilities project: http://sourceforge.net/projects/hivetranse/
The HiveMind Utilities team
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
