I've been following the blog for a while and I've been wanting to share something with you. Luckily I now have some time and decided to put together a mini-tutorial on how to build a project with Go and upload it to Google Code.
Many tutorials start by cloning a repository (downloading it from a remote server like Google Code, GitHub, bitbucket , etc ...), but very few take into account developers who are starting something and want to do that project using a version control system (CVS, Concurrent Versioning System) as Go.
The implementation of a version control system for software development allows you to avoid situations like the one we see in the Imagen 1 (I do not doubt that it happened to more than one of us).
On the other hand, once we master this system we can extend it to use it in other applications. For example, it can be used to have a version control of documents that we usually edit. This allows us to keep a historical record of the work carried out as well as the realization of different branches that can be contributions from various collaborators.
Why Git?
Well, mainly because it is one of the best out there. It was created by our dear friend Linus Torvalds in C in 2005 and is the one used to keep track of the versions of the Linux Kernel (not bad, right?).
It is relatively easy to use and according to a survey conducted in this 2013 that says goodbye, Eclipse IDE users have an adoption of 30%.
On the official site we can find all the relevant documentation, a book that covers the most important aspects of Go to delve a little more what we are going to see in this article.
Luckily we have one Spanish version which is quite well translated and quite complete as well. The translation is in GitHub and you can contribute to improving it.
Why in Google Code?
Well, there is not much to say about the Internet giant ... Although there are multiple options for hosting projects, many of us already have an account Google and therefore you already have your username Google Code, making things a bit easier.
Also Google Code It hosts hundreds of projects in different languages, it is free, it is exclusively for the use of Open Source projects and it is very easy to use.
On the other hand, you had to opt for one of many options and I just thought I'd try what the web giant offers us. In future installments I will be reviewing other offers that exist.
Soon…
So far a brief introduction and in the next installment we will review how to create our project in Google Code.
Regards!
Well, Google Code kills me (and accessing the projects it hosts) because it is blocked for my country (Cuba), I use Github fully, and although I could access Google Code, I don't see the point of using something other than Github, simply they are the best.
Yes, they talk a lot about Freedom on the web and they have us blocked.
The NSA uses ICANN to threaten Google, the United States can close the page it wants. If Google opened its services to Cuba, ICANN would close the domain (which Google would not like). Did someone say VPN? ^ _ ^
Well, it's that in Cuba. the bandwidth distribution is uneven, so a VPN is a luxury there.
Here they are cheap: http://www.vpnbook.com/freevpn ($ 0 to be exact)
Another difference is that on github some companies use it to search for their new talents, which is not the case with google code. On the other hand, if Google itself is passing some of its Opensource projects to GitHub, don't you think it's for something?… Greetings to all.
Google code is very useful, I use it for university tasks but not using Git but Subversion, I use svn because I am the one I basically master
Back in the day this git tutorial was recommended to me.
http://gitimmersion.com/index.html
I found it excellent.
If I don't remember badly, Google Code has already been covering editable content, downloads and such for months. I do not use it so I am not up to date with it, but I suppose it will be something that you will discuss in depth because precisely for January 2014 they had some limiting abrupt changes. And that I am pro Google XD
The truth is that I was not aware of the Google Code restrictions, it just seemed easy to me to start without having to get a new account (since many must have a Google account).
It was an option that I tried, it was useful to me and I shared it. Surely there are many other better options, but it all depends on how the work environment of each one is.
We will have to see what Google has in store for us in 2014, I know they are preparing a new site to centralize the activities of the developers.
Luckily they are 2.0 tools, when they take a policy that the user is not convinced, one simply stops using it and voila! Of course, you have to always take that into account, since it may happen that it ceases to exist without one having wished it ...