/srv/irclogs.ubuntu.com/2012/12/13/#ubuntu-meeting.txt

=== chiluk is now known as chiluk_away
=== chiluk_away is now known as chiluk
=== chiluk is now known as chiluk_away
=== statik_ is now known as statik
=== chiluk_away is now known as chiluk
=== chiluk is now known as chiluk_away
=== Ursinha is now known as Ursinha-afk
=== fabo_ is now known as fabo
=== Tonio__ is now known as Tonio_aw
=== doko_ is now known as doko
=== Pricey_ is now known as Pricey
=== Tonio_aw is now known as Tonio__
=== Tonio__ is now known as Tonio_aw
=== Tonio_aw is now known as Tonio__
=== Tonio__ is now known as Tonio_aw
=== Ursinha-afk is now known as Ursinha
=== yofel_ is now known as yofel
=== Quintasan_ is now known as Quintasan
=== Tonio_aw is now known as Tonio__
=== Tonio__ is now known as Tonio_aw
=== Tonio_aw is now known as Tonio__
=== chiluk_away is now known as chiluk
=== bdrung_ is now known as bdrung
=== rrnwexec is now known as rrnwexec_
=== chiluk is now known as chiluk_away
=== rrnwexec_ is now known as rrnwexec
=== chiluk_away is now known as chiluk
=== Tonio__ is now known as Tonio_aw
=== Tonio_aw is now known as Tonio__
=== Tonio__ is now known as Tonio_aw
=== Tonio_aw is now known as Tonio__
s-foxo/18:00
=== chiluk is now known as chiluk_away
=== chiluk_away is now known as chiluk
=== chiluk is now known as chiluk_away
=== chiluk_away is now known as chiluk
jono#startmeeting19:00
meetingologyMeeting started Thu Dec 13 19:00:23 2012 UTC.  The chair is jono. Information about MeetBot at http://wiki.ubuntu.com/meetingology.19:00
meetingologyAvailable commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired19:00
jonohey everyone, and welcome to the Ubuntu Accomplishments meeting!19:00
jonowho is here for the meeting?19:00
s-foxo/19:00
JasnaBencico/19:00
cwayne\o19:00
cielako/19:00
jono\o/19:01
jono:-)19:01
jonomhall119, are you here too?19:01
jonoso unfortunately I have to leave in 30m for a call, but I have a few agenda topics to raise19:01
jonois it OK if I raise these first?19:01
cielaksure19:01
jonoawesome :-)19:01
jonoso the first is regarding the server deployment19:02
jonoso mhall119 has been taking care of getting the validation, admin, and web gallery deployment instructions in place19:02
jonoone thing we need to decide on is how we push changes to IS for deployment19:02
jonotypically they prefer to simply pull a branch for a deployment19:02
jonoas such, I wanted to propose the following:19:02
jono - we will have the staging and production servers set up19:03
jono - staging pulls from trunk for each of the server-related projects19:03
cielakwill we have a separate project for the admin dashboard?19:03
jono - when we cut a new release of a project, trunk is branched to a version number (as we do with the -daemon and -viewer projects), and that version is pushed to production19:03
jonocielak, right now the admin is just a branch, but I will set up a project19:04
mhall119jono: I'm here19:04
cielakokay19:04
jonodoes that workflow sound OK to you folks?19:04
cielakseems fine to me19:04
jonothis way we can then just file an RT with a branch pull for an update19:04
s-foxsounds like a good idea to me19:04
jonomhall119, do you think IS will be happy with that?19:04
mhall119jono: why would staging pull from trunk?19:04
jonomhall119, as that is where we develop the projects19:05
jonothe idea being that you only push to trunk when your code works :-)19:05
jonoso trunk is sacred19:05
mhall119so this is feature staging, not deployment staging19:05
cielakso the projects that are going to have their 'production' branches are the validation server, the dashboard and comunity-accomplishments?19:05
jonomhall119, right19:05
mhall119ok19:05
jonocielak, right, so the only weird one is UCA19:05
jonowe can have production branches for validation, admin, and gallery19:06
jonoactually I guess we can just do the same for UCA19:06
jonomy thinking here though is that the server won't pull UCA from trunk and instead pull it from the releases PPA19:06
jonoas the accoms live in /usr/share19:06
cielakthe production one? or the staging one?19:07
jonocielak, for production19:07
cielakright19:07
cielakthis is fine with me19:07
jonocool19:07
jonomhall119, sound OK with you?19:07
mhall119jono: yeah, we'd want to pull from something close to what users are using19:08
mhall119so PPA instead of trunk19:08
jonosounds good19:08
jonoyep19:08
jonoOK, I will document this on a wiki page19:08
jonoand then we can point IS at it19:08
jonoto ensure it is what they expect19:09
jonoso the other topic I wanted to discuss was getting ready for the release in 13.0419:09
jonolast night I was chatting to Janos about the gallery19:09
jonounfortunately he can't be in this meeting19:09
jonohe has created a milestone and suggested we file bugs against the milestone that we need fixing in preparation for the release19:10
jonoI wanted to suggest we do the same across our different projects19:10
jonoI know we have many of these bugs already19:10
jonocielak, how are things looking with the daemon/viewer in terms of quality?19:10
cielakwe have not messed up anything, but new features that were added have not yet been thoroughly tested19:11
jonocielak, so I think we are going to want to put in place a more rigerous testing plan for this next release19:11
cielakas for the daemon and the viewer, I tend to assign bugs to 0.4 milestones19:11
jonosounds good19:11
jonodid we decide on a 0.4 release date?19:11
jonoI seem to remeber feb19:11
cielak15 feb19:11
jonocool19:12
jonothis makes sense19:12
jonoso I think if we can shoot to have the server deployed by then and release 0.419:12
jonoand then why don't we focus on getting our accoms and any other bug fixed after that19:12
jonoso the release after 0.4 will be 1.019:12
jonoand will be the release in 13.0419:12
jonomake sense?19:12
cielakso you mean we do not care much about bug fixing for 0.4, but for 1.0 instead??19:13
jonomy thinking is that 0.4 is all about bug fixing19:13
jonoI personally think we should lock down features19:13
jonobut to focus on the server, daemon and viewer mainly for 0.419:13
jonoand then we focus on UCA for 1.0 and any other bugs19:13
cielakokay, let it be this way19:14
jonocielak, is that OK with you?19:14
cielakthere are two more major features I'd like to implement in 0.419:14
jonooh?19:14
cielakso just wanted to ensure I understand the plan well ;)19:14
jono:-)19:14
jonowhich features, cielak?19:15
cielakfirst is getting the daemon to run scripts in paralell19:15
cielakthis will improve the performance, as most of time scripts are just waiting for servers to respond19:15
cielakthis is kind of experimental, I will investigate how that changes resource usage and execution time19:16
jonocielak, sounds cool19:16
cielakand the other thing is support for custom validation servers for third-party collection19:16
jonocielak, right19:16
cielakjust to make our platform fully expandable19:16
jonoyup19:17
jonocielak, are you going to work on both of those features?19:17
cielakI should have some more time to work on that during the winter break, and I am really excited to work on them, but if anyone wants, help is very welcome ;)19:17
cielakplus there is the thing of making the daemon a DBus service19:17
jonocielak, right19:18
jonocielak, would you mind emailing didrocks and discussing the dbus work there?19:18
jonoI know you have not had as much IRC time19:18
jonoI am hoping the dbus thing won't be a blocker for inclusion in the USC19:19
cielakI will, but first I will reproduce all the problems, to clarify what I had troubles with19:19
jonosounds great19:19
jonothanks, cielak :-)19:19
cielakjust being busy recently, but that should change soon19:20
jonook, I will take some time later to put together a release schedule with these dates19:20
jonocielak, awesome19:20
jonowe are not far off our 1.0 goal :-)19:20
jonothis is going to be *awesome*19:20
jono:-)19:20
jonoit will be super cool to see people's trophies on the web19:20
jonoand shared on Twitter :-)19:20
cielakindeed!19:20
jonook, those were my agenda items19:21
jonoany other topics?19:21
s-foxi have none.19:21
cielakI have one19:22
JasnaBencica lot of things I don't understand but this is great :) .... cielak should I still focus on 10.04 or new versions of Ubuntu so I can catch up with you guys easier?19:22
cielakJasnaBencic: we never really supporter 10.0419:22
jonoJasnaBencic, , 12.04 is our minimum version19:22
jonocielak, what topic?19:22
cielakI expect you may be successful running Accomplishments on 10.04, but we can't guarantee that19:22
cielakI wanted to ask if anyone has recently followed the Accomplishments Writing Guide19:23
cielakI don't remember us updating it frequently19:23
cielakso it might be wise to check if it's not outdated19:23
doctormonSorry late, is meeting still happening?19:23
cielakdoctormon: yes! :)19:23
jonocielak, I haven't checked into it recently19:24
jonothis is something we should check into, particularly after 0.419:24
jonodoctormon, still going  :-)19:24
s-foxZilvador,   did you follow the guide?19:24
jonoalthough I have to run in a few mins19:24
cielakso this is a thing that certainly should land on our todo list19:25
doctormonI'm here to tend to the code submitted for gtk-shelves; message to jono might have been lost in the pipes.19:25
Zilvadors-fox, I did. And I am planning to go through it soon to update it.19:26
s-fox^ cielak  :)19:26
cielakdoctormon: I would be interested in examining your code19:26
jonodoctormon, did you file a MP?19:26
cielakZilvador: awesome! you are very welcome to improve it :)19:26
jonook, sorry folks, I need to run to this call19:26
Zilvador:)19:26
jonothanks for joining everyone!19:26
jonofeel free to keep discussing19:27
cielakthanks jono! see you :)19:27
doctormonjono: No, because it's not production code.19:27
jonojust end the meeting when you need to19:27
jonodoctormon, ok19:27
cielakdoctormon: you did a simple proof-of-concept GTK app, right?19:27
JasnaBencicthank you jono19:27
doctormoncielak: lp:~doctormo/junk/gtk-shelves19:27
jonodoctormon, have a screenshot?19:27
doctormonTook a while to root through all the gtk bolocks though. The gtk devs were unhappy about it, *shrug* but it works.19:28
doctormonjono: You've seen the screenshot already, the difference is now you can scroll.19:28
doctormon(without it messing up)19:28
jonodoctormon, can you link us again?19:28
mhall119doctormon: have you tested it on various GTK themes?  I had one way of doing it that worked on some, but not others19:28
cielakdoctormon: testing out, this looks fine, but I wonder what would happen if the items would have variable height19:29
doctormoncielak: Bad things19:29
doctormonmhall119: Yes, this works by painting, not styles.19:30
doctormonjono: Image is gone on imagebin, cielak can you generate a screenshot for jono?19:30
cielakoops, the accomplishments viewer has items of different heights... is there a chance your trick could be applied in such case too?19:30
doctormoncielak: No, you'd have to find the height of the row and change the image accordingly. That's a lot of code.19:31
mhall119doctormon: cool19:31
doctormonRecommend you change the viewer habbit.19:31
doctormon(actually what I have is control over the icon display, it paints them all as a fixed size anyway)19:31
cielakdoctormon: the point is that the different height is not because icon size, but because the accompishment title varies, and long titles (or long translations) result in higher rows19:32
doctormonI took the titles out, too much trouble.19:32
mfischcielak: sorry I had another meeting19:32
* davidcalle has just arrived19:33
cielakyeah, but there is no way we could not display the title in the viewer19:33
cielakhello davidcalle :)19:33
* davidcalle waves :)19:33
doctormonBut it is possible to calculate the pango paint size of the text and consider that in the painting. But we're talking about a very different order of magnatude on the code there.19:33
cielakthere is a screenshot of doctormon's experimental branch: http://i.imgur.com/f6fAY.png19:33
doctormonFor instance, repeating each row is done by the context, we'd have to manually do all that.19:34
cielakdoctormon: yes, I expect so19:34
cielakthis would also significantly affect performance19:34
doctormonProbably. There are ways to show the title though. have a fixed number of letters and use an elipse. Do a hover over screen with title and other info.19:35
* janos_ these icons in the shot are not so good... simpler would be better19:35
doctormonUseful once we get the icon-level and branding destinctions in there. Maybe the trophies will each be unique enough.19:36
cielaka hover would make browsing difficult19:36
doctormoncielak: It's not for browsing, it's for admiring. Browsing is when you want to view the achievements you don't have yet. No?19:36
janos_is the UI searchable with ctrl-F or something?19:36
cielaka fixed number of letters is't a perfect solution too, though, look at how varied the titles are19:36
janos_i think titles are important19:36
cielakjanos_: the trunk/dailies contain already a search feature19:37
cielakdoctormon: so that would make sense only once we have tons of easily distinguishable icons for trophies19:37
janos_cielak: thanks i just meant that to highlight the importance of titles (searchability)19:38
doctormonWe could afix the position and give each more space, 3 lines height each.19:38
janos_but i do see doctormon's point about admiration19:38
janos_can a one-line title be vertical aligned in the middle?19:38
cielaka fixed 3 lines height seems like a kind of a good solution19:39
doctormonjanos_: It would be if we painted it ;-)19:39
cielakyeah, if painted manually, we can do everything19:39
cielakusing a custom, not theme-dependent font+size would be significant19:39
doctormonSo, we don't use the listview as just a painting canvas. We hijack the icon's own paint mechanism to do that side of things.19:40
doctormonSo it's basically 3 hijacks of different widget/parts.19:40
cielakbut drawing the text manually has one disadvantage - the more we move away from standard GTK, the more accesibility features we may loose19:40
doctormoncielak: In this case not, we're not painting the text onto the iconview widget.19:41
cielakbut onto it's embeded label?19:41
doctormoncielak: But the item's own internal draw method. The text is still in the item's data store, the item still has a bounding box. It's all good.19:41
cielakaah19:41
cielakthat's fine indeed19:41
doctormonNow don't ask me about drag and drop :-P19:42
doctormonIt might work ;-)19:42
cielakit should... I guess, but we never supported it anyway19:42
cielakI don't see any use of dragging the trophies, neither within nor outsite the window19:42
cielakdoctormon: and I expect this would not interfere with GtkTreeModelFilters we use?19:43
cielaksilly me, of course it wouldn't19:43
doctormon:-)19:45
cielakmy opinion is that it would be worth to work on that in a viewer's branch19:45
doctormonI've tried hacking on the viewers code, but it's deps are far too high for devel19:46
cielakwhat do you mean?19:46
doctormon(I can't get it to run without a server, dbus and all that other guff running)19:46
cielakdoctormon: you will need dbus and the accomplishments-daemon19:46
cielakserver shouldn't be needed, though19:47
doctormonExactly why do I need the daemon for to test a viewer? Is there no test daemon with pre-set data?19:47
cielakthe viewer is just the frontend for the daemon19:47
cielakit does not know at all how accomplishments work, how to process their files etc19:48
cielakit asks the daemon to do whatever is needed19:48
cielaka good thing about that is that it keeps the viewer much less complicated for you to hack19:48
cielakbut there is no way you could run it without the daemon19:48
cielakanyway, awesome work with the branch :) It would be great if you could reproduce these effects in the viewer, but if not I guess I could work on that, your code seems clear to me19:49
cielakin case of problems with getting the daemon to run you are welcome in #ubuntu-accomplishments19:50
* gepatino waves. sorry I'm late19:50
cielakhi gepatino, good to see you :)19:50
cielakokay, there are 10 more minutes time left, so if anyone wants to discuss anything else, please go ahead!19:51
gepatinois there something to talk about the web gallery?19:52
cielakjanos_: ^19:52
doctormonthanks guys!19:53
mhall119the only problem I had deploying the gallery was that the samples/users.json is out of date19:53
mhall119and wasn't setting the share id/folder properly19:53
mhall119probably made for an older version of the data model19:53
jonocielak, do you have a screenshot of doctormon's branch?19:56
cielakjono: http://i.imgur.com/f6fAY.png19:56
jonocielak, cool19:56
jonowould be cool if the trophies could have a little shadow too19:57
cielakI think this is to be done in the accomplishment icon19:57
jonocielak, so is he going to work on a production branch?19:57
cielakyes, it seems so19:58
jonocool19:58
mhall119we should change all the trophies to ponies19:58
cielakmhall119: +1 for a new ponies-related accomplishments collection19:59
cielakright, we're running out of time and it seems there is nothing more to discuss20:00
cielakthanks everyone for joining us!20:00
gepatinomhall119, could you send a mail with this info to the list? I'll try to take a look at it20:02
gepatinoI mean the issue with the samples/users.json file, not the ponies icons :)20:03
* janos_ reading up20:05
JasnaBencicmeeting done? cielak you'll get a lot of questions from me via mail :)  I'm very happy that I came here despite I didn't understand a lot :)20:07
cielakJasnaBencic: sure. you are also welcome to ask us all via the mailing list we use20:08
JasnaBencicok20:08
janos_mhall119: oh the samples/users.json was just for an initial proof of concept demo20:09
janos_mhall119, gepatino: yup, samples/users.json is just for developers, should not be in prod. I will update the readme20:11
gepatinook20:11
janos_oh i see the meeting is over :) heading over to the other channel then, bye all20:12
mhall119ok20:17
=== Tonio__ is now known as Tonio_aw
=== toddyhb is now known as toddy
=== ev_ is now known as ev
=== Seveas is now known as Guest65145
=== micahg_ is now known as micahg
=== jussi01 is now known as jussi
=== chiluk is now known as chiluk_away
=== fader_` is now known as fader_
=== Tonio_aw is now known as Tonio__
=== Tonio__ is now known as Tonio_
=== Tonio_ is now known as Tonio_aw
=== Tonio_aw is now known as Tonio_
=== Tonio_ is now known as Tonio_aw

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!