On 20/01/15 23:11, Tristam MacDonald wrote:
I know we've debated this to death at this point, but it seems to me
that in the past the consensus has typically been that GitHub would be
preferable to bitbucket.
Personally, the largest barrier to my contributing further to pyglet
is having to dust off my mercurial reference materials whenever I need
to generate a patch...
- Tristam
On Tue, Jan 20, 2015 at 17:36, Ben Albrecht <[email protected]
<mailto:[email protected]>> wrote:
Here's two nice articles that detail the hurdles to overcome when
migrating Google Code to GitHub:
(1) <http://beets.radbox.org/blog/github-issues.html>
(2)
<http://evennia.blogspot.com/2014/02/moving-from-google-code-to-github.html>
Also, an excerpt from an article
<http://blog.yhathq.com/posts/11-python-libraries-you-might-not-know.html>
in /r/python <http://www.reddit.com/r/python>today:
/There's a chance you haven't heard of |prettytable|
<https://code.google.com/p/prettytable/> because it's listed
on GoogleCode, which is basically the coding equivalent of
Siberia./
/
/
Made me chuckle. Glad we are moving on.
If either of you feel the inclination to convert to git and set up an
organisation then we can take a vote?
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.
