On Tue, Feb 03, 2015 at 06:28:37PM +0100, Richard Hartmann wrote: > Thanks! > > Richard > > Sent by mobile; excuse my brevity.
So it is now a bug against bugs.debian.org with a request for more info. See Don's response below. I'll follow up in #776982. I think I can provide the requested info. But, of course, suggestions from the team will help. 1) pseudo-package name: summit.debconf.org 2) description: Issues regarding the summit.debconf.org software and service 3) maintainer address: debconf-team@lists.debconf.org ? I would not be comfortable with this being just me or any other single person. Bug examples: https://wiki.debconf.org/wiki/Summit#TODO and #DONE TODOs in summit.git (and maybe my local TODO) Those are probably enough, but I can also dig up some relevant mailinglist threads from this year and last. -edrz >From debb...@buxtehude.debian.org Tue Feb 3 14:27:52 2015 Subject: Bug#776982: Request for summit.debconf.org pseudo-package Reply-To: ow...@bugs.debian.org, 776...@bugs.debian.org Date: Tue, 3 Feb 2015 11:23:17 -0800 From: Don Armstrong <d...@debian.org> To: sub...@bugs.debian.org Package: bugs.debian.org Severity: wishlist Control: tag -1 moreinfo Control: submitter -1 Eric Dantan Rzewnicki <e...@zhevny.com> Control: retitle -1 add summit.debconf.org psuedo-package On Tue, 03 Feb 2015, Eric Dantan Rzewnicki wrote: > The DebConf Infrastructure team requests a new pseudo-package, > summit.debconf.org, for use in tracking bugs, feature requests and so > forth for DebConf's instance of the Summit conference management > system. In order to create the psuedopackage, I need the 1) name of the psuedopackage Presumably, that's "summit.debconf.org" in this case. 2) a short description of what the pseudopackage will be used for (suitable for inclusion in https://www.debian.org/Bugs/pseudo-packages) 3) The e-mail address of the maintainer of the psuedopackage who will receive mail related to that mailing list I also like to see an example existing bugs (or e-mails which would have been/will be turned into bugs) which will be reassigned to this pseudopackage once it is created. This is primarily so that I know that the pseudopackage will be used. Finally, I must note that the name of the psuedopackage will never be available for a Debian package in the archive. [Given the name chosen, that seems fine.] -- Don Armstrong http://www.donarmstrong.com What I can't stand is the feeling that my brain is leaving me for someone more interesting. _______________________________________________ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
