Re: RFC: Proposal for template for uploads
--- The package can be found at example.com: - URL: http://example.com/debian/pool/main/f/foo - Source repository: deb-src http://example.com/debian unstable main contrib non-free - dget line: dget http://example.com/debian/pool/main/f/foo/foo_version-revision.dsc debcheckout with revision flag / tag ??? (this might work for git / bzr which support signed revisions / tags) -- With best regards Dmitrijs Ledkovs (for short Dima), Ледков Дмитрий Юрьевич -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFC: Proposal for template for uploads
Dmitrijs Ledkovs dmitrij.led...@gmail.com writes: - dget line: dget http://example.com/debian/pool/main/f/foo/foo_version-revision.dsc debcheckout with revision flag / tag ??? (this might work for git / bzr which support signed revisions / tags) Why have this in the RFS? By the time an RFS is being written, the source package needs to be uploaded anyway, which means there must always be a URL for ‘dget’ to use. Including more information in the RFS is good *only* if that extra information isn't clutter. -- \ “Dvorak users of the world flgkd!” —Kirsten Chevalier, | `\rec.humor.oracle.d | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFC: Proposal for template for uploads
On Sat, 16 May 2009 21:50:10 -0300 Rogério Brito rbr...@ime.usp.br wrote: Dear mentors, I am looking for a sponsor for my package foo. [Include one of:] This package is NEW to Debian. The ITP number is: #bugnumber This is a QA upload that fixes description problems. This is an RC bug fix upload: #bugnumber. This is an update of a package I already maintain. [or some other description of the kind of upload required] Alternatively (or possibly additionally), some reliable method of encoding this at the start of the subject line: RFS: QA: package RFS: NEW: package RFS: RC: package RFS: UPDATE: package (as long as NEW is tied to packages that need an ITP, not just those that will go through the NEW processing queue due to a SONAME bump or a new binary package.) --- Its summary is: * Package name: foo Version : version without Debian revision Debian Revision : Debian revision Upstream Author : Upstream Author em...@address.here.example.com * URL : http://www.example.com/ * License : License here Language: C | C++ | Perl | Python | Any other Section : section Long description: put the long description here --- It builds this/these binary package/s: foo-binary01 - short description 01 foo-binary02 - short description 02 foo-binary03 - short description 03 ... foo-binaryn - short description n --- The latest entry in the Debian changelog is: the description that is contained in your .changes file v.good idea. --- As required, I tested the package against unstable's version of lintian and it (is|is not) lintian clean. list of possible lintian warnings That's a lot better than the current template. --- The package can be found at example.com: - URL: http://example.com/debian/pool/main/f/foo - Source repository: deb-src http://example.com/debian unstable main contrib non-free - dget line: dget http://example.com/debian/pool/main/f/foo/foo_version-revision.dsc --- I would be glad if someone uploaded this package for me. Kind regards, Joe Doe Maintainer -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgp8jA9Lgxr85.pgp Description: PGP signature
Re: RFC: Proposal for template for uploads
[Neil Williams, 2009-05-17] RFS: QA: package RFS: NEW: package RFS: RC: package I like this. I'd add version, though (see below) RFS: UPDATE: package I ask my sponsorees to add a version in Subject field as well, this way I know if it's new upstream release or an update (so UPDATE tag is not needed) and I can distinguish different sponsorship requests (I remove the whole thread from my Debian/RFS mailbox once all problems are resolved and package is uploaded, sometimes package is uploaded without minor changes I asked for so old thread remains in the mailbox) -- http://people.debian.org/~piotr/sponsor signature.asc Description: Digital signature
Re: RFC: Proposal for template for uploads
On Sun, May 17, 2009 at 10:33:07AM +0100, Neil Williams wrote: On Sat, 16 May 2009 21:50:10 -0300 Rogério Brito rbr...@ime.usp.br wrote: Dear mentors, I am looking for a sponsor for my package foo. [Include one of:] This package is NEW to Debian. The ITP number is: #bugnumber This is a QA upload that fixes description problems. This is an RC bug fix upload: #bugnumber. This is an update of a package I already maintain. [or some other description of the kind of upload required] And when you're listing bug numbers, please put a summary of what the bug is. Make it *easy* for the sponsor to say yes, rather than meh, too busy, might look at it later. - Matt -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFC: Proposal for template for uploads
Hi.
After some time looking at some commonly complained lack of details in
requests for sponsoring, I took a few minutes and came up with the
template attached to this mail, based on the comments on top of what
mentors.d.n suggests.
This is all the information that I would like to know if I were
sponsoring packages from someone else and I think that others could,
perhaps, appreciate it.
The separation of parts of the document is also something to get more
legibility.
OK, I will stop now and just let you see it. Comment it. Modify
it. Adopt it. Trash it. It is yours.
Regards,
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
Dear mentors,
I am looking for a sponsor for my package foo.
---
Its summary is:
* Package name: foo
Version : version without Debian revision
Debian Revision : Debian revision
Upstream Author : Upstream Author em...@address.here.example.com
* URL : http://www.example.com/
* License : License here
Language: C | C++ | Perl | Python | Any other
Section : section
Long description:
put the long description here
---
It builds this/these binary package/s:
foo-binary01 - short description 01
foo-binary02 - short description 02
foo-binary03 - short description 03
...
foo-binaryn - short description n
---
The latest entry in the Debian changelog is:
the description that is contained in your .changes file
---
As required, I tested the package against unstable's version of lintian
and it (is|is not) lintian clean.
list of possible lintian warnings
---
The package can be found at example.com:
- URL:
http://example.com/debian/pool/main/f/foo
- Source repository:
deb-src http://example.com/debian unstable main contrib non-free
- dget line:
dget http://example.com/debian/pool/main/f/foo/foo_version-revision.dsc
---
I would be glad if someone uploaded this package for me.
Kind regards,
Joe Doe Maintainer
Re: RFC: Proposal for template for uploads
Rogério Brito rbr...@ime.usp.br writes: After some time looking at some commonly complained lack of details in requests for sponsoring, I took a few minutes and came up with the template attached to this mail, based on the comments on top of what mentors.d.n suggests. I have done a brief scan of the proposed template, and I very much approve. Implementing it as-is would already be a significant improvement over the current template. Thank you for this work. -- \ “A lot of people are afraid of heights. Not me, I'm afraid of | `\ widths.” —Steven Wright | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
