GIT WG
2019-11-19
Chris Wood and Paul Hoffman, chairs
Minutes taken by Paul Hoffman
Text from the slides are not given here
Video recording: https://www.youtube.com/watch?v=nNcCleIcesM

Administrivia happened

GitHub Configuration for IETF Working Groups, Paul Hoffman
	https://datatracker.ietf.org/doc/draft-ietf-git-github-wg-configuration/
	No slides, but went through issues from the GitHub repo
		https://github.com/ietf-gitwg/draft-ietf-git-github-wg-configuration
	Issue 6: https://github.com/ietf-gitwg/draft-ietf-git-github-wg-configuration/issues/6
		One sentence change, Martin will do it in his document
		See https://github.com/ietf-gitwg/using-github/issues/31
	Issue 5: https://github.com/ietf-gitwg/draft-ietf-git-github-wg-configuration/issues/5
		Martin will do it in his document
		See https://github.com/ietf-gitwg/using-github/issues/32
		Jeffrey Yaskin: the W3C does this as well
	Mark Nottingham: What is the deliniation between these documents?
		Paul: This document is "what does the IETF need to do to help WGs use GitHub"
			The other is "What should a WG do when using GitHub"
		Mark: Would prefer that the documents were combined, but is willing to let it slide
			At least make the titles clearer, and make sure the abstracts say who the audience is
	Issue 2: https://github.com/ietf-gitwg/draft-ietf-git-github-wg-configuration/issues/2
		Martin: This belongs in this document
		Rich Salz: This is already in progress
		Paul: Will include in this document

Using GitHub at the IETF, Martin Thomson
	https://datatracker.ietf.org/doc/draft-ietf-git-using-github/
	Issue 6: https://github.com/ietf-gitwg/using-github/issues/6
		Don't deal with BCP 9 in this document
		Only documents (not other WG processes) will be in scope for this document
		Sean Turner: Would ignore a prohibition even if it was here
	Issue 5: https://github.com/ietf-gitwg/using-github/issues/5
		GitHub sometimes attracts spam
		Do we want to anticipate this?
		Alissa Cooper: Taking action in the IETF is not common
			Are there other orgs that have had this happen?
			Martin: Knows of one in the W3C, was done on an ad hoc basis
				If you observe someone doing bad things, you can block them
		Sean: Normally sees less bad behavior in GitHub than on mailing lists
		Barry Leiba: Agrees
			Whatever you can do on a mailing list you can do in GitHubs
		Rich: Just close issues and move on
		Martin: No need to put something in this draft

Martin's draft will be revved and then WG Last Call starts on both documents

Tutorial, Chris Wood
	https://ietf-gitwg.github.io/
	Not a WG deliverable
	Been socializing its existence
	No signal yet if this is useful

If people have ideas for additions to the WG charter, send them to the list
	Otherwise, WG will likely shut down after docs are sent to RFC Editor
	Mailing list will stay open