% Created 2024-09-27 Fri 12:54
% Intended LaTeX compiler: pdflatex
\documentclass[usenames,dvipsnames,colorlinks,aspectratio=169]{beamer}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{wrapfig}
\usepackage{rotating}
\usepackage[normalem]{ulem}
\usepackage{amsmath}
\usepackage{amssymb}
\usepackage{capt-of}
\usepackage{hyperref}
\usepackage{color}
\usepackage{listings}
\usepackage{pdfpages}
\usepackage{xcolor}
\usepackage{graphicx}
\usepackage{xspace}
\usepackage{siunitx}
\usepackage{libertine}
\usepackage{fontawesome}
\mode<beamer>{\usetheme{Boadilla}}
\setbeamertemplate{navigation symbols}{}
\setbeamerfont{alerted text}{series=\bfseries}
\setbeamercolor{alerted text}{fg=blue}
\usecolortheme{default}
\usefonttheme{serif}
\usefonttheme{professionalfonts}
\lstloadlanguages{[ISO]C++}
\definecolor{codegreen}{rgb}{0,0.6,0}
\definecolor{codegray}{rgb}{0.5,0.5,0.5}
\definecolor{codepurple}{rgb}{0.50,0,0.82}
\definecolor{codeorange}{rgb}{0.95,0.3,0.1}
\definecolor{backcolour}{rgb}{0.95,0.95,0.92}
\lstdefinestyle{mystyle}{
commentstyle=\color{codegreen},
keywordstyle=\color{codeorange},
numberstyle=\tiny\color{codegray},
stringstyle=\color{codepurple},
basicstyle=\footnotesize,
breakatwhitespace=false,
breaklines=true,
captionpos=b,
keepspaces=true,
numbers=left,
numbersep=5pt,
showspaces=false,
showstringspaces=false,
showtabs=false,
tabsize=2
}
\lstset{style=mystyle}
\usetheme{default}
\author{Brett Viren}
\date{\today}
\title{DUNE GitHub Policy and Practices}
\hypersetup{
 pdfauthor={Brett Viren},
 pdftitle={DUNE GitHub Policy and Practices},
 pdfkeywords={},
 pdfsubject={},
 pdfcreator={Emacs 28.2 (Org mode 9.7-pre)}, 
 pdflang={English}}
\begin{document}

\maketitle
\begin{frame}[label={sec:orgd735f76}]{Overview of DUNE GitHub}
Since 18 Mar 2015, DUNE has control\footnote{I requested and GitHub granted a take-over from a previous absentee user.} of the GitHub organization:

