Still using Redmine for self-hosting here, Gitlab is too heavy for small teams. Thought about trying Phabricator but then its various components with strange names stopped me from trying, plus it seems clunky for small team too.
We use Redmine for ticket / issue / task tracking as well as rough timesheeting, and we use gitlab and gitlab CI along side it. I quite like how quick Redmine is and how it just gets out of your way. We find gitlab to be pretty quick however upgrades are painful due to regular bugs / regressions. Ideally I'd like to see something like Taiga and Gogs together which I think would absolutely fly.
Almost Everything We Do Will Be Open
101–110 of 208 posts
Re: Almost Everything We Do Will Be Open
#102As always, if anyone has any questions, we're here.
It would be nice at times to download old builds at certain commits that the CI server had built in the past.
Re: Almost Everything We Do Will Be Open
#103Decided to switch to gitlab when I realized github refused to release their tools on Linux even though according to stackoverflow statistics Linux users make up over 20% of programmers, matching the number of OS X programmers. It's unfortunate that they make a living off open source software created by a lead Linux developer but they act like Linux doesn't even exist. Not a big deal though, the userbase on github is…
Which tools are you talking about?
Re: Almost Everything We Do Will Be Open
#104Earlier quoted context omitted.
Which tools are you talking about?
Git.
apt-get install git
pacman -Sy git
emerge --ask dev-vcs/git
yum install gitRe: Almost Everything We Do Will Be Open
#105GitLab Enterprise user here. GitLab's open-source policy is one of the major reasons we chose it (along with self-hosting and fairly modern, built-in continuous integration), but the GitLab community could use some additional design and documentation effort. Things that almost make me want to switch back to GitHub: - GitLab is really hard to look at. All of our devs are having trouble visually locating comments in di…
Thanks for the feedback, we really appreciate it! The quick reply to your comments is: we're working on almost all of it. > - GitLab is really hard to look at. All of our devs are having trouble visually locating comments in diffs. We're always scrolling through the left-side menu looking for the issues tab. It's hard to visually differentiate between items like comments in merge requests. Our eyes just can't find an…
Re: Almost Everything We Do Will Be Open
#106Earlier quoted context omitted.
Settings -> Repository details -> Landing page -> Source
Sure, but that should be the default setting, even if it can be changed.
That's a strong statement... I prefer bitbucket default view actually. The fact I can see the latest commits right at the start is very useful to me.
Re: Almost Everything We Do Will Be Open
#107Earlier quoted context omitted.
Perhaps it's just me, but when they said the enterprise edition was "publicly viewable source code", I assumed they just meant it was "publicly viewable", with no further rights implied. I don't think they're really openwashing here, and the article was pretty clear to me. Besides, the community edition and CI code are both true open source.
Isn't there a slight problem with having the EE code publicly viewable? What I mean by this is, what's stopping someone from taking code from the EE, modifying it, and including it in the CE? On the flip side, what if a feature released to CE is too similar to code in EE, even if the author of the patch never read the EE code for inspiration? Would GitLab be within their rights to stop it? With these issues in mind,…
1. Copyright law.
2. For corporations it's probably more cost effective to pay a subscription than maintain a fork.
Re: Almost Everything We Do Will Be Open
#108Earlier quoted context omitted.
Is bitbucket considered not a competitor? I've found it quite suitable for anything github does, though I'm at max a 5 person team.
BitBucket is far superior to GitHub. It's not even a question.
Re: Almost Everything We Do Will Be Open
#109Earlier quoted context omitted.
That's not the definition of "open source", that's the definition of "free software". As you can see by this very article, "open" and "free" are not the same. http://www.gnu.org/philosophy/open-source-misses-the-point.e...
They are: http://opensource.org/osd The only difference is their argument. Free software uses ethical arguments, open source denies ethics altogether and uses consequentialist arguments related to business value and technical superiority (which are becoming increasingly criticized).
Re: Almost Everything We Do Will Be Open
#110Earlier quoted context omitted.
Well, you are. Let me read to you the definition of Open Source: > Open source software is software that can be freely used, changed, and shared (in modified or unmodified form) by anyone.
Great, the age-old debate on what is and isn't open source vs free software. We really needed that in here. Y'all need to stop whining about the irrelevant when companies like these are doing literally everything else right. It's pretty damn ungrateful.
It has nothing to do with being ungrateful. We express our appreciation when software is liberated, or when developers/companies are working toward it. But it does not change the fundamental philosophy.