Hi Benjamin, I don't know why the issues section is not present. We still have our jira area active, but it would be really nice to have as much 'one stop shopping' available as possible.
I will contact the Apache Infra team and see if I can get that feature up and running. Thanks for bringing this to our attention, Sean ________________________________ From: Benjamin hansen <benjaminkakke...@gmail.com> Sent: Saturday, December 31, 2022 5:04 PM To: dev@ctakes.apache.org <dev@ctakes.apache.org> Cc: u...@ctakes.apache.org <u...@ctakes.apache.org> Subject: Re: Apache cTAKES is now on GitHub ! [EXTERNAL] * External Email - Caution * Hi, this looks great. Awesome work. May I ask - is there any reason why the issues section in the new github repo has been deactivated? In my experience this is a great place to discuss issues and ask for help. It could be a good way to make the community a bit more active :) Thanks On Fri, Dec 30, 2022 at 7:49 PM Finan, Sean <sean.fi...@childrens.harvard.edu.invalid> wrote: > Hi all, > > I am pleased to announce that the cTAKES source code is now on GitHub at > https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!viVqLaCzQSb4zvpoyBsm2nLGuaXgzH7AX2s7CZsmYFCa1exu0w6KH9QGlTxxKQdsuv2Rgrmw-zTFAXtqwY2esVP3dgOuH1xuMprPYA$ > [ > https://urldefense.com/v3/__https://opengraph.githubassets.com/fcab5fb05ec83aeb556ec2e939a856d20cfb4d9684aa13253c82cc7370f1c9cd/apache/ctakes__;!!NZvER7FxgEiBAiR_!viVqLaCzQSb4zvpoyBsm2nLGuaXgzH7AX2s7CZsmYFCa1exu0w6KH9QGlTxxKQdsuv2Rgrmw-zTFAXtqwY2esVP3dgOuH1wQLpXfKg$ > ]<https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!viVqLaCzQSb4zvpoyBsm2nLGuaXgzH7AX2s7CZsmYFCa1exu0w6KH9QGlTxxKQdsuv2Rgrmw-zTFAXtqwY2esVP3dgOuH1xuMprPYA$ > > > GitHub - apache/ctakes: Apache > ctakes<https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!viVqLaCzQSb4zvpoyBsm2nLGuaXgzH7AX2s7CZsmYFCa1exu0w6KH9QGlTxxKQdsuv2Rgrmw-zTFAXtqwY2esVP3dgOuH1xuMprPYA$ > > > Apache ctakes. Contribute to apache/ctakes development by creating an > account on GitHub. > github.com > > > > > > > > > All current and future code development should be performed on the source > in GitHub. > > > Changes ( vs. Subversion Repository ) > ========================================= > > * VERSION: The project in GitHub has been versioned 5.0.0-SNAPSHOT. > * STRUCTURE: The project has been slightly restructured at a high > level. The typical user should not notice the difference. > * CODE API: All package, class, method and constant names remain the > same, so your code should not need to be refactored. > * DEPENDENCIES: If you include cTAKES modules as dependencies in > your maven project, you can simply change the version to obtain new > 5.0.0-SNAPSHOT builds. * > * BINARY PACKAGE: The binary package has some minor differences, but > the typical user should not notice them. > > * If you use maven dependency exclusions for resource ('-res') modules > because of unwanted ML models, you need to change the excluded name > extension from '-res' to '-model'. > > > Moving forward from the Subversion Repository > ============================================= > > * VERSION: The project in the SVN repository was versioned > 4.0.1-SNAPSHOT. > * DEPRECATION: The code and resources in the 4.0.1-SNAPSHOT > Subversion (SVN) repository will remain available for checkout, but should > be considered read-only. 4.0.1-SNAPSHOT built modules will remain > available for maven dependencies. All current and future code development > should be performed on the source in GitHub. > * RELEASE: There is no cTAKES 4.0.1 release. > > Next Anticipated Release > ======================== > > * VERSION: As you might guess from the snapshot version change, we > are gearing up for a version 5.0.0 release. > * WHY 5.0.0: There are so many new features over cTAKES 4.0.0, > including completely new modules, that the version number was bumped up. > * DOCUMENTATION: All of the new toys will be documented in the > confluence wiki at the time of the 5.0.0 release. > * DATE: There is no release date yet, but hopefully it will be very > very soon ... > > Happy New Year, > > Sean > > >
