more TODO cut/paste from email

1 files changed, 41 insertions, 0 deletions

diff --git a/TODO b/TODO
index 3230e06..226830d 100644
--- a/TODO
+++ b/TODO
@@ -89,3 +89,44 @@ General stuff:
 Once packages.d.o links to it, this really needs announcing widely; LWN
 at the least, might want to talk about it on the debian-publicity list
 first though.
+
+
+
+from joss:
+
+
+I think you could get bonus points for using different colors for
+co-maintained packages – although I don’t need this personally, I think
+this will be appreciated by others.
+
+...
+
+Patches in the quilt series and dpatch formats, and sometimes those in
+the simple-patchsys format as well, have often comments at the top of
+the file. It would be very nice to see them in the patch summary,
+together with the diffstat.
+
+
+
+from azeem:
+
+
+there are some maintainer overview pages like
+http://patch-tracking.debian.net/email/pkg-gnome-maintainers@lists.alioth.debian.org 
+have a high number of packages.  However, not all of them have patches
+to the upstream source in them and there is no indication on the
+overview page for which this is the case.  Thus upstream people have to
+click on every package/version link and check for themselves.  On top of
+that, it is not immediately clear that there are no upstream patches and
+people might just click on the Debian dir patch and wonder, see
+http://www.mail-archive.com/desktop-devel-list@gnome.org/msg14030.html
+
+I propose to make it visually clear that a given package/version has no
+upstream patches by either coloring the link differently or somehow
+otherwise differentiating the two.  A useful heuristic could be:
+
+15:02 < seanius> so basically you mean to look for any changes including
+        ".", excluding "./debian", and including "./debian/patches"
+
+Everything else is probably broken packaging and not worth the hassle.
+