I don't think it's a good idea to resurrect old software product names,
because you bring with them all the old connotations. To the extent people
know about Hivemind, they think of the product as old, out of date & dead.

Also, there were good reasons why Tapestry-IOC was not treated as a
distinct project. As our docs say: "The difficulty of managing the release
schedules of two complex frameworks proved to be an issue."
On Jul 21, 2014 3:22 AM, "Jochen Kemnade" <jochen.kemn...@eddyson.de> wrote:

> Hi,
>
> Am 19.07.2014 10:02, schrieb Lance Java:
>
>> I think having tapestry-ioc and tapestry (the web framework) is a bit
>> confusing. I also feel that it hinders the promotion / adoption of
>> tapestry-ioc as a standalone product.
>>
>
> I see your point. I don't really have a strong opinion about that matter,
> but here we go.
>
>  1. Do you agree that tapestry-ioc should be renamed?
>>
>
> No. That's in terms of "should", not "could". I'm not against a rename, I
> just don't think it's necessary.
>
>  2. Do you think it should be called hivemind?
>>
>
> No. I also think that the name hivemind is taken and we shouldn't
> resurrect it. People would probably start to dig out old documentation and
> mailing list threads.
>
>  3. Do you have an alternative name?
>>
>
> What about something with a relation to the word "tapestry"? Something
> like cotton, cloth, fabric (hm, I like that one, but there's at least
> http://www.fabfile.org/ and http://dev.mysql.com/downloads/fabric/).
>
>  4. Should a rename be done as part of 5.4 or 5.5?
>>
>
> I assume that's an XOR. ;-) I guess it depends on how thorough we want the
> change to be. Do we also want to rename all the packages and classes with
> "IOC" in them? Then we'd probably even have to wait for 6.0. If it's just
> the name and the documentation, I think we could do it for 5.4.
>
> Jochen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: dev-h...@tapestry.apache.org
>
>

Reply via email to