On 29 Jul 2019, at 22:30, Brian E Carpenter wrote:
The IETF rule is still that consensus is established on the mailing
list, so it's clear that what happens on GitHub is not definitive -
it's just a tool, which we can use for convenience as long as it
remains convenient.
A git repo is IMO useful for many things in IETF/IRTF work processes
(version control, collaborative editing, project directory
synchronization, issue tracking etc.). In the groups I am co-chairing, I
haven’t used GitHub.com as much as we possibly could have, because we
didn’t want to introduce too many dependencies on IETF-external
platforms.
If we think it’s generally useful (I think it is), should we consider
including a self-maintained gitlab server in the tools collections (and
use the data tracker login for that)?
Dirk
Regards
Brian
On 30-Jul-19 06:32, Livingood, Jason wrote:
I may suggest we not rush to judgment. US compliance & export
controls is part of any org operating from US, including ISOC and the
IETF LLC. The IETF LLC's responsibility here is touched on in
11.a.viii of the agreement with ISOC
(https://www.ietf.org/documents/180/IETF-LLC-Agreement.pdf). See also
the draft IETF LLC Code of Conduct, Sanctions section at
(https://github.com/ietf-llc/policies-consultation/blob/master/Code-of-Conduct-00.md).
Jason
On 7/29/19, 11:59 AM, "ietf on behalf of Stewart Bryant"
<ietf-bounces@xxxxxxxx on behalf of stewart.bryant@xxxxxxxxx> wrote:
This report suggests to me that the IETF should move its work off
GitHub
so that we own our own decision on who can and cannot take part
in our work.
https://eandt.theiet.org/content/articles/2019/07/github-restrictions-introduced-to-comply-with-us-sanctions
- Stewart
