[00:29] <rickspencer3> bdmurray: thanks
[00:29] <rickspencer3> in fact a work around was there
[00:30] <rickspencer3> 1. create a fresh bug: bug = self.launchpad.bugs[bug.id]
[00:30] <bdmurray> rickspencer3: right that's what I said ;-)
[00:30] <rickspencer3> 2. add a new tag list: bug.tags = bug.tags + ['needs-bug-squad']
[00:30] <rickspencer3> and then you can save it
[00:30] <rickspencer3> yeah, I guess I was saying "thanks"
[00:30] <bdmurray> okay, you're welcome!
[00:31] <rickspencer3> and putting the info here in case other people are interested
[02:20] <bac> hi wgrant
[02:24] <wgrant> bac: Hi.
[02:25] <wgrant> I just realised that Blueprint's UI has been redone, so things might have changed.
[02:25] <bac> wgrant: i'm still confused about bug 304627  -- looking at the code a private bug should not be displayed at all
[02:25] <wgrant> bac: Let me check on staging.
[02:25] <bac> wgrant: ah, ok
[02:25] <bac> wgrant: if you can find a representative blueprint please add it to the bug.  otherwise it looks like this is no longer an issue
[02:26] <wgrant> bac: Sure. I'll close it if I can't reproduce now.
[02:26] <bac> 'private bug' *does* appear in the +linkbug page but that's pretty trivial
[02:27] <wgrant> bac: ah, yes, the portlet no longer shows up on the main blueprint page. That's the portlet in question, but since it doesn't show up on the main page, it's not important.
[02:28] <bac> wgrant: ok, great
[02:28] <wgrant> bac: Sorry about that - I forgot about the redesign a couple of months ago.
[03:39] <wgrant> I never got bugmail for my dupe unmarking or comment on bug #378876 a couple of hours ago.
[03:44] <mwhudson> wgrant: bugmail is lagging
[03:49] <wgrant> mwhudson: I got other stuff from around the same time with only 20 minutes of lag in the Received trace.
[03:50] <mwhudson> wgrant: i guess that makes you lucky? :)
[03:50] <mwhudson> i don't know much more than you, IOW
[03:50] <wgrant> mwhudson: Heh. OK. I'll wait.
[04:06] <The_Tick> I'm trying to find all tickets on my project without a milestone, is there a way to do that?
[04:20] <jml> The_Tick: I don't think there's a way to do that on the UI.
[04:20] <jml> The_Tick: you might be able to write a script to do so (see https://help.launchpad.net/API)
[04:21] <wgrant> The API for IBugTarget.searchTasks isn't that great.
[04:21] <The_Tick> ugh
[04:21] <wgrant> I can't work out what those two milestone fields do,.
[04:22] <The_Tick> the only thing we're using lp for is a ticket logger
[04:22] <The_Tick> and I'm not sure if it's that great for it now
[04:22] <wgrant> The_Tick: It looks like you can order a bug search by milestone.
[04:22] <The_Tick> ooooh
[04:22] <jml> searching for "bugs without <thing>" has always been a weakness of Launchpad's IMO.
[04:22] <wgrant> Wasn't bug search meant to be totally redone for 3.0?
[04:22] <The_Tick> ok I go to bugs
[04:23] <jml> not that I know of :)
[04:23] <wgrant> The_Tick: If you go to the bug listing, and order by milestone, you'll find the bugs without a milestone at the end.
[04:23] <jml> wgrant: but hey, the plans are all public: https://dev.launchpad.net/VersionThreeDotO/Bugs
[04:23] <wgrant> To have them appear first, just replace the 'milestone' in the URL with '-milestone'
[04:23] <The_Tick> ya, I'm trying to find a view with milestones on the results
[04:24] <wgrant> The_Tick: A milestone is shown as a clockish-thing to the right of the summary.
[04:24] <wgrant> I'm not sure why they don't show the actual milestone name there.
[04:24] <The_Tick> wow, that's lame
[04:24] <The_Tick> thanks
[04:24] <wgrant> jml: There are a few search things there.
[04:24] <wgrant> Including customisable columns, which would resolve The_Tick's latest complaint.
[04:25] <wgrant> I guess none of them will make it, though.
[04:25] <The_Tick> I'm used to trac really
[04:25] <The_Tick> so just learning what this can and can't do is useful
[04:26] <wgrant> I suspect that things it can't do would be considered bugs.
[04:26] <The_Tick> what's the preferred way to complain nicely? :)
[04:26] <wgrant> https://bugs.launchpad.net/launchpad/+filebug
[04:27] <jml> The_Tick: also, the launchpad-users list can be a good proving ground for proto-bugs
[04:27] <wgrant> That too.
[04:27] <The_Tick> I'll just file bugs
[04:27] <The_Tick> we're a small project in the scope of things for you guys
[04:28] <jml> I've been pushing for feature parity with trac for some time now :)
[04:28] <The_Tick> dude trac's awesome except for the whole hosting it yourself thing
[04:28] <wgrant> Hopefully things will improve in a few months when fixes aren't entirely driven by Canonical.
[04:28] <jml> oh I don't know about that
[04:28] <The_Tick> and if lp used hg we'd use source control on lp too
[04:28] <wgrant> IMO Trac really sucks.
[04:28] <The_Tick> how so?
[04:29] <wgrant> The bug tracker seems clunky and generally painful. I'm not quite sure what exactly is wrong with it, though.
[04:29] <The_Tick> it is out of the box for end users
[04:29] <jml> it has a couple of really nice things
[04:29] <The_Tick> but then you go get the simpleticket plugin
[04:29] <The_Tick> the roadmap is really the nicest thing
[04:29] <The_Tick> and the timeline
[04:29] <wgrant> The timeline is something Launchpad is really lacking.
[04:29] <The_Tick> we really customized it for adium
[04:30] <wgrant> It was a pleasant surprise to find that Google Code had one. It's very useful.
[04:30] <The_Tick> ya, I have no clue what my growl project on lp is doing without it
[04:30] <The_Tick> ya, that was the biggest complaint they had
[04:30] <wgrant> I imagine you could probably rework the existing karma system to do a timeline in LP.
[04:37] <ajmitch> wgrant: karma for a person will only show a limited set of actions, won't it?
[04:37] <ajmitch> at least if you're just trying to reconstruct a timeline from karma
[04:39] <wgrant> ajmitch: It's not currently comprehensive, but it's not too bad. And there are bugs filed about tracking more things.
[05:17]  * ausimage wonders if buildd team member is da house?
[05:17] <ausimage> I have an issue building a package on my ppa that DOES build on my box :/
[05:25] <wgrant> ausimage: perhaps link to the build log?
[05:25] <ausimage> http://launchpadlibrarian.net/27718971/buildlog_ubuntu-jaunty-i386.soovee_1.06ppa2_FAILEDTOBUILD.txt.gz
[05:25] <ausimage> sorry :S
[05:26] <ausimage> wgrant: it says it can't find a file... that does exist and does appear in the local built package
[05:27] <wgrant> That's very probably a bug in the package. Possibly a race of some kind.
[05:27] <wgrant> How were you building it locally?
[05:28] <ausimage> dpkg-buildpackage -us -uc
[05:29] <ausimage> thats command I used
[05:29] <wgrant> That doesn't count. You need to use pbuilder or sbuild.
[05:29] <ausimage> ahhh...
[05:29] <wgrant> Otherwise you're building in an unclean environment.
[05:29] <wgrant> It might have missing build-dependencies, for example.
[05:30] <spm> wgrant: for this newbie builder here. which would you recommend of those two? or 6 of 1... ?
[05:30] <ausimage> yeah...
[05:30] <wgrant> spm: pbuilder unless you use LVM.
[05:30] <spm> 'k. ta!
[05:31] <wgrant> sbuild is much better and more like what the buildds use (failures will sometimes show up in sbuild and on the buildds, but not in pbuilder), but it's more heavyweight to set up.
[05:31] <ausimage> pbuilder... I will look at that tommorrow... and see if that helps
[05:31] <wgrant> ausimage: I can reproduce the build failure locally in sbuild. Not sure about pbuilder.
[05:32] <wgrant> So, it's not a buildd problem.
[05:32] <wgrant> But let me just have a look for anything obvious.
[05:32] <ausimage> k... must be an unclean thing...
[05:32] <wgrant> I get the same with just a 'dpkg-buildpackage -b' on my system.
[05:32] <wgrant> Ahhh.
[05:32] <wgrant> I see.
[05:32] <wgrant> The symlinks are borked.
[05:33] <ausimage> yeah that was at the back of my mind :/
[05:33] <wgrant> wgrant@irranat:/tmp/soovee-1.06ppa2$ ls -l svterm
[05:33] <wgrant> lrwxrwxrwx 1 wgrant wgrant 38 2009-06-10 14:32 svterm -> /media/stuff102/DBsite/pbparser/soovee
[05:34] <ausimage> wgrant: my packaging skills seem to kill revu too ;)
[05:34]  * ausimage fixes symlinks
[05:35] <wgrant> ausimage: Impressive. Although that box has a habit of killing itself sometimes...
[05:35] <ausimage> really?
[05:37] <ausimage> wgrant: I pushed a new package with the fixed symlinks
[05:37]  * ausimage crosses fingers
[05:38]  * wgrant will check in 3 minutes.
[05:38] <ausimage> cool
[05:42] <wgrant> We'll see in a few seconds...
[05:42] <wgrant> Failed again.
[05:42] <wgrant> Same error.
[05:43] <ausimage> wgrant: how can I symlink then ?
[05:43] <wgrant> er, same issue. There are absolute paths in the symlinks.
[05:43] <wgrant> What are they meant to link to?
[05:43] <wgrant> the 'soovee' binary in the root of the package?
[05:44] <ausimage> I have a single script that can read its name
[05:44] <wgrant> ln -s soovee svterm
[05:44] <wgrant> ln -s soovee svview
[05:44] <wgrant> How were you linking them before?
[05:45] <ausimage> with nautilus drag :/
[05:45] <wgrant> Oh.
[05:47]  * ausimage did the links how you should and pushed a new package 
[05:48] <ausimage> *showed
[05:48] <wgrant> OK. Let's see how this works.
[05:49] <ausimage> wgrant: I checked the dif between nautilus and ln -s *
[05:50] <ausimage> apparently nautilus uses the full path... and ln does not
[05:50] <wgrant> ausimage: ln uses whatever you tell it to - it will use an absolute path if you give it one, which is necessary sometimes.
[05:51] <ausimage> ahh
[05:52] <wgrant> dh_install: soovee-common missing files (debian/tmp/usr/lib/python2.6/dist-packages/soovee_app/pages/*), aborting
[05:52] <wgrant> It installed into python2.6/site-packages, though this is on Karmic...
[05:53] <ausimage> hmm not sure why that happened?
[05:53] <jrick> Somebody just said
[05:53] <wgrant> But it worked on Jaunty.
[05:53] <wgrant> So possibly some Karmic breakage.
[05:53] <jrick> sorry about that
[05:53] <wgrant> ausimage: So, it's fixed!
[05:54] <ausimage> it is :)
[05:54] <ausimage> cool
[05:54] <ausimage> now if only revu could stomach the package. it may have a chance at karmic, wgrant ;)
[05:55] <wgrant> ausimage: The first problem with that package is that it's native. That'll not be accepted into Ubuntu.
[05:55] <wgrant> But this is #ubuntu-motu talk.
[05:55] <ausimage> native?
[05:55] <wgrant> It has just a .dsc and .tar.gz, rather than a .dsc, .diff.gz and .orig.tar.gz.
[05:56] <wgrant> (and no '-' in the version)
[06:08] <ahn> Does VCSimports from a CVS repository preserve the full history during the import?
[06:09] <wgrant> ahn: Yes.
[07:58] <wgrant> One of my launchpadlib scripts died with a 401 at 06:13 UTC - but it worked for the three minutes before that, and works again now.
[07:58] <wgrant> I've not touched any of my OAuth tokens lately.
[08:00] <spm> wgrant: ~ 45 mins ago right?
[08:01] <wgrant> spm: Yes.
[08:10] <spm> wgrant: hrm. nothing obvious is showing up. none of the immediate suspects at any rate. :-/
[08:12] <wgrant> spm: Damn.
[08:12] <wgrant> spm: Should I file a bug, or just hope it doesn't happen again?
[08:13] <spm> hmmm. yes.
[08:14] <spm> my heart says file a bug, the head says we don't really have much beyond a transient to work with.
[08:14] <wgrant> Exactly.
[08:15] <spm> hmm. keep an eye out. if you see another soonish (days), get the UTC time and report them both. my 2c.
[08:16] <wgrant> Sure. Thanks.
[08:35] <wgrant> mwhudson: I finally got that bugmail I asked about.
[08:38] <wgrant> noodles775: In addition to bug #314370, it'd be easier for users to realise they need to select a different distroseries if it used the distroseries version instead of long codename.
[08:38] <wgrant> 'Ubuntu 9.04' is more recognisable and correct than 'The Jaunty Jackalope'
[08:39] <noodles775> wgrant: definitely. There's a bug somewhere to re-label distroseries throughout LP...
[08:46] <wgrant> noodles775: What does your 314370 branch do if it can't detect the distroseries? Select the latest one, like is done now?
[08:48] <noodles775> wgrant: if the user-agent distroseries doesn't match any of the valid series, yes, it uses the latest distroseries that has sources in the archive.
[08:49] <dhruba> Hi, I have installed Ubuntu Server 9.04 with NTP, DHCP, DNS and OpenLDAP on it. I have created a few users through phpLDAPAdmin. But while trying to login from the Ubuntu Client 9.04, it is giving a problem that the Home directory is not present. Again, it is giving that it is ignoring .dmrc file. But even through ls -la I could not find any .dmrc file
[08:49] <wgrant> noodles775: Would it be better to default to nothing instead?
[08:49] <wgrant> dhruba: You want #ubuntu, I suspect.
[08:50] <wgrant> noodles775: The detection should get most people, but then people are going to get lazy and forget to change it. Then when the detection fails, they're going to get the wrong packages.
[08:51] <noodles775> wgrant: good point... yep, that would be better...
[08:53] <wgrant> noodles775: Shall I file a bug?
[08:54] <noodles775> wgrant: yes, that would be great (as the branch has just landed as is). Thanks!
[08:55] <dhruba> Hi, I have installed Ubuntu Server 9.04 with NTP, DHCP, DNS and OpenLDAP on it. I have created a few users through phpLDAPAdmin. But while trying to login from the Ubuntu Client 9.04, it is giving a problem that the Home directory is not present. Again, it is giving that it is ignoring .dmrc file. But even through ls -la I could not find any .dmrc file
[08:55] <wgrant> noodles775: Plus it needs new UI changes and review and blah, so it would delay that branch quite a bit...
[08:55] <wgrant> dhruba: As i suggested earlier, you want to ask that in #ubuntu - this channel is for Launchpad, not Ubuntu, support.
[08:55] <noodles775> wgrant: exactly :)
[09:07] <wgrant> noodles775: Bug #385485
[09:07] <noodles775> Cheers wgrant
[09:32] <wgrant> bigjools: I just responded to that bug, but why don't you like a few percent of uses with alternate browsers having to select it manually?
[09:56] <maxb> 08:38 < wgrant> 'Ubuntu 9.04' is more recognisable and correct than 'The Jaunty Jackalope'
[09:56] <maxb> 08:39 < noodles775> wgrant: definitely. There's a bug somewhere to re-label distroseries throughout LP...
[09:56] <maxb> Yuck, I'd hate that
[09:56] <maxb> I find names vastly more recognizable and memorable than numbers
[09:57] <wgrant> maxb: You're not Joe Average User, though.
[09:57] <wgrant> Codenames aren't mentioned in more than a couple of places in releases of Ubuntu.
[09:57] <wgrant> They're not even on the default Firefox home page any more.
[10:00] <noodles775> or here http://www.ubuntu.com/
[10:01] <wgrant> Or releases.u.c.
[10:01]  * wgrant checks ShipIt CDs.
[10:01] <wgrant> Not there, either.
[10:01] <wgrant> So I don't know the codename unless I check sources.list.
[10:06] <persia> The codename is also present as part of the .disk/info file on the CDs, and in /etc/lsb-release
[10:15] <wgrant> persia: True, but I think users are even less likely to look there than sources.list.
[10:15] <persia> wgrant, I don't expect users to look in either of those places, but I do expect software to do so, and I'm not sure that the software won't present those strings to users.
[10:16] <wgrant> persia: Perhaps.
[10:17] <wgrant> But Ubuntu 9.04 is the official one, so Launchpad should probably use it in user-facing places.
[10:17] <persia> So, I agree with the general idea that "Ubuntu 9.04" is more recognisable and correct than "Jaunty Jackalope", but I'm unsure that it's accurate to say that the names aren't presented anywhere.
[10:17] <persia> Yes, very much so.  I mean to provide data, not to disagree with the intent.
[10:17] <wgrant> Right.
[10:52]  * wgrant thwacks Launchpad a bit for mandating authentication at some API URLs and not others.
[10:53] <persia> wgrant, Is the auth mandate not consistent with the data collection from the web UI?
[10:53] <wgrant> persia: Hm?
[10:54] <wgrant> they seem to be gratuitously making launchpadlib users authenticate.
[10:54] <wgrant> But a few lines of code later, it all magically works without an OAuth token.
[10:55] <persia> wgrant, Ah.  It's the gratuitous bit that I was asking about.  There's a larger and larger amount of information that seems to be user-customised, and I'd expect this to be reflected in the API, so auth would be mandated.
[10:55] <persia> On the other hand, if the information collected never contains private information, then I suppose that's annoying (or if one can collect the same information without an auth token)
[10:56] <wgrant> The browser UI already makes use of the API anonymously, which is how I realised launchpadlib could too.
[10:58] <persia> Ah.
[11:17] <maxb> It is rather irksome that you need to authenticate even to see things that you can screenscrape without a login
[11:24] <mwhudson> wgrant: hurrah
[12:37] <ricemark20> i need gwibber 1.0.1, 1.0.2 does not work with twitter client
[12:59] <cumulus007> Hi, I was wondering if the translations in Ubuntu get synchronized with Launchpad during the lifetime of a release?
[13:00] <cumulus007> and also, will translations from Jaunty be ported to the Karmic branche when there are no changes in the source?
[13:02] <dpm> cumulus007: I think you might mean the other way round: translations done through the Launchpad interface are released in Ubuntu regularly through language packs -> https://wiki.ubuntu.com/TranslatingUbuntu/LanguagePacks
[13:03] <cumulus007> hm, so the language packs are being updated during the lifetime of a release?
[13:03] <dpm> cumulus007: yes, although for Jaunty we have not had any updates yet
[13:04] <dpm> cumulus007: and yes, translations from Jaunty will be ported over to Karmic.
[13:04] <cumulus007> okay, that's what I wanted to know :)
[13:06] <dpm> good :)
[15:16] <fta> hi, anyone to consider a request for more space in a PPA? https://answers.edge.launchpad.net/soyuz/+question/73791
[15:17] <adeuring> fta: I have asked our admins to address your request
[15:17] <fta> thanks
[16:00] <ion_> Hi
[16:00] <ion_> What’s the actual effect of the “affects me too” thing? Is there a public list of people affected by each bug or something like that?
[16:02] <intellectronica> ion_: you can only get the list of affected users using the API for now. it's being used when collecting statistics to decide which bugs are most important to work on
[16:03] <ion_> Alright
[16:03] <intellectronica> there's still no visible ui for that. when  there will be one, it is likely to be a way of ordering bugs
[16:03] <ion_> Wouldn’t the list of subscribers be somewhat equivalent for a rough number of people who have an interest to the bug?
[16:13] <intellectronica> ion_: not really. people who have an interest in the bug are the people subscribed to the bug. people affected by the bug are people who actually get the bug on their system
[16:15] <stefanlsd> Im looking at launchpadlib.  Is there some documentation what constitutes private data and non-private data?
[16:15] <persia> stefanlsd, Loosely put, private data is bugs, teams, blueprints, branches, etc. that have the "private" flag set.
[16:16] <intellectronica> stefanlsd: private data is data you can't see :)
[16:17] <intellectronica> stefanlsd: there is no general privacy mechanism in launchpad. for bugs, you can set the private attribute of the bug to true, and then only people subscribed to the bug can see it
[16:19] <stefanlsd> intellectronica, persia: so - change non-private data - 'The application will be able to access Launchpad on your behalf for reading and changing non-private data.- this would mean the application has access to change anything (bugs, teams, blueprints etc) not marked as private?
[16:19]  * persia defers to someone who actually knows about the internals
[16:20] <intellectronica> stefanlsd: basically, launchpadlib, authenticating as you, gets exactly the same permissions you would get working with the web interface
[16:23] <stefanlsd> intellectronica: i get that (like launchpadlib wont be able to do something i wouldn't be able to do through the web interface, i suspect the authentication token stuff is to be more restrictive for the application). Although im still not entirely sure what this restricts... i guess the main distinction is read or change. and then private or non-private.
[16:24] <intellectronica> stefanlsd: the most important thing to remember is that you get exactly the same permissions using launchpadlib as you do with the web interface. that's all there is to it, really
[16:25] <stefanlsd> intellectronica: ok, i can accept that, but then why have this whole token authorization issue?
[16:25] <james_w> stefanlsd: the distinction for private/non-private is useful for when you are using someone else's script
[16:26] <james_w> you can choose "non-private" then, and be sure that even if the script is malicious they still couldn't access anything they couldn't access through the web UI authenticated as themselves
[16:26] <james_w> though they may still be able to make changes that they couldn't make as themselves
[16:26] <intellectronica> stefanlsd: i don't understand. that's just how it's implemented
[16:28] <stefanlsd> ok. thanks guys. im gonna play more with it and see if i can understand it better through implementation
[17:38] <fta> PPA exceeded its size limit (7628.00 of 7120.00 MiB).. again
[17:38] <fta> i'm getting tired of this, all my ppas are full :(
[17:39] <ion_> Hehe
[17:39] <fta> too bad for firefox 3.5 b99
[17:39] <elmo> fta: you should totally ask for a refund
[17:41] <ion_> fta: Couldn’t you get the new Firefox directly into karmic?
[17:41] <fta> needs some staging first
[17:41] <maxb> Re the earlier conversation, is it documented anywhere exactly what the API considers "private information"?
[17:41] <ion_> Ah, never mind, didn’t think of the ≤jaunty audience.
[17:41] <fta> and i'm still waiting for https://answers.edge.launchpad.net/soyuz/+question/73791
[17:43] <fta> and bug 381296
[18:17] <fta> Rejected: PPA exceeded its size limit (23084.00 of 20480.00 MiB) => boom, chromium out too
[18:46] <savvas> fta: it's just a developer preview, still not out :P
[18:46] <fta> savvas, ??
[18:46] <fta> savvas, it == ?
[18:47] <savvas> fta: ah sorry, I was talking about chromium
[18:49] <fta> savvas, yes, it is. but it's the only thing we have for linux, and plenty of people are requesting it, so i provide it in a ppa.. which is full every two days or so
[18:49] <savvas> you're doing a great job by the way :)
[19:00] <fta> savvas, thanks. most people are using PPAs without realizing there's someone working behind the scene to keep the thing alive
[19:12] <james_w> to just install a lazr package or wadllib/launchpadlib do I need buildout, or is that just for development?
[19:21] <mvo> hello! what can I do about: bzr: ERROR: Directory not empty: "/srv/bazaar.launchpad.net/push-branches/00/00/0c/50/.bzr/repository/lock/gxmtz4db2g.tmp": [Errno 39] Directory not empty
[19:27] <mvo> nevermind my last bzr question, I think its fine again
[19:44] <Peng_> How do you mark a merge proposal as superseded? Will it happen automatically?
[21:25] <bdmurray> Is there some way to find out the full list (or more than the top 10) of "Other Tags" for Ubuntu?
[21:41] <bdmurray> well viewing the source of +manage-official-tags had it but that seems ghetto
[21:47] <ahn> Is there a way to delete an empty bzr branch?
[21:50] <nhandler> ahn: Yes, go to https://code.launchpad.net/~USER/PROJECT/BRANCHNAME/+delete
[21:58] <ahn> nhandler: Thank you
[21:59] <ahn> Second question: when setting up a sub-project under a super-project, the bug tracking option include "In Launchpad" and "In the Super Project bug tracker (bugs.launchpad.net).  What is the difference?
[22:10] <salgado> ahn, looks like a bug in LP to me.  I think it somehow got tricked into thinking that the super project doesn't use Launchpad for bug tracking
[22:10] <salgado> ahn, what's the super project in question, btw?
[22:49] <ahn> salgado: netrek-project
[22:50] <ahn> It seems that there is no way for me to delete a vcs-import branch.
[22:50] <ahn> I actually need this branch renamed and assigned to a different subproject.  Do I need to email help@launchpad.net?
[22:51] <salgado> ahn, better to ask a question on the URL that's on the topic
[22:52] <salgado> that should be on the topic, at least
[22:52] <salgado> ahn, https://answers.launchpad.net/launchpad/+addquestion
[22:53] <ahn> Thank you.  After years of being SF, LP is a bit new.  I will try your link.