You can also sign up for github and make a fork of the ParaView repository that is located here: http://github.com/Kitware/ParaView/tree/cvshead
Or create your own project external to paraview, github offers a nice 'download' button. And some getting started guides- http://github.com/guides/home Pat On Wed, Aug 12, 2009 at 8:47 AM, Karthik Krishnan<[email protected]> wrote: > On Wed, Aug 12, 2009 at 7:47 AM, David Doria <[email protected]> > wrote: >> >> On Tue, Aug 11, 2009 at 1:52 PM, David Doria <[email protected]> >> wrote: >> >> The new code is here: >> http://www.rpi.edu/~doriad/VTK_List/vtkLidarScanner.zip >> >> Is there a vtk sandbox or something that I can work in instead of mailing >> the file to the list each update? Do I need to email the devel list to get >> access/code reviews/ etc? > > you can do one or both of two things. > > 1. Attach these things as a feature request on the VTK/paraview bug tracker. > 2. Use the Insight-journal system to upload your code along with > documentation. Revisions can be maintained there. > > > > _______________________________________________ > Powered by 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 VTK FAQ at: > http://www.vtk.org/Wiki/VTK_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.vtk.org/mailman/listinfo/vtkusers > > _______________________________________________ Powered by 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 ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
