Or we can deprecate it like x/crypto/openpgp

This is in the proposal track but I'm not sure it's really a proposal. I agree that it would be nice if x/text had an active maintainer, but the proposal review committee can't cause that to somehow happen.

There are many Go programmers with an interest in localisation. Could an experienced maintainer coordinate a working group perhaps?

That seems a potentially more profitable avenue to pursue, but again isn't really in the purview of the proposal committee.

Thank you - I didn't know to what extent this was the case. I've edited to make this a regular issue instead. Please remove from the milestone.

I discussed that at Gophercon EU with @thanm, as I am actually interested in working on this for our own needs. However, for now, I still haven't managed to untangle how to build updates.

@fgm good to hear that you are interested. For building updates, I think there is a CL https://go-review.git.corp.google.com/c/text/+/304029 that needs to move forward. I'll talk with folks about that.

OK, https://go-review.git.corp.google.com/c/text/+/304029 is now submitted. @fgm I think you should be able to build updates now (if not let me know and I can try to help).

Really glad there's movement on this.

When it comes to CLs in x/text, is there a reviewer with +2 approval powers we can cc for attention? (I understand we need at least two +1s from Google staff?)

@golightlyb you can CC me on reviews for the time being, I can pull in other folks from the team where needed.

@fgm, are you unblocked at this point?

Thanks, no hurry, just wanted to check in.

Taking out of proposal process. It's not really a language or library change proposal. @mpvl agrees that having a new maintainer would be good, but that person is signing up for a lot of subtle algorithms. :-)

Update: been working on the various RFCs and associated tools.