Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Is Google code similar to Github where you can put your source code for collaboration?
Which is the de-facto SCM it's using?
And which one is recommended for project hosting?
Update 2013:
All major repo hosting services supports git, and supports smart https access (see below):
code.google.com (with cases like this one, July 2011)
bitbucket.org
tfs.visualstudio.com (!, as explained by Scott Hanselman)
Currently (July 2013), the main difference (between GitHub and other services) is in term of release management, more specifically:
integration with Travis CI (continuous integration, possible more or less with all services)
release artifacts: See "GitHub Release Your Software (July, 2d 2013)":
The ability to associate to a tag up to 100MB of binaries.
Initial answer (September 2010)
One big difference is the support by GitHub for smart http, as explained in the ProGit "smart http" section, supported since April 2010.
Being behind a firewall at work, that is more than useful to actually push anything to the remote repo!
I don't think "Google Code" support it officially, even though some contributors try to push that feature.
Yes, they are similar but support different versioning systems. Also the collaboration style is different. While Github (and Launchpad and BitBucket and all the other DVCS hosters) focus more on active collaboration between forked projects, Google Code's primary way of collaboration is through tickets.
So none of them is per-se better than the other, but perhaps fits your project management and contribution/collaboration style better. The whole debate between centralized and decentralized code versioning systems is related to that.
Some features that you should consider:
Open source:
Google: Always open source.
Git: Open source for free account, but you can pay to switch to close source.
VCS: Both google & github support Git (and others)
Wiki: Google wiki is poorly supported, unless you love to write with wiki tags. You can find many project in Google project hosting has there wiki in Git hub.
Statitstics: Github provides many nice statistics chart, while Google provides only a list of updates
Git:
Google:
AFAIK Google code is yet to support git natively. At least as far as I can tell by the comments on the ticket open for this.
So if you are using or would like to use Git then Github will be naturally more suitable.
On the other hand if you are using SVN and would like to continue to then Google code might be a more natural fit.
I have found Github projects easier to set up and get going but that is fairly subjective. Some of my friends also claim that Github's support/ecosystem is better than Google's.
Use GitHub. GitHub gives each account its own namespace for project names, so you don't have to worry about your project names having already been taken by people's projects. If you're using Google Code, however, then you do have to worry about this.
If you need private repos, you won't get that with Google Code. At least not yet; see this open issue: http://code.google.com/p/support/issues/detail?id=1829
Related
I am pretty sure the answer is "no" or we'd hear about it, but wanted to double-check. Does Github Copilot even send any local code to the backend?
Ideally, I'd want an AI autocompletion tool to share proprietary code within an organization, and only there.
All calculations of GitHub Copilot happen on their Servers, none on your local machine. And if you don't disable telemetry as explained in their FAQ your interaction with Copilot (accepting/rejecting Suggestions) might be used to improve copilot, even tho they say your code will not be used. All this Information can be found in the FAQ: https://github.com/features/copilot (bottom of the page)
There are other competitors to Copilot that offer what you are looking for. Especially AI Learning on proprietary Code for your organization. But I won't disclose any names here since it could be seen as advertisement.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I would like to publish a series of programming tutorials along with some code on github. The tutorials will be written in markdown. There will be several markdown documents with references to each other.
Now I wonder what would be the best option:
Put plain markdown files into the repository, together with the code
Use the github wiki for the tutorials and link to the code
Use github pages (e.g. with jekyll) for the tutorials and link to the code
I am not very familiar with github pages nor with the github wiki, so any hint about (dis)advantages in this context is helpful!
You have mentioned three different ways you can go about doing this, I'll elaborate on each of them...
Markdown files in repository
This method isn't actually too bad, because its possible for people to contribute to it as long as they know Markdown (and Markdown is very easy to learn anyway) as they simply need to send off a pull request after forking your repository. Also, since Github uses something called Github Flavored Markdown you can embed the code directly into each file and have some nice looking syntax highlighting.
Github Wiki
Using the Github wiki is a feasible option because it will make it easy for other people to contribute to it. However, you may prefer to have changes made by other people on a approval type system, this is when you'd go with the first option because of the pull requests feature. I personally wouldn't recommend that you use the wiki purely because it undermines the Github repository itself (having an empty repository with heaps in the wiki). This is just my personal opinion though.
Github Pages generator
You could use the Github Pages generator and make a website using that. However I would like to point out that it uses Jekyll to generate the site, and that the generator will only create one page automatically, the rest of the pages will be up to you to make using Markdown and a bit of HTML. It will look nicer, but it will be much more time consuming.
My personal recommendation
I recommend that you have the tutorial itself hosted in a Github repository written in Markdown, and then you can create a page using the page generator that will link to all of the parts of the tutorial (acting as a landing page)
Is GitHub for Windows open source? If so, I can't seem to find the repository.
According to Tom Preston-Werner, one of the GitHub founders, in his post "Open Source (Almost) Everything", about the open-sourcing philosophy
Don't open source anything that represents core business value. [...] Notice that everything we keep closed has specific business value that could be compromised by giving it away to our competitors. Everything we open is a general purpose tool that can be used by all kinds of people and companies to build all kinds of things.
However, Hubot, previsouly a closed-source asset of GitHub, was eventually open-sourced in late 2011.
For the past year or so we've been telling people about Hubot [...] So we decided to rewrite him from scratch, open source him, and share him with everyone.
Currently, the Windows Github client is not an open source software... but who knows, it might be open-sourced one day.
Phil Haack (who currently works at GitHub) gave a hint in his blog comments to this effect:
At the moment, it is not open source. Many of the libraries we created are open source. As we polish up more and more of those libraries, we'll release more components we used to make the app.
So no, the application is not open source, but keep a look out for some parts of it being published on GitHub. (But bear in mind that this is just a blog comment, not an official announcement of any kind).
According to the latest news, GitHub for Windows is renamed to GitHub Desktop. It is redisigned with Electron and completely open sourced. The beta version has been released. The weblink of GitHub Desktop open source repository leaves here: https://github.com/desktop/desktop .
We have a fairly large project, and I've decided that Google Code is not quite living up to expectations. Github looks like a much more suitable platform -- but I feel like there's no escape for us. Is it a case of migrating stuff over manually? We're using svn currently, so I understand that we'll need to move to git somehow - is this going to be possible considering that I don't have admin access to our repository? Also, I know this is subjective and I don't want to start a holy war, but please also comment on your feelings about Google Code vs Github. Should we also be considering SourceForge?
I've used all, and now I am using github and I am completely satisfied. Sourceforge had annoying ads and was slow, google code didn't have the features I wanted/needed.
As for moving to github, they have a guide here, the process should be quite simple:
http://help.github.com/svn-importing/
We're using svn currently, so I understand that we'll need to move to git somehow - is this going to be possible considering that I don't have admin access to our repository?
Nope, you can use git svn to convert a repo, even if you don't have admin access. Here's a good tutorial (from one of the GitHub guys, no doubt) that explains how to convert an SVN repo to Git (including how to migrate tags and branches properly, which git-svn doesn't do very well).
but please also comment on your feelings about Google Code vs Github.
I've never used Google Code for personal projects. I know from a visitor's standpoint, I like the interface and tools used by GitHub a lot better.
Should we also be considering SourceForge?
Ugh... I personally think SourceForge is probably the worst of the free source code hosting facilities nowadays.
I think before you go through all the work to migrate to github (which is great yes) I would consider what your problem actually is. If it is just that you are using svn and that is not a distributed version control system you could just migrate your google code repository to be HG (Mercurial) based and you would get all the benefits of a distributed version control system but could otherwise stay at google code (which has great features that github does not have as well..)
Google announced today that they're closing Google Code. They added a migration tool to export projects to GitHub, it just takes one click.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
Does anybody know of an plugin that can be used to integrate Jira with TFS?
See Combining TFS with Jira - any experiences or advice?
The options are as follows:
TFS4JIRA (commercial / free for personal & non profit use)
UseTFS (commercial / free for community and open-source projects)
Atlassian Connector for Visual Studio (free)
Disclosure: I work for the UseTFS vendor Pigsty.
Apparently it's not a huge priority for Atlassian:
http://jira.atlassian.com/browse/BAM-1950
I've succeeded to integrate TFS and Atlassian Fisheye / Crucible through SvnBridge. It works like a charm. There are couple of additional steps:
You should implement patch 8517 (http://svnbridge.codeplex.com/SourceControl/list/patches) and build SvnBridge with it;
You should change SVNKit version in FishEye. FishEye uses 1.3.3 version of SVNKit which doesn't work with SvnBridge (there are some PROPFIND errors). You should download 1.3.7 version from http://svnkit.com/ and put it into FishEye.
After that everything should work.
There is one more optional patch for SvnBridge which prevents some error logs on server.
But eventually everything works perfect!
You can contact me for binaries and instructions...
I looked for something like this a while ago and couldn't find anything. I also talked to Atlassian developers directly and they didn't know of nothing that could help either.
That said, I ended up writing a custom integration piece for my customer to create TFS items from Jira items and then have the TFS status updates reflected back into Jira. It took just over a day to build so it's fairly straight forward to do assuming you know a bit of Java and both the Jira API (I used the XMLRPC interface) and TFS API's. Due to the way both systems work it required building a small middleware piece to listen for events from TFS and also to act as a REST end point for a custom action in Jira to call when the user clicked a "send to TFS" button.
Apart from that it was a case of adding some custom fields to the work item definitions on both sides to hold the cross reference values and then doing the mapping of values from one item to the other.
Unfortunately I don't have the code to share since it's on the customer site, otherwise I'd throw what I have up on a gist for you to look at. Sorry.
You can use SVN Bridge to provide an SVN interface over your TFS installation. Then set up Jira / FishEye as if it was an SVN repository.
You could use the TFS Integration Platform. However there is no adapter for JIRA yet, however using the TFS Integration Platform (and I assume a good easy API JIRA has) means it shouldn't be too hard to do.
I created a project a while back on this topic which may come handy for you.
It's released on github. feel free to branch it and make changes.
https://github.com/mahpour/TFSToJira