Arnold Schrijver shared this article before Xmas, but I didn’t take the time to read it yet. Keeping it in mind, since Git workflows seem to have evolved lately.
1 Like
So, I read the article, and I’m not convinced of its utility. It makes a good inventory of various strategies but fails to give live examples of said strategies in the wild. E.g., it would have been nice to have a couple of links to existing projects related to each strategy: what does the Linux team use? Do they combine strategies? Did they move from one approach to the next? Over the two decades of Git, how did the Linus Torvalds team(s) evolved their usage? What strateg(y/ies) do most prominent projects use? Is there a correlation between project size and Git approach? What about licenses? Etc.
Although well-written and documented, I feel the article only scratches the surface, without really telling the difference between strategies that kinda look the same.
What decentralized Git workflows would be or are suitable for software syndicates, @spacekookie? Do you share my feeling about this article?
1 Like
