# Gerrit

Gerrit is a web-based code review tool and Git server that provides access control for hosted Git repositories.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Lix Announces New Governance Model and Zulip Communications Space

DevFeed: [Lix Announces New Governance Model and Zulip Communications Space](<https://devfeed.tech/articles/meta-news-on-lix-in-october-2025-31376.md>)

Original publisher: [Read original article](<https://lix.systems/blog/2025-10-13-meta-lix-news/>)

Published: 2025-10-13T00:00:00Z

Content type: news

Language: en

Sources: [News on Lix](<https://devfeed.tech/sources/news-on-lix.md>)

Topics: [communications](<https://devfeed.tech/topics/communications.md>), [Gerrit](<https://devfeed.tech/topics/gerrit.md>), [Matrix](<https://devfeed.tech/topics/matrix-org.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [communications](<https://devfeed.tech/tags/communications.md>), [community](<https://devfeed.tech/tags/community.md>), [gerrit](<https://devfeed.tech/tags/gerrit.md>), [governance](<https://devfeed.tech/tags/governance.md>), [matrix](<https://devfeed.tech/tags/matrix.md>), [news](<https://devfeed.tech/tags/news.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

Lix announces a new governance model with core, committer, and community teams. The project is also adopting Zulip for high-bandwidth discussions while continuing to use Matrix for chats and announcements.

### Source excerpt

As Lix continues to evolve, we're excited to share some major updates that mark a new chapter in our journey. This blog post is the first of its kind: we want to give you a deeper look into the decisions, plans, and developments shaping the future of Lix.

## Multiple teams and monolith

DevFeed: [Multiple teams and monolith](<https://devfeed.tech/articles/multiple-teams-and-monolith-27298.md>)

Original publisher: [Read original article](<https://blog.pchudzik.com/201901/multiple-teams-in-monolith/>)

Published: 2019-01-10T16:50:48Z

Content type: article

Language: en

Sources: [Paweł Chudzik](<https://devfeed.tech/sources/pawe-chudzik.md>)

Topics: [Development](<https://devfeed.tech/topics/development.md>), [Git](<https://devfeed.tech/topics/git.md>), [legacy](<https://devfeed.tech/topics/legacy.md>), [maintenance](<https://devfeed.tech/topics/maintenance.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Gerrit](<https://devfeed.tech/topics/gerrit.md>), [Testing](<https://devfeed.tech/topics/testing.md>)

Tags: [deployment](<https://devfeed.tech/tags/deployment.md>), [development](<https://devfeed.tech/tags/development.md>), [gerrit](<https://devfeed.tech/tags/gerrit.md>), [git](<https://devfeed.tech/tags/git.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [release](<https://devfeed.tech/tags/release.md>), [teams](<https://devfeed.tech/tags/teams.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The article explains how a team reorganized work on a large legacy monolithic application after the team doubled in size. It describes a Git-based branching workflow in which teams use dedicated development branches, merge tested changes to master, and create release-candidate branches for stabilization.

### Source excerpt

At work I'm are engaged in the maintenance and development of a pretty big legacy monolithic application. Some time ago team size basically doubled. To keep things simple and activate more people we decided that we need to split the huge team into smaller more focused parties. Here is how we are working on many features of the same code base in single monolith with multiple teams. Read more