search

mwkirk / javapns

Test import of svn javapns repo from Google Code
3 stars 0 forks source link

Github #132

Open mwkirk opened 11 years ago

mwkirk commented 11 years ago

Original author: mavar...@gmail.com (July 03, 2012 07:55:32)

Can you move to github so this would be easier to submit updates to the project.

Original issue: http://code.google.com/p/javapns/issues/detail?id=132

mwkirk commented 11 years ago

From sype...@gmail.com on July 03, 2012 13:44:07 Before undertaking such a move, could you elaborate on how it is difficult to submit updates to the project here? Google Code projects integrate well with Eclipse, and committing updates is a very simple matter. How would it be easier on Github?

mwkirk commented 11 years ago

From mavar...@gmail.com on July 03, 2012 15:35:36

Non-members may check out a read-only working copy anonymously over HTTP.

svn checkout http://javapns.googlecode.com/svn/trunk/ javapns-read-only

In github anybody can fork open source project and work on his own copy without the need to request membership e t.c., latter on he can suggest patch for processing, no need to wait for membership e t.c..

There is a wide opensource community in github (In fact there are already 2 projects with javapns code in github), and this would be much easier from my perspective to participate in development, then it is currently.

mwkirk commented 11 years ago

From sype...@gmail.com on July 03, 2012 16:01:19 I do not think there are much requests for developer status on this project (and I doubt there are much delays to get developer status here), so I'm not sure it is worth moving the entire site to Github just for that... (and you are always free to submit patches here whenever you want). But since I'm not the project owner, I'll leave this request open for consideration.

mwkirk commented 11 years ago

From sype...@gmail.com on July 04, 2012 01:29:54 After looking at the forks of JavaPNS on Github, they seem to have been created for modifications so small that it's a bit ridiculous that they weren't contributed here. Forking a project to add a single small feature doesn't make sense to me. If the feature had been added here, it would have been part of the official distribution, maintained, and documented in all future releases. I'm wondering if it's simple laziness of not wanting to get familiar with Google Code to submit a minor update, or maybe impatience for having to wait a bit to get a developer status approved... Anyway, I'm still convinced that there's no advantage of spending time and energy moving the project to Github, as Google Code is also a widely-adopted repository. If I'm wrong, please do tell why, and specifically how it is supposedly so easier to commit code to Github..

mwkirk commented 11 years ago

From mkli...@gmail.com on March 04, 2013 19:36:31 My $.02...

Moving to GitHub is definitely an undertaking, but I'm willing to bet that it would increase participation and contributions dramatically.

Git and GitHub have (by far) the most momentum in revision control systems and code hosting. Folks generally prefer Git over Subversion these days -- especially for open-source projects. GitHub has a very appealing site design and UI. Perhaps you can do everything on Google Code that you can on GitHub, but the fact is that people really like GitHub.

Sadly, Google Code just isn't "hip", and there's probably no point going against the grain. If there's interest in seeing this project flourish, moving to GitHub is most likely worth the time investment.

I'm certainly not one of the cool kids, but I know I catch myself kind of hating it when I have to come to creaky, old Google Code to check out a project. More importantly, I really don't want to deal with Subversion. I gave in and moved to Git, and now I much prefer it over Subversion.