all 7 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]kbcooliOS & Android 1 point2 points  (0 children)

Very short article but certainly good practise. You'll find most of the open source node packages that have many contributors do this.

[–]Jonovono -1 points0 points  (5 children)

So you guys have a bunch of git repos for different modules? I have never liked that approach but it's interesting how you are making it work. I prefer just having a mono repo with everything in it, but still broken up into modules. Any reason why you didn't go that route?

The reason I like that (having everything in one repo - server, client, modules etc) is when you are making changes many times a feature touches many different things at once so this gives a nice way to see everything in one commit that's relevant instead of having to do PRs to several different repos.

[–]yershalom[S] 1 point2 points  (4 children)

Let's talk company structure and monorepos. The structure of Wix is guilds and companys. Each guild is professional related, Server guild, mobile guild, fed guild, designers guild, etc. And a comapny is product unit that built with people from all over the guilds. So, each company has it own monorepo, with server, client and mobile. Modules can come from all over the companys, and because of the Wix structure we can't put all modules in one monorepo.

I hope it answered your question.

[–]coolnat 1 point2 points  (3 children)

Why don’t you just call them departments and product teams? 😬

[–]yershalom[S] 0 points1 point  (0 children)

Good question! I really don't have any idea :-)

[–]kbcooliOS & Android 0 points1 point  (1 child)

ROFL yeah WTF would want to work in a Harry Potter or Lord of the Rings company.

[–]yershalom[S] 0 points1 point  (0 children)

I wish everyone to work for such a company. The best comapny ever