pkg kde talk - Sep 2005 - News about our lists (Re: [Pkg-kde-bugs-fwd] Bugzilla Change Password Request)

> You (or someone impersonating you) has requested to change your Bugzilla
> password.  To change your password, visit the following link:
> http://bugs.kde.org/token.cgi?a=cfmpw&t=8lyjUxJ4
  This was me at aKademy. You may remember this thread:

    http://lists.alioth.debian.org/pipermail/pkg-kde-talk/2005-June/000241.html
    http://lists.alioth.debian.org/pipermail/pkg-kde-talk/2005-June/000245.html

  I privately mailed Stephan a week ago, saying this:

-----------------------------------8<-------------------------------------------
> > Out of curiosity, why was it disabled in the first place?
> We don''t allow anonymous changes to bugs.kde.org (list accounts
allow you to
> resend their password so everyone can login via them and mess reports up).
  I understand this. Still, I am very interested on having a "role
  Bugzilla account" for the Debian KDE maintainers to use, and would
  like to discuss under which circumstances would you allow a
  full-access account that is also a list.

  Would any of these options be enough? Which one would you prefer?:

    - a public list like now, but the traffic of which goes to a filter
      first, which would redirect password resends or similar messages
      to the list administrator instead.

    - a list with moderated subscription and non-public archives; only
      the Debian KDE maintainers and a couple collaborators doing bug
      triage and forwarding would be allowed to subscribe.

  In either case, access to the password would be (as it''s always been)
  restricted to the strictly necessary people.

  Also, I am quite interested in knowing (given the promise of
  restricted acceess given above) if this account could gain access to
  the enhanced bug reporting & manipulation interface that people with a
  svn account have. In Debian we receive a lot of bug reports against
  KDE packages, and we (the packagers) are trying to figure out ways to
  improve the forwarding of these; this would be a small help.

  Christopher Martin and myself will be in M?laga. If after this mail
  you still have some concerns, perhaps you could find some minutes to
  spend with us there to discuss this?

----------------------------------->8-------------------------------------------

  And yes, in M?laga we were able to address this. Now the list will
  send any mail from bugzilla-admin-daemon@ktown.kde.org to the list
  owner (Christopher and myself at the moment).

  To use the "enhanced interface" I mention above, go to:

    https://bugs.kde.org/enter_bug.cgi

  Which results in sensibly faster bug reporting/forwarding.

  The password is the same now as it was in the past. As a reminder, it
  is stored in:

   
haydn:/var/lib/gforge/chroot/home/users/adeodato/pkg-kde/home/bugs-fwd-passwd

  Josh, I''m CC''ing you to mention that, if you''re
interested in using
  the pkg-kde-bugs-fwd@l.d.a.o Bugzilla account to forward some bugs
  upstream, I''m more than willing to give you the password. :)

                                 * * *

  More things. As I said, Christopher and me are now the list owners.
  I''ve changed some small details, like making the list footer shorter.
  I''d like very much to remove the [LABEL] that Mailman puts in the
  subject, so if somebody would strongly prefer for it to stay, please
  speak up now (note that lists.d.o lists don''t have such label).

  For -commits, I''ve made things so that only mail from @costa.d.o
  addresses is accepted. The Reply-To header is set to -talk, and if
  somebody still sends non-commit mail there, they''ll get a notice
  saying mail was rejected and that it should be sent to -talk instead.

  Cheers,

-- 
Adeodato Sim?
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
 
Kindness is a language which the deaf can hear and the blind can read.
                -- Mark Twain