Nicolas Cellier wrote
If killer feature is not the social part, then we don't really need github. Git, MC, or any other distributed VCS already handle the trivial ability to fork.
Okay, fine ha ha, the social part is *the* killer advantage. Perhaps I should've inserted "committing" before "workflow". As to the triviality, IMHO it doesn't get much simpler than clicking "Fork" and then "Create PR", and I don't know of anything nearly that simple in the mcz world. Maybe per-project inboxes might have helped a bit, but always more to do than resources. Nicolas Cellier wrote
IMO, time spent to convince that a change must be merged back is not lost time.
Sure, but the key now is that you can do all that convincing *after* you continue with your own work, instead of being stalled. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html