From dfac652d1f0be4e48e144f35e55c2670606cfbfa Mon Sep 17 00:00:00 2001
From: Ian Jackson <ijackson@chiark.greenend.org.uk>
Date: Sun, 9 Aug 2015 19:14:10 +0100
Subject: [PATCH] wip

---
 NOTES   | 73 +++++++++++++++++++++++++++++++++++++++++++++++++++
 NOTES-2 | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 154 insertions(+)
 create mode 100644 NOTES
 create mode 100644 NOTES-2

diff --git a/NOTES b/NOTES
new file mode 100644
index 0000000..950533c
--- /dev/null
+++ b/NOTES
@@ -0,0 +1,73 @@
+
+
+1 motivation
+
+what is version control system
+
+ use it to review code, maintain diffs from upstream, do merges, etc.
+
+ but also publication tool
+
+Debian has for VCSs
+
+ for development by maintainers
+
+   lots of people using lots of different vcs
+   many (?) most contributors using git somehow
+
+ for publication
+
+   the Debian archive
+
+   yes, it's a vcs, but it's terrible
+
+what was missing: a unified publication system for git histories which
+contain the same things as the archive
+
+that is what dgit is
+
+
+
+3 why x-vcs-git is not sufficient
+
+   tree you get might be arbitrarily strange
+     - patches unapplied
+     - debian/ only
+     - maintainer's "special stuff"
+
+  SO dgit /is/ in some sense a replacement for debcheckout
+
+  compared to debcheckout
+   - always gives you the version that is in the archive
+   - always gives you the same kind of tree, rather than giving
+     you the maintainer's git tree (might be strange)
+   - you can push!
+
+
+4 example workflows
+
+
+
+wrinkles
+
+gitignore
+autogenerated files
+
+
+
+
+    all NMUers/sponsors/etc. who like git
+
+
+
+   everyone!
+
+ one common
+
+
+why not x-vcs-git
+
+
+
+coming soon
+
diff --git a/NOTES-2 b/NOTES-2
new file mode 100644
index 0000000..e348a7a
--- /dev/null
+++ b/NOTES-2
@@ -0,0 +1,81 @@
+
+talk for NN mins
+  questions later
+
+========================================
+
+    maintainers maintaining own package
+
+    everyone else
+      NMUers
+      sponsors
+      sponsees
+      teams working on cross-package transitions
+      BSP participants
+      cross-package goals (reproducible builds)
+
+first, 2nd group
+
+
+1 dgit
+
+treat Debian archive as a git repo
+
+  dgit clone
+  dgit fetch
+  git fetch (eg, sponsee's branch)
+  dgit push
+
+
+
+2 what dgit is not
+
+  replacement for
+    git-dpm
+    git-buildpackage
+    git (except when fetching/pushing from/to Debianish archives)
+    pristine-tar
+    git-import-dsc
+    git-import-dscs
+
+  intended to be complementary to existing packaging tools
+
+
+3 example non-maintainer workflows
+
+  push demo ?
+
+  sponsor
+
+  diff experimental vs unstable vs wheezy
+
+
+========================================
+then
+
+  maintainers how can you help
+    pls use dgit push kthxbye
+
+  what's in it for you
+    directly merge/cherrypick nmus, proposed patches
+    your real history visible at browse.dgit.d.o.
+    your downstream dgit users will thank you
+
+
+
+4 who should be using it right now
+
+  source format   git workflow tool      NMUer     maintainer
+                                        sponsor
+                                          etc.
+
+  1.0 native      any                    YES        YES
+
+  1.0 with diff   any                    YES        YES
+
+  3.0 (quilt)     git-dpm                YES        YES
+
+  3.0 (quilt)     raw git                YES        
+
+  3.0 (quilt)     gbp                    YES        TBC
+
-- 
2.30.2