3 ms·

Like I said before, we were already self hosting (albeit not with Gitlab's tooling) before moving to a hosted solution. If it were as easy as you claim it to be

Like I said before, we were already self hosting (albeit not with Gitlab's tooling) before moving to a hosted solution. If it were as easy as you claim it to be then we would never have switched aware from self hosting. I am a control freak so I actually prefer self hosting myself. But it was steadily becoming impractical. I apologize if I've badly explained the problems we encountered. But please don't assume I'm some idiot who doesn't know what I'm doing just because your business has it's own different set of requirements than ours. > "Your AWS complexities are not gitlab's problem, they are yours.* I'm not blaming Gitlab. I'm saying AWS complexities make some solutions infeasible. I also said some of the compliance regulations we adhere to also add complexities that make some solutions less practical. I really don't understand why are you being so abrasive about this.

jacquesm 9y ago
Because your initial comment pans gitlab quite extensively without them necessarily being the party that deserves your scorn.
- laumars 9y ago
  > Because your initial comment pans gitlab quite extensively I said they have 2 issues arise a year (which, by the way, was already counter argued before you joined the thread). I did also compliment 2 other aspects of their business. So to say my "initial comment pans gitlab quite extensively" and "your scorn" is needlessly sensationalising things. We are all professionals so can we please have a grounded discussion?
  - jacquesm 9y ago
    > which, by the way, was already counter argued before you joined the thread I tend to open a bunch of tabs and go through them one-by-one so apologies for the duplicates. > I did also compliment 2 other aspects of their business. The proper description of that is 'damning with faint praise', of which your comment is an excellent example. > So to say my "initial comment pans gitlab quite extensively" and "your scorn" is needlessly sensationalising things. No, I think it is a quite accurate description of your comment. Whether you agree with that or not is up to you, but just take the fact that I read it as such as a datapoint. > We are all professionals so can we please have a grounded discussion? That's an assumption that I won't comment on.

jacquesm 9y ago

Because your initial comment pans gitlab quite extensively without them necessarily being the party that deserves your scorn.

laumars 9y ago
> Because your initial comment pans gitlab quite extensively I said they have 2 issues arise a year (which, by the way, was already counter argued before you joined the thread). I did also compliment 2 other aspects of their business. So to say my "initial comment pans gitlab quite extensively" and "your scorn" is needlessly sensationalising things. We are all professionals so can we please have a grounded discussion?
- jacquesm 9y ago
  > which, by the way, was already counter argued before you joined the thread I tend to open a bunch of tabs and go through them one-by-one so apologies for the duplicates. > I did also compliment 2 other aspects of their business. The proper description of that is 'damning with faint praise', of which your comment is an excellent example. > So to say my "initial comment pans gitlab quite extensively" and "your scorn" is needlessly sensationalising things. No, I think it is a quite accurate description of your comment. Whether you agree with that or not is up to you, but just take the fact that I read it as such as a datapoint. > We are all professionals so can we please have a grounded discussion? That's an assumption that I won't comment on.