This is an informal poll, conducted with devotee much like the way GR's and
elections are done.

The poll can only be submitted by DD's, and results will be non-anonymous and
published immediately.

Do not erase anything between the lines below and do not change the
choice names.

Please fill in, and send to jeroen-poll-maintainer-field@debian.org. Contact
jeroen@debian.org with questions.

Pointer to discussion:
http://lists.debian.org/debian-devel/2005/05/msg00260.html

Thanks to Matt Zimmerman, Adeodato Simó, and others for help and suggestions

-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
916d57b1-c5bb-4406-b4b1-a6d44fc8f412
[   ] Choice 1: Maintainer field should remain unmodified
[   ] Choice 2: Change Maintainer on source changes only
[   ] Choice 3: Change Maintainer on any change (including binary rebuild)
[   ] Choice 4: Choice 3 + Preserve Maintainer: field as Debian-Maintainer:
[   ] Choice 5: I don't care
[   ] Choice 6: None of the above / Further discussion
-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-

Some remarks with the options:

1. Choose this if you specifically want the Maintainer: field to not be
   changed not even for minor source updates unnecessarily. See also
   option 5

2. If a Debian source package is modified by a derivative relative to the
   source package in Debian, the Maintainer field should be changed to an
   appropriate contact within the derivative community

3. If a Debian source package is rebuilt (modified or unmodified) by a
   derivative, producing new binaries, the Maintainer field should be
   changed to an appropriate contact within the derivative community.

4. See http://lists.debian.org/debian-devel/2005/05/msg00077.html

5. Choose this if you don't mind either way, and consider it accepteable
   that derivatives decide for themselves

--Jeroen