collaborators

And when one person rebases the feature branch it wreaks havoc for collaborators on the feature branch.

Or the collaborators on a branch are few and they agree when to rewrite history.

We're up to 250 employees now, with hundreds of collaborators around the world.

I wouldn't want multiple collaborators editing my code all at once - I wouldn't know what they are doing.

So it's reasonable that scientists are peeved when they invest all this time and don't perceive their collaborators as acting in good faith, or feel like their collaborators are trying to cut corners to pinch pennies.

Also adding more collaborators to this workflow would be very time consuming...

Along the way, you might find {activities, collaborators, products, ideas} that get you really excited.

I feel like one could waste a lot of time contacting and vetting prospective collaborators.

Do these possibly represent each of the project collaborators?

It's really hard to persuade your collaborators of your competencies, especially in the case of no-techs more if there is your boss or for a critical decision.

The direct answer to your question is, because some antivirus systems want to work with a central server (or, in Oliver Friedrich's Immunet case, with a P2P network of collaborators).

At best, I've turned my users into collaborators.