I find it very difficult to follow the code development on github, since it doesn’t support full diff emails and only notifications, which are just noise and require too too many steps to get to each diff. Plus often you have to click again and again to even see a diff. That’s very inefficient and it’s very difficult to track.
Would it be possible for fastai_v1 to setup a commit diffs email feed service? As discussed here and here github is not interested in providing such service, probably because they want everybody to come back to their service as often as possible, like any other for-profit organization out there.
@jeremy, would it be possible to setup gitdub on the fast.ai server to provide such service? This short article shows the steps to set it up. We can then send all its output to, say, free gmail group, to which anybody can subscribe to, instead of needing to setup a local listserv. I’d be happy to create and manage the gmail group as I manage several already.
Of course, even better, it’d be to be able to discuss changes right at the mailinglist-level and not through github, because’s most of the time nobody is looking at what happens on github, other than PRs and Issues, so it is not very likely for a discussion to happen. And this forum is a way too far from where the action is happening (git) and there is no way to get all developers to pay attention, other than through forcefull hear, hear @jeremy, @sgugger, @etc.
Clearly, I’m missing the good ol’ days when all dev work was done in the simple world of dev maillist. But I’d be happy with at least having a read-only diff feed delivered to my mailbox, because I do want to know of most code changes happening inside the project. In general, and also to minimize the chance of stepping on someone’s feet as I can tell from commits that so and so is now working on this notebook. And this all can be done through github, but it’s very very inefficient, so I don’t do it.
I also found this modern reflection on Mailing lists vs Github as a dev environment, which was an insightful read.
p.s. just looking around, I see that pytorch uses https://pytorch.slack.com/ for dev environment, whereas https://discuss.pytorch.org/ is only used for user support. git dev is happening on its dev mailing list.