Live data from Hacker News

GitLab acquires Peach Tech and Fuzzit

about.gitlab.com

1–10 of 55 posts

Re: GitLab acquires Peach Tech and Fuzzit

#3
This seems to be similar to GitHub adding automated code analysis and screening as well as detecting flaws in what would become the built artifacts like external APIs. In a sense they are delivering static analysis which used to cost a lot of money, time and dedicated manpower (i.e. HP Fortify).

It makes sense for those companies to expand beyond what they already have. Starting with version control systems, going on to Wikis, static websites, actions/automation, CI, artifact hosting. It will eventually contain the entire lifecycle it seems.

Re: GitLab acquires Peach Tech and Fuzzit

#6

@syste Are these soft landing acquisitions as described in your handbook? Also will the technology be open sourced like Gitter was?

Thanks for asking. We don't comment on individual acquisitions beyond what is in the OP. For everyone else there reference our handbook page about acquisitions is on https://about.gitlab.com/handbook/acquisitions/

We won't necessarily open source all the acquired technology like we did with Gitter and RedHat does with every acquisition. We'll follow our buyer based open core model https://www.heavybit.com/library/video/commercial-open-sourc... Maybe the relevant product managers have more to say about the current plans.

Re: GitLab acquires Peach Tech and Fuzzit

#7
post #3

This seems to be similar to GitHub adding automated code analysis and screening as well as detecting flaws in what would become the built artifacts like external APIs. In a sense they are delivering static analysis which used to cost a lot of money, time and dedicated manpower (i.e. HP Fortify). It makes sense for those companies to expand beyond what they already have. Starting with version control systems, going on…

Lol!

Re: GitLab acquires Peach Tech and Fuzzit

#8
post #3

This seems to be similar to GitHub adding automated code analysis and screening as well as detecting flaws in what would become the built artifacts like external APIs. In a sense they are delivering static analysis which used to cost a lot of money, time and dedicated manpower (i.e. HP Fortify). It makes sense for those companies to expand beyond what they already have. Starting with version control systems, going on…

There is a joke in all of this:

One could argue that GitLab gets more and more mature but somehow still has Peach Fuzz.

Re: GitLab acquires Peach Tech and Fuzzit

#9
post #6

@syste Are these soft landing acquisitions as described in your handbook? Also will the technology be open sourced like Gitter was?

Thanks for asking. We don't comment on individual acquisitions beyond what is in the OP. For everyone else there reference our handbook page about acquisitions is on https://about.gitlab.com/handbook/acquisitions/ We won't necessarily open source all the acquired technology like we did with Gitter and RedHat does with every acquisition. We'll follow our buyer based open core model https://www.heavybit.com/library/vid…

@joiningnow123 - Thanks for the question. We plan to open source all the fuzzing engines built by Fuzzit. We also plan to open source Peach Tech's protocol fuzzer however this will be some time next year when we begin integrating it.

Re: GitLab acquires Peach Tech and Fuzzit

#10
post #6

@syste Are these soft landing acquisitions as described in your handbook? Also will the technology be open sourced like Gitter was?

Thanks for asking. We don't comment on individual acquisitions beyond what is in the OP. For everyone else there reference our handbook page about acquisitions is on https://about.gitlab.com/handbook/acquisitions/ We won't necessarily open source all the acquired technology like we did with Gitter and RedHat does with every acquisition. We'll follow our buyer based open core model https://www.heavybit.com/library/vid…

The biggest disadvantage of the buyer based open core model is can completely ignore what the buyer wants (ex: reporters not to be charged the same as developers, because that makes no sense).
Post reply on HN