uima-ee has been renamed uima-as; please change other uses as you come
across them to follow this convention.
-Marshall
Marshall Schor wrote:
OK, without further a-do, we change the name to uima-as. At some
point when I get a moment, I'll enter a Jira, assign it to me, and
rename the
OK, without further a-do, we change the name to uima-as. At some point
when I get a moment, I'll enter a Jira, assign it to me, and rename the
uimaj-ee things in SVN to uimaj-as in the sandbox. After I do that,
I'll notify everyone... by posting here again. (If some other
committer wants
Thank you Marshall. What a guy!
On Jan 23, 2008 9:06 PM, Marshall Schor [EMAIL PROTECTED] wrote:
OK, without further a-do, we change the name to uima-as. At some point
when I get a moment, I'll enter a Jira, assign it to me, and rename the
uimaj-ee things in SVN to uimaj-as in the sandbox.
+1
Jörn
On Jan 21, 2008, at 10:49 AM, Michael Baessler wrote:
+1 for changing the name to uima-as.
I think a clear and transparent name is very important that people
get interested in and work with.
It is also better and easier to integrate to the core if we decide
to move it from the
+1 for changing the name to uima-as.
I think a clear and transparent name is very important that people get
interested in and work with.
It is also better and easier to integrate to the core if we decide to
move it from the Sandbox to the core any time in the future.
-- Michael
Marshall
I also vote for changing the name to UIMA AS. No new pro/con items to
suggest, but do feel that con's #2 and #3 are pretty weak. Strength of view:
For ChangeAgainst Change
There is a new sandbox project, currently called uima-ee. Should we
change it's name?
A suggested alternative uima-as.
Some arguments pro / con changing the name
Pro:
1. uima-as goes with UIMA, Asynchronous Scaleout, and the name,
therefore, more clearly matches the functionality.
