[12:08] mpt: any progress on the main template, with facets-as-tabs? [12:09] sabdfl: I haven't had time to do that yet, I've been working on the Rosetta copy-and-paste buttons [12:09] mpt: ok cool [12:09] can you make that next on your list? [12:09] night all [12:10] ok, though I'm not that keen on something which will make them take up more space [12:10] 'night [12:10] later sabdfl [12:10] night sabdfl :-) [12:12] ugh === mpt gets incorrect conflict markers [12:21] These files violate naming conventions: [12:21] examples/.arch-ids/\(U+E2)\(U+99)\(U+AA)\(U+E2)\(U+99)\(U+AC).id [12:21] examples/\(U+E2)\(U+99)\(U+AA)\(U+E2)\(U+99)\(U+AC) [12:21] -- [12:22] they do ?! it shouldn't afaict [12:23] lifeless: ? [12:26] fmt:approximateduration is in spiv's review queue, later all [12:27] stub, I have an update to the migration script already but I cannot merge it yet, I have there other changes, can you merge to stagging to test it? [12:27] carlos: Sure [12:27] stub, carlos.perello@canonical.com--2004/launchpad--devel--0 [12:28] stub, the other changes should not affect that script [12:29] Are the changes you care about only in the script? if so, I don't have to worry about merging. [12:29] carlos: ^^^ [12:29] stub, the needed changes to get the script running is only in the script, the branch touches other files [12:30] but those changes are not related, it belongs to other changeset === carlos -> bed [12:36] stub, do you need anything else to test it? [12:36] Nop [12:36] e [12:37] ok, thanks [12:37] good night === mdz [n=mdz@ca-studio-bsr1o-251.vnnyca.adelphia.net] has joined #launchpad === mpt [n=mpt@200-171-140-32.dsl.telesp.net.br] has left #launchpad [] === Mez [n=Mez@cpc2-lich4-3-0-cust115.brhm.cable.ntl.com] has joined #launchpad [01:58] Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=salgado] Make EnumCol work with default=DEFAULT. Fixes bug 1659. (patch-2263: andrew.bennetts@canonical.com) === asgeirf [n=asgeirf@202-161-14-195.dyn.iinet.net.au] has joined #launchpad [03:05] spiv: Where you going to stop the librarian accepting files with evil filenames? (eg. containing / or \0) If so, can you update Bug388 with characters you deem as evil? [03:06] stub: The only characters I'm inclined to deem as evil are / and \0. [03:06] But part of me feels that it's not the librarian's problem ;) [03:06] Once the DB constaints are in place, it won't get as far as the Librarian. [03:08] are characters that look like "/" evil too? [03:08] What's the use case for disallowing them? (I admit I don't really have one for allowing them either0 [03:08] ) === spiv has a left shift key that's starting to get a bit dodgy [03:09] jamesh: The reason to disallow / and \0 are because they're invalid in posix filenames (although / is of course valid in a pathname). [03:10] But I'm struggling to see any way that it actually matters. [03:10] I guess the database column being called "filename" rather than "pathname" is one argument. [03:10] spiv: Because broken clients can upload a file with filename 'c:/foo/bar.txt', which then can't be downloaded in any sane fashion. [03:10] spiv: I suppose the web browser would replace them anyway, if a user is downloading and saving them [03:10] stub: Why can't they be downloaded? === Keybuk [n=scott@descent.netsplit.com] has joined #launchpad [03:11] stub: on Windows, I think that would get downloaded as c__foo_bar.txt [03:11] spiv: Because they are invalid and look like a hacking attempt (eg. what should firefox do if you ask it to download a file called ~/.bashrc ? ) [03:11] been a while since I've checked though [03:11] stub: Probably save it do $downloaddir/.bashrc [03:11] it's pretty easy to test for though [03:12] spiv: But we don't know that, and we shouldn't let invalid data get into the system in the first place. [03:12] If you can convince me that it's invalid, I'll be much happier :) [03:13] It would probably be specified in the MIME rfc under the filename attibute to the mimetype [03:14] I am leaning slightly towards disallowing them, but I'd really like to have a strong reason other than a vague feeling that it's probably better. [03:14] If only so that I can put a more useful comment in the code than "Disallow / and \0, just in case" ;) [03:15] See section 2.3 of RFC 2184 [03:15] Er, [03:15] 2183 [03:16] Although it's discussing MUAs rather than HTTP clients. [03:18] actually, MIME is a red herring. These filenames are served up as part of URLs, which IIRC can include anything if properly UTF-8 encoded and quoted [03:18] But clients might still have issues, and I'm not going to test all the clients ;) [03:19] http://www.w3.org/Protocols/rfc2616/rfc2616-sec19.html#sec19.5.1 [03:20] I'm inclined to disallow anything that indicates the client uploading the file is screwed, because we really don't want data from that source ;) [03:20] Arbitrary restrictions have a way of biting you in the arse unexpectedly six months later :) [03:21] Does the Librarian actually set that header? [03:21] Or not bother, since the filename is the final component of the URL? [03:21] Your example of c:/foo/bar.txt inclines me to not bother disallowing anything -- I'm interested in learning how to make "safe" filenames for every OS out there. [03:22] It doesn't send it, no. [03:22] My example is actually based from real world experiance with broken windows clients that tended to upload filenames such as c:\foo\bar.txt [03:22] Which is a 100% valid posix filename. [03:24] 'safe' can be defined as ASCII and not containing / \ : or \0 , which is probably a bit strict now days (we could extend that to UTF-8 and not containing / \ : or \0 === spiv is still wavering [03:24] Indeed - c:\foo\bar.txt is 100% valid, but is totally broken. Users report it as a bug, so you shouldn't let it get in the first place. [03:25] The only use case I can think of for allowing a filename like that is so you can laugh at the silly person still using IE4 (or whatever it was) [03:26] stub: on Windows, you'll get in trouble with *, ? and a few others [03:26] I tend to not like \0 and it tends to break C code unexpectedly [03:27] true. Anyway, I would really only bother disallowing [03:27] Sure, and filenames longer than a certain length might trigger buffer overflows in some C code too ;) [03:27] the fun ones are filenames with \n in them === mpt [n=mpt@201-27-4-102.dsl.telesp.net.br] has joined #launchpad [03:27] Right, whitespace can break badly written shell scripts... [03:27] ... / and \0 , because the first indicates the client is screwed and the second is scary [03:27] and libtool [03:28] / and \0 are the only invalid characters in a POSIX filename :-/ [03:28] ^G in them is fun [03:29] Ok, so the two reasonable choices are 1) free for all, 2) everything except / and \0. === stub wonders if PostgreSQL lets him store a \0 in a text column anyway [03:29] Trying to restrict more than that is the path to madness, as we try to guess what breaks windows and whatnot. [03:30] utf-8 filenames are certainly "normal" in linux now [03:30] Well, the librarian stores filenames as unicode. [03:31] Keybuk: Is that now 'standard', or is it still the filename is assumed to be in the encoding being used by the terminal? [03:31] There's no guarantee clients won't upload encoded names, though. [03:31] there's nothing in the filesystem to force it (unless your fs=fat) [03:31] spiv: If it aint a valid UTF-8 sequence, PostgreSQL will barf [03:32] And I don't think HTTP has any standard way to serve non-ASCII filenames. [03:32] so how you read filenames is how they're displayed [03:32] stub: Well, it'd be double-encoded would be the issue. [03:32] But we can't do much about people uploading garbage except serve that garbage back at them :) [03:32] spiv: Can't happen - the filename is decoded on upload [03:33] Keybuk: JFS also wants unicode filenames, iirc [03:33] stub: By "client" I don't mean the librarian client, I mean Joe Bloggs with his dodgy Web Browsez0r 0.9. [03:33] really? sweet [03:35] stub: (once I fix a bug) The librarian client always sends filenames utf-8 encoded, and the librarian server utf-8 decodes them into unicode objects, which of course are then re-encoded for insertion into the database. [03:35] The librarian server already barfs on non-utf-8 filenames. [03:36] OS-X is UTF-8 -- it becomes necessary to define the encoding when you have a Unicode aware filesystem browser. And Win32 is all Unicode apis so I don't think the encoding is even exposed to developers. I assume the existing Linux ones all just break if the filenames arn't encoded the way they expect :-( [03:39] stub: on Windows, there are two APIs for pretty much everything: the unicode one and the "ANSI" one [03:40] where the ANSI one is the legacy encoding [03:41] so you can create files with the unicode API that apps using the ANSI API can't read === camilotelles-afk is now known as camilotelles [04:10] so now that my duplicate launchpad users are all sorted, is there a way for me to change 'name93' to 'mdz'? [04:11] mdz: Currently only by asking stub, I think :/ [04:11] I'm not sure what's left to stop us from letting users edit that. [04:12] https://wiki.launchpad.canonical.com/WhatNamesCanBeChanged says it ought to be allowed. [04:14] does stub read scrollback? [04:14] stub: ^^^ [04:14] who's responsible for the code of conduct signing stuff? [04:15] stub reads scrollback afaik, yeah. [04:20] cprov, iirc. === asgeirf_ [n=asgeirf@203-173-20-214.dyn.iinet.net.au] has joined #launchpad [04:32] Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial] only-one-ubuntu-wikiname constraint and people merge patch to cope (patch-2264: stuart.bishop@canonical.com) === robitaille [n=daniel@d154-5-117-228.bchsia.telus.net] has joined #launchpad === camilotelles is now known as camilotelles_zzz [05:46] mdz: Updated [05:46] stub: thanks === mpt [n=mpt@201-27-4-102.dsl.telesp.net.br] has left #launchpad [] [08:10] stub: thanks for fixing #1313! [08:11] Just karma whoring [08:11] :) [08:12] Well, that's probably fair enough, given that it was probably our most frequently reported dupe. [08:27] 1212 ? [08:28] bah [08:28] ignore me [08:28] win 18 === sabdfl [n=mark@pdpc/supporter/silver/sabdfl] has left #launchpad [] === sabdf1 [n=mark@217.205.109.249] has joined #launchpad === carlos [n=carlos@243.Red-83-47-24.pooles.rima-tde.net] has joined #launchpad [10:41] morning [10:48] stub, hi, how was the whitespace script test? still running? [11:36] carlos: still running [11:37] that's good [11:37] means the bug would be fixed === WaterSevenUb [n=WaterSev@azevedo.astro.up.pt] has joined #launchpad [12:11] stub: could you tell me which upstream apps have the most bugs filed against them? just top 5 or 10 === WaterSevenUb [n=WaterSev@azevedo.astro.up.pt] has joined #launchpad === camilotelles_zzz is now known as camilotelles [12:24] stub: ping [12:43] lifeless: ping [12:44] sabdfl: pong, just talking about you :0 [12:45] (jdub is giving his oscon talk to debsig) [12:45] lifeless: coolio :-) [12:45] lifeless: could you give me read-only access to the staging db please? i have accounts on mawson and asuka [12:46] mawson is staging right ? [12:46] asuka, i think [12:47] not sure which db it is [12:47] mawson is dogfood, asuka is staging [12:47] stub and salgado might know [12:47] Kinnison: db names? [12:47] bah, don't have the right keys with me, I can do it when I get home if stub hasn't surfaced by thenm === lifeless is in holiday mode :) [12:48] ok, cool, thanks === carlos [n=carlos@243.Red-83-47-24.pooles.rima-tde.net] has joined #launchpad [12:51] sabdfl: people seem to use: psql -h asuka.ubuntu.com -U ro -d launchpad_staging [12:51] sabdfl: from mawson [12:52] sabdfl, ^^ that's what daf and I use [12:52] psql: FATAL: no pg_hba.conf entry for host "82.211.81.131", user "ro", database "launchpad_staging", SSL off [12:53] sabdfl: if you have access to asuka/mawson, you should have sudo access to the launchpad use [12:53] sabdfl, from mawson [12:53] *user* [12:53] thats what we usually give people who are working with those machines [01:22] yo [01:25] hey stubarooney [01:26] name | count [01:26] ----------------------+------- [01:26] malone | 304 [01:26] launchpad | 281 [01:26] bazaar | 246 [01:26] rosetta | 159 [01:26] think you can let me see staging read-only, from mawson or asuka? [01:26] foaf | 51 [01:26] hct | 14 [01:26] soyuz | 6 [01:26] sympa | 4 [01:26] ubp-hoary-unofficial | 3 [01:26] ubuntu | 3 [01:26] bluefish | 2 [01:26] blender | 2 [01:26] buildd | 2 [01:26] fdclock | 2 [01:26] thats plenty [01:26] gnomebaker | 2 [01:27] sabdfl: You should be able to connect to launchpad_staging on asuka as the ro user now (from your mawson account, using the command given before) [01:28] mark@mawson:~ $ psql -h asuka.ubuntu.com -U ro -d launchpad_staging [01:28] psql: FATAL: no pg_hba.conf entry for host "82.211.81.131", user "ro", database "launchpad_staging", SSL off [01:28] nup [01:28] did you see jdub's presentation? [01:28] argh... username mark, not sabdfl :-( [01:29] :-) === Mez [n=Mez@cpc2-lich4-3-0-cust115.brhm.cable.ntl.com] has joined #launchpad [01:29] sabdfl: ok - try again [01:29] rocking, thanks [01:31] very exciting [01:33] sabdfl: what was his presentation about? [01:39] sivang: aiui it was his oscon presentation, replayed. [01:40] stub: i'm [trivial] 'ing a two-liner that lets you exclude dbschemas from the vocabs [01:42] it might be better to have dbschema items be markable as deprecated, so they don't show up [01:42] the use case for this is the debbugs tracker, we only know of one, we don't want people registering more [01:43] sounds sane. A deprecated flag doesn't sound appropriate for your use case though - the way you are doing it seems to be the best option. === carlos -> lunch [01:58] see you later === mpt [n=mpt@200-171-140-32.dsl.telesp.net.br] has joined #launchpad === mpt [n=mpt@200-171-140-32.dsl.telesp.net.br] has joined #launchpad === camilotelles [n=Camilo@201.32.223.192] has joined #launchpad [02:17] nofht all [02:17] bah [02:17] night all === ddaa [n=ddaa@ordo.xlii.org] has joined #launchpad [02:20] stub: do i need your approval if want to edit security.cfg? (add delete to bugsubscription) [02:21] BjornT: Nope - as long as I know about it. [02:21] stub: cool === ondrej [n=ondrej@maple.active24.cz] has joined #launchpad [02:25] mm all === cprov [n=cprov@200-171-140-32.dsl.telesp.net.br] has joined #launchpad [02:26] is there a plan to do cleanup in rosetta breezy target? so f.e. glib2.0 is not list 7x times? [02:31] Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial] polish home pages (patch-2265: mark.shuttleworth@canonical.com) === Seveas [n=seveas@seveas.demon.nl] has joined #launchpad [02:39] carlos: ^^ q from ondrej [02:41] sabdfl: feeling better today? heard you were/are sick (yesterday)... [02:42] ondrej: yes, much better today thanks. lurgie from brazil had me nailed yeterday [02:43] :-) that's good... hope to see you on next CC meeting... === WaterSevenUb [n=WaterSev@azevedo.astro.up.pt] has joined #launchpad [03:00] hey ho [03:01] yo kiko [03:02] kiko: is salgado around? [03:02] any idea why we don't have a Person.karma cache? [03:02] We're not sure where he is, sabdfl [03:02] We think he might be at classes [03:02] I am sure where he is [03:02] he's at classes [03:04] kiko: please could you ask him to do the following: [03:04] - add a karma field to the Person table [03:04] - replace Person.karma() with that field [03:05] - make update-stats.py also update karma [03:05] so we have the karma value cached, and can index and query it [03:05] sabdfl, could you file a bug? :) === kiko tries to get the man to use his tool [03:05] suggestion for rosetta: there should be simple way how to use suggested translation: copy & paste is not very efficient... simple javascript could be implemented, so you can just click and have it prefilled in input box... [03:06] product? foaf does not exist [03:06] ondrej: I'm working on that at the moment [03:06] ondrej, yeah, known trick it's in the pipeline [03:06] sabdfl, launchpad [03:06] sabdfl: It was renamed to ex-foaf, with its bugs etc rolled into launchpad [03:06] there are only three lp products now -- launchpad, malone, rosetta [03:06] ok, thanks for info [03:07] kiko: https://launchpad.net/malone/bugs/1794 [03:08] sabdfl, thanks, I'll make sure it's done [03:09] ondrej: https://wiki.launchpad.canonical.com/TranslationReview [03:09] though, that spec does not reflect what i asked for in Brazil. MPT? [03:09] i didn't want radio buttons... [03:11] nice, I like those scanned paper notes :-) [03:13] btw, from https://wiki.ubuntu.com/Calendar Sep 1st - StringFreezy - does this mean that *upstream* (from translation teams POV) strings are freezed and L10N teams can start work on translations? [03:13] sabdfl: Should you eventually get karma if your suggestion gets accepted? If so, there needs to be some way of identifying whose suggestion is being accepted. And as the radiobuttons copy into the field just like the copy buttons do, in case you want to tweak one of them. [03:14] It's much simpler than the previous version of the spec :-) [03:15] I was also asked this question: how and when are translations from rosetta propagated to Ubuntu? It makes sense not only to translate some *random* strings in rosetta, but also to test them inside live system. === mpt finishes sending his chart fixage off to PQM [03:16] ondrej, the translations are exported into language packs, which are then rolled into the distribution, so indeed they are used [03:17] ondrej: but the documentation string freeze is only Sep 8th [03:17] kiko: so every new release of language-pack contains up-to-data translations from rosetta? [03:17] that is correct [03:22] is there a way how to review translations in one language and all packages? I have team member who is not so sure of his translations, and marks all as "Need Review", so I would like to review all of them in one big batch (601 translation strings suggested) [03:22] and if not it would be nice thing to have === SnakeBite [n=SnakeBit@84.242.143.64] has joined #launchpad [03:25] there is a review interface planned [03:26] just didn't see this suggestion in TranslationReview wiki page, so I thought it would be usefull to mention it :-) [03:27] yeah, it's a great suggestion -- mpt, which spec covers the mass-review UI? [03:27] morning [03:28] err, https://wiki.launchpad.canonical.com/RosettaSpecification page broken: ImportErrorCannot load macro ListSpecifications [03:28] ondrej, agh. [03:28] elmo? [03:29] what? [03:29] elmo, I wrote a couple of macros to automate some queries our moin instance [03:30] s/our/on our [03:30] elmo, what would be a good way to install them and allow me to update them as I go? [03:30] send them to me [03:30] okidok [03:31] kiko: I hadn't heard of the mass-review idea before [03:32] elmo, sent [03:32] I don't think we have a spec for it [03:32] ondrej, perhaps you would like to write the spec? :-) [03:32] mpt, in capetown we discussed it -- it would be across potemplates [03:32] spiv: ping [03:33] Well, if we do, I don't think it's one I was involved in [03:33] either that or I have a bad memory [03:34] or too many drugs [03:35] yeah, that must be it [03:35] pink mushrooms [03:37] bradb: pong [03:37] bradb: want that review done? [03:37] spiv: yes please! [03:37] if possible, of course [03:40] there were beautiful [03:42] sabdfl: do the tables "changesetfilename", "changesetfile" and "changesetfilehash" have any future? They are going to require additional work to support with import-archivelocation and they are quite arch-specific in design (assume on-disk changeset-based storage). [03:43] I'd rather have them ignored now (no longer updated) and delete at the first oppurtinity. [03:44] mpt: err, I am not good at writing specifications :-) [03:45] but I can try :-) [03:48] ondrej: So you are wanting to review all the translations made by a particular person? === jblack [i=jblack@static-209-158-45-74.scr.east.verizon.net] has joined #launchpad [03:53] ondrej, It needs some manual changes, I'm doing it from time to time, but it's a bit hard. Will fix glib now. [03:56] https://wiki.launchpad.canonical.com/TranslationMulti [03:57] excellent, thanks ondrej [03:57] carlos: ok, thanks... I guess this will settle down with StringFreezes? [03:58] ondrej, it should not affect StringFreezes... usually is the same but from different versions that our automatic system was not able to handle [04:00] I mean - you will do one big manual cleanup at that time...? [04:00] ddaa: ping [04:01] jblack: sir? [04:01] Good morning! (afternoon for you). [04:01] Do you have time for an interview this morning? [04:01] hu? [04:02] Who are we interviewing? [04:02] I'm interviewing you. dislodging data, dependancies, etc. [04:02] this is for a nice solid roadmap [04:03] iirc, you're doing the lp part of the supermirror. [04:03] ondrej, if I have time, yes [04:03] I'm only on usual overload, not overloaded overload, so I guess I have the time :) [04:03] ondrej, but I'm a bit busy atm with jordi and daf out [04:03] Ok. Whats a good offset from now to start? [04:04] jblack: not sure if I can tell you anything though. I did not have time even to touch the LP things I'm supposed to do. [04:04] carlos: ok, I will ping you if something as glib2.0 is there again... [04:05] This is just in the context of building a raodmap. [04:05] ondrej, there are more, I know, but I will try to fix the ones people ask for first [04:05] "Whats a good offset from now to start?" I do not understand your question. [04:06] now + 0 min, now + 1 hour, six hours from now, after you've had a cup of wine.... [04:06] jblack: let's do it now. [04:06] Great. [04:08] I'm that pink number on the bottom. === SnakeBite [n=SnakeBit@84.242.143.64] has joined #launchpad === BjornT [i=10183@82-135-221-189.ip.takas.lt] has joined #launchpad [04:38] ondrej, done: https://launchpad.net/distros/ubuntu/breezy/+sources/glib2.0/+translations [04:39] ondrej, next week the deprecated entries will disappear [04:43] spiv: will you have a chance to do that review today? [04:44] carlos: thanks === Keybuk [n=scott@descent.netsplit.com] has joined #launchpad [04:46] spiv, can I merge the last branch you reviewed? or do you need anything else after my last answers? [04:47] bradb: In your mail now. That should keep you busy ;) [04:49] carlos: Your devel branch? [04:49] spiv: cool, thanks [04:49] spiv, yeah [04:49] spiv, I think the only open issue is related with the new Interface you suggested [04:50] carlos: Hmm, I don't see a reply to it, and my review had a few questions. [04:50] spiv, I answered them... [04:50] spiv: You're up! Will you be up in a little bit? [04:50] spiv, when did you get my last email? [04:51] jblack: Unlikely, it's past my bedtime. You might get lucky though ;) [04:51] carlos: The 12th, I think. === jblack crosses his fingers [04:52] spiv, my laptop's email server went down [04:52] carlos: I've definitely seen no answers to my review of your devel branch... [04:52] spiv: how much longer will you be around? i'm hoping to fix this up and land today, if possible. [04:52] it should go out now === spiv double checks the spam folder. [04:53] bradb: About to crash, sorry. [04:53] ok, no worries, thanks for the review === Mez [n=Mez@cpc2-lich4-3-0-cust115.brhm.cable.ntl.com] has joined #launchpad [04:54] bradb: But if the changes you make are all more or less as proposed in the review (and you make all the changes required by the review), you can merge. [04:54] I guess that's technically merge-conditional rather than needs-reply. [04:54] Except that I want to review the changes after merge in that case, just in case :) [04:55] The nice thing about having that huge list of tests is that we can be confident it actually works, even if it's ugly. [04:55] yep, i live by that motto [04:55] Yeah, I'll mark it merge-conditional on the wiki for you. [04:55] thanks [04:56] carlos: ok. [04:56] carlos, I hate POParser already [04:57] kiko, ok, now we are three, should we create a club? :-P [05:00] I might be able to fix it somewhat [05:00] I'm trying [05:01] carlos, would it make sense to strip() all lines in a pofile? [05:01] kiko, daf has a new parser that should be compatible with current one, I don't think you should expend too much time with it, we should move either to daf's one or fix gettext's one [05:01] kiko: Glad you're here. [05:01] spiv: Still around? [05:02] carlos: Also, update the wiki when you reply to a review, to mark it needs-review again. [05:02] kiko, before or after remove msgid "" and msgstr "" ? [05:02] spiv, ok [05:02] carlos: That way I only need to look at one place to know if I have review work to do. [05:03] carlos, in general, I mean -- should trailing whitespace be taken into account? [05:03] carlos, a new parser? wow, where? [05:03] kiko, he sent me it a while ago, but still has some bugs [05:03] jblack: Yes, but only barely. [05:03] Do you have time to look at an email and add 3 lines to it? [05:04] If you're quick ;) === jblack gives spiv big/sad puppy eyes [05:04] What email address to you prefer for sending? [05:04] andrew@canonical.com [05:04] kiko, if you do it before any file parsing, that's ok === mpt comes across the text "Acknowledge CoC" in a template [05:04] Anyone know what that means? [05:04] cprov? [05:05] code of conduct [05:05] is that the question? [05:06] I know what a CoC is [05:06] (though I'm going to change that to "Code of Conduct" here anyway) [05:06] mpt: yes, this actions is documented in the spec, consists in a approval of a not digitally signature of CoC by a CC member (aka LP Admin) [05:06] but what does "Acknowledge" mean in this context? [05:07] cprov: Sorry, "approval of a not digitally signature" ... [05:07] sounds like Approve to me [05:07] cprov: So someone signs the Code [05:07] or someone says they agree to it [05:07] but doesn't digitally sign it? [05:07] spiv: btw, bisect.bisect appears to return the index that would be the insertion point for the item, so 1. it will always be one greater than the position of the item that interests us, 2. it's not documented to raise an IndexError at all, as best i can tell [05:07] cprov: And then an admin has to say "yes, this is equivalent to a real signature"? [05:07] kiko: Will you be here in ~ 20 minutes? [05:08] hmm [05:08] I shouldn't be [05:08] mpt: sorry, typed bad english ... yes, in fact it could be a REAL signature sent by fax to a member [05:08] jblack, in 2h? [05:08] in 2h, for up to 2h ? [05:08] cprov: So this is something an admin does [05:08] all right [05:09] cprov, "could" or "will be"? [05:09] jblack, sure [05:09] mpt: exactly, the page is restricted [05:09] bradb: https://chinstrap.ubuntu.com/~dsilvers/paste/fileuPFG4M.html [05:09] Its a date. I'll wear my prettiest dress. [05:09] kiko: it is ;) [05:10] bradb: Note the (seconds, '') trick, which perhaps should be more prominently commented. [05:10] cprov: How about "Register Someone's Signature"? [05:11] cprov: huh? "could" or "will be"? [05:12] mpt: sound sane, but is it intuitive for the CC members ? maybe "Approve CoC Signature", I'm not sure about the name "Acknowledge", but it was approved by Mako in AU [05:14] Well, you only need to do it if it wasn't an automatic signature [05:16] mpt: yes, if the candidate has no GPG yet, or whatever everything but the normal COC GPG signed. [05:17] so I think "Register" makes more sense for something that Launchpad didn't know about [05:17] previously [05:17] "Approve" would be for something that's already in Launchpad === mpt wonders how he ended up with an empty portlet [05:19] mpt: indeed, but if you think the process itself (apart of register a new CoC signature) means you are *approving* a new member of the UBUNTITES super-team, my suggestion still reasonable [05:21] cprov: Do people still need to be approved separately even if they sign the Code digitally? [05:22] cprov: Offhand, do you know which file generates the portlet on /codeofconduct ? [05:22] mpt: no, digitally signature automatical promote the user as UBUNTITE [05:23] ok, so this is more about their signature than it is about approving them. [05:23] mpt: right, it makes sense [05:23] spiv: i think the algorithm that uses bisect.bisect is broken [05:24]