[02:48] daker: could be, I'm not sure it's been tested with anything but Ubuntu SSO [03:29] Ronnie: are you around? [05:35] hi, does anybody know how to change CNAME in our ubuntu-CC.org domain, with the use of magic key? [05:55] salvadhor: shucks, I can't recall. I do have it in my email archives. One moment, please [06:10] salvadhor: shoot, can't find it. try emailing rt@ubuntu.com [06:14] ok, thanks ;) [08:42] good morning [09:59] mhall119: pong [10:00] new bug 734232 [10:00] Launchpad bug 734232 in loco-directory "false URLs in event description. (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/734232 [10:00] I'm sorry this one seems complicated ^^" [10:12] YoBoY: i think we call a standard django function for that, so it will be even more complicated [10:14] yes, I look in the diff when daker added this feature and it's just a "urlize" option https://code.launchpad.net/~daker/loco-directory/fix.656191/+merge/37907 [15:23] commented on that bug [15:23] o/ [15:23] I'm pretty sure there are 3rd party alternatives to the urlize filter that might be more capable [15:23] morning nigelb [15:23] hello mhall119 :) [15:40] mhall119: ping [15:40] cjohnston: ping [15:40] mhall119: can't we use a textile markup solution for the description fields ? [15:40] hi mhall119 :) [15:41] cjohnston: some new styling code for forms (both for ubuntu-website and loco-directory - need to test both at the same time) [15:41] https://code.launchpad.net/~ronnie.vd.c/ubuntu-website/django-forms/+merge/53173 [15:41] https://code.launchpad.net/~ronnie.vd.c/loco-directory/form-base-styling/+merge/53174 [15:43] mhall119: the new twidenash script is pushed to twidenash, how would you suggest to branch it in LD (https://code.launchpad.net/~ronnie.vd.c/loco-directory/twidentica/+merge/51626) [15:52] how do you search for the right venue in the long list of the US venues ? [15:53] Ronnie: textile? [15:53] Ronnie: I'm going to incorporate the bzr_apps stuff into LD, so we can use it to manage both twidenash and light-django-theme [15:54] http://en.wikipedia.org/wiki/Textile_%28markup_language%29 [15:56] YoBoY: that would be an option, I have also considered supporting creole wiki markup [15:56] mhall119: great, than this merge could wait for that, or we could temporary merge it, and later on remove the static twidenash file. what do you suggest? [15:57] mhall119: textile what? [15:57] Ronnie: sorry, that was YoBoY who brought up textime [15:57] textile [15:58] mhall119: why not, I wa thinking on textile because it's in http://docs.djangoproject.com/en/dev/ref/contrib/markup/ and I already know this one from Redmine :p [15:59] YoBoY: unfortunately that was introduced in django 1.2, but our production server has django 1.1 [16:00] ha yes sorry ^^ [16:00] we'd have to look into back-porting it [16:00] but that would make most sense, since we'd be able to take advantage of it in the future [16:01] mhall119: installing it trough easy_install on the server? [16:01] Ronnie: installing what? [16:01] django [16:01] 1.2.5 [16:01] we want to stick with the stock lucid packages [16:02] is there a good reason for it? [16:02] the server are not only for LD perhaps ^^" [16:03] is [16:03] 1) It's easier for us and IS to maintain if we use the repositories [16:03] 2) What YoBoY said [16:03] 3) It lets us show that the LTS server is capable of hosting webapps [16:04] if we get to where we *need* django 1.2, we should try and get it into the backports repo (if it's not there already) rather than using virtualenv or easy_install [16:07] http://docs.djangoproject.com/en/1.1/ref/contrib/ << it's here also (the textile) this mean it's available on 1.1 also ? [16:09] oh, I'll take a look at it then [16:09] :) [16:09] not an urgent feature, just to keep in mind for the future ^^" [16:14] seems to work [16:15] for which parts do you want to use textile (some sort of wiki function?) [16:15] most text fields probably [16:15] event details, meeting detail, agenda description [16:16] we'll add python-textile as a new dependency [16:17] but I think that's okay [16:18] descriptions / détails / future report pages ... don't know ^^ [16:20] it's a part of the bug 715581 if you want [16:20] Launchpad bug 715581 in loco-directory "Agenda item description field is too small (affects: 1) (heat: 4)" [Medium,Confirmed] https://launchpad.net/bugs/715581 [16:28] YoBoY: they're different issues and different fixes, so make a new bug please [16:47] mhall119: ok [17:07] mhall119: bug 734401 [17:07] YoBoY: Bug 734401 on http://launchpad.net/bugs/734401 is private [17:08] too fast ^^" the bug is not entirely registered yet :p [21:06] mhall119, bug #734498 [21:06] Launchpad bug 734498 in loco-directory "textfields should accept markup formating (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/734498 [21:07] no is the bot kidding ツ [21:22] how to report a bug on the bot ? :D [21:22] to irc folks YoBoY [21:22] YoBoY: do you just like to report bugs [21:23] no I like also to organize events [21:24] and I report bugs only on the application I use [21:31] re-test bug #734498 [21:31] Launchpad bug 734498 in django-openid-auth "The SReg extension isn't working correctly (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/734498 [21:32] god dog ubot4` [21:32] s/god/good [21:40] howdy [21:55] hello cjohnston [22:04] https://bugs.launchpad.net/loco-directory/+bug/734520 [22:04] Launchpad bug 734520 in loco-directory "profile images not displaying correctly if no image on LP (affects: 1) (heat: 6)" [Undecided,New] [22:10] czajkowski: iirc thats a bigger problem that will take work on our part and lp part [22:10] nods [22:10] well the bug is ust reported [22:10] it's not a biggie [22:11] but just to have it logged [22:11] and seeing as more people are singing in using open user it looks fine [22:11] just people with no LP images are making it look messy [22:12] i dont think we should be getting anymore openid users.. mhall119 am i wrong? [22:12] cjohnston: why not? isnt that for folks who dont want to sgn up t LP ? [22:13] you shoudlnt' be able to sign up for LD without an LP account [22:14] which is a bit annoying for folks tbh [22:14] :s [22:14] we dont have the backend in place to support it [22:14] we pull all of our info from LP [22:14] but you can log intp LP with open id right ? [22:15] Not sure [22:15] I think you only can with ubuntu sso [22:15] but you still have to create an LP account [22:16] I guess it's somethign to think about, means if we get teams to create events on the LD but invite non Ubuntu folks, they cant sign up to attend [22:16] which means we;re back at using eventbrite or other apps for larger events [22:17] cjohnston: not trying to ne negative here [22:17] just soudning things out [22:17] but at the same time, you cant be a team member without an lp account.. or alteast an "online" team member [22:17] *sounding [22:17] this has been debated prolly 2 dozen times [22:17] hmmm [22:17] food for thought [22:17] mm [22:17] nn [22:17] and alot more negative [22:18] czajkowski, cjohnston: this scheme i made once, when i needed to know the link between openid/LP/LD http://img155.imageshack.us/img155/7037/schemaopenidld.png [23:08] cjohnston: the openiduser## bug still exisys [23:08] technically you can log into LD with only an SSO account, not an LP account, but we should block that [23:09] the main issue we have right now is that username isn't an SSO field, it's strictly an LP field [23:09] there is some mechanism to sync the two, but it doesn't always work, and when it doesn't work, we get openiduser## [23:09] also if someone has just SSO but no LP profile, we get openiduser## [23:14] there is no way to detect this "non existing username" and replace it by the openid ident ? [23:16] YoBoY: possible yes, but as of right now the LP API is based solely on username [23:17] we've spoken to them about this, and they plan on making the API accept the openid ident too [23:17] hmmmm, maybe I'll be allowed to work on my outstanding django-openid-auth branches tomorrow [23:42] czajkowski, I didn't realise you had connections with @BrynS on Twitter :P