Github

[GoogleCodeExporter]

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

Original issue reported on code.google.com by mavar...@gmail.com on 3 Jul 2012 at 7:55

[GoogleCodeExporter]

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?

Original comment by sype...@gmail.com on 3 Jul 2012 at 1:44

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

# 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.

Original comment by mavar...@gmail.com on 3 Jul 2012 at 3:35

[GoogleCodeExporter]

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.

Original comment by sype...@gmail.com on 3 Jul 2012 at 4:01

• Changed state: Future

[GoogleCodeExporter]

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..

Original comment by sype...@gmail.com on 4 Jul 2012 at 1:29

• Added labels: Unscheduled

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

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. 

Original comment by mkli...@gmail.com on 4 Mar 2013 at 7:36

[GoogleCodeExporter]

Following up on my previous comment:

I decided to test GC to GitHub migration, just to gauge the effort involved. I 
truly understand the maintainers' desire not to spend a lot of time/effort on 
this. Fortunately, it wasn't too bad. After a little research, I did it in 
about two hours since others have done the heavy lifting (repo and issue 
migration).

The test GitHub repo is here:  https://github.com/mwkirk/javapns

I migrated the repo and the issues. I haven't tried the wiki, but that seems 
doable as well. If there's a desire to migrate, I'm willing to help. I can 
provide instructions for what I did, or actually do the migration. I'm no 
GitHub guru, but, fortunately, it wasn't too difficult. Just get in touch with 
me.

FWIW, I usually frown on requests like this (i.e. "Please change this to the 
way I do it!"). They usually just waste the maintainers' time. However, I truly 
believe this project would benefit from moving to GitHub. Not everything is 
great about GitHub. Their issue system lacks some features, but it can be made 
to work. Some folks don't like their wiki. However, some things are clear:

• Git has become the VCS with the most traction. Its CLI can be cryptic at 
times, but there are some great GUIs that take away the pain for new users 
(e.g. Tower, SourceTree).
• Git's branching model seems to work well with the way folks want to work 
these days. 
• GitHub has a very active community, and many projects have moved from 
Google Code, SourceForge, etc. to GitHub to increase participation.
• I've seen lots of projects that seem to languish in Google Code. I'd hate 
to see that happen to this one.

Obviously, Google Code supports Git now, but I really think GitHub is at least 
half the reason to move the project. Google Code just doesn't seem to attract 
participants.

My interest is this is, admittedly, selfish. I use this library, and I'm 
concerned about the queue problems mentioned in #115. I'd like to see more 
folks working on this, and I'd like for it to be easier to contribute myself.

Original comment by mkli...@gmail.com on 5 Mar 2013 at 12:31

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by sype...@gmail.com on 11 Oct 2014 at 9:41

• Changed state: WontFix