[11:38] <glade88> hello.. what all teams are allowed to have a 16x16 team icon instead of a 14x14 one?
[11:40]  * wgrant wasn't aware that they could.
[11:42] <glade88> wgrant: the ubuntuforums.org staff, ubuntumembers, ubuntu-marketting, bash etc have 16x16 icons
[11:42] <glade88> translation teams have their country's flag which is also not a 14x14 image
[11:44] <wgrant> It's possible that that happened before the imposition of the restriction,
[11:45] <LarstiQ> which begs the question, what's the rationale behind the restriction?
[11:45] <glade88> perhaps..
[11:46] <glade88> wgrant: earlier I had in mind that brainstorm moderators team should be allowed a 16x16 icon when UF staff like teams have..
[11:46] <wgrant> LarstiQ: It doesn't beg the question.
[11:47] <LarstiQ> wgrant: as in, English?
[11:47]  * LarstiQ uses it as begets
[11:47] <wgrant> http://begthequestion.info/
[11:49] <LarstiQ> hmkay
[11:50] <LarstiQ> so, English dicussions aside, why?
[11:50] <glade88> IMO.. 14x14 is a bit too small..while 16x16 was just okay.
[11:50] <wgrant> So it fits into places it's meant to, I suspect.
[11:51] <wgrant> It's much nicer having a uniform subscriber list.
[11:51] <glade88> wgrant: its shown up only on user pages
[11:51] <glade88> and with different sized icons, its not uniform now
[11:51] <wgrant> I believe it's also shown in bug subscription lists.
[11:52] <wgrant> See https://bugs.edge.launchpad.net/ubuntu/hardy/+source/newsbeuter/+bug/275019
[11:58] <LarstiQ> wgrant: do you actually use beg the question for its logical meaning?
[12:03] <wgrant> LarstiQ: I do not.
[12:05] <LarstiQ> wgrant: ok. Neither have I ever seen anyone use it that way.
[12:05] <wgrant> Doesn't mean using it the other way is right.
[12:06] <LarstiQ> mja
[12:07] <LarstiQ> wgrant: I just use drogredenering or circular reasoning.
[13:52] <Hobbsee> oh, nyah.  darn launchpad.
[13:52] <Hobbsee> pleaes don't delete my form data.
[13:54] <persia> You mean when you submit something with a typo?
[13:55] <Hobbsee> no - putting in a summary, then hitting advanced, when filing a bug.
[13:56] <Hobbsee> wipes the summary
[13:58] <persia> Oh, I haven't looked at non-advanced bug filing since feisty, except once when the name changed from "complicated" to "advanced".
[14:02] <nhandler> I just noticed the "Does this bug affect you?" button on launchpad edge. Is there any documentation about what happens when someone says that they are affected by a bug? Does it just confirm the bug? Does it increment a counter of how many people are affected by the bug? Are you able to say that you are affected by a bug you report? When you report a bug, are you automatically marked as being affected by it?
[14:03] <qense> I think you just get subscribed
[14:03] <nhandler> qense: I really hope that it does more than that. Subscribers are not the same as people affected by a bug.
[14:03] <qense> yeah
[14:04] <wgrant> It adds an entry to BugAffectsUser, so it could easily display a count.
[14:04] <wgrant> It's not just subscription.
[14:04] <wgrant> It might not be subscription at all.
[14:04] <nhandler> Is there any documentation about this new feature?
[14:05] <wgrant> NAFAIK.
[14:05] <wgrant> But IANALPD
[14:05] <wgrant> But going by usual Launchpad standards, particularly as this is such a new feature...
[14:06] <qense> well, than I was wrong
[14:06] <qense> Is the counter already displayed?
[14:06]  * wgrant pokes around.
[14:08] <wgrant> qense: Doesn't look like it.
[14:08] <wgrant> If it is displayed, it's a bug, because I can't see it.
[14:09] <nhandler> So let me get this straight. Saying the bug affects you increments some counter, but the counter is not available to anyone? This sounds like a pointless feature to me
[14:09] <wgrant> nhandler: I suspect that the feature isn't complete yet.
[14:09]  * wgrant digs up the bugs.
[14:11] <wgrant> intellectronica would know, but isn't around...
[14:11] <wgrant> It would be nice if these plans were public...
[14:11] <wgrant> ISTR several bugs on this topic, and only seeing one marked as fixed. So I presume it's not yet complete.
[14:12]  * Hobbsee wonders why it was rolled out, if it was incomplete.
[14:13] <wgrant> Hobbsee: Why not?
[14:13] <wgrant> More for the regulars to complain about. All the better.
[14:13] <Hobbsee> wgrant: seems unprofessional?
[14:13] <wgrant> Watching if things break, rather than rolling it out all at once...
[14:13] <wgrant> Hobbsee: It's a pre-release. 'tis fine.
[14:13] <Hobbsee> wgrant: oh, i thought this rolled out to production.
[14:14] <wgrant> No, 1.2.10 isn't due for a while yet.
[14:20] <persia> I thought all committed gode automatically went to edge if it didn't break anything.
[14:21] <qense> can you already browse the variable using the API?
[14:23] <wgrant> persia: Such things would often be kept in another branch until completion.
[15:33] <Slash_Network> hello all
[15:33] <Slash_Network> can sombody help me ?
[15:34] <wgrant> !ask
[15:35] <Slash_Network> It's about comfirming my key to sign the code of conduct. I don't know what I put in the "signed text"
[16:29] <elcuco> hi all, i am tryign to register a new project in launchpad, however my code is only available from svn (no bazar). what are my options?
[16:32] <Dominic> elcuco: you don't have to have any code on lp if you don't want to.  You can also import the code from an external svn server and it'll update a branch in lp's bzr repo if you like.
[16:32] <Dominic> elcuco: you can go through the registration process, then once you're registered, click on the 'Code' tab and it'll give you the options
[16:33] <elcuco> Dominic: yes, i am there, and i see now the svn configuration. i am still trying to understand if i will have write commit to my svn repo
[16:33]  * elcuco is trying to open a translation project for kde
[16:34] <Dominic> I think it's purely a read-only import of svn into an lp hosted bzr repo, so you'd just use your existing commit access back to the main svn repo and it'd show up later in lp's bzr
[16:35] <Dominic> but I guess you could then branch the bzr version if you liked on lp
[16:35] <elcuco> the deal is that i don't want users to deal with anything *but* the gui
[16:37] <Dominic> I'm not sure you even need to have the code visible in lp to use translations, but I haven't used it
[16:38] <elcuco> lp has it's own translations, but they are tied up to ubuntu. i don't want that, i want the branches to be tied up with kde's upstream 'code'
[16:38] <elcuco> lp seems interesting for translating, and this is what i am trying to use
[16:39] <Dominic> indeed, but I don't think you even need to configure the code bit to make use of the translation section.  Might be worth playing on staging.launchpad.net and you can try it out without harming anything
[16:39] <Dominic> but even still, if you set up a code import from svn, nobody's going to be able to commit back anyway unless they had valid credentials
[16:40] <elcuco> so this means i am still translating in void, without option to commit back "upstream". correct?
[16:40] <Dominic> I don't know, I haven't used the translations section from a dev perspective to know how it works, sorry.
[16:42] <oojah> elcuco: The launchpad translations aren't necessarily tied to ubuntu.
[16:42] <oojah> Some of my personal projects use lp for translations but aren't even on any distros.
[16:43] <oojah> elcuco: The important bit is that the people developing the code decide to use launchpad for the translations.
[16:43] <elcuco> oojah: is it possible to commit from LP to upstream? (only translations)
[16:43] <oojah> If they don't incorporate the translations done on launchpad into the repo, then it's a bit of a waste of time.
[16:44] <oojah> elcuco: Not as far as I know, but I'm only a lp user.
[16:44] <oojah> Once translations are ready, they can then be downloaded as a tar ball.
[16:45] <oojah> Well, at any point.
[16:45] <oojah> They don't have to be "complete" :)
[16:46] <elcuco> but my translations are a moving target, i need a constant "merge"
[17:52] <epsy> hi, i've noticed a small issue with team maps: most of the time bubbles just doesnt fit the map frame..and it looks..weird
[17:56] <epsy> you can't have both the whole bubble and the pin tofether
[19:07] <Accidus> Anyone here has some experience with launchpadlib?
[19:08] <beuno> Accidus, a little bit. What seems to be the problem?
[19:09] <Accidus> Hmm... Well, it's probably due to my misunderstanding of the concept, but I'm having problems with iterators.
[19:09] <beuno> Accidus, want to pastebin the code/output somewhere?
[19:10] <Accidus> For the argument's sake, take proj = launchpad.projects['launchpadlib']
[19:10] <beuno> I also happen to know Verterok is around, and he's played with it more than I have
[19:10] <Accidus> It's rather short. Do you still prefer a pastebin?
[19:10] <Accidus> (most of the code is authenticating, which is standard code)
[19:11] <beuno> sure, pastebins are IRC-friendly
[19:11] <Accidus> Okay. Just a sec.
[19:11] <Verterok> Accidus: shoot, I'll try to answer :)
[19:12] <Accidus> Just a sec then. I'll make a pastebin :).
[19:16] <Accidus> Okay
[19:16] <Accidus> http://pastebin.com/m4e84477b
[19:17] <Accidus> It seems that the iterator entry misses some key attributes.
[19:17] <Accidus> For example, the entry_links one
[19:17] <Accidus> Or the self_link one
[19:18] <Accidus> But, well, I could be dead wrong, because this is just an iterator entry, not a normal entry (like 'project' or 'person')
[19:18] <Verterok> Accidus: let me check
[19:25] <Verterok> Accidus: I think that: proj.releases should be enough :)
[19:25] <Verterok> that 'll return the collection of releases
[19:26] <Accidus> Hmm... Interesting.
[19:26] <Accidus> proj.releases doesn't appear in the doc
[19:26] <Accidus> While releases_collection_link does
[19:27] <beuno> Accidus, sounds like a bug!  ;)
[19:27] <beuno> (in the docs)
[19:27] <Verterok> Accidus: run yout py, with: 'python -i' and play with the dir() funtion in the interactive interpreter
[19:28] <Accidus> Ah, probably
[19:28] <Accidus> Verterok: I'm using the dir() excessively :0)
[19:28] <Accidus> That doc file is hard to use :)
[19:28] <Verterok> ;)
[19:28]  * beuno was hinting at Accidus to file a bug so the docs can be updated
[19:28] <Verterok> Accidus: I almost never look the docs, just the code :)
[19:28] <Accidus> Don't worry. I'm filing a bug.
[19:29] <Accidus> Although I'm not sure how to report it.
[19:29] <Accidus> "In the docs appears the "releases_collection_link" attribute, but if you try to use it you get b0rked objects, while the "releases" attribute works fine?
[19:30] <beuno> yeap, let the dev figure the rest out  :)
[19:31] <Accidus> Sounds good. I'll probably add more flesh to the report though. I'd hate to receive such a report myself.
[19:32] <beuno> well, the more flesh it has, the more chances it'll get fixed. So feel encouraged to add as much as you can
[20:13] <Accidus> Hooray! It works!
[20:13] <Accidus> Now to wrap it up into a single script :)
[20:13] <Verterok> Accidus: great!
[20:14] <Accidus> Verterok: How do you figure out an operation's arguments if not from the api doc?
[20:14] <Verterok> mmm...a good question...don't know the answer
[20:14] <Accidus> Okay. Thanks :)
[20:15] <Verterok> Accidus:  I assume looking the code that write the http request ;)
[20:16] <Accidus> Hehe. Welllllllll... Not really. I think that looking at the API doc first
[20:16] <Accidus> is a better action.
[20:17] <Accidus> If it's not there/not updated, then doing some guesswork
[20:17] <Accidus> And if push comes to shove, asking in the answers page for launchpadlib.
[20:17] <Accidus> Only if you're in a real hurry I'd guess looking at the request a recommended action :))
[20:19] <Verterok> Accidus: sure, y'r right
[20:22] <Verterok> Accidus: it's just that I  like to know the internals :)
[20:23]  * Verterok must leave now, seeya later
[20:25]  * Accidus knows the feeling.
[20:25] <Accidus> See you later! And thanks for all the help