You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ctakes.apache.org by Jörn Kottmann <ko...@gmail.com> on 2012/09/11 11:36:16 UTC
Re: INFRA-5079 (cTAKES svn import)
Did you hear anything regarding this? Otherwise we either
proceed with #1/#2 or by now we can also ping the infra guys.
Jörn
On 08/30/2012 05:15 PM, Mattmann, Chris A (388J) wrote:
> Hi Guys,
>
> +1 to option #3 as well, with a deadline of say early next week. If it's not done by
> early next week, #1 or #2 sound fine.
>
> Cheers,
> Chris
>
> On Aug 30, 2012, at 8:11 AM, Jörn Kottmann wrote:
>
>> +1 to do alternative 3 for a while. The last mail which said they
>> do it Wednesday sounded to me like it will happen really soon.
>>
>> Jörn
>>
>>
>> On 08/30/2012 04:57 PM, Chen, Pei wrote:
>>> Hi cTAKES Mentors,
>>> The request to perform the svn import is taking longer than anticipated (It's been some time now with several follow up's with infra, but still no luck)...
>>> Any suggestions here to move the incubation process along?
>>>
>>> Throwing out some alternatives:
>>> 1) Do we really need the full revision history from SF on Apache? It would be nice, but don't want to wait indefinitely to begin coding either.
>>> 2) We start development on the apache svn. Ask infra if it's possible to preserve this folder when they perform the import, and we perform a merge any time after the import. This would mean developers would have to configure their workspace multiple times and we'll need to figure out the merges.
>>> 3) Continue waiting for infra.
>>>
>>> Open to ideas...
>>> Thanks,
>>> Pei
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
RE: INFRA-5079 (cTAKES svn import)
Posted by "Masanz, James J." <Ma...@mayo.edu>.
I did put in our report to the board that this is holding us up.
But the board report isn't until Wed, 19th
> -----Original Message-----
> From: ctakes-dev-return-375-Masanz.James=mayo.edu@incubator.apache.org
>
[mailto:ctakes-dev-return-375-Masanz.James=mayo.edu@incubator.apache.org
]
> On Behalf Of Coarr, Matt
> Sent: Wednesday, September 12, 2012 9:57 AM
> To: ctakes-dev@incubator.apache.org
> Subject: Re: INFRA-5079 (cTAKES svn import)
>
> -1
>
> I think it is really important to keep the history of our svn
repository.
> We have a very diverse development team with a lot of projects working
> together and being able to see logs and diffs over time is a huge help
> when developing and refactoring.
>
> Is there any one else in infra we can talk to? Or can we get
temporary
> privileges to do the import ourselves?
>
> My $.02
>
> Matt
>
>
> On 2012-09-12 10:49 , "Masanz, James J." <Ma...@mayo.edu>
wrote:
>
> >+1 on closing infra-5079 and using what's in apache SVN
> >(and using SF.net if we want to look at history)
> >
> >Regards,
> >James Masanz
RE: INFRA-5079 (cTAKES svn import)
Posted by "Finan, Sean" <Se...@childrens.harvard.edu>.
-1
If at all possible I'd like to keep a "usable" history of changes (a text dump of commit notes is not much help).
One reason: as a new contributor to cTakes, I would like to have a history available if I make a change to existing code that has unexpected results - so that I can see if a previous similar change had the same problem. (expounds what Matt already wrote).
-----Original Message-----
From: Steven Bethard [mailto:steven.bethard@Colorado.EDU]
Sent: Wednesday, September 12, 2012 11:04 AM
To: ctakes-dev@incubator.apache.org
Subject: Re: INFRA-5079 (cTAKES svn import)
I'm also -1 on losing history unless we really have to.
Steve
On 12 Sep 2012, at 16:56 , Coarr, Matt wrote:
> -1
>
> I think it is really important to keep the history of our svn repository.
> We have a very diverse development team with a lot of projects working
> together and being able to see logs and diffs over time is a huge help
> when developing and refactoring.
>
> Is there any one else in infra we can talk to? Or can we get
> temporary privileges to do the import ourselves?
>
> My $.02
>
> Matt
>
>
> On 2012-09-12 10:49 , "Masanz, James J." <Ma...@mayo.edu> wrote:
>
>> +1 on closing infra-5079 and using what's in apache SVN
>> (and using SF.net if we want to look at history)
>>
>> Regards,
>> James Masanz
>
Re: INFRA-5079 (cTAKES svn import)
Posted by Steven Bethard <st...@Colorado.EDU>.
I'm also -1 on losing history unless we really have to.
Steve
On 12 Sep 2012, at 16:56 , Coarr, Matt wrote:
> -1
>
> I think it is really important to keep the history of our svn repository.
> We have a very diverse development team with a lot of projects working
> together and being able to see logs and diffs over time is a huge help
> when developing and refactoring.
>
> Is there any one else in infra we can talk to? Or can we get temporary
> privileges to do the import ourselves?
>
> My $.02
>
> Matt
>
>
> On 2012-09-12 10:49 , "Masanz, James J." <Ma...@mayo.edu> wrote:
>
>> +1 on closing infra-5079 and using what's in apache SVN
>> (and using SF.net if we want to look at history)
>>
>> Regards,
>> James Masanz
>
Re: INFRA-5079 (cTAKES svn import)
Posted by "Coarr, Matt" <mc...@mitre.org>.
-1
I think it is really important to keep the history of our svn repository.
We have a very diverse development team with a lot of projects working
together and being able to see logs and diffs over time is a huge help
when developing and refactoring.
Is there any one else in infra we can talk to? Or can we get temporary
privileges to do the import ourselves?
My $.02
Matt
On 2012-09-12 10:49 , "Masanz, James J." <Ma...@mayo.edu> wrote:
>+1 on closing infra-5079 and using what's in apache SVN
>(and using SF.net if we want to look at history)
>
>Regards,
>James Masanz
RE: INFRA-5079 (cTAKES svn import)
Posted by "Masanz, James J." <Ma...@mayo.edu>.
+1 on closing infra-5079 and using what's in apache SVN
(and using SF.net if we want to look at history)
Regards,
James Masanz
> -----Original Message-----
> From: ctakes-dev-return-373-Masanz.James=mayo.edu@incubator.apache.org
> [mailto:ctakes-dev-return-373-Masanz.James=mayo.edu@incubator.apache.org]
> On Behalf Of Chen, Pei
> Sent: Wednesday, September 12, 2012 9:45 AM
> To: ctakes-dev@incubator.apache.org
> Subject: RE: INFRA-5079 (cTAKES svn import)
>
> Yes Jörn. Since we already have the latest export of the code already in
> the current Apache SVN, I would prefer with #1 mainly for simplicity. It
> may not be so straightforward to merge code/fixes especially once we start
> renaming project folders and namespaces. If others are okay with it, we
> can ask to close the infra-5079 jira and move forward with the latest svn
> codebase sans the old revision history; for the unlikely chance we may
> need the history, we can go to SF files or the dump file.
>
> --Pei
>
> > -----Original Message-----
> > From: Jörn Kottmann [mailto:kottmann@gmail.com]
> > Sent: Wednesday, September 12, 2012 10:13 AM
> > To: ctakes-dev@incubator.apache.org
> > Subject: Re: INFRA-5079 (cTAKES svn import)
> >
> > There is already a ping on the issue from the 7th September, but there
> > was no reply since then.
> >
> > Jörn
> >
> > On 09/11/2012 11:36 AM, Jörn Kottmann wrote:
> > > Did you hear anything regarding this? Otherwise we either proceed
> > > with
> > > #1/#2 or by now we can also ping the infra guys.
> > >
> > > Jörn
> > >
> > > On 08/30/2012 05:15 PM, Mattmann, Chris A (388J) wrote:
> > >> Hi Guys,
> > >>
> > >> +1 to option #3 as well, with a deadline of say early next week. If
> > >> it's not done by
> > >> early next week, #1 or #2 sound fine.
> > >>
> > >> Cheers,
> > >> Chris
> > >>
> > >> On Aug 30, 2012, at 8:11 AM, Jörn Kottmann wrote:
> > >>
> > >>> +1 to do alternative 3 for a while. The last mail which said they
> > >>> do it Wednesday sounded to me like it will happen really soon.
> > >>>
> > >>> Jörn
> > >>>
> > >>>
> > >>> On 08/30/2012 04:57 PM, Chen, Pei wrote:
> > >>>> Hi cTAKES Mentors,
> > >>>> The request to perform the svn import is taking longer than
> > >>>> anticipated (It's been some time now with several follow up's
> > >>>> with infra, but still no luck)...
> > >>>> Any suggestions here to move the incubation process along?
> > >>>>
> > >>>> Throwing out some alternatives:
> > >>>> 1) Do we really need the full revision history from SF on Apache?
> > >>>> It would be nice, but don't want to wait indefinitely to begin
> > >>>> coding either.
> > >>>> 2) We start development on the apache svn. Ask infra if it's
> > >>>> possible to preserve this folder when they perform the import,
> > >>>> and we perform a merge any time after the import. This would mean
> > >>>> developers would have to configure their workspace multiple times
> > >>>> and we'll need to figure out the merges.
> > >>>> 3) Continue waiting for infra.
> > >>>>
> > >>>> Open to ideas...
> > >>>> Thanks,
> > >>>> Pei
> > >>
> > >>
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > ++++++++
> > >> Chris Mattmann, Ph.D.
> > >> Senior Computer Scientist
> > >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > >> Office: 171-266B, Mailstop: 171-246
> > >> Email: chris.a.mattmann@nasa.gov
> > >> WWW: http://sunset.usc.edu/~mattmann/
> > >>
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > ++++++++
> > >> Adjunct Assistant Professor, Computer Science Department University
> > >> of Southern California, Los Angeles, CA 90089 USA
> > >>
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > ++++++++
> > >>
> > >
RE: INFRA-5079 (cTAKES svn import)
Posted by "Chen, Pei" <Pe...@childrens.harvard.edu>.
Yes Jörn. Since we already have the latest export of the code already in the current Apache SVN, I would prefer with #1 mainly for simplicity. It may not be so straightforward to merge code/fixes especially once we start renaming project folders and namespaces. If others are okay with it, we can ask to close the infra-5079 jira and move forward with the latest svn codebase sans the old revision history; for the unlikely chance we may need the history, we can go to SF files or the dump file.
--Pei
> -----Original Message-----
> From: Jörn Kottmann [mailto:kottmann@gmail.com]
> Sent: Wednesday, September 12, 2012 10:13 AM
> To: ctakes-dev@incubator.apache.org
> Subject: Re: INFRA-5079 (cTAKES svn import)
>
> There is already a ping on the issue from the 7th September, but there was
> no reply since then.
>
> Jörn
>
> On 09/11/2012 11:36 AM, Jörn Kottmann wrote:
> > Did you hear anything regarding this? Otherwise we either proceed with
> > #1/#2 or by now we can also ping the infra guys.
> >
> > Jörn
> >
> > On 08/30/2012 05:15 PM, Mattmann, Chris A (388J) wrote:
> >> Hi Guys,
> >>
> >> +1 to option #3 as well, with a deadline of say early next week. If
> >> it's not done by
> >> early next week, #1 or #2 sound fine.
> >>
> >> Cheers,
> >> Chris
> >>
> >> On Aug 30, 2012, at 8:11 AM, Jörn Kottmann wrote:
> >>
> >>> +1 to do alternative 3 for a while. The last mail which said they
> >>> do it Wednesday sounded to me like it will happen really soon.
> >>>
> >>> Jörn
> >>>
> >>>
> >>> On 08/30/2012 04:57 PM, Chen, Pei wrote:
> >>>> Hi cTAKES Mentors,
> >>>> The request to perform the svn import is taking longer than
> >>>> anticipated (It's been some time now with several follow up's with
> >>>> infra, but still no luck)...
> >>>> Any suggestions here to move the incubation process along?
> >>>>
> >>>> Throwing out some alternatives:
> >>>> 1) Do we really need the full revision history from SF on Apache?
> >>>> It would be nice, but don't want to wait indefinitely to begin
> >>>> coding either.
> >>>> 2) We start development on the apache svn. Ask infra if it's
> >>>> possible to preserve this folder when they perform the import, and
> >>>> we perform a merge any time after the import. This would mean
> >>>> developers would have to configure their workspace multiple times
> >>>> and we'll need to figure out the merges.
> >>>> 3) Continue waiting for infra.
> >>>>
> >>>> Open to ideas...
> >>>> Thanks,
> >>>> Pei
> >>
> >>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ++++++++
> >> Chris Mattmann, Ph.D.
> >> Senior Computer Scientist
> >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >> Office: 171-266B, Mailstop: 171-246
> >> Email: chris.a.mattmann@nasa.gov
> >> WWW: http://sunset.usc.edu/~mattmann/
> >>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ++++++++
> >> Adjunct Assistant Professor, Computer Science Department University
> >> of Southern California, Los Angeles, CA 90089 USA
> >>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ++++++++
> >>
> >
Re: INFRA-5079 (cTAKES svn import)
Posted by Jörn Kottmann <ko...@gmail.com>.
There is already a ping on the issue from the 7th September,
but there was no reply since then.
Jörn
On 09/11/2012 11:36 AM, Jörn Kottmann wrote:
> Did you hear anything regarding this? Otherwise we either
> proceed with #1/#2 or by now we can also ping the infra guys.
>
> Jörn
>
> On 08/30/2012 05:15 PM, Mattmann, Chris A (388J) wrote:
>> Hi Guys,
>>
>> +1 to option #3 as well, with a deadline of say early next week. If
>> it's not done by
>> early next week, #1 or #2 sound fine.
>>
>> Cheers,
>> Chris
>>
>> On Aug 30, 2012, at 8:11 AM, Jörn Kottmann wrote:
>>
>>> +1 to do alternative 3 for a while. The last mail which said they
>>> do it Wednesday sounded to me like it will happen really soon.
>>>
>>> Jörn
>>>
>>>
>>> On 08/30/2012 04:57 PM, Chen, Pei wrote:
>>>> Hi cTAKES Mentors,
>>>> The request to perform the svn import is taking longer than
>>>> anticipated (It's been some time now with several follow up's with
>>>> infra, but still no luck)...
>>>> Any suggestions here to move the incubation process along?
>>>>
>>>> Throwing out some alternatives:
>>>> 1) Do we really need the full revision history from SF on Apache?
>>>> It would be nice, but don't want to wait indefinitely to begin
>>>> coding either.
>>>> 2) We start development on the apache svn. Ask infra if it's
>>>> possible to preserve this folder when they perform the import, and
>>>> we perform a merge any time after the import. This would mean
>>>> developers would have to configure their workspace multiple times
>>>> and we'll need to figure out the merges.
>>>> 3) Continue waiting for infra.
>>>>
>>>> Open to ideas...
>>>> Thanks,
>>>> Pei
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW: http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>