I’ve been working on Open-Source projects like Symfony or Twig for 10 years now. It has been a great journey so far and I learned a lot, from community management to technical processes. Using a monolithic repository for Symfony is probably one key component to its success and it helped us scale easily. I want to share with you some reasons why using the same strategy for your proprietary projects might be a good idea as well.


Comments are closed.

Kind of strange to present a Go program at a PHP conference.

Cathy Theys at 12:14 on 18 Nov 2016

Some overall organizational implications, and some in depth command line examples. A little bit for everyone.

Andy Snell at 18:12 on 19 Nov 2016

Very interesting presentation, but maybe not for everyone. From a high-altitude view, I really liked learning about how Symfony internally organizes their component libriaries and how they handle the monorepo vs multirepo problem. On the other hand, it's unlikely that I would ever need to take advantage of the subtree splits unless I moved to a company already using it.

Jay at 11:54 on 21 Nov 2016

Very interesting and relevant for our company as we are in the process of planning changes. Concepts were easy to follow and presented in an organized and clear way. Probably the highlight of the conference for me.

The presentation explained things very well, but I think the applications are limited to people with large codebases and/or large infrastructures. I still enjoyed it.

While the delivery of the talk was fine, it was absolutely not appropriate for a keynote. I was sitting at a table with a lot of entry-level folks, and they were completely lost, both from the technical angle and why this might even be relevant to them.