Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-25 Thread Joachim Breitner
Hi, Am Freitag, den 24.05.2013, 15:11 +0800 schrieb Paul Wise: One setting per row sounds like it would waste vertical space so if you can figure out the fluid column system I linked to, that would be good. fluid layout implemented, see the attached patch (and

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-24 Thread Joachim Breitner
Hi, Am Freitag, den 24.05.2013, 11:51 +0800 schrieb Paul Wise: On Thu, 2013-05-23 at 23:27 +0200, Joachim Breitner wrote: thanks! Let me know if my code causes any trouble. From IRC: raphael pabs: always displaying the config div of the ddpo is quite annoying on small screens I'm

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-24 Thread Paul Wise
On Fri, 2013-05-24 at 09:08 +0200, Joachim Breitner wrote: I assume he was talking about the width of the screen (as the height is scrolled for almost every multi-package maintainer anyways), where the settings have caused the scrollbar to appear? I assumed likewise. That’s a valid point,

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-23 Thread Paul Wise
On Mon, May 20, 2013 at 5:31 PM, Joachim Breitner wrote: ok, I’ll work on it as soon as the other patches have been reviewed and merged (to avoid having to re-do the separate table work afterwards). Patches reviewed, merged and deployed. Also thanks for motivating me to get a git-svn

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-23 Thread Joachim Breitner
Hi, Am Donnerstag, den 23.05.2013, 22:06 +0800 schrieb Paul Wise: On Mon, May 20, 2013 at 5:31 PM, Joachim Breitner wrote: ok, I’ll work on it as soon as the other patches have been reviewed and merged (to avoid having to re-do the separate table work afterwards). Patches reviewed, merged

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-23 Thread Paul Wise
On Thu, 2013-05-23 at 23:27 +0200, Joachim Breitner wrote: thanks! Let me know if my code causes any trouble. From IRC: raphael pabs: always displaying the config div of the ddpo is quite annoying on small screens I'm inclined to agree, could you make a patch that hides it by default but

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-20 Thread Joachim Breitner
Hi, Am Montag, den 20.05.2013, 09:20 +0800 schrieb Paul Wise: On Mon, May 20, 2013 at 2:58 AM, Joachim Breitner wrote: I did not yet add an option to show comaintained packages in a separate table. Would that be desirable? I expect that would be useful to some folks. ok, I’ll work on

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-20 Thread Jakub Wilk
* Joachim Breitner nome...@debian.org, 2013-05-19, 20:58: +if (!strcmp($comaint, no)) { +$maintainer_data = Maintainer:; +} else if (!strcmp($comaint, only)) { +$maintainer_data = Co-Maintainer:; +} else { +$maintainer_data = Maintainer and Co-Maintainer:; +

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-20 Thread Joachim Breitner
Hi, Am Montag, den 20.05.2013, 21:11 +0200 schrieb Jakub Wilk: * Joachim Breitner nome...@debian.org, 2013-05-19, 20:58: +if (!strcmp($comaint, no)) { +$maintainer_data = Maintainer:; +} else if (!strcmp($comaint, only)) { +$maintainer_data = Co-Maintainer:; +}

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-19 Thread Joachim Breitner
Hi, Am Sonntag, den 19.05.2013, 11:22 +0800 schrieb Paul Wise: I expect this would be a popular feature. I would suggest making it an option rather than the default though. I just found out that the option already exists: http://qa.debian.org/developer.php?login=nomeatacomaint=no but it is

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-19 Thread Paul Wise
On Sun, May 19, 2013 at 5:31 PM, Joachim Breitner wrote: I would have worked on this myself, but it seems that http://quantz.debian.org/~nomeata/developer.php or http://qa.debian.org/~nomeata/developer.php does not work. If it would it would be easier for occasional contributors to send in

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-19 Thread Joachim Breitner
Hi, Am Sonntag, den 19.05.2013, 11:22 +0800 schrieb Paul Wise: Control: user qa.debian@packages.debian.org Control: usertags -1 + ddpo On Sun, May 19, 2013 at 6:01 AM, Joachim Breitner wrote: As always: Please indicate if you agree with the bug even if you don’t implement it right

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-19 Thread Joachim Breitner
Hi, I did some more cosmetic polishing (I hope I managed to stop before it became bikeshedding). Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-19 Thread Paul Wise
On Mon, May 20, 2013 at 2:58 AM, Joachim Breitner wrote: I did not yet add an option to show comaintained packages in a separate table. Would that be desirable? I expect that would be useful to some folks. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-18 Thread Joachim Breitner
Package: qa.debian.org Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, most of the packages listed on my page at http://qa.debian.org/developer.php?login=nome...@debian.org are team-maintained; when I want to get information about them I check the team’s developer page. But

Bug#708838: developers.php: Hide or sort differently co-maintained packages

2013-05-18 Thread Paul Wise
Control: user qa.debian@packages.debian.org Control: usertags -1 + ddpo On Sun, May 19, 2013 at 6:01 AM, Joachim Breitner wrote: As always: Please indicate if you agree with the bug even if you don’t implement it right away, as it would encourage patches. I expect this would be a popular