Change:
this step would automatically inform the IETF Secretariat that this repository should be backed up as described in backup. <ins> 2.6. The IETF Datatracker should allow working group chairs to add links to repositories (for GitHub and other repository services) on the working group "About" page under "Additional URLs".  This feature is already under development. </ins> 3. I-D.thomson-github-bcp contains discussion of the different possible

Discussion:
This needs to be more concrete than the current text. I just removed the following from -using: organization on the WG Charter page in the datatracker under More Info. Similarly, if there are multiple mailing list options, links to those mailing lists should be given. An example of this is at URL I wouldn't recommend that exact language, but the the text definitely should mandate some means of linking from working group status pages to the GitHub organization.
Sorry to be late on this. I don't see what more concrete thing you are asking for. The current text already has the steps, including putting a pointer on the WG page (although not in the charter itself).
There is work-in-progress to add "general external references" to each of users, groups, docs, in datatracker. Some details are in URL
Discussed in Singapore; will add some text in this document. migration style. I guess you are initializing things from refnames: value side with a unique id saved into cache, but I didn't see where you used that. What is migration style? Where can I find "typical" examples to emulate? The idea is that existing "additional URLs" fields -- for example, look at URL or URL -- will have those fields that are common (as specified in the python script) moved into the new tables. I am calling those new commonly-named things "extref" for "external referfence" The value is just a string, but the idea is that it is an identifier that is useful in some external context, and having common names for these thing makes more automation possible. For example, a "GitHub Repository" extref. We want that name normalized, so that tooling can fetch it. Right now the additional URL's are a set of text fields, and the names are not consistent: "Github repo" "GitHub Repository" "Repository", etc., are all used. That is the point of the refnames map, to capture all the existing names via regexp and map them into a common name which gets an ID in the external_refs table, which is then used as foreign keys in the "list of external references" for each of the person, group, doc, entries.

It will not be perfect, but I looked at all the names and in use (the tables mentioned in the python outline) and I think it gets almost all things right. I am unsure, for example, of the YANG links; what tooling of theirs breaks if the name becomes generic? Perhaps I just don't remove a link when migrating. What is not shown or done is mapping these extrefs into the source, such as URL, and displaying them. That's the real work, I just want commentary on the data structures first. For example, in URL I could add a "standard" extref that says "On github I am richsalz" Then this could be used by scripts to populate repo's and auto-link back to the DT accounts. Hope that helps you help me help the IETF. :)