pgdad / canviz

Automatically exported from code.google.com/p/canviz
0 stars 0 forks source link

Move to GitHub? #74

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Would love to be able to contribute to this project much more easily, and Pull 
Requests would be an awesome way to do that.

Happy to help if desired!

Original issue reported on code.google.com by m3mo...@gmail.com on 31 Jan 2014 at 4:19

GoogleCodeExporter commented 9 years ago
I do prefer the Github issue tracker and web interface in general, but I have 
only dabbled very little in actually using git and am not comfortable with it. 
On the other hand I've used Subversion for a decade and I'm very comfortable 
with it. I'm aware Github lets you access a Git repository as if it were a 
Subversion repository, and that may be an intermediate solution I could explore 
at some point, however right now moving to Github would take time and would not 
provide me with much benefit that I can see, and there's no problem with 
keeping the project at Google Code, so that's where it's staying until I get 
motivated otherwise.

If you have proposed changes to Canviz, please discuss them on the discussion 
group first.

Original comment by ryandesi...@gmail.com on 2 Feb 2014 at 10:15

GoogleCodeExporter commented 9 years ago
FYI -- we created a github fork and added some updates we wanted.  
https://github.com/Spark-Innovations/canviz

Original comment by m3mo...@gmail.com on 25 Apr 2014 at 11:40

GoogleCodeExporter commented 9 years ago
Given Google's announcement yesterday that Google Code is shutting down later 
this year, I'll be revisiting this matter in the coming months. Google offers a 
migration tool, but the complication is that the canviz Subversion repository 
currently contains two projects, canviz and path, and also copies of some 
third-party libraries. I will want canviz and path to become separate git 
repositories at GitHub, ideally with all of their history. I will have to see 
if I can use svndumptool to separate the two projects into two Subversion 
repositories before importing to GitHub.

Original comment by ryandesi...@gmail.com on 13 Mar 2015 at 5:02