We've met, and we talked about Plasma, then talked about Plasma Mobile and
came up with plans, minutes for both attached!
Plasma Mobile, live pad: https://notes.kde.org/p/plasmamobileplan
Cheers,
--
sebas
http://www.kde.org | http://vizZzion.org
--
http://vizZzion.org
Plasma Team meeting, 4-9-2017
Present: kbroulik, notmart, Sho, jensreu, bshah, sebas
kbroulik:
* Did various improvements to Folder View
** improved startup performance with lazy loading in panel like plasmoids do it
** pressing Esc in showing desktop mode will cancel a rename op first instead
of always blatantly throwing you out of showing desktop
* Some minor performance improvements, e.g. creating margins/fixedMargins
objects on demand, avoiding needless clearing of SVGs
* ConfigModel can now be used with an Instantiator, used in digital clock to
show holiday plugin config only for enabled ones
* Dolphin now prefers Place name in title bar (so you get "Home" instead of
lowercase user name or "Trash" (or "Papierkorb") instead of trash:/)
!! I started an Etherpad for 5.11 release announcement !! Please fill in your
features and noteworthy improvements !! https://notes.kde.org/p/plasma_5_11
notmart:
* wayland foreign: this has all the comments adressed, please review:
https://phabricator.kde.org/D7521 and https://phabricator.kde.org/D7369
Diff 7521 "[WIP] make use of foreign protocol" [Needs Review]
https://phabricator.kde.org/D7521
Diff 7369 "[WIP] Wayland foreign protocol" [Needs Review]
https://phabricator.kde.org/D7369
* some triaging on plasmashell bugs
* work on kirigami papercut bugs, related to looks, scrolling and formfactor
switching
* work
* theme ScrollView, along with workarounds for rendering correctly on desktop
and correct scrolling
* plasma-mobile
** better working activity switching by slide
** new top panel with just a simple quick settings thing in it, quick target is
just to have a simple prototype that doesn't "look broken" (more on that on pm
meeting)
* QtQuickControls2 style: a ScrollView that has a better management of mouse
wheels/touchpad
* QtQuickControls2 style: asked lists to make it a frameworks, apps want to
depend from it to not look awful on desktop
Sho:
* [Launchers] Worked a few more rounds with Ivan on KAStats-based favorites
** Still buggy ... getting concerned re 5.11 considering we need VDG help
post-merge to fix the context menu design, and message freeze is approaching
fast :/
* [Kirigami] Worked on resizing drawers with a drag handle - works in Konvi,
will likely submit a code example
* [Kirigami] Chatted with Marco about scrolling, color stuff, framework-ness,
...
* [QtWS] More coordination stuff, poking, prodding, emailing
** Still missing some replies with registration confirmation and questionnaire
answers, if you spoke up about attending please check your inbox and reply
* [Other] Spent some time on the text view code for the Konversation Qt Quick
rewrite
bshah:
- [Neon] Upto applications are done in neon CI
- [Mobile CI] Code changed to use the packages from neon CI
- [Mobile CI] Some work to make use of Multijob in Mobile CI, so there is just
one meta job instead of _src, _bin and _pub jobs
- [Packaging] Found most elegant solution to QCOM_BSP problem, working with JBB
on telegram to implement it
- I hope to have initial images with neon packages and qt5.9 ready by wednesday
sebas:
* trying to get Fairphone interested, mild but not much succes so far
* bit of coordination with Purism, see librem thread on plasma ML
* my laptop's giving problems again and its Plasma install is borked, needs
fixing
* not much Plasma things otherwise
* pending is still the touchscreen rotation code and of course the OSD patches
which I still don't know how to properly position
We also talked about Plasma mobile, notes of that are here:
https://notes.kde.org/p/plasmamobileplan
snapshot for posterity:
Strategy / Goals:
Attract more developers from the outside
Increase awareness for Plasma Mobile in Free software ecosystem
Get Plasma Mobile to a basic 1.0 state, functional as daily driver for limited
use cases
to me is mostly being a decent dumb phone, 1998-grade functionality
Split PM work into different areas with their coordinator:
Technical / low-level / stack: bshah
Technical UI: notmart (plasma-shell homescreen, kirigami framework base for
apps.. apps need someone adopting them)
Design: jensreu
PR / communication: sebas
The idea is that these "coordinators" / "topic owners" keep track and
coordinate among each others and work as a team to advance PM towards the goals
above - Project management for the distinctive areas to happen on phab
Create a design vision, taking current state-of-the-art in PM into account, and
flesh it out with designers
Jens to sit down with Sho and Notmart and AlexL to define what can and can't be
done, then take it into design team to work on mockups
Create a clear list of functional objectives: what's needed for a 1.0 version?
requirements will divide in roughly 3 completeness categories
functionalities kinda there
functionalities with missing frameworks, complete implementation needed
framework present, UI missing
(See the list below, let's create a phab tasks and go through it 1 by 1)
Create a marketing / PR strategy for PM ( https://phabricator.kde.org/T6919 )
sebas and paul to further flesh out PR plan, both for PM and for the purism
crowdfunding campaign (also: what do we need to know from purism?)
Rough list of requirements for an 1.0 version
TODO: list by priority and assign those that are most important right now
homescreen
app drawer
settings app
clock
network (wifi, gsm, vpn)
bluetooth
sound
sound policy stuff
dialer
contacts
sms
alarms
www
email
app package management
camera
photo management
sharing
data types / file associations
calendar
virtual keyboard
locale management
screen locker
Important modules for the Sessings in an 1.0 version:
locale management
input languages
ringtone / notification tones
time and date
roaming
apn
tethering
data limits, ...
Either separate info application or within the main settings module, important
information is needed
data usaege
power usage
storage usage
