14:30:08 #startmeeting SailfishOS, open source, collaboration 28th of January 2016 14:30:08 Meeting started Thu Jan 28 14:30:08 2016 UTC. The chair is stephg. Information about MeetBot at http://wiki.merproject.org/wiki/Meetings. 14:30:08 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:12 lbt i recall you inquiring about merbot before too :P 14:30:14 #info Happy Data Protection Day and welcome to the second SailfishOS OSS and collaboration meeting of 2016 14:30:20 #info Meeting information and agenda can be found here: https://lists.sailfishos.org/pipermail/devel/2016-January/006903.html 14:30:26 #info tortoisedoc hello world developer 14:30:27 I'm the meeting chair today and will be doing my best to keep time and order. Please behave, be gentle and show due respect. 14:30:33 We have a few things to get through today so please lets not stray from the topics too much 14:30:39 #topic Brief introduction (5 minutes), please prefix your name/handle with #info 14:30:45 info away! 14:30:47 :D 14:30:49 #info Kimmo Lindholm, community, wannabe porter, tohs et al 14:30:51 duh 14:30:56 tortoisedoc: triggerhappy? 14:31:04 #info tortoisedoc hello world developer 14:31:11 #info David Greaves, Sailor and Mer guy 14:31:12 #info Steph Gosling, community, also wannabe porter 14:31:13 kimmoli : nah, typing tourette 14:31:20 #info elfio, sailfishOS fan 14:31:22 #info Munnu Jolla enthuatist, wannabe developer 14:31:28 #info Tommi Keisala, community 14:31:30 #info occirol, community, developer 14:31:35 #info Simonas Leleiva, sailor (porting, pootle, and stuff) 14:31:35 #info Juhani Lassila, Jolla 14:31:37 #info schmittlauch, Jolla phone owner, tablet backer, community member, hopefully future developer 14:31:40 #info M4rtinK, community member, modRana developer 14:31:47 #info Eugenio Paolantonio, community member 14:31:56 #info Topias Vainio, founder of the Telegram Jolla Fan Club group, wannabe Sailfish dev 14:31:56 #info François, community 14:31:57 #info tathhu, community 14:32:07 #info Lewis Rockliffe, community 14:32:15 #info Pami Ketolainen, backend developer @ Jolla 14:32:15 #info Richard de Bruin, community 14:32:23 #info Eetu, community 14:32:29 #info pascalstein, Jolla phone owner, Jolla tablet owner, community member, believer in SailfishOS 14:32:45 #info Martin Brook, vgrade, community porter 14:32:47 pascalstein : i buy your jolla tablet any day :P 14:33:21 tortoisedoc: not for sale, i love it too much 14:33:27 #info Vesa-Matti Hartikainen, Jolla, SW Program Manager 14:33:37 #info Jarkko Lehtoranta, developer @Jolla 14:33:41 #info Amilcar Santos, app developer 14:33:47 bah why it will be deadware soon enoug ;) 14:34:00 pascalstein : so sell it to me :P 14:34:08 (j/k) 14:34:15 tortoisedoc: how much would you pay for a tablet with SF2.0 wihout prop bits? 14:34:23 #info Carmen Fernández, community, sailor 14:35:02 ok then 14:35:06 vgrade : lets move this discussion to #sailfishos 14:35:15 Because tortoisedoc is constrained with time we're going to deal with his two (short items). On the agenda first, please stay on topic, we won't be long! 14:35:23 #info due to participant time constraints the agenda is to be juggled slightly 14:35:33 #topic libcontentaction Merge Request on Mer (tortoisedoc, 5 minutes) 14:35:37 ortoisedoc, stage is all yours 14:35:38 ? 14:35:38 thanks stephg; 14:36:12 daitheflu: tortoisedoc to do his bits quickly then the agenda will be as per the email 14:36:15 id like to get some feedback on the timeframe for the libcontentaction merge request that is currently pending on my side 14:36:24 link ? 14:36:51 #info Carol Chen, community memeber (sorry for being late) 14:37:11 #info a tentatively valid MR for libcontentaction is ready; what are the next steps? What timeframe to expect? 14:37:34 lbt : see mer-core/libcontentaction on mer git (for some reason my credentials do not seem to work anymore) 14:37:50 tigeli was reviewing the commit 14:38:19 but there is no info on the next steps (what needs to be done next, what will be followed up..) 14:38:20 https://git.merproject.org/mer-core/libcontentaction/merge_requests/1 14:38:34 quicker than me :) 14:38:48 #link https://git.merproject.org/mer-core/libcontentaction/merge_requests/1 14:39:32 couple more minutes guys, the silence is deafening ;) 14:39:48 or are we done here? 14:39:54 I guess the first thing is to check the Maintainer file 14:39:57 i can make some noise but i might get kicked out ;) 14:40:00 to see who should be nagged 14:40:05 ok i see 14:40:07 so its tigeli 14:40:16 but what I am saying is 14:40:22 Tigeli is not working at Jolla anymore so probably not having too much time to contribute in his new job 14:40:35 oh, that's sad news 14:40:37 http://www.merproject.org/dash/repo/libcontentaction.html 14:40:38 can there be some things done on my side to help expedite ? 14:40:47 #link http://www.merproject.org/dash/repo/libcontentaction.html 14:40:48 #info Fabio Isgro community 14:40:51 (test cases, etc) 14:41:06 ...which leads us to the next topic 14:41:08 #info bree, tester 14:41:15 tortoisedoc: ping all of the maintainers 14:41:22 ok this is unresolved so onto tortoisedoc next topic: 14:41:24 sledges : done already many times 14:41:28 #topic Merge Request policies on Mer (tortoisedoc, 10 minutes) 14:41:35 yes 14:41:37 all 12 maintainers? 14:41:38 thanks stephg 14:41:41 lol 12? 14:41:44 http://www.merproject.org/dash/repo/libcontentaction.html 14:42:12 #info previous link is incorrect - use http://www.merproject.org/dash2/ until I replace the /dash one with the newer version 14:42:17 this topic is about understanding how to proceed and what to expect when submitting a merge request 14:42:20 thx lbt 14:42:31 is there a process of sort? 14:42:32 #link http://www.merproject.org/dash2/repo/merproject.org/mer-core/libcontentaction.html 14:42:47 also, which tools need to be taken in consideration ? 14:42:57 this all in hindsight for the developer to be able to help as much as possible 14:43:04 and facilitate the merging 14:43:28 for instance, for libcontent action implementation is done, and testing on device is done as well 14:43:29 all should be documented in https://wiki.merproject.org/wiki/Contribution which needs housekeeping:) 14:43:32 tortoisedoc: the process was evolving and then jolla hit the iceberg and ... it needs to be rescued and dried out 14:43:34 but how about unittests? 14:43:41 (i.e. dash and stuff isn't documented there now... sorry about that) 14:43:53 lbt : sure thing, not blaming the hard working crew, just hunting for solutions :) 14:44:15 #info contribution instructions to be found in the mer wiki 14:44:20 #link https://wiki.merproject.org/wiki/Contribution 14:44:27 for instance, I (as a developer) am not even aware if the unittests are run at all or not 14:44:34 sure. It's part of the timeframe ... it's good to highlight this. 14:44:35 (by the OBS I mena) 14:44:55 I have some tasks to update the automation on Mer OBS to run various checks 14:45:03 or if they are supposed to be (of course they should, but you never know..) 14:45:59 run various checks include unit tests I assume? 14:46:01 5 more minutes folks 14:46:16 on Mer tests are only generally run as part of the build 14:46:18 #info those instructions are outdated and needs lots of gardening 14:46:27 thx sledges 14:46:40 there was (a *long* time ago) a qa-runner system that never really got off the ground 14:47:49 okay 14:47:58 sorry my time's up, so i need to leave 14:47:59 but 14:47:59 lbt: nice dash2, with obs projects and archs \o/ 14:48:06 you're right that we should quantify this 14:48:17 i will then ping all 12 mantainers one by one :P until someone can tell me what to do next with libcontentaction :D 14:48:27 anyone up for an action to garden the Contribution page ? 14:48:35 thanks guys! 14:48:41 maybe me? 14:48:54 * sledges will help lbt 14:49:04 mark you two down then for action? 14:49:05 lbt: happy to help, but i will probably need guidance as to what it needs to say 14:49:05 tortoisedoc_away: I really haven't had any extra time to work on mer, sorry 14:49:23 #action lbt, sledges & others to garden the contribution page 14:49:25 hi tigeli 14:49:35 thx lbt 14:49:48 one more minute unless tortoisedoc_away is actually away 14:50:23 ok thanks everyone for indulging us with the reordering of the agenda 14:50:31 #topic Status update from Jolla (tablets, financing, resourcing, etc.); please address the subject of tablet covers - LastuCase and MapBagrag (10 minutes) 14:50:38 As with last week, the topic wasn't asked by anyone specifically for this meeting but coderus had raised it in the past. 14:50:43 It's marked as sticky in TJC. 14:50:51 I see we have several sailors today which is good, so here we go.. 14:51:11 #info a new blog post on the official Jolla blog detailing shipment for some tablet owners 14:51:16 #link https://blog.jolla.com/jolla-tablet-closure/ 14:51:16 #link https://blog.jolla.com/jolla-tablet-closure/ 14:51:24 too quick :P 14:51:30 argh!:)) 14:52:11 veskuh_: or jlassila is there anything Jolla would like to say? 14:52:11 Hi all! So I'm here to answer any questions you have regarding the latest blog. 14:52:14 any questions to that? jlassila is here to help with answers :) 14:52:15 #link https://blog.jolla.com/jolla-tablet-closure/ 14:52:16 thanks 14:52:20 Closure indeed. Glad to see clear communication as to what's happening, moving forward. 14:52:26 gerbick: +1 14:52:45 So basically, if you did not read the post yet: 14:52:56 The situation in a nutshell is that we are able to ship a small additional batch of tablets (540 to be exact) that have been assembled already. For all the rest we have a refund program described in the blog. 14:53:09 jlassila: Can you add an option "Donate full amount to Jolla" 14:53:20 To help the restructuring and not want the refund 14:53:21 What's happening with those accesories like the LastuCase? Will they be refunded? 14:53:24 Yes this will definitely be an option! 14:53:24 pascalstein: I saw that comment and think it's a nice gesture 14:53:32 how about the referral-race tablets? :P 14:53:35 pascalstein +1 14:53:35 How may tablets were sending in first batch? 14:53:40 Yes all accessories will be refunded as well. 14:53:46 cfb014, 121 :P 14:53:50 According to the plan 14:54:06 Unless you ordered directly form e.g. Lastu of course. 14:54:11 Thanks, @tathhu 14:54:34 Is Jolla dropping the idea of SailfishOS on tablets or are there still plans about other tablets? 14:54:35 jlassila: I think there was also concern of the makers of the Lasucase and mapbagrag being unpaid as of yet 14:55:21 Well we'll deal with this project first before planning additional tablets. 14:55:38 also any idea where all the "Jolla Tablets" that have been showing-up on various Chinese actions sites are coming from ? 14:55:39 some people have already paid the VAT in the autumn; is having paid the VAT an indication of being within the 540 who will receive a tablet? 14:55:40 Also I'd like to know if there is another partnerting on the roadmap apart of Intex one 14:55:43 schmittlauch: the scalability enablers are in the sailfish os now so in future scaling up to bigger screens is easier. 14:56:18 and as for Sailfish OS & tablets - I think this is indeed quite important to know for app developers 14:56:21 If you have been invited to our shop to finalize the order, you will receive a tablet for sure. 14:56:28 Will the current and next to be send out tablets be fully supported in SailfishOS? 14:56:41 schmittlauch: we have sailfishos ported by community on all many factors and screen sizes (last one being oneplus x) https://wiki.merproject.org/wiki/Adaptations/libhybris 14:56:41 And all it's iterations to come 14:56:42 as many counted on the tablet form factor being available (Twablet, Mieru, etc.) 14:56:43 if any of the 540 backers don't want their tablets will they be given the option of refund? and these tablet then go to the 540+n backer? 14:56:50 \o/ 14:57:01 uuf lots of questions :) 14:57:18 So many questions… 14:58:09 M4rtinK - those chinese tablets on Taobao have been flashed with Android. I've confirmed that 4 times over. They do not have Sailfish on them. 14:58:15 Sailfish OS will be supported for tablets, but of course the installed base is quite small. 14:58:22 I'm afraid that, as there probably won't be that many apps for a tablet with max 700 users, many people wil install another OS on the device. 14:58:40 coley: I'd expect at the shopping stage those lucky users will have the option to back out 14:58:40 So can the tablet be seen as a dead platform (at least currently)? 14:58:50 #info Sailfish OS will be supported for tablets, but of course the installed base is quite small. 14:59:09 Or will Jolla make sure their own apps are still working 100% on the tablets... 14:59:11 @gerbick No. Some are with Sailfish OS, I can comfire 14:59:26 They can't leave the backers behind now by just shipping the tablets and then dropping support 14:59:32 Those first 500 with it still have been removed TylerTemp_ 14:59:37 If you are among the 540 and don't want a tablet, you're spot will be given to the next one in line. 14:59:49 #info If you are among the 540 and don't want a tablet, you're spot will be given to the next one in line. 14:59:50 it's really hard to drop support for a device in sailfish :) 14:59:57 :) 15:00:21 the tablet is an x86 device with a large screen. hopefully there will be more of those, either as community ports or licensed devices 15:00:31 jlassila: we'll see any more partnership coming apart of intex one? 15:00:49 in the near future 15:00:50 I bet on both, community port first and later licensed ones 15:00:55 We have some interesting discussions going on, but unfortunately can't tell yet. 15:00:55 schmittlauch: if a non complex app is written by using scalability guidelines, it will work fine on any form factor https://sailfishos.org/develop/docs/silica/sailfish-application-scalability.html/ 15:00:58 couple more minutes for this then I'll roll it into the next (related) topic 15:01:13 pascalstein: ^^ 15:01:13 jlassila: thanks 15:01:35 jlassila: What about that "positive surprise" that was mentioned in the new year blog pst 15:01:49 Well good question! 15:02:16 We have something up our sleeve yes, but we just didn't get it into this communication. 15:02:29 jlassila: have all invitations to shop already been sent out? 15:02:30 pressure to get this out was too big to wait. 15:02:51 jlassila, a small question 15:02:57 I got for mistake two perks 15:02:57 Can we expect what you have up your sleeve still this month? 15:03:08 Out of the 540 about 70 have already received invitations, rest is yet to be sent. 15:03:08 Or the communication about it at least. 15:03:11 first the 199 dollar and the second for 189 mark 15:03:26 may I ditch just one ? 15:03:40 in order the 199 is first then 189 one 15:03:46 dr_gogeta86: you may have better luck asking care@ that? 15:03:55 dr_gogeta86: you should contact our supprt about this. 15:03:55 70 received invitations, those from October? 15:04:15 Yes those are older invitations. 15:04:39 ok one more minute:- jlassila have you got anything else you'd like to add? 15:04:58 Can't promise any shcedule for the next news, don't want to overpromise. 15:05:12 please communicate more frequently, that's all :) 15:05:24 thank you very much! 15:05:25 heartbeat:)) 15:05:26 jlassila: thanks for answer our questions 15:05:28 Mobile Word Congress is in a few weeks, we're targeting to have some news there! 15:05:38 wow, great! 15:05:38 *exited 15:05:41 are those 540 devices 64GB or 32GB or mixed? 15:05:41 hehe 15:05:42 you mean mobile powerpoint congress ;) 15:05:43 My pleasure. 15:05:45 random appearances in irc also appreciated ... 15:05:48 (mobile world congress) 15:05:51 kimmoli: +1 15:05:53 jlassila: thanks a lot for answering and joining! highly appreciated! 15:06:04 ok then moving on 15:06:10 Mobile Excel, we shall!;) 15:06:11 #topic What are Jolla plans to rebuild trust with the community? (daitheflu, 20 minutes) 15:06:12 I'll still hang around for the next topic! 15:06:16 daitheflu, the stage is all yours 15:06:25 thanks stephg 15:06:35 Since the subject is propitious for trolls, I'll try to keep things factual and constructive. 15:06:44 good call! :) 15:07:00 For reasons -that are mostly known- the community is slowly (but surely) fading away. I see a lot of people leaving for greener land. Reading blog.jolla.com comments is painful and you will see a lot of people really, REALLY pissed. These people were the same that supported Jolla a few months ago. 15:07:11 Some of them invested time (and maybe even money) to comment, fill bugs in TJC, discuss, help... Some also spent some time to develop app(s). As you know, you can't really earn money from this since the store doesn't support paid apps. 15:07:19 And sadly, some of these people don't even want to ear about Jolla anymore :( 15:07:32 I understand why they are pissed. To be honest, I'm also pissed : I spent almost all 2015 learning C++ and Qt so I can actually develop for SFOS. I did trust the "open source", "people powered" marketing stuff, I invested time and money. And I really feel betrayed right now. I know I'm not alone, just read the TJC or the blog comments. 15:07:47 So, for a few months now, the community has been left with almost nothing more than a laconic blog post ~every month. As a consequence, it's slowly dying. And Jolla doesn't seem to care. At least, I haven't seen them doing anything to invert this momentum. 15:07:58 So my questions are simple : 15:08:05 1. What does Jolla plan to do to rebuild trust with the community ? 15:08:12 2. How can we (=what's left of the community) help ? 15:08:57 Thanks for the topic. I can discuss this if I may. 15:09:03 please 15:09:34 First of all: We fully realize that lately we have not been able to nurture the community as we should have. 15:09:34 It’s been really tough and challenging times, we were quite deep in the death valley this time and we have had to concentrate on saving the company, and now rebuilding everything and so on. 15:09:48 The thing really is that we DO care. 15:10:23 Honestly, lately this has also been a resource issue - as you know, Carol is no longer with Jolla (a big Jolla supporter still, thanks Carol!!). We’re looking to solve this part of the gap in some way very soon. More on that when we have the answers. 15:11:05 For actual plans on this front, we need to come back to this. I do not have the answers here. 15:11:17 I guess we may see some injection with new community members with the Intex device 15:11:27 which will hopefully get sold to sailfish first-timers 15:11:30 jlassila: <3 15:11:32 jlassila: communication always helps! 15:11:35 what about the Pootle translation instance ? 15:11:44 effort has been renewed 15:11:49 is at least that finally ready ? 15:11:51 Maybe this is a bit offtopic but I think it's related: does Jolla have any plan to don't fall again? that could help to trust again 15:12:08 * lbt notes that the Mer Project is still a community project at the core of Jolla and we've seen a lot more community (and Jolla) activity there recently 15:12:14 elfio: I suspect they didn't plan to fall the first time ;) 15:12:17 M4rtinK: when it's ready, it will be published right out 15:12:28 #info the Mer Project is still a community project at the core of Jolla and we've seen a lot more community (and Jolla) activity there recently 15:12:41 stephg: of course 15:12:56 When working with mer packages, Stskeeps has been very helpful :) 15:13:08 Are there still talks with investors about open-sourcing SFOS according to the idea Stskeeps mentioned last year? (dual-license, etc.) @jlassila 15:13:19 first face-to-face input about how can community help will be brainstormed in two days at FOSDEM: https://together.jolla.com/question/126575/fosdem-2016-get-together/?answer=126578#post-id-126578 15:13:24 thank you all those who can come! 15:13:34 do you think you guys can setup a stream to that 15:13:36 topics are in the round-table comments 15:13:42 schmittlauch: Yes that is still on the agenda. 15:13:50 \0/ 15:13:52 #info first face-to-face input about how can community help will be brainstormed in two days at FOSDEM 15:13:58 #link https://together.jolla.com/question/126575/fosdem-2016-get-together/?answer=126578#post-id-126578 15:13:59 ghosalmartin, periscope :P 15:14:10 also I second daitheflu - it was really painful during the recent crisis as you could not actually help! 15:14:18 even if you wanted 15:14:24 And how about the inclusion of all the translations that are done by the community? 15:14:28 ghosalmartin: surely if someone hacks it together (people of caliber that come to fosdem;)) 15:14:28 sledges: see you at FOSDEM! 15:14:50 because I think many people feel so betrayed that only a big step like open-sourcing could make them return. 15:14:52 and even if the topic of "how can the community help ?" was raised - no answers were given & no action was taken 15:15:03 sledges: just a simple skype call or hangouts, or alternative 15:15:04 this is not how you foster community support... 15:15:08 sledges: can you say more about the progress on community translations? 15:15:34 schmittlauch: definitely! 15:15:37 mal- is developing FM Radio API framework and app, the contribution of which Jolla is planning to embrace, paving way to other similar contributions while SailfishOS is not yet opensource 15:15:45 M4rtinK: the issue remains valid. You still cannot actually help, even if you want to 15:15:58 "How can community help" well mer/nemo is now in a better state to accept contributions than it was just recently 15:16:11 mal-'s goal is to reward Fairphone 2 Sailfish OS port with that app 15:16:28 I can count the number of obnoxious little issues I'm sure could be fixed by a simple patch, if only there was the source (there kinda is for the QML..) and a place where to send those patches... 15:16:59 r0kk3rz: I meant "how can the community help rebuild trust between Jolla and...well...people" 15:17:10 LarstiQ: for community translations we still need to polish the workflow of community<->Jolla, document that (will commence in FOSDEM), and finalise community languages translation packs served via Jolla Store 15:17:15 M4rtinK: +1 15:17:31 other infra (of actual translation suggestions and their sync) has already been tested last year 15:17:40 daitheflu: we are also open to all kinds of ideas and suggestions! 15:18:21 jlassila: I have a bunch of them that I'll probably post on TJC sometime. Just wanted to hear from Jolla before 15:18:21 #info for community translations we still need to polish the workflow of community<->Jolla, document that (will commence in FOSDEM), and finalise community languages translation packs served via Jolla Store 15:18:25 mal-'s case is a low hanging/short term fruit, opensourcing has never been off the table 15:18:34 I'll just note that some of the translation efforts have been going almost from day one 15:18:39 What about the last Jolla phones that are on stock to be sold for a lower price? 15:18:40 like the Czech/Slovak one 15:18:49 How many are there left in stock in total? 15:19:00 Indeed M4rtinK :) 15:19:01 and they even picked-up some ex-MeeGo translators 15:19:26 I just want to make sure I'm not investing time and resources in something that will die in 6 months because there are just a hundred guys still interested in the project 15:19:49 M4rtinK: that's great when you gather a community around a culture/language, having said that i would like to encourage you to upvote also keyboard layouts, as that let's us prioritise things easier: https://together.jolla.com/question/124266/keyboard-contributions-for-inclusion-in-sfos/ 15:20:12 sledges: well I have been wondering about the layouts 15:20:17 daitheflu, personally i've bought an android phone just to replace its main os ... 15:20:30 sledges: and kinda worried if that also gets deadlocked indefinitely 15:20:57 daitheflu: I'm in the same position as you and take some comfort that there is still a thriving community around the n900 and the n9 too... 15:20:57 M4rtinK: and i wondered why the numbers are so low on upvotes, so here's when you come in ;) 15:20:59 lots have been submitted but AFAIK non actually pulled to the official repos (??) 15:21:21 stephg: N900 for sure - N9 - not so sure... 15:21:22 M4rtinK: it was during the time the split layout was implemented, so it was difficult to standardise anything 15:21:31 with sfosv2 it should be doable 15:21:42 M4rtinK: point is these are old 'un-supported' devices 15:22:09 5 more minutes folks 15:22:14 thanks sledges, its little details like that which make all the difference 15:22:26 well, unfortunately old device with a community is more of an exception than a rule 15:22:34 anyway - back to topic 15:22:46 any appliable action items or stuff to info/link ? 15:22:56 r0kk3rz: yep, i'll get in a habit of repeating little details more often == communication :)) 15:23:05 at least something community can do in the meantime ? 15:23:18 sledges: :) 15:23:21 #info Jolla ask for help in prioritizing translations 15:23:24 BTW, even negative information will help 15:23:26 #link https://together.jolla.com/question/124266/keyboard-contributions-for-inclusion-in-sfos/ 15:23:27 FWIU, upvote on TJC 15:23:31 M4rtinK: create a transifex2pootle convertor ;) 15:23:38 "we will never opensource X" 15:23:48 would help community prioritize efforts 15:24:03 i already mentioned - that has never been off the table 15:24:09 rather than wait for the thing to be maybe open-sourced someday 15:24:31 M4rtinK: They will for sure never opensource 2rd party components like AlienDalvik or Exchange 15:24:33 I will take on an action point to communicate more and more often! 15:25:05 Even small details/communication can help 15:25:07 M4rtinK: *3rd party 15:25:12 It doesn't have to be big news all the time 15:26:04 You can even communicate more by being active on Together. A short reply can do a lot of good. 15:26:04 one more minute 15:26:27 schmittlauch: yeah, that can be expected - any people are already working on replacement as a result 15:26:28 community TJC moderators are doing great job in pinging required people around 15:26:42 I keep the telegram community up-to-date on where the community can help :) 15:26:48 schmittlauch: so that kinda works as expected 15:26:52 M4rtinK: schmittlauch: yes, android compat layer by krnlyng :) 15:27:04 #action jlassila to communicate more often, even with small details, such as responding on TJC 15:27:11 toxip: how big is the group ooi?:) 15:27:30 but other components are a gray area 15:27:31 cybette: <3 15:27:41 and in irc ? 15:27:47 sledges: atm only about 90 members... we used to have 120 on the old group but we hit some trouble with that so we had to migrate 15:27:53 sledges: android compat which brings us nicely onto AoB 15:27:58 M4rtinK: if you think we are too silent, step up and become a TJC mod, to ping us directly :) way to help -> we're more responsive on TJC thanks to you 15:28:04 #topic All other business (everyone, 10 minutes) 15:28:11 kimmoli: step by step :) 15:28:29 cybette: i'm just poking with a toothpick 15:28:38 toxip: cool! 15:28:38 so two things from me, all of the porty-goodness that's been going on (its fast moving and I don't know what it all is, I want to hear!) 15:28:47 sledges: well, I already at least monitor, vote & comment on TJC quite a lot 15:28:49 and also, there's this thing I've heard about called FOSDEM ;) 15:28:51 *poring (to those unaware:) 15:28:54 jlassila: Will the SailfishOS roadmap page be updated? 15:29:07 sledges: but would probably not have enough time to be a proper mod 15:29:27 #link https://sailfishos.org/roadmap/ 15:29:39 pascalstein: very good point! 15:29:45 pascalstein: We need to take that as an action point. 15:30:09 Now it looks like development stopped, which we know is not 15:30:10 #action jlassila updates to the SFOS roadmap 15:30:24 Is there any news on the "new" hardware company that will be formed? 15:30:29 Currently the future is not as clear as it used to be, so this is not a very easy task. 15:30:34 I wouldn't promise update at this point. 15:30:51 +1 ddh87 15:31:12 jlassila: Do you have any idea when the shipments of eg Jolla phones and accessoires from the webstore are back in normal operation 15:31:18 veskuh_: can you elaborate so I can info it:- resource I presume? 15:31:22 Jlassila: There has to be a plan for SFOS af this point. A goal where the software has to be next years and all the steps to take. 15:31:43 The current mailing says there is no visibility on the logistical part of it... Can you clarify please 15:31:46 stephg: it's known what to drop, but probably current status could be updated, veskuh_ ? 15:31:49 The fan club has been hoping for a possibilty to buy a license for community ports that would allow the installation of alien dalvik, jolla store and ms exchange for example. Do you have anything to share about that? 15:32:22 stephg: current status can be updated, the timeline for future is more difficult 15:32:23 toxip: good Q. The 1+ guys are itching to get something like that 15:33:02 ddh87: sure we do have plans, but they are living/changing. 15:33:05 #info the current roadmap status can be updated but timelines for future features/development are not yet clear 15:33:15 vgrade: there's a high potential on the 1+ side. We could get a really nice injection of new community members there 15:33:48 Access to jolla store for more of the ported devices is hopefully somewhere in the near future 15:33:58 jlassila: something which could be investigated on your side? 15:34:08 Hey, is it possible to download Dalvik package with a Jolla and install it on a ported device? How legal is it? 15:34:09 toxip: that would come nicely together with paid apps in general, but nothing ongoing there atm; please suggest ways to pay for apps, like would all people be fine with bitcoins? :) etc; especially those who know finnish paid appstore nuances 15:34:18