\begin{center}
\url{https://github.com/DUNE}
\end{center}

After almost \alert{10 years} (wow!), the DUNE GH org contains:

\begin{itemize}
\item \href{https://github.com/orgs/DUNE/repositories}{147 Repositories} (git, Issues, Wiki, Discussion, Pages, etc)

\item \href{https://github.com/orgs/DUNE/people}{337 People} (org member)

\item \href{https://github.com/orgs/DUNE/teams}{25 Teams} (map people to repos)

\item \href{https://github.com/orgs/DUNE/projects}{12 Projects} (project management units)

\item \href{https://github.com/orgs/DUNE/outside-collaborators}{42 Outside Collaborators} (non-member users)

\item \href{https://github.com/orgs/DUNE/followers}{103 Followers} (notified of activity)
\end{itemize}
\end{frame}
\begin{frame}[label={sec:org6232f67}]{Why a DUNE GitHub Policy and Practice Document}
There is \textbf{no major problem} to solve here and the concerns are mild:

\begin{itemize}
\item Effectively and so far, I am the only \textbf{active} GitHub \href{https://docs.github.com/en/get-started/learning-about-github/github-glossary\#organization-owner}{``organization owner''} (``organizer'')
\begin{itemize}
\item This is fine and I am happy to continue serving in this role.
\end{itemize}

\item I want to document the things I do so others can step in if I can no longer serve.

\item I want DUNE collaboration to be aware of and ratify the defector policy I follow.

\begin{itemize}
\item And give DUNE a chance to alter it if/where it is not appropriate.
\end{itemize}
\end{itemize}


Note, DUNE does have ``passive'' organizers with the ``owner'' bit set:
\begin{itemize}
\item Currently: \textbf{Anne Heavey} and \textbf{Steve Timmy}.
\item Past: Patrick Gartung, David Adams, Ben Morgan and Matt Worcester.
\end{itemize}
\end{frame}
\begin{frame}[label={sec:org4131f4f}]{Overview of Policy and Practices Document}
Sections:

\begin{description}
\item[{Definitions}] (1 page) terms used in the formal language of the next P\&P sections.
\item[{Policy}] (2 pages) Membership, Contents, Permissions, Organizers (``owners''), Authority individuals (meaning DUNE collaboration, not the cops).
\item[{Procedures}] (1 page) Membership requests and removal, creating repositories and responding to requests from DUNE Authorities.
\end{description}

The draft document is in GitHub of course: \href{https://github.com/DUNE/dune-ghpandp-doc}{DUNE/dune-ghpandp-doc} repo and rendered \href{https://github.com/DUNE/dune-ghpandp-doc/blob/main/dune-github-pandp.pdf}{PDF}.
\end{frame}
\begin{frame}[label={sec:org93127a9}]{Some P\&P highlights - owners}
We are at the policy minimum of 3 ``organizers'' (aka GH org ``owners'')
\begin{itemize}
\item Main job: vet/invite new users and (rarely) give the ``owner'' bit to another member.
\item Must be a DUNE collaborator / DUNE GitHub member.
\item Anne would not mind being replaced, we should find a replacement.
\end{itemize}

No actual effort is needed unless I get hit by a bus, then:
\begin{itemize}
\item Organizers should be capable to learn the active tasks.
\item And/or, be able to give ``owner'' bit to someone one that will take the ``active'' role.
\end{itemize}
Being a ``passive'' organizer is a valuable and easy role to fulfill.
\end{frame}
\begin{frame}[label={sec:org8292b28}]{Some P\&P highlights - membership}
DUNE collaboration membership required for DUNE GitHub membership.

\begin{itemize}
\item Request via \textbf{Email}:
\begin{itemize}
\item Must come from address registered with DUNE Collab DB.
\begin{itemize}
\item Else, I reply to registered address requesting a confirmation.
\end{itemize}
\end{itemize}
\item Request via \textbf{Slack}:
\begin{itemize}
\item Access to DUNE Slack is taken as immediate proof of collaboration membership.
\end{itemize}
\end{itemize}

There is currently \textbf{no audit} for post-hoc membership status.
\begin{itemize}
\item Some DUNE GitHub members are no longer DUNE collaborators.
\item Not a ``big deal'' (imo) but to honor the policy something needs to be done.
\begin{itemize}
\item GitHub API + DUNE Collab DB likely ingredients in developing an auditor.
\item Difficulty: associating GitHub username to DUNE Collab DB entry.
\end{itemize}
\end{itemize}
\end{frame}
\begin{frame}[label={sec:org634783f}]{Some P\&P highlights - permissions}
Generally, DUNE GH follows a \textbf{flat and open} permission model.
\begin{itemize}
\item Repo visibility: policy says repos SHOULD be \textbf{public}.
\begin{itemize}
\item GH changed default to \textbf{private} at some point and we've never reversed that.
\item If we ratify ``public by default'' I'll reverse the setting.
\item This will apply only to future repos, current ones can be manually switched as needed.
\end{itemize}
\item Repo pushing: nominally, \textbf{all} DUNE members can push commits to \textbf{all} DUNE repos
\begin{itemize}
\item Additional access controls are possible at Repository and Teams layers.
\end{itemize}
\item Pull Requests: any GitHub user can offer a PR to any DUNE repo.
\begin{itemize}
\item Any DUNE GH member is free to merge, close or ignore any PR.
\end{itemize}
\end{itemize}

The \textbf{flat and open} model has been working fine so far.
\end{frame}
\begin{frame}[label={sec:org97d7d58}]{Some P\&P gaps needing filling - outside collaborators}
\textbf{Outside collaborators} are GH users that may be given special access to the DUNE GH org.

\begin{itemize}
\item The doc does not cover this role well (lumped into all ``non-members'').
\end{itemize}

Currently DUNE has 42 ``outside collaborators''.
\begin{itemize}
\item \textbf{Spot checks} indicate only ``read'' on public repos, no special permissions/access found.
\end{itemize}

Likely no problem, but work needed to understand and maybe make some changes.
\end{frame}
\begin{frame}[label={sec:org0865d35}]{What next?}
Not sure.  DUNE collaboration has no procedure for P\&P docs (right?), suggest:

\begin{itemize}
\item Fill in some of the ``tbd'' parts (me).
\item \href{https://github.com/DUNE/dune-ghpandp-doc/blob/main/dune-github-pandp.pdf}{Read it} and give comments (you).
\begin{itemize}
\item I have comments from Anne Heavey still to process - thanks Anne.
\end{itemize}
\item Iterate on the draft as needed in this meeting (yes?)
\item Ratification: Kirby?  Spokes?  Other?
\item Define some process for future updates?
\end{itemize}
\end{frame}
\end{document}
