Start new release and annotate with bugs being fixed.

[youtubedl] / debian / README.source

diff --git a/debian/README.source b/debian/README.source
index 6a942b0861ba47068bed5bf780b3751638fec772..f0cea40f7538e60ea8a9300c151d5beb0fea9ca4 100644 (file)
--- a/debian/README.source
+++ b/debian/README.source
@@ -1,12 +1,14 @@
 Debian packaging for youtube-dl
 -------------------------------
 
+# Basic building of the package
+
 A quick summary of how one can update the Debian packaging of youtube-dl is
 to, assuming that one already has the packages `devscripts`,
 `git-buildpackage`, and `pristine-tar` installed:
 
-    gbp clone --all ssh://git.debian.org/git/collab-maint/youtube-dl.git
-    cd youtube-dl
+    gbp clone --all https://github.com/rbrito/pkg-youtube-dl
+    cd pkg-youtube-dl
     gbp import-orig --pristine-tar --uscan
     [ Make here some adaptations, like updating debian/patches, if needed ]
     gbp buildpackage --git-pristine-tar
@@ -15,4 +17,33 @@ These are the important steps and may need to be changed according to
 deviations, say, in the release process of upstream releases (e.g., if
 upstream changes the location where the tarballs reside).
 
- -- Rogério Brito <rbrito@ime.usp.br>, Mon, 18 May 2015 02:17:12 -0300
+# Maintaining the repository
+
+I keep my development of the package (in particular, the master branch) at
+GitHub and I usually try to have my changes there, since I am not always
+with my SSH/GPG keys at hand.
+
+For the benefit of the co-maintainers, I keep a backup copy of the changes
+at git.debian.org, where, due to said keys not being available at all times,
+I can't push my changes, which leads, sometimes to my GitHub repository to
+be ahead of the Debian mirror.
+
+I prefer that, if possible, when working with the master branch:
+
+* Please, check if I don't have changes already made at:
+
+      https://github.com/rbrito/pkg-youtube-dl
+
+* People send me pull requests there
+
+* If they are not comfortable with the use of GitHub for any kind of reason
+  (political, ideological etc.), that they send me patches via email (git
+  send-email is best).
+
+  This can be sent to my personal email or to the Debian BTS. I'm flexible.
+
+Of course, if it is not possible to coordinate in the way described above,
+alas... :-(
+
+
+ -- Rogério Brito <rbrito@ime.usp.br>, Thu, 19 Oct 2017 16:19:25 -0200