Sponsorship in Debian ( Ubuntu-originated packages in Debian ( ubuntu keyring?))
 

[Arno Töll, 2011-05-20]
> So from my experience, in reality you need to seek a new sponsor for
> every upload you want to get into the archive and this takes a lot of
> time and patience. For example I'm currently waiting and seeking since
> over a month to get a RC bug fix and upstream update into unstable until
> Asheesh signaled interest to help me recently.

Did you ask your previous sponsor first? When I see a package I
sponsored on mentors again - I ignore it (if sponsoree is not happy with
my "service", he/she is free to try someone else after all).

When I already sponsored a package, it's easier to sponsor next upload
(as I can assume I checked everything previously and just check the
debdiff output¹ next time)

[¹] not interdif's!
--
http://people.debian.org/~piotr/sponsor


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110520091058.GY17596@piotro.eu">http://lists.debian.org/20110520091058.GY17596@piotro.eu

Sponsorship in Debian ( Ubuntu-originated packages in Debian ( ubuntu keyring?))
 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 20.05.2011 11:10, Piotr Ożarowski wrote:
> Did you ask your previous sponsor first? When I see a package I
> sponsored on mentors again - I ignore it (if sponsoree is not happy with
> my "service", he/she is free to try someone else after all).

Yes. I did. Don't get me wrong, I do not want to blame my former
sponsor(s) as they may have reasons for being unable to help me and I
was happy I found someone helping me at all (that's not self-evident at
all, if you skip through d-mentors).
In fact I was speaking about my situation to several people by now and I
told all of them "thanks for your interest, but let's speak with my
former sponsor(s) first".


> When I already sponsored a package, it's easier to sponsor next upload
> (as I can assume I checked everything previously and just check the
> debdiff output¹ next time)

I know and I provided everyone willing to sponsor me a comprehensive
change log where I explain what I did and why, altogether with a diff
outlining all changes when compared to the previous version.

Moreover I don't want to attract you to my particular case, that's off
topic here and I hope Asheesh will help me soon there. All I wanted is
to outline, the current procedure seems not to work that good in
some/many(?) cases.


- --
with kind regards,
Arno Töll
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJN1jPCAAoJEMcrUe6dgPNt8vwQAMdSDF0HQ1 w4B4Zkyek/ag8U
ztqFSp80h8Kz4teATvagP0KEy7kZJ0bVQohUesiPJYNu3Zszvq c85gVf8Pg/cw+O
PUhXqUtoF9+jmzanmIWL6W8CR4he0AGQDAiOQIKcOu3uHW8uE0 EzuZXsZ7oA0GVZ
H6CMT9WxF5g7IceXNCWgSiSiOBZnDuFPGi452TPsgyECeS6pEx RYq8ZZoSyI5/X/
WSZ0vUl55uWAZRQ4e8kLZR9CMXri2LTjvfNvXVVxcozkfRjirs 1VaklHtSM+1/Pn
6cJ3xMcsYqQLcqnQaLKfxTVeILtnZTLGY3YaLJJ11NhXTHnQjk aQmZbINanyFN/r
ZaDLo7vxFENVHKQHM4oSnmRa8L4lZcLjtQizZuY1LQx3QlZCBL XrQPDEN7QL7KMu
KScId/8Grh/jwNeaPpToOkruKTKoZXOkq57vlbIWmFcxT+QTnAh+xdh3+SOnc POM
6db3Wa5YHlt9CKhcCMCOHkCaPSDjngRoUUGNK/VHYebbek1yKqUeiVX8Q139X3GH
xWo1TcJgTRPHP8StYcrJe262SMYuzo2k4WFSBHJ1RJxQK2j9MZ 0oX+kKpaVlWnY/
ZRqHX66PADu8ANkl5bAX2Si7oxdzdMdIC+uwnk0FGz9vRLcofD eXTDgw80kzjFHr
eU3DHwqeTQSjYz56228H
=61jc
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4DD633C2.2080903@toell.net">http://lists.debian.org/4DD633C2.2080903@toell.net

Sponsorship in Debian ( Ubuntu-originated packages in Debian ( ubuntu keyring?))
 

[Arno Töll, 2011-05-20]
> I know and I provided everyone willing to sponsor me a comprehensive
> change log where I explain what I did and why, altogether with a diff
> outlining all changes when compared to the previous version.

good, let me know when you will need an upload of something Python
related :-)

> All I wanted is
> to outline, the current procedure seems not to work that good in
> some/many(?) cases.

I do not read mentors list that often anymore mostly because a lot of
packages there are not even lintian clean (no to mention that most
packagers didn't read docs... because they're too long and there are too
many of them, "try and error" is just easier...) so when I sponsor a NEW
package now, it usually comes from someone I sponsored already (see
question #4 from my FAQ) or from PAPT/DPMT team member.

I think debexpo could improve the situation thanks to review system
(I'd love to be able to filter requests with at least X positive reviews
or with a positive review from someone I trust, but who is not a DD yet
or from someone I sponsored before and marked as prospective maintainer)
--
http://people.debian.org/~piotr/sponsor


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110520094739.GZ17596@piotro.eu">http://lists.debian.org/20110520094739.GZ17596@piotro.eu