> It takes time, more than effort, to keep up with the various Go developer > lists where changes actually take place. The case of libbio changes happened > at a time when no one in the Plan 9 community was really looking at the > threads until it was too late to comment. Now we’re caught trying to > keep up again. So either we start posting codereview emails to the 9fans > list, or we find a better way to collaborate and make Plan 9 a first tier > target for Go.
I know that David and I are monitoring golang-dev pretty closely. By the same token, I suspect that Gorka and Nemo don't (I don't know this for a fact, I'm speculating). What would help immensely would be if we could advertise each of the willing contributors' own interest in the development so that we can fill gaps when they arise. For example, I have no idea where Anthony Martin is heading with the notes code, but I am aware that he is probably ahead of the pack in that direction. Should I spot something in golang-dev that I understand may affect coding Plan 9's note handling for Go, I would like to be able to alert him. Not knowing how closely he himself monitors golang-dev, or how much he would appreciate being nagged, right now I err on the side of caution. It will take time to build a team of contributors that is familiar with everyone else's role, but that is a good reason to get cracking now, rather than later. ++L
