171–180 of 325 posts
Earlier quoted context omitted.
Yes but Bitbucket has unlimited private repositories. So if your company has lots of projects compared to lots of people Bitbucket's pricing model is better.
GitLab.com is completely free, and has both unlimited private repositories and unlimited collaborators!
Earlier quoted context omitted.
GitLab.com is completely free, and has both unlimited private repositories and unlimited collaborators!
The difference is that Bitbucket offers unlimited private repos for free.
Earlier quoted context omitted.
Yes but Bitbucket has unlimited private repositories. So if your company has lots of projects compared to lots of people Bitbucket's pricing model is better.
GitLab.com is completely free, and has both unlimited private repositories and unlimited collaborators!
That being said, what both GitHub and GitLab are missing is actually becoming a "social network" or maybe more an active network. There are tons of interesting projects that pops up every day, that I would be interested in knowing about, contributing, but there's basically no way to learn about them.
Kudos to the GitLab team for all its work :)
Earlier quoted context omitted.
We considered that but we value having a completely open source version for all projects more. For more information about how we see the difference between CE and EE please see https://about.gitlab.com/about/#stewardship
What about having a single product, and charging for a proprietary license + support? This may work better with GPL as many large orgs are allergic to it. With MIT license, many sites probably just implement the branding changes etc in the CE product on their own.
If GitLab plays their cards right, they can take the market from github. That, in my book, will be good because unlike github, we can all contribute to making GitLab better. The only question left is if your servers are powerful enough to run gitlab. Maybe I'll sacrifice a goat for some new server hardware and 256GB of ram.
Don't be cruel to animals. I'll ship you the 256GB of ram personally, email me at sytse at company domain.
Earlier quoted context omitted.
[videolan infra guy here] The whole idea of VideoLAN infrastructure migration from gitweb/trac/etc to gitlab and not to github was to use and promote free and open-source software. Using closed-source software there is out of question, really.
Gitlab EE is actually open source. https://gitlab.com/gitlab-org/gitlab-ee
"This software and associated documentation files (the "Software") may only be used if you (and any entity that you represent) have agreed to, and are in compliance with, the GitLab Subscription Terms of Service, available at https://about.gitlab.com/terms/#subscription (the “EE Terms”), and otherwise have a valid GitLab Enterprise Edition subscription for the correct number of user seats."
Earlier quoted context omitted.
Can you comment more on why a hobbyist should not need their own repo? If I'm doing SaaS for everything, my monthly costs start to go up. I've found it is far cheaper, and far (way!) more educational to take an extra box out of the basement and install Ubuntu/GitLab/Node/Java/Apache/Etc. I have to pay for internet either way, and the electricity cost is nowhere near the cost of having multiple Saas?
Most of the time, it's because of opportunity cost: The time you're spending building a server, learning how to manage repos, setting up redundancy and just trying to get the thing working, you could've spent on whatever product you were trying to produce, and would likely be much further along with if you hadn't done everything the hard way. That's not to say there isn't educational value, but a common piece of advi…
I'm from the old school, I use SaaS/PaaS mostly for stuff I know is painful to do yourself (sometimes file storage, nearly always email) but the rest lives on vanilla boxes configured with ansible (frankly ansible is faster to use once you get your head around it than learning 5 different PaaS setups).