When comparing Launchpad vs Google Cloud Source Repositories, the Slant community recommends Google Cloud Source Repositories for most people. In the question“What are the best hosted version control services?” Google Cloud Source Repositories is ranked 8th while Launchpad is ranked 11th. The most important reason people chose Google Cloud Source Repositories is:
Cloud Source Repositories is free for up to 5 project-users per billing account. The free tier comes with up to 50GB free storage total and 50GB free egress per month.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Support for web based translation
Launchpad makes it easy to translate free open source projects into virtually any language in the world. Users are allowed to start working on translating any project they want just by having a Launchpad account and a web browser. Most of the time they don't have to even join a team to start working and the editor is web based, so there is no need for any special software.
Pro Integrated build/deployment system
If you use launchpad, it gives you a build system (on their platform) as well as easier deployment - user merely adds your PPA to their sources.list file. Deployment (on Ubuntu, at least - other debians as well) doesn't get simpler than this.
Pro Great bug tracking features
Launchpad is built to be used for open source projects, as such it needs a powerful bug trackers to allow developers who want to contribute to jump right in. Launchpad displays bug statistics (total number of bugs, number of bugs fixed etc...) as well. Bugs can be searched and displayed from every project hosted on Launchpad or for single projects.
Pro Free tier
Cloud Source Repositories is free for up to 5 project-users per billing account. The free tier comes with up to 50GB free storage total and 50GB free egress per month.
Pro Excellent security
Everything is stored encrypted in Google's datacenters. You can give fine grained control to other Google accounts and collaborate.
Pro Integrated with other Google Cloud Platform services
Trigger deployments or create custom integrations using Google Cloud Pub/Sub, deploy directly to App Engine or Cloud Functions, and use Cloud Build for CI. Check out code securely (Service Accounts) from your Cloud Compute instances or Container Engine images. View logs in Stackdriver.
Cons
Con The web interface is complicated and hard to use
Other project hosts such as GitHub, BitBucket or GitLab have easy, simplistic UIs that help new and experienced developers alike to browse code right through the browser. LaunchPad on the other hand is very weak at this. Most of the projects have poor (if any) documentation and no way to determine a project's worth easily. The fastest way to do so with LaunchPad would be to download the project and look through the code manually, which is quite tiresome.
Con No inline editing
Unlike some other popular repositories, there is no way to edit inline directly from the source browser. Although, you can easily open up a Theia-based IDE in the browser to edit and run your code by clicking the "Open in Cloud Shell" button. You will still have to commit your changes from the Cloud Shell command line, though.
Con Markdown styling is not as good as GitHub or GitLab
Your README files will not render as nicely as GitHub and GitLab, which may irritate you if you're migrating your repos with nicely-formatted docs.
Con Must set-up billing account
For all Google Cloud Platform projects you must enable Billing. This isn't uncommon for cloud hosting providers but it still could be considered a CON.