+[title]
(PITCH)
The Debian archive is (amongst other things) a version control system.
- Clone (checkout) <=> apt-get source
- Commit+push <=> upload
+Clone (checkout) <=> apt-get source
+Commit+push <=> upload
-But:
+But the archive has no really sensible branching. It history browsing
+is appalling. And it has pretty bad interaction with other VCSs. In
+particular we want to be using git.
- No sensible branching
- history browsing is appalling
- Terrible interaction with other VCSs
- In particular we want to be using git
-
-Solution
+So what to do ?
Well, we might replace it. But the archive is various other things
besides an appallingly bad VCS. And a lot of our co-developers are
With dgit you do all direct source code management in git. As a dgit
user you do not interact with the archive directly.
+[start demo]
+
dgit is particularly useful for NMUers: you can prepare an RC bugfix,
-with full support from git, withut needing to know anything about the
+with full support from git, without needing to know anything about the
package's usual VCS arrangements.
-[demo]
-
dgit also has great potential for downstreams - that is, derivatives
and users who want to modify a package. Having used dgit clone or
fetch, you can merge into your downstream branch. (There are some
infrastructure. We intend to move this to a VM of its own - I've
spoken to DSA (in the person of Tollef) about this.
+[questions etc.]
+
+The package itself is in testing, and you can simply install the same
+.deb on stable if you want.
+
+So that's what I had prepared to say. I think I have time for
+questions.
~ijackson / talk-2014-debconf-dgit.git / blobdiff