/srv/irclogs.ubuntu.com/2014/03/17/#ubuntu-meeting.txt

=== vladk|offline is now known as vladk
=== vladk is now known as vladk|away
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== vladk|away is now known as vladk
=== vladk is now known as vladk|away
=== vladk|away is now known as vladk
=== vladk is now known as vladk|away
=== vladk|away is now known as vladk
=== vladk is now known as vladk|away
=== vladk|away is now known as vladk
=== vladk is now known as vladk|away
=== vladk|away is now known as vladk
=== JoseeAntonioR is now known as jose
=== vladk is now known as vladk|offline
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|offline
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|away
=== chuck_ is now known as zul
=== pgraner` is now known as pgraner
=== lool- is now known as lool
=== jono is now known as Guest78266
=== psivaa_ is now known as psivaa
=== jasoncwarner___ is now known as jasoncwarner
mdeslaur\o16:41
jjohanseno/16:41
jdstrandhi!16:41
tyhickshello16:41
jdstrand#startmeeting16:41
meetingologyMeeting started Mon Mar 17 16:41:34 2014 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:41
meetingologyAvailable commands: action commands idea info link nick16:41
jdstrand#startmeeting16:41
jdstrandThe meeting agenda can be found at:16:41
meetingologyjdstrand: Error: Can't start another meeting, one is in progress.16:41
jdstrand[LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting16:41
jdstranderf16:41
jdstrand#endmeeting16:42
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Mon Mar 17 16:42:06 2014 UTC.16:42
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-03-17-16.41.moin.txt16:42
jdstrand#startmeeting16:42
meetingologyMeeting started Mon Mar 17 16:42:12 2014 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:42
meetingologyAvailable commands: action commands idea info link nick16:42
jdstrandThe meeting agenda can be found at:16:42
jdstrand[LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting16:42
jdstrand[TOPIC] Review of any previous action items16:42
=== meetingology changed the topic of #ubuntu-meeting to: Review of any previous action items
jdstrand[ACTION] chrisccoulson send oxide and qtwebkit benchmark results to mailing list16:42
meetingologyACTION: chrisccoulson send oxide and qtwebkit benchmark results to mailing list16:42
chrisccoulsonthat's done16:43
jdstrandchrisccoulson: cool. where did that go? I haven't gone through all of my email yet from being off friday16:43
chrisccoulsonjdstrand, https://lists.launchpad.net/oxide/msg00003.html16:44
jdstrandawesome!16:44
* jdstrand hugs chrisccoulson :)16:44
jdstrand[TOPIC] Weekly stand-up report16:45
=== meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report
jdstrandI'll go first16:45
jdstrandI have pending updates16:45
jdstrandand an embargoed issue16:45
jdstrandmdeslaur: you're up16:46
mdeslaurI'm on triage this week16:46
mdeslaurI just published a couple of usns, and I have a few more that are at the testing stage16:46
jdstrandmdeslaur: (fyi, sb eattie is off today)16:47
mdeslaurthat's about it, I'll be going down the list after that16:47
mdeslaurtyhicks: you're up16:47
tyhicksI submitted v2 of the dbus-daemon patches upstream last friday16:47
jjohansen\o/16:48
tyhicksso now I'm looking at kdbus and helping out with apparmor work items this week16:48
tyhicksif I can get to it, taking another look at the test-kernel-security.py failures on powerpc would be good, too16:48
tyhicksthat's it for me16:48
tyhicksjjohansen: you're up16:49
jjohansenI'm pulling my hair out, err working on apparmor again this week.16:49
chrisccoulsonheh :)16:49
jjohansenThere where some qrt test failures that sarnold reported at the end of the week that we need to finish looking in to.16:50
jdstrandjjohansen: that is 2.8.95 related?16:50
jjohansenand there are still issues around ipc, with sockets16:50
jjohansenjdstrand: yes16:50
jdstrandhrm16:50
jdstranddo we expect 2.8.95 to land this week?16:51
jdstrand(that is for sarnold and jjohansen)16:51
jjohansenjdstrand: I think so16:52
sarnoldjdstrand: I think so, there were more QRT failures on the nexus 4 than I expected, but it was rough even getting it to run there, so perhaps itshouldn't be a surprise16:52
jdstrandhmm16:53
jjohansenjdstrand: 2 of the failures are due to things not being supported in the test environment/platform and not being properly detected as such. The others I haven't looked into yet16:53
jdstrandtyhicks: didn't you do qrt on the nexus 4?16:53
jdstrandI thought it was working16:53
jdstrandbut might be misremembering16:53
sarnoldjdstrand: .. and I think the 2.8.0 apparmor packaging on the nexus 4 fails your test plan in the same ways as the new 2.8.95 apparmor fails it, so I'm hopeful there :)16:53
tyhicksjdstrand: I'm pretty sure that I did16:53
tyhicksbut I'd guess that sarnold is talking about testing 2.8.95 on the nexus 416:54
jdstrandsarnold: I'm interested in hearing more specifics about that16:54
jdstrandtyhicks: yes, but just said that 2.8.0 fails similarly16:54
tyhicksoh16:54
jdstrandsarnold: we can discuss outside of the meeting16:54
jjohansenyep16:54
jjohansenI think that is it from me, sarnold your up16:55
sarnoldI'm on community this week16:56
sarnoldalso landing apparmor this week16:56
sarnoldand I still have juju, schroot, strongswan, glusterfs, and cgmanager MIRs to start and finish.16:56
sarnoldso I'm really hoping we can land apparmor today :)16:57
sarnoldI think that's it for me, chrisccoulson you're up :)16:58
chrisccoulsonthis week, i've got mozilla updates16:58
chrisccoulsonalso planning to land oxide in the archive16:58
chrisccoulsonand finish my ever growing list of oxide code reviews :)16:59
chrisccoulsonand hopefully get https://code.launchpad.net/~chrisccoulson/oxide/network-callbacks merged, which has turned in to quite a significant chunk of work now16:59
chrisccoulsoni think that's me done :)16:59
jdstrandchrisccoulson: network-callbacks is the lion's share of the UA overrides work you mentioned in the oxide meeting?17:01
chrisccoulsonjdstrand,  it is. but it also contains hooks for storage access permissions (well, currently only cookies, but this is going to be extended to local storage, appcache, indexeddb and webdb as well) too17:03
chrisccoulsonand it has support for third party cookie blocking17:03
jdstrandack17:03
jdstrand[TOPIC] Highlighted packages17:03
=== meetingology changed the topic of #ubuntu-meeting to: Highlighted packages
jdstrandhe Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.17:03
jdstrandSee https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.17:03
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/slurm-llnl.html17:03
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/gksu-polkit.html17:03
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/lib3ds.html17:04
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/google-authenticator.html17:04
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/libdigidoc.html17:04
jdstrand[TOPIC] Miscellaneous and Questions17:04
=== meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions
jdstrandI have some questions related to our major deliverables for 14.0417:04
jdstrandbased on the oxide standup today, oxide should be landing in the archive this week. webbrowser-app will follow after that and there is still quite a bit to do, but it is still believed that we will deliver oxide (and other teams webbrowser-app, UbuntuWebView and webapp-container)17:06
jdstrandthat is awesome17:06
jdstrandapparmor 2.8.95 seems like it is close and sounds like it should land this week. We really need to make sure it does to pave the way for the next update17:06
jdstrandjjohansen: you mentioned that there is a bug related to ipc, with sockets. is that the remaining known bug?17:07
jjohansenthe as in singular? no17:07
jjohansenits one of the remaining problems17:08
jjohansenv5 behavior (old kernel should be fine)17:08
jdstrandjjohansen: assuming 2.8.95 was fixed and landed in the archive, what is left for landing ipc?17:08
jjohansennew kernel has issues17:08
=== vladk|away is now known as vladk|offline
jjohansenjdstrand: there needs to be some revisions around ptrace, signals, and other policy17:09
jjohansenthere needs to be some fixes to the network code17:10
jjohansenI think its doable this week17:10
jdstrandjjohansen: the network code is doable this week?17:10
jjohansenI think so17:10
jdstrandis the sockets ipc bug for this week?17:11
jjohansenyes I plan to fix that this week17:11
jdstrandjjohansen: 'new kernel has issues' - is that the network code, v5 behavior, or something else?17:12
* jdstrand meant to add to his items this week to comment on the ipc policy17:14
jjohansenjdstrand: there are a few things, network code, there is a replacement issue around compound labels, there needs to be a versioning behavior change around the xtrans table in the parser that is fed into the kernel17:14
jdstrandok. so, I'm just trying to create a list so I better understand where we are17:15
jjohansenjdstrand: lets put it this way, its good enough to pass the current regression tests, but issues are known (which just means we need to add more tests)17:15
jdstrandcause I'm starting to get nervous about ipc landing17:16
* jjohansen too17:16
jjohansenoh and I need to do testing of it as a backport on precise and make sure its working right there17:16
jdstrandjjohansen: is the versioning change for this week?17:17
jjohansensome that should be working but I haven't tested yet with the latest kernel17:17
jjohansenjdstrand: yes it is needed17:17
jdstrandjjohansen: is the replacement issue around compound labels the socket issue or something else?17:17
jjohansenjdstrand: it is something else17:18
jdstrandis the replacement issue for this week?17:18
jjohansenjdstrand: I have a patch to fix it, but applying that patch causes the kernel to die for a different but related reason so I need to fix that17:18
jdstrandok17:19
jjohansenjdstrand: the replacement issue can be put off, as things can work with out it.17:19
jdstrandjjohansen: were you able to upload test packages to the ppa based of sarnold's 2.8.95 from last week?17:19
jjohansencompound labels just don't get updated correctly after replacement17:19
jjohansenjdstrand: I have not, yet. I can do that today17:19
jdstrandjjohansen: re ppa> well, only if it helps people. perhaps wait until you have the final packages we plan to upload since they may land tomorrow17:20
jdstrandpersonally, I won't be able to install them today17:20
jdstrandbut could tomorrow17:21
jjohansenokay17:21
jdstrandsb eattie is off today, so delaying to at least tomorrow makes sense to me17:21
jdstrandjjohansen: 'there needs to be some revisions around ptrace, signals, and other policy' - are you talking about policy language?17:22
jjohansenyes, its minor17:23
jjohansenthe actual work won't take long17:23
jdstrandok, so known issues. iirc, no one really responded to the policy language changes in the thread17:24
jdstrandof course, we worked through a lot of that before17:24
jdstranddo we feel like the policy language is in good shape (other than this minor issue)?17:24
jdstrandjjohansen: ^17:25
jjohansenI don't even know that I'd call it an issue, as looking for clarification, so we are happy with a final syntax17:26
jdstrandI see-- so, "yes, the final syntax is very close"17:26
jjohansensomething that needs input from more than just me17:26
jjohansenyes we are close17:27
jjohansenwe are talking about sugar, not functionality17:27
jdstrandright. perhaps respond to the list saying the lack of response is blocking it landing?17:27
jjohansencan do17:27
jdstrandjjohansen: does this look about right> http://paste.ubuntu.com/7109323/17:28
jdstrandoh, I forgot to ask about testing17:28
jdstrandjjohansen: do you know where we stand on coverage for these new features?17:28
jjohansenptrace is pretty good, signal less so17:29
jdstrandjjohansen: I know that is a lot in sb eattie's domain, but curious if you knew17:29
jdstrandok'17:30
jdstrandok17:31
jjohansenthat said, signal is not as bad as it may seem. It is actually getting tested in several of the other regression tests17:31
jdstrandso, I think I captured all that. I'd like outside of this meeting to discuss a plan to land this, with assigning people to do different things17:31
jdstrandtyhicks: should we push the v2 dbus patches once upstream ACKs them?17:32
jdstrandtyhicks: push to trusty that is17:32
tyhicksjdstrand: that's something I've been wondering17:32
tyhicksjdstrand: I think it would be a good idea17:32
jdstrandtrusty is 5 years LTS17:32
jdstrandit seems like it would be17:33
tyhicksjdstrand: I feel confident in them and have tested them a considerable amount17:33
tyhicksI think so17:33
jdstrandok, we need to come up with a plan for all this stuff17:33
jdstrandDoes anyone have any other questions or items to discuss?17:33
jjohansenyeah I think that its a good idea, to push them in17:33
tyhicksall except for the last 2 patches in the series are a drop-in replacement17:34
tyhickswe wouldn't push those last 2 patches, becaues they depend on a dbus-daemon method that isn't in trusty's dbus-daemon17:34
mdeslaurtyhicks: what's special about the last to?17:34
mdeslauroh17:34
tyhicksmdeslaur: it is a new method to get a peer's security credentials17:34
mdeslaurok17:35
tyhickswe would live with our current distro-patched org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method17:35
tyhicksthat's no big deal17:35
jdstrandmdeslaur, tyhicks, jjohansen, sarnold, chrisccoulson: thanks!17:38
jdstrand#endmeeting17:38
tyhicksthanks!17:38
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Mon Mar 17 17:38:41 2014 UTC.17:38
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-03-17-16.42.moin.txt17:38
mdeslaurthanks jdstrand!17:38
sarnoldthanks jdstrand!17:38
jjohansenthanks jdstrand17:38
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|offline
mdeslaur\o21:00
infinityo/21:00
mdeslaurinfinity: having a fun monday? :P21:00
stgraberhello21:01
infinitymdeslaur: Nope!21:01
mdeslaurstgraber: hi!21:01
mdeslaurhehe21:01
infinityIt's a miracle if I get any actual work done on Mondays, with all the meetings.21:01
infinitySo, I think we have apologies from slangasek and pitti today?21:02
mdeslauryep21:02
mdeslaurhow many do we need to be to have quorum?21:02
slangasekin fact I may unapologize21:02
infinitykees: You around?21:02
mdeslaurslangasek: hi!21:02
infinityI'm not actually sure what quorum is for the TB.  4?  Is this documented somewhere?21:03
slangasekwell, I suppose quorum only matters if we need to vote on something :)21:04
mdeslaurtrue, but it was also to satisfy my curiosity :P21:04
stgraber4 sounds right21:04
mdeslaur#startmeeting Technical Board meeting21:05
meetingologyMeeting started Mon Mar 17 21:05:06 2014 UTC.  The chair is mdeslaur. Information about MeetBot at http://wiki.ubuntu.com/meetingology.21:05
meetingologyAvailable commands: action commands idea info link nick21:05
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Technical Board meeting | Current topic:
mdeslaur#topic Action review21:05
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Technical Board meeting | Current topic: Action review
stgraberany besides the LTS stuff which we said we'd do by e-mail (I really need to reply to some of those...) I'm not sure that we have anything to vote on anyway21:05
stgrabers/^any //21:05
mdeslaurso, we still have kees' "MRE" item21:05
mdeslaurbut he's not here, so let's defer that for now21:05
infinityI guess that carries, since he seems to not be around to speak to it. :P21:06
mdeslaurdoes anyone have any other action items that aren't on the wiki page?21:06
mdeslaur#topic Scan the mailing list archive for anything we missed21:07
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Technical Board meeting | Current topic: Scan the mailing list archive for anything we missed
infinityWe could take the LTS stuff from email to meeting, if we feel we're in a position to JFDI on some voting there.21:07
slangasekdid the Ubuntu GNOME people make it today?21:07
infinityslangasek: FWIW, I agree with your "nothing shorter than 3y for an LTS commitment".21:07
slangasekdarkxst said he was interested in discussing21:07
darkxstslangasek, hey, I am here21:07
mdeslaurI'd prefer waiting for a reply to slangasek's email21:07
slangasekdarkxst: hello21:07
mdeslauroh, cool. hi darkxst21:07
slangasekdarkxst: hi - have you seen my mail today regarding the need for an overlap between LTSes to give users a chance to upgrade?21:08
darkxstyes, I just replied now21:08
darkxstonly just woke up ;)21:08
darkxst"Was simply not aware that upgrades aren't enabled until 16.04.1. Certainly our intention is to provide some overlap for upgrades."21:09
slangasekok21:09
slangasekand yes, we generally hold off on flipping the switch on the server regarding upgrades until the .1 point release21:10
infinityIf you're okay with providing 3y, I think we should just go with that and approve it, unless there are objections?21:10
darkxstand if 3 years support is the minimum we will support that time frame,21:10
slangasekand that's a common switch that affects all flavors, not something we could make a per-flavor exception for21:10
slangasekI think "3 years minimum" is the consensus, at least among the TB members here21:10
infinityIs anyone gathering up all the LTS statuses somewhere handily central, so we can do the LP changes required to mark all the packagesets?21:11
slangasekif we have the 3-year committment, are we happy to approve Ubuntu GNOME for LTS?21:11
infinity+121:11
mdeslaur+121:11
slangasek+121:11
stgraber+121:11
slangasekdarkxst: welcome to the LTS :)21:11
darkxstthanks ;)21:12
mdeslaur[AGREED] Ubuntu GNOME is a 3 year LTS21:12
mdeslaurgah21:12
slangasekinfinity: well, I'm gathering them in the sense that they're all in a suitable mailbox21:12
slangasekinfinity: but if I have access to tweak the packagesets, I don't know how; is that something you could take the action for?21:12
infinityIt, hilariously, take an LP MP to make it happen, IIRC.21:13
slangasekand if you need me to send you the summary of LTS flavors I can do that21:13
infinitys/take/takes/21:13
infinityslangasek: If you want to summarize the flavour/support bits, I can handle the LP side.21:13
slangasek[ACTION] slangasek to send infinity the summary of flavor LTS support for adjusting in Launchpad21:13
meetingologyACTION: slangasek to send infinity the summary of flavor LTS support for adjusting in Launchpad21:13
stgraberEdubuntu, Kubuntu, Kylin => 5 years and GNOME, Xubuntu, Mythbuntu and Studio => 3 years21:14
stgraberthat's what I have in my notes here anyway21:14
slangasekok, stgraber steals the action21:14
infinityHeh.21:14
infinitystgraber: Triple check and drop me an email (or an MP, if you're feeling adventurous).21:14
slangasek[ACTION] infinity to mark 14.04 LTS flavor support in Launchpad: Edubuntu, Kubuntu, Kylin => 5 years and GNOME, Xubuntu, Mythbuntu and Studio => 3 years21:15
meetingologyACTION: infinity to mark 14.04 LTS flavor support in Launchpad: Edubuntu, Kubuntu, Kylin => 5 years and GNOME, Xubuntu, Mythbuntu and Studio => 3 years21:15
slangasekthere, it'll be in the meeting notes too21:15
mdeslaurI gather we're all in agreement about those?21:15
stgraberhmm, did I miss an e-mail from Lubuntu or did they not answer wrt LTS status?21:16
infinityI have no objections, after the back-and-forth that was had about XFCE support seemed to come to a reasonable conclusion.21:16
slangasekyes, I'm +1 for all of the above21:16
mdeslaur+1 from me also21:16
gilirstgraber, Lubuntu answered on tb mailing list :-)21:17
stgrabergilir: oh yeah, sorry, just found it.21:18
stgraberso Lubuntu 3 years21:18
infinityAhh, indeed.21:18
infinity+1 to that too.21:18
stgraber+121:18
infinityDoes that actually make all the flavours LTS this round?21:18
stgraberso that's kind of nice, we have all flavours participating in the LTS this time around21:18
mdeslaur\o/21:18
infinityAlright, we should probably commit that to LP this week, so the Final Beta is showing the right support lengths.21:19
infinitySince everything currently says 9m across the board.21:20
mdeslaurDoes anyone have any other items they would like to discuss?21:21
stgrabernothing here21:21
slangaseknot me21:21
infinityNein.21:21
mdeslaurok, moving on21:21
mdeslaur#topic Check up on community bugs21:21
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Technical Board meeting | Current topic: Check up on community bugs
mdeslaurno open bugs21:21
mdeslaur#topic Select a chair for the next meeting21:22
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Technical Board meeting | Current topic: Select a chair for the next meeting
mdeslaurnext in the list is sabdfl21:22
infinitys/sabdfl/pitti/ I'd assume.21:22
mdeslaurpitti: tag, you're it21:22
mdeslaurand...we're done!21:23
mdeslaur#endmeeting21:23
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Mon Mar 17 21:23:21 2014 UTC.21:23
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-03-17-21.05.moin.txt21:23
mdeslaurthanks everyone!21:23
infinityLovely.  Thanks.21:23
stgraberproductive, short and sweet, I like that! thanks!21:23
=== Guest25821 is now known as jrgifford
=== Ursinha is now known as Ursinha-afk

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