Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Move to GitHub
#11
(12-15-2012, 04:24 AM)nyov Wrote: Hi all.
I just saw this thread by chance and wanted to put my 2(mio) cents here.

First, I put up a github mirror of your repository[1] (before I ever read this forum) because, while I can't really use the software as is,
it's the only really open source one of its kind[2] and I don't much trust "encrypted" scripts like b**billing and such
since they tend to "phone home" without my permission and generally can't be audited (nice selling point for you guys right there).
Yeah open-source is really our primary advantage over every other hosting solution. And Google (Code) sites rank the best on Google. Tongue

(12-15-2012, 04:24 AM)nyov Wrote: Second, I would encourage a move to a decentralized vcs, be that git or mercurial (github or bitbucket for hosted versions) because of the workflow they represent.
I don't frequent forums very much. I also don't likely sign up to projects for commiting rights to any VCS, I simply don't push my code back,
Call me lazy, but this is where Github (et al) shines.
I clone a repo, do my stuff, and if it's good I fork it on github, push my changes and open a pull request at the source (or mail a patch to someone).
Then they can take it or leave it and I don't care much about it. So for one-shot code submissions it's great. No commitment needed.
Which means for any project hosted there, it's likely receiving more code love than any vcs requireing signup/commit access beforehand.
Definitely a more complete solution. With Subversion the best we can do is have users/potential committers submit a patch/diff.

(12-15-2012, 04:24 AM)nyov Wrote: (I don't know how googlecode works, but I'm not likely to get a google account anytime soon, so f*** them Wink
The funny thing is the only reason I have a GitHub account is because I have a Google account. Big Grin

There's a pretty good chance we'll be moving from Google Code to GitHub in the future. Question though, what about wiki/documentation space? The Google Code implementation is quite simple/straightforward.

(12-15-2012, 04:24 AM)nyov Wrote: Merry Christmas
Merry Christmas!
Kevin Mark - TheHostingTool Lead Developer
Reply
#12
(12-19-2012, 02:58 PM)Kevin Wrote: And Google (Code) sites rank the best on Google. Tongue
Errr. Right, that's likely, got me there Big Grin

(12-19-2012, 02:58 PM)Kevin Wrote: The funny thing is the only reason I have a GitHub account is because I have a Google account. Big Grin
huh, funny. how come?

(12-19-2012, 02:58 PM)Kevin Wrote: Question though, what about wiki/documentation space? The Google Code implementation is quite simple/straightforward.
Well, it doesn't necessarily have to be a "move". Since googlecode supports git as well, and 'synching' between git repos is really core functionality (simple and easy), it could be like just another mirror (though either one should be 'read only' to avoid differing histories and merge conflicts between repos).
Besides I don't care if I clone a git repo from googlecode, github, gitorious or anywhere else, really.
It's just that collaborating with others (and getting code back) is really beautifully simple on github, which means it might help the project more.

So, keeping a google code wiki with a github repository wouldn't be a strange thing, but github supports wiki's too with Markdown syntax (http://github.github.com/github-flavored-markdown/)
instead of traditional mediawiki or other syntax -- and they are versioned git repositories themself so you can commit updates to them besides using the github interface for editing.

And as I said, you can have github pages (http://pages.github.com/) if a versioned wiki is not enough.
So, if you create a branch named gh-pages on your repo with a html page, like this https://github.com/twitter/bootstrap/tree/gh-pages
that page will be generated and available at http://twitter.github.com/bootstrap/

The easiest way to play around with it is to just create a repo or fork one, and fool around with it, test-drive the wiki, the issues pages and all that.
Then removing all that crap forever again is really just a button click away in the repo admin page.

There is also another slightly hidden feature, for all the subversion die-hards.
You can checkout a git repo on github with a subversion client and commit back to it. (https://github.com/blog/1178-collaborati...subversion)
(While I haven't ever tested the commit feature, the svn history on the git-converted svn stuff looks slightly different when checked out from github - so you couldn't just switch the svn repo url but would need a new checkout from the github repo.)

Hope that helps. Have fun.
Reply
#13
You do know that there is a Wiki and Bug Tracker feature in GitHub, right? Tongue
Remote Servers - Shared, Reseller & KVM Hosting Services
Reply
#14
Github's nice. It would make it very easy for people to fork the development branch, make changes they want to submit, and then submit a merge request. If kevin is the only one developing though, then it doesn't make a ton of sense to go through and make the changeover from Google Code.

Happy 2013 everyone.
Nick - TheHostingTool Staff Coordinator

[Image: standard.png]

Reply
#15
I've begun migrating the project to GitHub Smile

https://github.com/TheHostingTool/TheHostingTool
Kevin Mark - TheHostingTool Lead Developer
Reply
#16
YAY. Big Grin
Remote Servers - Shared, Reseller & KVM Hosting Services
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)