[Insight-developers] Image memory model
Stephen Aylward
stephen.aylward at kitware.com
Mon Jul 6 11:12:56 EDT 2009
Hi,
Great idea!
The IJ does have an associated SVN (cvs?) system, but perhaps it isn't well
documented / supported / integrated.
Julien - any suggestions / ideas on how this can be done?
Stephen
On Mon, Jul 6, 2009 at 11:02 AM, Luis Ibanez <luis.ibanez at kitware.com>wrote:
> The Insight Jounal is not the most convenient revision control
> system for code. If you make a fix to Dan's code, you will
> have to package the source code again in a .zip file and
> upload it to the IJ server. That's a very inconvenient way
> of managing source code modifications.
>
>
> It is common practice for us, that when we are about to move
> an Insight Journal contribution from the Insight Journal into
> the Code Review directory, we contact the authors and ask for
> the most recent version.
>
>
> One way to avoid this would be to have a Insight Journal
> Sandbox SVN repository, where all ITK developers as well
> as the paper author can have write access.
>
>
>
>
> Luis
>
>
>
> ---------------------
> Stephen Aylward wrote:
>
>> If this is being discussed on the Insight-Developers' mailing list,
>> and if this is generally useful to the community,
>> then shouldn't this go into the Insight Journal as an avenue for moving
>> into ITK proper?
>>
>> Basically, I disagree with the statement
>> "keep the code updated in the NAMIC sandbox. It makes a lot easier for
>> everybody to access the code"
>>
>> If there is a shortcoming in the InsightJournal, then it should be
>> addressed rather than sending the Insight community to other sites.
>>
>> Stephen
>>
>> On Mon, Jul 6, 2009 at 2:56 AM, Dan Mueller <dan.muel at gmail.com <mailto:
>> dan.muel at gmail.com>> wrote:
>>
>> Hi Luis,
>>
>> My NAMIC username/password no longer seems to be valid (or I have
>> forgotten the details). Who do I contact to reset this?
>>
>> Regards, Dan
>>
>> 2009/7/5 Luis Ibanez <luis.ibanez at kitware.com
>> <mailto:luis.ibanez at kitware.com>>:
>> >
>> > Hi Dan,
>> >
>> > I would suggest to keep the code updated in the NAMIC sandbox.
>> > It makes a lot easier for everybody to access the code and
>> > commit improvements.
>> >
>> >
>> >
>> > BTW: This memory model is a great contribution to ITK.
>> > We should keep it in the list of features for ITK 4.0.
>> >
>> >
>> >
>> > Luis
>> >
>> >
>> >
>> > -------------------
>> > Dan Mueller wrote:
>> >>
>> >> Hi all,
>> >>
>> >> Wow, time flies when your having fun. I started this email
>> thread over
>> >> one year ago, but only now got to finishing everything off.
>> >>
>> >> I have just submitted an article to the Insight Journal with my
>> first
>> >> attempt at implementing some alternative memory models. The URL
>> is not
>> >> yet active, but once the submission is approved, it should live
>> here:
>> >> http://hdl.handle.net/1926/3068
>> >>
>> >> Question: should I update the NAMIC sandbox with my
>> implementation, or
>> >> just keep everything in the journal?
>> >>
>> >> Cheers, Dan
>> _______________________________________________
>> Powered by www.kitware.com <http://www.kitware.com>
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ITK FAQ at:
>> http://www.itk.org/Wiki/ITK_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.itk.org/mailman/listinfo/insight-developers
>>
>>
>>
>>
>> --
>> Stephen R. Aylward, Ph.D.
>> Director of Medical Imaging
>> Kitware, Inc. - North Carolina Office
>> http://www.kitware.com
>> (518) 371-3971 x300 (NY Line)
>> (919) 969-6990 x300 (NC Line)
>> stephen.aylward (Skype)
>>
>
--
Stephen R. Aylward, Ph.D.
Director of Medical Imaging
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(518) 371-3971 x300 (NY Line)
(919) 969-6990 x300 (NC Line)
stephen.aylward (Skype)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/mailman/private/insight-developers/attachments/20090706/8ba58342/attachment.htm>
More information about the Insight-developers
mailing list