[SailfishDevel] Community Beta Group
Hi all, We have finally extended the scope of our Community Beta Program, please read the following post: https://together.jolla.com/question/81276/official-announcement-community-b eta-group/ As we roll-out the opt-in as part of our releasing process - which should happen rather soon - , I would like to evaluate the interest from you, developers, to participate into this group and also collect feedback on how you perceive such activity, how much time would you be willing to give, any foreseeable advantage in participating (api/abi changes...). Being part of Community Beta means in practice, sending us feedback on the early software releases through the dedicated channels we make available, interact with fellow developers, share knowledge among other things. Your feedback is very welcome. Thanks a lot in advance and have a nice weekend! Cheers, Eric ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Developer wiki?
Hi, We plan to deploy a sailfishos dedicated wiki in March timeframe so we can address the need for such documentation and consolidate some of the information that is currently scattered across mer/nemomobile wikis. This is aligned with the sailfishos.org site renewal, priority is given first to restoring the silica documentation and broaden the scope of the site to accomodate other audiences than developers only. Cheers, Eric On 06/02/2015 12:52, "peter.pykalai...@gmail.com" wrote: >Indeed. Lack of docimentation and how tos are a real problem. Even bigger >problem than having stupid restrictions on harbour apps. > >// Pete > >Andrey Kozhevnikov kirjoitti pe helmikuuta 6 12:20:48 2015 GMT+0200: >> That would be very helpful :D >> >> 06.02.2015 15:14, Kaj-Michael Lang пишет: >> > Is there a developer wiki available ? >> > >> > Something like the Nokia developer wiki, where various how-to-do-that >> > articles could be created and shared ? >> > >> > >> >> ___ >> SailfishOS.org Devel mailing list >> To unsubscribe, please send a mail to >>devel-unsubscr...@lists.sailfishos.or > >-- >// Peter Pykäläinen >Lähetetty Jollastani >___ >SailfishOS.org Devel mailing list >To unsubscribe, please send a mail to >devel-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] [Update] Changelog for SailfishOS update 10 (1.1.1.26)
Hi all, We've released update10 today. The Changelog can be found (and commented on) here: https://together.jolla.com/question/71741/release-notes-software-version-11126-vaarainjarvi/ Changelog and instructions are appended below, for discussions please go to together. Whats new? -- * Device lock now supports alphanumeric code https://together.jolla.com/question/19890/alphabetic-device-lock/ * Option to keep display on while charging (Settings > System > Display > Keep display on while charging), disabled by default https://together.jolla.com/question/37616/keep-display-on-while-charging/ * Silence/ignore an incoming call by flipping the phone or by pressing the power key https://together.jolla.com/question/371/silence-incoming-calls-by-turning-the-phone-face-down/ * Snooze alarm (both clock and calendar) by flipping the phone or by pressing power key https://together.jolla.com/question/8559/alarm-clock-alarm-unintuitive/ https://together.jolla.com/question/3/bug-power-button-not-active-during-clock-alarm/ * Copy-paste functionality between Android and native SailfishOS apps https://together.jolla.com/question/4064/sharing-clipboard-with-android-applications/ * 'Sort by recipient' option in Sent, Drafts, Outbox folders in Mail app * Option to delete backups to free disk space (Settings > System > Backup > Select snapshots > Select All from pulleymenu) * On creating a new calendar event with reminder, the reminder time set is saved and used as default for the subsequent new calendar event entries. https://together.jolla.com/question/10327/feature-request-calendar-reminder-turned-on-by-default/ * Ability to edit a single occurrence of a recurring event https://together.jolla.com/question/27716/enable-edit-of-single-occurrence-event-for-repeating-calendar-event/ * Double 'click' on Power key locks the phone up immediately - more info at Zendesk * Double 'click' on Power key when phone locked makes the lock dialog appear (if no lock in use then directly to home view) - more info at Zendesk) * New overlays for Maps - satellite, car (daylight mode), transit (public transport) and night mode * Quicker access to favorite places on Maps * Search for media, albums and artists in Media player via 'Search' pulley menu item in the different views * Finer control to enable/disable AGPS assistance for obtaining location fix via 'Faster position lock' option in Settings > System > Location * Automatically save draft emails on page exit https://together.jolla.com/question/4040/mail-prompt-before-discarding-message-being-composed/ * Accounts framework has undergone a fair amount of unification, making the account setup process more user friendly * Fruux, Memotoo and Yahoo! now available as separate provider accounts in the 'Add accounts' page. * Copy unsaved numbers from call log via context menu https://together.jolla.com/question/41245/possibility-to-copy-number-by-long-press-in-call-history-released/ * CardDAV support for Fruux and Memotoo service providers (experimental) * Browser engine updated to Gecko 31 to improve compatibility with various web sites and improving scrolling performance * Kazakh keyboard layout now available * New MMS settings under Settings > Apps > Messages : Maximum message size, Request reports and Download MMS automatically * Perform general maintenance tasks such as cleaning up backup storage to free space, restarting network connectivity, android runtime etc via Sailfish Utilities app available in Jolla Store. * Once installed, you can access it via Settings > System > Utilities UI interaction changes -- * Hierarchy indicator at the top left corner of the view replaced by a single indicator trailing off the edge of the view * In accounts settings view, changes made are immediately saved. * Previously, an explicit user action (pressing 'Accept') was required. * App dialogs are now visually separated from normal app pages by having accept and cancel buttons from the page area to a persistent header Highlights of improvements -- Improvements in core OS Memory handling and performance related improvements * New rendering engine that significantly reduces both CPU and GPU load * Minimized apps now drop surfaces and OpenGL context to reduce memory usage * More responsive Android apps through rewritten Wayland system integration * Contacts database loading improvements * Ensures that phone UI never gets killed when OOM (Out of Memory) handling kicks in * Improved browser memory handling when closing tabs * Automatically unloading browser tabs in low memory situation * Drops memory-heavy HTML email viewer from memory when not used in a while * Loads Phone dialers, Device lock, Facebook and Twitter feed pages in memory on demand * Enables memory compaction configuration option in kernel * Adds memnotify patch to kernel to get notifications on memory thresholds being crossed * MCE is now able to receive and set up memory thresholds with
Re: [SailfishDevel] Follow up on faenil's topics in Community meeting 24.04.2014 @ 10:00 UTC
Hi Andrea and Lucien, From: Andrea Bernabei mailto:and.berna...@gmail.com>> Reply-To: Sailfish OS Developers mailto:devel@lists.sailfishos.org>> Date: mercredi 25 juin 2014 18:52 To: Sailfish OS Developers mailto:devel@lists.sailfishos.org>> Subject: Re: [SailfishDevel] Follow up on faenil's topics in Community meeting 24.04.2014 @ 10:00 UTC To avoid misunderstandings: I *do* believe sailors read the threads at TJC, and they file bugs, when they can. The problem, imho, is not sailors not reading, it's TJC having too many reports to be an efficient bug tracking solution. If I were a sailors, and I were to really track all threads on TJC and file bugs in the internal bugzilla, I think I wouldn't have time to keep coding sailfish pieces. Really keeping track of threads in TJC is a fulltime job by itself, we *can't* expect sailors to be able to follow it very close... I'll be *very* happy to be proven wrong...all I want is the best for Jolla Going through and linking the TJC reports does take time of course, but I can tell we’re continuously improving. We look at tags and as an area owner, it does already fairly limit the scope of what needs to be looked at by who on daily basis. Automation and triggers are next to support a better overall workflow. It’s not about proving anyone right or wrong but improve continuously :) 2014-06-25 17:42 GMT+02:00 Andrea Bernabei mailto:and.berna...@gmail.com>>: yes, and who's more likely to report valid bugs of the two categories? :D (I say more likely, no offence meant to casual users, I just think the focus for a bug reporting tool should be on power users, which, from the opinions I gathered in the last months, don't have many nice words about TJC) All reports are equal by nature, though it’s surely easier when a more experimented user can explain an issue adopting the developer’s mindset; factual observation supported by accuracy and possibly pointers to affected components. Back to some of our core values it translates exactly to doing it together and putting users (all of them) first, offering a framework where they can talk to us and where we can answer (yes, this can be improved still and we’re working on it…). TJC was cool because there was nothing before it...now a few months passed, Jolla should look into specialising the bug reporting offer, or (as Eric is also suggesting) it should make the link with the internal bz so strong that I don't have to be worried if I'm wasting my time by reporting super detailed bugs to a place probably nobody is going to read. TJC is still cool, c’mon :) If you (and/or the other Community members you fetched feedback from on IRC) are eager to contribute in making TJC a better place for developers/power users to report issues in a more formatted manner than the average users you refer to actually do, I would be more than happy to see an initiative where you create specific guidelines (a wiki post?), with a reporting template proposal under https://together.jolla.com/questions/scope:all/sort:activity-desc/tags:guidelines/page:1/ This would be IMHO a perfect way to start and make better use of what is currently available, and move forward together. I believe we can improve together TJC and meet some of your expectations without relying on yet another dedicated tool and more importantly, cluster users into using these based on what sounds a little like segregation to me. Truly, the target is to blend into a movement, adopt, learn, share, no matter the background… 2014-06-25 17:25 GMT+02:00 mailto:sfietkonstan...@free.fr>>: I'm wondering how TJC is handled internally by Jolla. Some insights on how sailors proceed is very welcomed. To reply to Faenil, I would say that it depends on the users. Power users like us are often on IRC and discuss directly with some Sailors. And they can feel that TJC is a mess (especially compared to a bugtracking tool). However, the average Jolla user might just post something on TJC and either forget about it, or just follow his own issue(s). - Mail original - De: "Andrea Bernabei" mailto:and.berna...@gmail.com>> À: "Sailfish OS Developers" mailto:devel@lists.sailfishos.org>> Envoyé: Mercredi 25 Juin 2014 17:16:54 Objet: Re: [SailfishDevel] Follow up on faenil's topics in Community meeting 24.04.2014 @ 10:00 UTC DISCLAIMER: I'm saying the following words with a smile on my face, I may sound harsh but please believe me, I don't mean to :) Eric, just go into the IRC channel, and ask people there (who are, usually, the most active community members): 1) what do you think of TJC as a bug reporting tool? 2) do you think it can work? but most importantly 3) Are you *actually* reporting bugs on TJC? I heard many people who are not reporting bugs on TJC because they think it's not worth it (for different reasons) and I'm not reporting them myself, because I keep stumbling on unanswered posts. Well, here you could actually nicely make use of
Re: [SailfishDevel] Follow up on faenil's topics in Community meeting 24.04.2014 @ 10:00 UTC
El 25/06/14 16:40, Eric Le Roux escribió: There was a fair deal of discussion yesterday during our meeting (see, http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-06-24-08.44.html)<http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-06-24-08.44.html%29> on two important topics raised by faenil. The URL is not correct... ;-) Thanks Manuel! And apologies :) Here: http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-06-24-08.44.html Cheers, Eric -- Bye, Manu. manu at manu.ms http://www.manu.ms Manuel Soriano * Lo Perello/Valencia/Spain * ( AbM Compliant ) La política es el arte de buscar o crear problemas, hacer un diagnostico falso, aplicar remedios equivocados para nunca resolverlos. (Graucho Marx y yo) ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] Follow up on faenil's topics in Community meeting 24.04.2014 @ 10:00 UTC
Dear Community members! There was a fair deal of discussion yesterday during our meeting (see, http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-06-24-08.44.html)<http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-06-24-08.44.html%29> on two important topics raised by faenil. I hope the following can clarify and give the expected amount of transparency and insight. About the Community Beta Program: I bet it won't be a surprise for any of you but we are currently having such activity with a limited amount of participants. Just a few Community members whom with we interact closely, getting extremely valuable feedback before we launch our SailfishOS updates to the public. It has remained confidential for multiple reasons but in a nutshell, we still need to improve on infrastructures and processes in order to scale-up gracefully. We are confident that we could do so in a not so distant future, but first, we want to make sure the path is neat and clear for both our Community testers and us. Loaning a test device, having feedback channels and needed monitoring is, as you can easily imagine, a costly exercise for any small structure. The mention yesterday of cost of operations is at the core of our decisions, and it's not only about the financial aspect of maintaining infrastructure but getting the most out of any investment we make. Be assured we're committed to bring more of these activities to you, and broaden the scope. The Opt-in way to test single features/patches as well as the Jolla Launcher Alpha testing are here to demonstrate our engagement to get as many of you onboard. >From the new-comers to the most seasoned developers, we do it together. Expect more to happen on this very front... About SailfishOS bugzilla instance: We are in a situation where we have multiple input sources to monitor, Nemo & Mer bugzillas, together.jolla.com, git repositories... We do have enablers in our internal bugzilla instance to achieve a seamless tracking, and plans to get some automations that will provide more visibility on our activities. On this very topic, I invite you to check https://github.com/bayoteers and also evangelize how awesome our bugzilla extensions are :) In this context, we clearly need to evaluate what would be the benefit of a new instance and what would it be used for so the ROI remains as high as possible. There was a concern that together.jolla.com isn't working for bug reports. Let me assure you that it does, even beyond expectations, because of the tools and process mentioned above that we keep improving. So from my personal perspective, before we do deploy another instance for feedback, I'd rather want to see consolidation (which directly relates to the Nemo middleware migration to Mer). I would suggest we revisit this topic in the future and focus now on the existing above mentioned channels... Cheers, Eric Le Roux Bugzilla & TJC admin @ Jolla ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
