IRC logs for #automotive for Wednesday, 2016-01-20

*** jlrmagnus has quit IRC00:00
*** Aleks1917 has joined #automotive00:12
*** mvick has quit IRC00:29
*** jlrmagnus has joined #automotive00:55
*** waltminer has quit IRC01:01
*** mdurnev has joined #automotive01:13
*** Aleks1917 has quit IRC02:00
*** jlrmagnus has quit IRC02:01
*** Sisco has quit IRC02:11
*** Sisco has joined #automotive02:12
*** mdurnev has quit IRC02:22
*** mdurnev has joined #automotive02:23
*** brlogger has joined #automotive02:41
*** Sisco has quit IRC03:17
*** Sisco has joined #automotive03:17
*** parco has quit IRC04:25
*** rjek has quit IRC05:38
*** rjek has joined #automotive05:38
*** juergbi has quit IRC07:14
*** juergbi has joined #automotive07:16
*** gmacario has joined #automotive07:43
*** leon-anavi has joined #automotive08:07
CTtpollardgood morning08:08
*** toscalix has joined #automotive08:14
*** kooltux_ has joined #automotive08:14
toscalixReminder: we will have the GENIVI Tools Team today at 10:00 UTC08:23
*** ctbruce has joined #automotive08:27
*** kooltux_ has quit IRC08:39
*** CTtpollard has quit IRC08:54
*** CTtpollard has joined #automotive08:57
jbocklagewill the steering committee call take place today?08:59
toscalixGENIVI BIT telco haven't finished yet so we will start the GDP call in a few minutes09:02
*** fredcadete has quit IRC09:05
gmacarioWhere can I get WebEx details for the GENIVI Tools Team meeting? I do not see an invite in my calendar09:05
*** tcouniha has joined #automotive09:07
gmacariotoscalix: Where can I get WebEx details for the GDP meeting? I do not see an invite in my calendar09:07
paulsherwoodpresumably those details are the same for the tools meeting - it follows on?09:08
gmacarioGot the email, strangely enough there was no calendar invite09:08
gmacarioThanks paulsherwood09:09
*** fredcadete has joined #automotive09:10
gmacarioI wrongly assumed that WebEx was the same as the previous BIT telco :-(09:12
*** philrob has joined #automotive09:12
paulsherwoodgmacario: yup, sorry - i think the aim is to move to webex audio now09:13
paulsherwoodand the BIT stays private, so has to be different details09:13
*** stevel_ has joined #automotive09:14
*** jeremiah_ has joined #automotive09:25
*** jonathanmaw has joined #automotive09:40
jeremiah_toscalix: Sorry I can't make the call today, but I will try to next week.09:44
toscalixI will update you in our call09:45
jeremiah_Thank you09:45
rjek <-- Linux 3.8 or newer?  Have the keyring functionality enabled?  (You probably do.)  Your untrusted local users can get root.09:48
*** philrob has quit IRC09:50
toscalixGENIVI Tools Team Meeting in 7 min. aprox.09:53
*** kooltux_ has joined #automotive09:53
*** gunnarx has joined #automotive09:59
*** gunnarx has joined #automotive09:59
toscalix== GENIVI Tools Meeting week 03 Jan 20th 2016 ==10:00
toscalixChair today: Agustin Benito (toscalix)10:00
toscalixTime: 1 hour10:00
toscalixUpdate action items:
toscalixObjectives for  2016Q110:00
toscalixAny other topic that cannot be part of AOB that we should discuss?10:00
gmacarioHi there again! Nothing more from myself10:00
toscalixUpdate Action Items10:01
toscalixI created a Kanban Board for this group10:01
toscalixand put the backlog into review state, so we can go through them now10:01
toscalixthe goals is to move those either to ToDo or to In progress if there is somebody that will execute it, including a soft deadline so I can keep track of when I should include them10:02
toscalixin the agenda here10:02
toscalixlet's go for the first one, GDP-610:03
toscalixdiscuss Franca/Franca_installation_automation relationship10:03
toscalixAny taker?10:03
*** samuli has quit IRC10:03
toscalixsorry :-)10:04
gunnarxcatching up... going to fast... :)10:04
toscalixsorry...will slow down10:04
*** samuli has joined #automotive10:05
*** philrob has joined #automotive10:05
gunnarxI had also created a general Tools Kanban board (rapidView=6).  I will delete it.  I thought boards were visible in the "Boards" menu automatically, but no, only when you have visited it once10:05
gunnarxSo rapidView=8 it is.10:06
gunnarxNext, checking the query being used10:06
gunnarxok, same as I have, not including the CIAT issues10:07
gunnarxOK I have caught up now :)10:07
gunnarxWe can look at Go-specific board after we're done with Tools board, OK?10:08
*** fredcadete_ has joined #automotive10:08
toscalixok. I was asking about Tool-610:08
toscalixIf there is no taker....let's move on10:08
gunnarxWas assigned to klaus birken10:08
gunnarxis klaus here?10:09
gunnarxIt's right now an open question to Klaus basically, I would suggest assigning him again, and pinging him if there is no progress...10:09
toscalixit seems no... I will ping him10:09
toscalixNext one is Tool-1110:09
*** fredcadete has quit IRC10:10
toscalixEnsure any hosting/publishing of images meets LRT requirements10:10
toscalixI take that one since it is related to the work we are doing at GDP10:10
toscalixI will provide a soft deadline after the meeting10:11
philrobKlaus is travelling this week (PST)10:11
toscalixNext one... Tool-1210:11
gunnarxhang on toscalix .10:11
gunnarxthe labels on tool-11?10:11
gunnarxcont_integration <- are we using that10:11
toscalixyes... some labels are being used already. There is a labels catalogue that is being used by GDP10:12
gunnarxcurrently "CIAT" means Go-server related issues basically.  I was meaning to discuss that when we talk about that Kanban board.10:12
gunnarxcatalogue on wiki?10:12
toscalixI have as action item together with joel to create a general catalogue10:12
toscalixWiki page:10:12
gunnarxI propose don't use the label "compliance" in the meaning "FOSS license compliance", not in GENIVI where it has another meaning :)10:13
toscalixwe need a catalogue to ensure two people do not use different labels for the same JIRA and Confluence10:14
gmacariotoscalix: +110:14
toscalixgunnarx: good point10:14
gunnarxok thanks for the wiki link10:14
gmacarioAnd possible fewer instance of JIRA and Confluence :P10:15
gunnarx"compliance" is not listed in the catalogue so we're ok10:15
toscalixshould we go for Tools 12 now?10:15
gunnarxPropose to add "license_compliance"?10:15
toscalixwill add it.10:15
gunnarxadded.  ok tool-1210:16
gunnarxcan someone email the question out to mailing lists?10:17
toscalixI added an issue about it10:17
toscalixI take it10:18
gunnarx? isn't tool-12 the issue?10:18
gunnarxyou add a subtask to do something to fulfil tool-12 :-)10:18
toscalixtool-38 about the label10:19
toscalixah, wait, the mail question is about Tool-12, ok, sorry10:19
toscalixSo tools-12 is about opening the discussion in a wider forum?10:20
toscalixcan we assign to somebody to make a proposal about this or to drive the discussion?10:20
gunnarxtoscalix: 10:16 <gunnarx> added. ok tool-1210:20
gunnarxadded means I already added the license_compliance label to the wiki page.10:20
gunnarxwe work fast here :)10:20
toscalixhow it should be10:21
toscalixwho takes the responsibility of driving the discussion about Tool-12?10:21
toscalixlet's move on then10:22
toscalixchoose code review approach for pipelines...10:22
toscalixCodethink is testing the plugin gerrti-go.cd10:22
gunnarxmakes sense to me10:23
toscalixbut that is just one tool10:23
toscalixThe idea of the issue is to explore other options too10:23
gunnarxWell gerrit provides code review as we know10:23
gunnarxWhen it comes to go, what you want is to build proposed patches... usually done by integrating gerrit with the build tool10:24
toscalixAs soon as we get to valid conclusions we will bring them here10:24
gunnarxif you want alternatives, provide commit access to a repo to anyone.  proposed patches go to a branch, the branch is built by build tool the normal way10:24
gunnarxreporting on the result... either ask submitters to manually monitor build tool...  there are also desktop widgets for build status10:25
toscalixSo we can go back to this issue when we bring our results. Are you ok with this?10:25
gunnarxwell that's the alternative I can come up with atm10:25
gunnarxSure.  But how?  Email a request for feedback then?10:25
toscalixI will include it in the issue itself10:25
toscalixyou can watch it so you get notified10:26
toscalixthen we decide how to proceed (mail...or call)10:26
*** pavelk has joined #automotive10:27
gunnarxwelcome pavelk, tools meeting ongoing :)10:27
toscalixNext one then... Tool-2210:27
gunnarxpavelk :
toscalixBuild DLT-Viewer10:28
gunnarxThat one should have the go label10:28
gunnarxActually it does have it, but it has one more label so the query includes it10:28
toscalixadding it10:28
gunnarxwhich it shouldn't10:28
toscalixah, ok10:28
gunnarxbut I don't know how to write that query better either, I tried10:28
toscalixlabels in capital letters is not a good idea with this tool since it is case sensitive10:29
gunnarxcan't find a useful way to query on "includes" a label, only "equal to"10:29
gunnarxit is?10:29
gunnarxI just followed Paul's lead :)10:29
toscalixthis tools needs management10:29
toscalixpower comes with a price10:30
gunnarxok, well anyhow, skip tool-22, we'll take it in the Go review10:30
toscalixAs you probably know, we are working on having simple acceptance tests in GDP10:31
toscalixbut that is just a little aspect.10:31
pavelktoscalix: what framework do you use?10:31
stevel_I plan to reconnect with Collabora on use of their LAVA farm in coming weeks10:31
toscalixwe will go for scripts at the beginning10:31
pavelkOK, are there any sample available?10:32
toscalixnot yet10:32
toscalixwe are still working on making the images available to then check licenses10:32
gunnarxfor deploying/running tests there's LAVA, or as said before we could investigate JTA10:32
toscalixsomebody needs to take ownership of this tasks and bring a proposal10:33
stevel_At very least JTA should have some test cases10:33
toscalixor at least move this topic forward10:33
stevel_Happy to take sub-task to work with collabora on LAVA10:33
gunnarxfor writing the test code there are different contributions from different companies.  If a company writing a component has their own preferred way they won't change, but normally it's possible to run and collect results from different ones.10:33
gunnarxFor newly written component tests I'd cast a vote for gtest (google test)10:34
toscalixstevel_: can you add the subtask yourself?10:34
stevel_Sure if you want.10:34
toscalixgo ahead please10:34
stevel_I was assuming lead wanted to be one to add. But I can do :)10:34
toscalixthis is not "my kanban" but ours :-)10:34
toscalixgreat, thank you10:35
toscalixNext one is Tool-2710:35
stevel_Viva Freedom!10:35
toscalixMapping of Franca IDL constants to the UML model missing in YAMAICA10:36
pavelkTools-27 looks more like a feature request for Yamaica10:36
pavelk...and as such into their issue tracker10:36
gunnarxwhich means bugzilla?  until migration is completed?10:37
pavelkI don't know what they currently use10:37
toscalixwho is the main contact for YAMAICA?10:37
gmacarioAccording to this is and
pavelkI suspect this is Manfred Bathelt10:38
gmacarioMain contacts are Manfred Bathelt and Juergen Gehring - See
gunnarxyes and Manfred is the default assignee on a new bugzilla10:38
toscalixthanks gmacario Then I will contact them so see how they want to handle this request10:39
gunnarxWe should just transfer it to bugzilla I suppose?10:39
toscalixThat is my thought but since we are migrating...let's see.10:40
toscalixI will contact them first, just in case10:40
gmacarioYes and BTW I see zero bugs in Bugzilla so far10:40
gunnarxtoscalix, these tools issues we're discussing, they are for driving tools forward10:40
gunnarxbug reports go to specific projects I assume, not to tools project?10:41
gunnarx^^ bug and feature requests10:41
toscalixexactly, but seems it was added here as action item, I want to make sure we close it properly10:41
gmacarioOne suggestion for driving tools forward is speeding up killing old tools10:41
toscalixgmacario: I hope that is the outcome of this10:42
gunnarxso as I see it, bugs will in the future go into JIRA but under a different project, but at the moment bugzilla still being used for the bugs10:42
toscalixin GDP we are about to stop using bugzilla for bugs, moving them to JIRA and making a note in every open bug10:43
toscalixwe are still talking about how to do that10:43
gunnarxif you agree then I suggest to transfer TOOL-27 to bugzilla, but of course toscalix, if you feel like sending an email you cna10:43
toscalixwe will publish a mail about it10:43
toscalixand talk to Joel10:43
gunnarxunfortunately the original requesting person has been lost in various moves between systems, because I assume it's not a feature request from paulsherwood10:43
toscalixSince this is the first time I go through this, I prefer to talk to them first instead of putting a feature request directly in bugzilla10:44
philrobseems wise10:44
toscalixbut the default behaviour should be to go to whatever tool they are using ... yes10:44
gunnarxit's up to you, but I don't see it10:44
gunnarxbut yes, since you will look like the person requesting, it might be weird to just put it in bugzilla10:45
gunnarxpavelk, are you or could you be a champion for this feature request?10:45
pavelkWhich one? Tools-27?10:46
toscalixI propose myself to do it10:46
gunnarxtoscalix, again up to you, but there is really no need to agree that bugs/feature requests are reported in bugzilla.  this is already the process.  maintainers _should_ expect to get them10:46
gunnarxand react to them.10:46
toscalixI just do not know them so...10:46
gunnarxpavelk, yes tool-27, just looking for a champion10:46
gunnarxbecause I don't know who made the request originally10:46
toscalixI have a lot in my plate, if pavelk takes it over...I will be happy10:47
toscalix13 min to go10:47
pavelkI don't use Yamaica, but can move the request to Bugzilla10:47
toscalixpavelk: assigned. Thank you10:48
pavelktoscalix: skipping Tools-28?10:48
toscalixit has assignee10:49
pavelkAh, OK10:49
toscalixI am concentrating right now in those that don't10:49
toscalixthat is, the ones I am as assignee10:49
gunnarxtool-29 was more of a tools team charter thing, goal setting, working towards better / wider tool testing on multiple platforms10:49
pavelkIt overlaps with Tool-24...10:50
*** kooltux_ has quit IRC10:50
toscalixI think that we need somebody that put some though in testing and drive a discussion that leads into a proposal10:50
toscalixso we merge all this issues into a single one10:50
gunnarxtool-24 is a little more focused.10:50
gunnarxI could bring the question to YAMAICA team but then the general goal setting would be lost10:51
pavelkgunnarx: so tool-24 is a subissue of tool-29?10:51
gunnarxdon't know10:51
toscalixI would say so. We can put it as sub-task10:51
gunnarxtoscalix, maybe worth thinking about how to organize tool team higher-level goals, compared to actions10:51
toscalixthe second point for today was.... 2016Q1 goals10:52
toscalixwe will have no time...but yes10:52
gunnarxI can own tool-29 if you want, but it's a long term goal thing10:52
toscalixlet's leave the testing topic for that discussion?10:52
philrobwe discussed with Manfred how to recycle the CommonAPI C++ test suite in the context of CIAT, Manfred was requested to provide Jenkins job configuration to enable more analysis10:53
pavelkIt looks like tool-29 is more about testing the /tools/, while tools-24 is about a tool for testing10:53
gunnarxpavelk, you are right10:53
toscalixphilrob: I would appreciate if you add a comment on the task itself describing what was discussed, or a link we can follow, at least10:53
philrobwill do10:53
toscalixphilrob: thanks10:54
toscalixTool-29...we skip it for now10:54
gunnarxphilrob, jenkins job for building is not really necessary, we already build commonapi tools on go server.  but if it is for testing, yes10:54
toscalixSeems a reminder note from a previous meeting10:55
gunnarxoh, another big lofty goal :)10:55
toscalixI wonder if any of you remember an action item out of this discussion10:55
pavelkthere are some initial thought on the (private) wiki10:55
toscalixIt is stated as Improvement10:55
gunnarxI have much outstanding work to do so I shouldn't take this on...10:55
toscalixWhat I would reuqet then is an Asignee to move it forward or leave it as it is for now10:56
gunnarxbut a picture outlining goals for target vs host dev environment would help communication a lot10:56
toscalixgunnarx: if you are too busy, I prefer to leave it as it is than having it in the backlog forever10:57
toscalixsince it will increase the Tolls team management cost to add it to the backlog (ToDo)10:57
pavelktoscalix: the earlier strategy was to find volunteers to document their ways to build components for GEnIVI10:57
gunnarxwell it relates to things we must do imho10:57
toscalixany taker to move this forward?10:58
*** jonathanmaw_ has joined #automotive10:58
toscalix2 min left...10:58
gunnarxno but I'll add some comment to clarify next steps10:58
*** jonathanmaw_ has quit IRC10:59
toscalixthat is a step forward, thanks10:59
*** jonathanmaw_ has joined #automotive10:59
toscalixlats one.... Tool-3110:59
toscalixTest Eclipse Automotive release as basis for franca_install_automation instead of Eclipse DSL release10:59
toscalixany taker to move this issue forward?11:00
pavelkSomebody remembers who was the originator?11:00
gunnarxI wanted Klaus to help me out on it.11:00
gunnarxgive me a sec11:00
pavelkIn my rough understanding, Eclipse Automotive has a different scope, but this is to be verified11:01
gunnarxok, info from trello is not moved over.  so we follow the Trello link to get the status?11:02
pavelkEclipse DSL is for tools developers.  Eclipse automotive seems to be for automotive software developers11:02
gmacarioI need to leave now. Talk to you soon!11:02
*** jonathanmaw has quit IRC11:02
toscalixgmacario: thanks11:02
pavelkthe task might be then about packaging franca and CAPI tools for Eclipse Automotive11:03
gunnarxIt's simply whethere franca_install_automation should be based on Eclipse Automotive or not11:04
pavelkOh, I take it back: "The EAIWG will define and maintain the requirements, a technical architecture and a roadmap that defines a common platform for the development and management tools required for the automotive electronic development processes. "11:04
toscalixgunnarx: is it ok to put this in your plate so next week you report your conversation with Klaus?11:04
gunnarxI've not been able to get good input from creators of Eclipse Automotive, which I believe is Klaus' company11:04
gunnarxtoscalix, yes, assign me11:04
gunnarxand I'll assign klaus, or kill it :)11:04
philrobassign it to klaus11:05
toscalixSo we are done. 5 min past11:05
toscalixsorry for the delay11:05
toscalixwe will finish here11:05
toscalix== GENIVI Tools Meeting End ==11:06
toscalixI gess after this meeting marathon, since it is the first time...some need a coffee break :-)11:08
toscalixthank you for participating/following up the meeting. It was a tedious but neccessary one11:09
toscalixI beliueve11:09
gunnarxSure it's necessary to go through all open topics but I was missing discussions about way-of-working not covered today.  We had not the time to look at the Go-server related board11:13
gunnarxsome things hard to discuss effectively on IRC11:14
*** jonathanmaw__ has joined #automotive11:15
*** jonathanmaw__ has quit IRC11:15
gunnarx I notice the tools kanban board query includes the Go pipeline cards.  I would propose a query that excludes them since they are on a separate board.11:15
*** jonathanmaw has joined #automotive11:15
toscalixI will try to create a filter expluding the label "CIAT"11:17
*** jonathanmaw_ has quit IRC11:18
toscalixa question is.... if is already in production... would it make sense to treat it like any other "team"11:18
toscalixI mean... its own project?11:19
toscalixwe can also move there what we are doing related with go and CIAT11:19
toscalixwe do not need to do it now though11:20
pedroalvareztoscalix: we are waiting for you in the meeting11:21
pedroalvarezerr.. wrong window11:21
*** jonathanmaw has quit IRC11:29
*** jonathanmaw_ has joined #automotive11:29
pedroalvarezso, has anybody tried ?11:29
*** jonathanmaw_ has quit IRC11:29
*** jonathanmaw has joined #automotive11:29
CTtpollardit does look good, I like that you can screen share a specific application, and not just the desktop11:30
*** kooltux_ has joined #automotive11:46
gunnarxtoscalix, yes that's what I wanted to agree upon.  Options: Use the label as of now, add a "component" instead (makes most sense), or make it an own project.  I think for me the component option would be fine.11:51
gunnarxpedroalvarez, tried once, didn't work :)11:52
gunnarxneeded chrome to work, which defeats the whole purpose :)11:53
gunnarxseriously, I guess it *should* work with firefox11:53
pedroalvarezdidn't expect it to not work for some browsers11:57
CTtpollardit claims to work with firefox11:58
rjekwin 2311:59
pedroalvareztbf i haven't tried a real call. Just opened the app12:00
*** philrob has quit IRC12:08
gunnarxWebRTC is cool, if it works12:11
pedroalvarezas an alternative to have the meetings?12:14
*** stevel_ has quit IRC12:19
*** CTtpollard has quit IRC12:28
*** CTtpollard has joined #automotive12:29
gunnarxsuccess! (with firefox)12:38
pedroalvarezI understand your previous comment now. Didn't know used WebRTC12:42
*** mdurnev has quit IRC12:43
gunnarx sure12:43
gunnarxthe base library is open source too github/appearin12:43
radiofreehmm is there a known issue with qt5.5 (+ qtwayland ivi-shell patches in qt's gerrit) and ivi-extension?12:44
radiofreethe ivi-shell component of the patches work (things show up in hmi-controller)12:44
gunnarxactually maybe it's just the rest api binding/sdk they published.  haven't looked in detail12:44
radiofreehowever when you use ivi-extension the qt app crashes when you make it visible12:44
radiofree(i.e make the surface visible on a visible layer... up until that point it's fine)12:45
gunnarxradiofree, what system, what configuration?12:45
radiofreeerm.. it's a non-genivi system running on a jetson, weston 1.912:45
gunnarxtry it on GDP so someone can help you ;-)12:46
radiofreeivi-extension does work, it's just Qt apps + QtWayland 5.5.1 crash under there12:46
gunnarxmaybe someone can help you anyway...12:46
* radiofree will give that a go12:47
CTtpollardI've got a dev branch of gdp working with weston 1.6 and qtwayland 5.4.212:48
radiofreei'll debug a bit more first, it's odd it works fine in ivi-shell using hmi-controller, i wonder what ivi-extension is doing to crash it12:48
CTtpollardI believe agl have a later version of qtwayland working with ivi shell12:48
radiofreeyes, this version works with ivi-shell, it just doesn't work with ivi-extension12:48
CTtpollardmy build is using extension 1.212:50
CTtpollardpedroalvarez: what extension were you trying with weston1.9?12:50
radiofreeright, ivi-shell and ivi-extension *work*12:50
radiofreeqt apps using qtwayland *with ivi-shell patches* upgraded to qt 5.5.1 work in ivi-shell (i.e stock upstream weston with ivi-shell/hmi-controller and the fancy window manager demo)12:51
pedroalvarezwayland-ivi-extension but was with qt5.412:51
radiofreeqt (and *only* qt) apps *don't* work when using ivi-extension12:51
radiofreethey work up until the point (i.e get surface, add to layer, move... region etc....) you make them visible12:52
radiofreethen bam! segfault!12:52
radiofreeusing patch set 7 from
radiofreepatch set 7 being the last patch set before they were reworked to apply to the dev branch for 5.612:53
*** pavelk has quit IRC12:54
radiofreeusing qt 5.5.x will be better in the gdp, you don't have to patch qtmultimedia to use gstreamer 1.0 anymore13:00
radiofreewell, better in gdp if this ivi-extension bug can be fixed...13:00
gunnarxradiofree, what is this "non-genivi" system you are talking about?  makes no sense to me...13:00
*** kooltux_ has quit IRC13:02
*** kooltux_ has joined #automotive13:03
radiofreegunnarx: i'm not working on the gdp, or genivi, i've just noticed ivi-extension doesn't work with qt5.613:04
radiofree5.5 even13:04
*** kooltux_ has quit IRC13:14
*** kooltux_ has joined #automotive13:16
*** waltminer has joined #automotive13:22
paulsherwoodgunnarx: were you joking? there are non-genivi systems in the world :)13:29
gunnarxin a meeting, will explain later :)13:29
*** kooltux_ has quit IRC13:32
*** pavelk has joined #automotive13:47
*** toscalix_ has joined #automotive13:49
*** samuli_ has joined #automotive13:50
*** Figure_ has joined #automotive13:51
*** wto_ has joined #automotive13:52
*** KaZeR_ has joined #automotive13:54
*** leon-anavi has quit IRC13:56
*** Figure has quit IRC13:56
*** samuli has quit IRC13:56
*** toscalix has quit IRC13:56
*** KaZeR has quit IRC13:56
*** wto has quit IRC13:56
*** CTtpollard has quit IRC13:58
*** jonathanmaw_ has joined #automotive13:58
*** jonathanmaw__ has joined #automotive13:59
*** ctbruce has quit IRC13:59
*** jonathanmaw has quit IRC14:00
*** Aleks1917 has joined #automotive14:02
*** leon-anavi has joined #automotive14:03
*** jonathanmaw_ has quit IRC14:03
*** CTtpollard has joined #automotive14:04
*** ctbruce has joined #automotive14:05
pedroalvarezgunnarx: from "Video conversations with up to 8 people for free."14:25
paulsherwood+11 for appear.in14:26
pedroalvarezwe are just giving it a try, and it works nicely14:28
pedroalvarezalthough it seems you can't share your screen from firefox14:28
radiofreecan you share your screen with any browser in
radiofreerequires an extension14:33
radiofree(in chrome)14:33
CTtpollarddid not request a plugin for me, and I can share specific applications not just the screen14:34
radiofreeworks in firefox hello14:34
radiofreeCTtpollard: in
CTtpollardahhh, it appears I have the extension installed14:35
*** ToxicGumbo-work has joined #automotive14:36
CTtpollardno idea when I enabled that14:36 works with screen sharing14:39
radiofreehow many people can join that?14:39
*** waltminer has quit IRC14:43 814:43
*** gunnarx has quit IRC14:43
*** gunnarx has joined #automotive14:44
*** gunnarx has joined #automotive14:44
radiofreepedroalvarez: no, talky.io14:44
pedroalvarezdon't know then14:44
pedroalvarez"Add over 15 people to the conversation."14:46
radiofreeand screensharing works without any plugins14:47
gunnarxWell... it allows me to share web browser only right now.14:48
gunnarxdoesn't seem 100%14:48
gunnarxlol, they have an integrated game to play while you wait14:50
radiofreeterminal sharing works for me, this is important :)14:52
gunnarxI had a few friends for a short while, but then they left :(14:52
gunnarxSeems to work though :)14:52
pedroalvarezrequested me to install a plugin for screen sharing, but thats ok14:52
gunnarxOh, I guess I was not identified either.  "Your Name"14:53
gunnarxwhat?  did do that?14:53
radiofreepedroalvarez: talky?14:53
gunnarxhere no plugin, just accepting access to audio and video14:53
pedroalvarezradiofree: yeh14:54
radiofreeyep, no plugin, and i shared my terminal window14:54
pedroalvarezusing chrome here14:54
radiofreepedroalvarez: in firefox?14:54
pedroalvarezi can try again14:54
gunnarxff for the win14:54
pedroalvarez"Chrome requires a helper extension available from the Chrome Web Store. You can pick a window or desktop to share, which helps a lot when using multiple monitors!"14:55
gunnarxpedro, create your own room and try it.14:56
gunnarxhint: use arrow keys to control the space ship14:56
pedroalvarezthat's awesome14:57
radiofreeit's settled then ;)14:57
jbocklageSteering Committee meeting?15:04
*** waltminer has joined #automotive15:07
*** jonathanmaw__ has quit IRC15:10
*** jonathanmaw has joined #automotive15:13
gunnarxthe damn lander game is worse than flappy bird, will drive you insane!15:15
gunnarx\o/ I just landed. Need to stop now.15:16
*** Aleks1917 has quit IRC15:21
*** Aleks1917 has joined #automotive15:22
*** jonathanmaw has quit IRC15:34
*** CTtpollard has quit IRC15:41
*** CTtpollard has joined #automotive15:42
*** gmacario1 has joined #automotive15:49
*** gmacario has quit IRC15:49
*** jonathanmaw has joined #automotive15:49
*** toscalix_ is now known as toscalix15:55
toscalixjeremiah: suggested Jitsi for GDP calls any experience having several people in the video conference?15:56
toscalixif not, I can try15:57
*** Tarnyko2 has joined #automotive16:09
*** mvick has joined #automotive16:10
*** Aleks1917 has quit IRC16:28
*** wto_ is now known as wto16:50
*** Sisco has quit IRC17:09
*** Sisco has joined #automotive17:17
*** ctbruce has quit IRC17:21
*** fredcadete_ has quit IRC17:26
*** jonathanmaw has quit IRC17:31
*** leon-anavi has quit IRC17:33
*** jlrmagnus has joined #automotive17:37
*** Aleks1917 has joined #automotive17:48
*** gan has joined #automotive18:16
*** gan has joined #automotive18:16
*** toscalix_ has joined #automotive18:16
*** gunnarx has quit IRC18:22
*** toscalix has quit IRC18:22
*** RzR has quit IRC18:22
*** ZrZ has joined #automotive18:24
*** waltminer has quit IRC18:29
*** ZrZ is now known as rZr18:30
*** pavelk has quit IRC18:56
*** pavelk has joined #automotive18:56
*** Tarnyko2 has quit IRC18:56
*** samuli_ has quit IRC18:56
*** samuli_ has joined #automotive18:56
*** jlrmagnus has quit IRC18:59
*** jlrmagnus has joined #automotive19:02
*** gmacario1 has quit IRC19:04
*** gmacario has joined #automotive19:34
*** pavelk has quit IRC19:37
*** jlrmagnus has quit IRC19:38
*** toscalix_ has quit IRC19:55
*** waltminer has joined #automotive20:07
*** toscalix_ has joined #automotive20:18
*** toscalix_ has quit IRC20:28
*** jeremiah_ has quit IRC20:37
*** waltminer has quit IRC20:40
*** toscalix_ has joined #automotive20:42
*** jlrmagnus has joined #automotive20:46
*** toscalix_ has quit IRC20:48
*** jlrmagnus has quit IRC21:06
*** jlrmagnus has joined #automotive21:20
*** gan has quit IRC21:28
*** waltminer has joined #automotive21:47
*** jlrmagnus has quit IRC21:52
*** ToxicGumbo-work has quit IRC21:56
*** jlrmagnus has joined #automotive21:57
*** waltminer has quit IRC22:47
*** Aleks1917 has quit IRC22:56
*** Aleks1917 has joined #automotive23:01
*** waltminer has joined #automotive23:12
*** jlrmagnus has quit IRC23:33
*** jlrmagnus has joined #automotive23:48

Generated by 2.14.0 by Marius Gedminas - find it at!