Mailing-List: contact ctakes-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ctakes-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of Pei.Chen@childrens.harvard.edu
 designates 134.174.20.73 as permitted sender)
From: "Chen, Pei" <Pei.Chen@childrens.harvard.edu>
To: "ctakes-dev@incubator.apache.org" <ctakes-dev@incubator.apache.org>
Subject: RE: SVN source structure for Apache cTAKES?
Thread-Topic: SVN source structure for Apache cTAKES?
Thread-Index: 
 Ac1jkZoz61Ddo7rETwSP7rK7pwICMAAVBV+AAA1dAHAAVCgcgP//3t4AgAC59QD//mwHIIADghyAgAARCgCAACzMAP//9suAgAAuW6CAATZKAIACtRiA///sydA=
Date: Mon, 23 Jul 2012 15:18:35 +0000
Message-ID: <924DE05C19409B438EB81DE683A942D91D08E9@CHEXMBX1A.CHBOSTON.ORG>
References: <519746BA-628F-4408-BEBF-9847F87A48A9@colorado.edu>
 <F085F637EA9843429DA7A267BBB709A019364DBD@IMCMBX04.MITRE.ORG>
 <924DE05C19409B438EB81DE683A942D91CFC1C@CHEXMBX1A.CHBOSTON.ORG>
 <EB37FE0B-20ED-4919-9472-35561E13C842@jpl.nasa.gov>
 <07C990EDDC0F6E45841CE85E11289EB706C30231@msgebe11.mfad.mfroot.org>
 <924DE05C19409B438EB81DE683A942D91D00EC@CHEXMBX1A.CHBOSTON.ORG>
 <C2F05475-1074-447E-9DCE-C5692006D8C2@jpl.nasa.gov>
 <924DE05C19409B438EB81DE683A942D91D02D3@CHEXMBX1A.CHBOSTON.ORG>
 <D6063C70-1C38-48C4-B00B-95C642A8C692@jpl.nasa.gov>
 <500D1835.5070101@gmail.com>
In-Reply-To: <500D1835.5070101@gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi,
My apologies as we tried to be transparent as we can in the original projec=
t proposal:
- There are currently over 50 contributors/developers actively contributing=
 to cTAKES spread across over 8 sites (Mayo, BCH, Colorado University, Pitt=
sburgh, UCSD, MITRE, etc.).
- We have already communicated to developers as well as known users about t=
he move to Apache as soon as we could.  They have also been invited to the =
various ctakes-dev@ mailing lists as soon as they were created (which seems=
 to be a first logical step in also becoming contributors/committers).

If there is anything we could have clarified, please let us know. We are gr=
ateful to have such active mentors help us out here and feel free to ask us=
 any questions regarding cTAKES itself (as we may not even know enough abou=
t the Apache way to ask the right questions :) ).  I'm all for being open a=
nd transparent as much as we could.

Regarding the 2.6 release:=20
If it is okay with the group, I would strongly suggest to keep 2.6 as plann=
ed (in SF)  for now.  There were communication and expectations that went o=
ut already for it to be completed by next week. The code was already done a=
nd frozen some time ago, documentation/links was also already done some tim=
e ago as well (so there is really no duplication of effort here).
https://wiki.nci.nih.gov/display/VKC/cTAKES+2.6+-+Relation+Extractor

Note: There is a window over the next 2-3 months where there are no expecte=
d/scheduled changes the current code base which we could take advantage of.=
  All of the developers are aware of the migration; so we can make a clean =
cut from SourceForge in the code and therefore we can also have a coordinat=
ed effort amongst all of the developers.  I am confident that we will have =
many more release (probably fair frequent initially) while we are in incuba=
tion, but I think the Apache way is still a learning process for us,  let a=
lone 50 other developers.  I'll be more than happy to create a mirror/snaps=
hot of what's currently in SF and we'll begin the process.

--Pei

-----Original Message-----
From: J=F6rn Kottmann [mailto:kottmann@gmail.com]=20
Sent: Monday, July 23, 2012 5:25 AM
To: ctakes-dev@incubator.apache.org
Subject: Re: SVN source structure for Apache cTAKES?

On 07/21/2012 06:03 PM, Mattmann, Chris A (388J) wrote:
> I'm not saying that 2.6 CAN'T go out at SF.net -- I'm simply=20
> encouraging the Apache cTAKES committers (who also seem to be wearing=20
> the SF.net cTAKES hats as well) to consider making 2.6 here -- both=20
> from a community perspective, but also from a provenance one, and also fr=
om a not duplicating effort one, and finally from an Apache good will persp=
ective.

I fully agree here with Chris, also the other things he said in the earlier=
 mails.
I strongly recommend to do the 2.6 release here, in the end of the day you =
have to migrate everything over to Apache anyway, why not do it now?

Are there good reasons why 2.6 cannot wait a bit until it is released?

You will need to do releases as part of your graduation from the Incubator,=
 it would be great if you can count 2.6 as one of these.
Depending on how often you plan to release that might safe your a few month=
 of graduation time.

J=F6rn