Closed GoogleCodeExporter closed 9 years ago
Can you mention this in the mailing list? Also post details about Google
closing Google Code and suggestions (add a comment in this report too, so we
have a record).
I'd love to move to github and git. but others may prefer to keep working with
mercurial (and then possible in bitbucket).
Thanks for your post!
Original comment by useboxnet
on 19 Mar 2014 at 5:44
I can't find any source that confirms this, the best I found is some news that
Google Code was killing downloads, but that's old news (2013; and it doesn't
look like pyglet downloads are disabled).
If you can't provide extra information, I'll close this issue as invalid.
Original comment by useboxnet
on 20 Mar 2014 at 8:42
I'm sorry, I was wrong about Google closing Code. I read news about Google
killing downloads and since it was a while ago (at least half year from now) my
memory tricked me. Still, I think moving to other code hosting is reasonable
idea. Even Google itself is using GitHub (https://github.com/google/). I am
aware that some project members might have an objections, so it need to be
discussed. Google Code is dead, even if Google won't shutdown downloads this
service didn't see any updates for years, I think, which is very visible
nowadays. Many projects already moved from Google Code to one of its
alternatives. I can send this proposition to mailing list if you still think
it's worth consideration.
Original comment by fen...@gmail.com
on 20 Mar 2014 at 9:43
I think it's a valid request, but I also think that there are other things to
do and this topic starts to sound a little bit like "bikeshedding".
I'm not sure that using github will increase valuable contributions (also, why
github? could it be bitbucket with mercurial? I guess then we could argue that
the problem is that we don't use git -- even it is actually my personal
preference). We may get more pull requests, but I'm not that sure that the code
would get into the repository.
Why do I think that? Because it's not that difficult to read the docs we have
available and use hg (clone, hack, post a diff into a issue), so "not being in
github" is a poor excuse. I've contributed to several open source projects and
every single time I had to figure out how to do it (also, assuming an specific
workflow just because a project is hosted in github may be wrong!).
Please, excuse me for the rant! Thanks for posting this, even if Google Code is
not closing :)
Original comment by useboxnet
on 20 Mar 2014 at 9:54
Personally I'm a big fan of git over mercurial, but besides that, I think that
moving to either Github or Bitbucket would give this project the break through
it needs and deserves. Note that I'm not actually a Pyglet user, but I'm a big
enthusiast. I looked into using Pyglet 1.5 years ago, but the project seemed in
perpetual alpha and I used Pygame instead. Today I decided to give the project
another look (note that the project I used Pygame for was halted not long
after, so it's not like I've been using Pygame for 1.5 years now, on the
contrary, I think Pygame is bloated and ugly), and to my surprise I see that
while there still is a nice list of new commits coming in every month, it's
still in alpha (of 1.2).
Github doesn't have the slogan "social coding" without a reason. The easability
to browse code, create issues and endorsing it by starring it are all things
which lower the threshold to contribute, in whatever way possible, and spread
word about the project. Note that many of these points go for Bitbucket as
well, but Github executes them all just a bit better with a very clean and
intuitive UI/UX.
Moving to Github would also bring access to third-party services such as Travis
for running the tests automatically.
Original comment by gwildorsok
on 20 Mar 2014 at 9:03
The article the topic starter was talking about is probably this one:
http://www.infoworld.com/t/application-development/whats-next-googles-kill-list-
signs-point-google-code-235117
Original comment by gwildorsok
on 28 Mar 2014 at 9:44
Original issue reported on code.google.com by
fen...@gmail.com
on 14 Mar 2014 at 5:37