You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org> on 2012/09/11 16:57:08 UTC
[jira] [Created] (UIMA-2470) Donation of uimaFIT
Richard Eckart de Castilho created UIMA-2470:
------------------------------------------------
Summary: Donation of uimaFIT
Key: UIMA-2470
URL: https://issues.apache.org/jira/browse/UIMA-2470
Project: UIMA
Issue Type: Task
Components: Sandbox
Reporter: Richard Eckart de Castilho
Donation of uimaFIT.
uimaFIT provides Java annotations for describing UIMA components which can be used to directly describe the UIMA components in Java code without the need for traditional UIMA XML descriptors. This greatly simplifies refactoring a component definition (e.g., changing a configuration parameter name). uimaFIT also makes it easy to instantiate UIMA components without using XML descriptor files by providing convenient factory methods. This makes uimaFIT an ideal library for testing UIMA components because the component can be easily instantiated and invoked without requiring a descriptor file to be created first. uimaFIT is very useful in research environments in which programmatic/dynamic instantiation of UIMA pipelines can simplify experimentation. For example, when performing 10-fold cross-validation across a number of experimental conditions, it can be quite laborious to create a different set of descriptor files for each run, or even a script which generates such descriptor files. uimaFIT is type system agnostic and does not depend on (or provide) a specific type system.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (UIMA-2470) Donation of uimaFIT
Posted by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477254#comment-13477254 ]
Richard Eckart de Castilho commented on UIMA-2470:
--------------------------------------------------
Thanks for your comments. Unfortunately I was delayed with progress on this issue due to a broken mainboard.
I'd tend to agree with Joern that the changes should be done after adding the code to the Apache repository. In that way the full transition history is available in the SVN. I can provide the necessary patches then - it would a good opportunity to get into the habit too.
I also had a quick poke at what changing the package names from org.uimafit to org.apache.uima.uimafit - it's quite a major change after which several test cases need to be revised. I'm also thinking how some backwards-compatibility-layer could be introduced after such renaming, so that an Apache uimaFIT can in some places make use of the current uimaFIT 1.4.0 annotations.
> Donation of uimaFIT
> -------------------
>
> Key: UIMA-2470
> URL: https://issues.apache.org/jira/browse/UIMA-2470
> Project: UIMA
> Issue Type: Task
> Components: Sandbox
> Reporter: Richard Eckart de Castilho
>
> Donation of uimaFIT.
> uimaFIT provides Java annotations for describing UIMA components which can be used to directly describe the UIMA components in Java code without the need for traditional UIMA XML descriptors. This greatly simplifies refactoring a component definition (e.g., changing a configuration parameter name). uimaFIT also makes it easy to instantiate UIMA components without using XML descriptor files by providing convenient factory methods. This makes uimaFIT an ideal library for testing UIMA components because the component can be easily instantiated and invoked without requiring a descriptor file to be created first. uimaFIT is very useful in research environments in which programmatic/dynamic instantiation of UIMA pipelines can simplify experimentation. For example, when performing 10-fold cross-validation across a number of experimental conditions, it can be quite laborious to create a different set of descriptor files for each run, or even a script which generates such descriptor files. uimaFIT is type system agnostic and does not depend on (or provide) a specific type system.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (UIMA-2470) Donation of uimaFIT
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453501#comment-13453501 ]
Marshall Schor commented on UIMA-2470:
--------------------------------------
I took a look at the zip file. I do not think there are any showstoppers. I think some changes may be needed when coming into the UIMA project, but these can be done either ahead of time, or by working on the code here. Because some of these are pervasive, it may be best to do them before putting the code into Apache. The most major one is the maven "group-id" - which is currently "org.uimafit". In our project, I believe we only are setup within Apache to upload artifacts using the group id "org.apache.uima". Other, more minor changes, are not strictly required, but encouraged (to support the Apache Way of working); these include removing @author tags, and removing copyright statements at the top of every file (these can be moved to the notice file if the copyright owners want to preserve this information - for instance, the UIMA notice file for somethings include the phrase "Portions of UIMA were originally developed by
International Business Machines Corporation and are licensed to the Apache Software Foundation under the "Software Grant License Agreement", informally known as the
"IBM UIMA License Agreement". Copyright (c) 2003, 2006 IBM Corporation.
Also, you may of course delete Mac-specific files, like .DS_Store :-)
I encourage other UIMA committers to also take a quick look!
> Donation of uimaFIT
> -------------------
>
> Key: UIMA-2470
> URL: https://issues.apache.org/jira/browse/UIMA-2470
> Project: UIMA
> Issue Type: Task
> Components: Sandbox
> Reporter: Richard Eckart de Castilho
>
> Donation of uimaFIT.
> uimaFIT provides Java annotations for describing UIMA components which can be used to directly describe the UIMA components in Java code without the need for traditional UIMA XML descriptors. This greatly simplifies refactoring a component definition (e.g., changing a configuration parameter name). uimaFIT also makes it easy to instantiate UIMA components without using XML descriptor files by providing convenient factory methods. This makes uimaFIT an ideal library for testing UIMA components because the component can be easily instantiated and invoked without requiring a descriptor file to be created first. uimaFIT is very useful in research environments in which programmatic/dynamic instantiation of UIMA pipelines can simplify experimentation. For example, when performing 10-fold cross-validation across a number of experimental conditions, it can be quite laborious to create a different set of descriptor files for each run, or even a script which generates such descriptor files. uimaFIT is type system agnostic and does not depend on (or provide) a specific type system.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (UIMA-2470) Donation of uimaFIT
Posted by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453086#comment-13453086 ]
Richard Eckart de Castilho commented on UIMA-2470:
--------------------------------------------------
A code drop package has been prepared at
http://code.google.com/p/uimafit/downloads/detail?name=uimaFIT-grant-staging-rev-919.zip
We are now waiting for an OK from the UIMA team regarding the contribution package format. If the format of the package is accepted by the UIMA team, we'll create the corresponding paperwork, otherwise we will create a new package respecting the feedback form the UIMA team.
Since the CLA and SGA documents need to include a hash to clearly identify the code drop package and since multiple parties are involved in the process, we believe this is the logistically most viable procedure.
> Donation of uimaFIT
> -------------------
>
> Key: UIMA-2470
> URL: https://issues.apache.org/jira/browse/UIMA-2470
> Project: UIMA
> Issue Type: Task
> Components: Sandbox
> Reporter: Richard Eckart de Castilho
>
> Donation of uimaFIT.
> uimaFIT provides Java annotations for describing UIMA components which can be used to directly describe the UIMA components in Java code without the need for traditional UIMA XML descriptors. This greatly simplifies refactoring a component definition (e.g., changing a configuration parameter name). uimaFIT also makes it easy to instantiate UIMA components without using XML descriptor files by providing convenient factory methods. This makes uimaFIT an ideal library for testing UIMA components because the component can be easily instantiated and invoked without requiring a descriptor file to be created first. uimaFIT is very useful in research environments in which programmatic/dynamic instantiation of UIMA pipelines can simplify experimentation. For example, when performing 10-fold cross-validation across a number of experimental conditions, it can be quite laborious to create a different set of descriptor files for each run, or even a script which generates such descriptor files. uimaFIT is type system agnostic and does not depend on (or provide) a specific type system.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (UIMA-2470) Donation of uimaFIT
Posted by "Tommaso Teofili (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453800#comment-13453800 ]
Tommaso Teofili commented on UIMA-2470:
---------------------------------------
I've also had a look at it and I agree with Marshall that the important thing which may be worth fix before committing the code under ASF svn are changing the groupId and (if possible) move the copyright notice in the NOTICE file while putting the Apache License header on top of the other files.
This last thing is, as far as I know, not strictly required but it's usually better since otherwise users / adopters happen to wonder about legal issues with the code with regard to the copyright owner or similar concerns.
Another minor thing would be fixing the code formatting, we usually have 2 spaces indent (see guidelines at http://uima.apache.org/codeConventions.html)
> Donation of uimaFIT
> -------------------
>
> Key: UIMA-2470
> URL: https://issues.apache.org/jira/browse/UIMA-2470
> Project: UIMA
> Issue Type: Task
> Components: Sandbox
> Reporter: Richard Eckart de Castilho
>
> Donation of uimaFIT.
> uimaFIT provides Java annotations for describing UIMA components which can be used to directly describe the UIMA components in Java code without the need for traditional UIMA XML descriptors. This greatly simplifies refactoring a component definition (e.g., changing a configuration parameter name). uimaFIT also makes it easy to instantiate UIMA components without using XML descriptor files by providing convenient factory methods. This makes uimaFIT an ideal library for testing UIMA components because the component can be easily instantiated and invoked without requiring a descriptor file to be created first. uimaFIT is very useful in research environments in which programmatic/dynamic instantiation of UIMA pipelines can simplify experimentation. For example, when performing 10-fold cross-validation across a number of experimental conditions, it can be quite laborious to create a different set of descriptor files for each run, or even a script which generates such descriptor files. uimaFIT is type system agnostic and does not depend on (or provide) a specific type system.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (UIMA-2470) Donation of uimaFIT
Posted by "Joern Kottmann (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453820#comment-13453820 ]
Joern Kottmann commented on UIMA-2470:
--------------------------------------
+1 to import it as it is. In my opinion all the work which needs to be done to get it into a release able state is best done in our repository.
> Donation of uimaFIT
> -------------------
>
> Key: UIMA-2470
> URL: https://issues.apache.org/jira/browse/UIMA-2470
> Project: UIMA
> Issue Type: Task
> Components: Sandbox
> Reporter: Richard Eckart de Castilho
>
> Donation of uimaFIT.
> uimaFIT provides Java annotations for describing UIMA components which can be used to directly describe the UIMA components in Java code without the need for traditional UIMA XML descriptors. This greatly simplifies refactoring a component definition (e.g., changing a configuration parameter name). uimaFIT also makes it easy to instantiate UIMA components without using XML descriptor files by providing convenient factory methods. This makes uimaFIT an ideal library for testing UIMA components because the component can be easily instantiated and invoked without requiring a descriptor file to be created first. uimaFIT is very useful in research environments in which programmatic/dynamic instantiation of UIMA pipelines can simplify experimentation. For example, when performing 10-fold cross-validation across a number of experimental conditions, it can be quite laborious to create a different set of descriptor files for each run, or even a script which generates such descriptor files. uimaFIT is type system agnostic and does not depend on (or provide) a specific type system.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira