Issue 155 in pydicom: Consider moving repos to GitHub

3 views
Skip to first unread message

pyd...@googlecode.com

unread,
Nov 9, 2014, 3:54:26 PM11/9/14
to pydic...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Difficulty-Medium

New issue 155 by agrothberg: Consider moving repos to GitHub
https://code.google.com/p/pydicom/issues/detail?id=155

Using git / GitHub allows others more flexibility in contributing source
code.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

pyd...@googlecode.com

unread,
Nov 9, 2014, 3:59:27 PM11/9/14
to pydic...@googlegroups.com

Comment #1 on issue 155 by agrothberg: Consider moving repos to GitHub
https://code.google.com/p/pydicom/issues/detail?id=155

There are various guides on the net that address making this a simple
process:
http://evennia.blogspot.com/2014/02/moving-from-google-code-to-github.html

pyd...@googlecode.com

unread,
Nov 9, 2014, 4:01:38 PM11/9/14
to pydic...@googlegroups.com
Updates:
Status: Started
Owner: Sue...@gmail.com

Comment #2 on issue 155 by Sue...@gmail.com: Consider moving repos to GitHub
https://code.google.com/p/pydicom/issues/detail?id=155

I've already begun writing and testing scripts to make the conversion over
to Github. Right now we are focused on getting the 0.9.9 release out and
will likely make the switch to Github once we have that out of the way.

pyd...@googlecode.com

unread,
Nov 9, 2014, 4:02:58 PM11/9/14
to pydic...@googlegroups.com

Comment #3 on issue 155 by agrothberg: Consider moving repos to GitHub
https://code.google.com/p/pydicom/issues/detail?id=155

Any timeline for the 0.9.9 release?

pyd...@googlecode.com

unread,
Nov 9, 2014, 4:38:24 PM11/9/14
to pydic...@googlegroups.com

Comment #4 on issue 155 by Sue...@gmail.com: Consider moving repos to GitHub
https://code.google.com/p/pydicom/issues/detail?id=155

Darcy may have a better idea of the timeline for the next release. We have
identified a number of issues that we want to tackle prior to the release.

In the meantime, the best way to make a contribution is to fork the Google
Code repository and make the change there. We can easily pull in changes
from a fork.

pyd...@googlecode.com

unread,
Nov 9, 2014, 4:39:33 PM11/9/14
to pydic...@googlegroups.com

Comment #5 on issue 155 by agrothberg: Consider moving repos to GitHub
https://code.google.com/p/pydicom/issues/detail?id=155

Right now I have fork over at: https://github.com/cancan101/pydicom with my
patches.
Reply all
Reply to author
Forward
0 new messages