From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <91774b6345d79748c720755d28a9f6ef@proxima.alt.za>
To: 9fans@9fans.net
Date: Mon,  2 Dec 2013 19:52:14 +0200
From: lucio@proxima.alt.za
In-Reply-To: <84A59510-4C11-44EB-AC27-F53BD44194F9@corpus-callosum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] Go and 21-bit runes (and a bit of Go status)
Topicbox-Message-UUID: 8dcfbd72-ead8-11e9-9d60-3106f5b1d025

> It takes time, more than effort, to keep up with the various Go develop=
er
> lists where changes actually take place.  The case of libbio changes ha=
ppened
> 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=E2=80=99re caught try=
ing to
> keep up again.  So either we start posting codereview emails to the 9fa=
ns
> list, or we find a better way to collaborate and make Plan 9 a first ti=
er
> 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