01:49:29 https://devclass.com/2023/11/07/mozilla-will-move-firefox-development-from-mercurial-to-microsofts-github/ 01:49:34 what the hell is this!? 01:49:57 njsg, lol @ ur comment coin lands on ms edge 02:07:47 dunno why you'd go git when M$$$ owns it 02:08:54 though some opensourse projects still use git, like RPM an DNF an others 02:09:48 the problem really is that kids these days won't contribute to any FOSS project AT ALL unless if it is on Giggityhub 02:09:57 because everything else is deemed "oooooooold and unsexy" 02:10:19 basically the Linux kernel is the largest outlier out there these days due to its arcane workflow 07:37:28 I'd say a problem (not saying it's affecting mozilla, but rather that it might pop up in some projects) is people thinking other people "won't contribute [...] unless it is on [insert AJAX platform here]" 07:38:33 and the use of that sometimes ignores the possibility people won't contribute (either by choice or because it is impossible) if it must go through that platform 17:46:37 The last time I was involved in a collaborative dev project, we used git, and some of the developers hosted their repositories on github, but others didn't, and the official one wasn't, and the workflow for collab involved IRC. 17:47:52 When you wanted a branch pulled, you said something like "I fixed the STF segfault on my stf-segfault branch." 17:48:23 And the lead dev (it was a small team) would then look at your fix and probably merge it. 17:48:37 We all had remotes for each others' repos. 17:48:44 Granted, this was several years ago. 17:49:02 Though I think the fact that it was a small team is the larger thing that sets it apart. 17:50:55 Also, are there IRC channels where people don't idle? 22:05:24 I think that workflow might be the intended one in git's design (not that it means it's the only one, of course)