karenetheridge/gist:45fd1b8271a45b93f65d62d53d706365

## gistfile1.txt
11:08 < ether> I have a message from the Perl QA Hackathon!  Could System::Info be made into a debian package?  is there a proper channel for making this request?
11:10 < Dom> the official way is to email the bug tracking system with an 'RFP'
11:10 < Dom> using reportbug on a debian system, or https://www.debian.org/devel/wnpp/#l2
11:10 < Dom> X-Debbugs-Cc: [email protected]
11:11 < Dom> or, persuade someone here to take care of it :)
11:15 < axhn> Or: Learn the packaging skill and find a sponsor who will do the upload
11:15 < Dom> quite
13:17 < carandraug> ether: did you open a RFP?
13:19 < ether> did not see the response until just now; I shall do so
13:19 < ether> ..or have the person making the request do so :)
13:27 < carandraug> ether: I could give it a go if someone there writes the long description
15:38 < carandraug> ether: I got it packaged, and autopkgtest passes. If whoever wants it packaged bothers to write a long description...
16:01 < ether> from #pts:  16:00 < sawyer> ether: Can you tell them we all love them? :)
16:01 < ether> we don't thank you enough for what you do
16:21 < ether> carandraug: ok, I've kicked Tux to write a description :)
17:06 < carandraug> ether: I got my pound of flesh from you too some years ago, on the many perl support channels
17:06 < carandraug> ether: the guidelines for long description are 'Long description should mention the main module name to make searching easier.  This is often used at the start of the long description.'
17:07 < carandraug> and for short description I wrote 'package·to·obtain·basic·system·information'
17:08 < carandraug> also, our tools pick whatever text is on Description section of the module with the same name as the distribution. If someone writes one for us, they might want to use there too.
	11:08 < ether> I have a message from the Perl QA Hackathon! Could System::Info be made into a debian package? is there a proper channel for making this request?
	11:10 < Dom> the official way is to email the bug tracking system with an 'RFP'
	11:10 < Dom> using reportbug on a debian system, or https://www.debian.org/devel/wnpp/#l2
	11:10 < Dom> X-Debbugs-Cc: [email protected]
	11:11 < Dom> or, persuade someone here to take care of it :)
	11:15 < axhn> Or: Learn the packaging skill and find a sponsor who will do the upload
	11:15 < Dom> quite
	13:17 < carandraug> ether: did you open a RFP?
	13:19 < ether> did not see the response until just now; I shall do so
	13:19 < ether> ..or have the person making the request do so :)
	13:27 < carandraug> ether: I could give it a go if someone there writes the long description
	15:38 < carandraug> ether: I got it packaged, and autopkgtest passes. If whoever wants it packaged bothers to write a long description...
	16:01 < ether> from #pts: 16:00 < sawyer> ether: Can you tell them we all love them? :)
	16:01 < ether> we don't thank you enough for what you do
	16:21 < ether> carandraug: ok, I've kicked Tux to write a description :)
	17:06 < carandraug> ether: I got my pound of flesh from you too some years ago, on the many perl support channels
	17:06 < carandraug> ether: the guidelines for long description are 'Long description should mention the main module name to make searching easier. This is often used at the start of the long description.'
	17:07 < carandraug> and for short description I wrote 'package·to·obtain·basic·system·information'
	17:08 < carandraug> also, our tools pick whatever text is on Description section of the module with the same name as the distribution. If someone writes one for us, they might want to use there too.