Re: Application usage statistics and targeted user surveys

2017-06-15 Thread Aleix Pol
On Thu, Jun 15, 2017 at 10:22 PM, Ben Cooksley  wrote:
> On Fri, Jun 16, 2017 at 1:42 AM, Aleix Pol  wrote:
>> On Tue, Jun 13, 2017 at 6:56 PM, Volker Krause  wrote:
>>> On Monday, 12 June 2017 01:56:21 CEST Aleix Pol wrote:
 On Sat, Jun 10, 2017 at 10:22 AM, Volker Krause  wrote:
 > On Tuesday, 6 June 2017 15:01:57 CEST Aleix Pol wrote:
 >> On Thu, May 25, 2017 at 4:42 PM, Volker Krause  wrote:
 >> > On Wednesday, 24 May 2017 17:38:22 CEST Aleix Pol wrote:
 >> >> On Tue, May 23, 2017 at 6:31 PM, Aleix Pol  wrote:
 >> >> Hey Volker, I figured out this one. Never mind.
 >> >>
 >> >> I've done a proof of concept integrating it in Discover, here's 2
 >> >> patches:
 >> >> https://phabricator.kde.org/D5960
 >> >> https://phabricator.kde.org/D5961
 >> >
 >> > There's still two aspects missing in the integration:
 >> > - configure Provider to actually submit (see productIdentifier,
 >> > feedbackServer and submissionInterval properties)
 >> > - probably add some data sources (in the current form you only get an
 >> > indication on how many users you have, and untargeted surveys, nothing
 >> > more)
 >> >
 >> > The second point will need some more QML wrapper API. I'll look into
 >> > adding a QML plugin to KUserFeedback directly for this.
 >> >
 >> >> Now to proceed I'd like to give a try to whole system including the
 >> >> server. Do you have documented how to set it up anywhere? Would make
 >> >> it easier.
 >> >
 >> > INSTALL contains the deployment documentation, both for the full setup
 >> > with
 >> > authentication on an Apache server, and locally for unsecured testing
 >> > using
 >> > the built-in PHP server.
 >> >
 >> > I've also got a playground server on my own infrastructure now that I
 >> > can
 >> > provide accounts for. And Jan has published his ongoing work on
 >> > creating a
 >> > Docker image for the server here:
 >> > https://github.com/KDAB/kuserfeedbackdocker
 >> >
 >> > Regards,
 >> > Volker
 >>
 >> Hi Volker,
 >> More noob feedback:
 >> I set up a local system I could tinkle with using your colleague's
 >> docker. Worked quite well. But, I was getting an issue, possibly fixed
 >> by this patch:
 >> https://phabricator.kde.org/D6117
 >
 > This looks good, I'll try to get that path unit-tested to make sure this
 > works with sqlite too. However, you should not actually hit this path in
 > the first place, which is probably also why you are not seeing any data.
 >
 >> Now I get to see things being sent on the UserFeedbackConsole
 >> application, but I only see timestamps. I added debug information to
 >> see what is being sent and (after updating the discover patch above)
 >> and I see all sort of data, being delivered. Is it being lost in the
 >> internets? Or am I not looking into it correctly? If I export the
 >> product using UserFeedbackConsole I also only get timestamps :(.
 >
 > Do you see the empty columns for the other data in UserFeedbackConsole, 
 > or
 > do you only see the Timestamp column? In the former case the data is
 > either not transmitted, or rejected by the server for some reason, we'd
 > need to look at the JSON payload sent to the server in that case. In the
 > other case, you probably need to set up a product schema first with
 > UserFeedbackConsole (easiest via Schema -> Source Templates in the Schema
 > view).

 Here's what I'm seeing: https://imgur.com/a/BmH2B
 I've seen the schema view, I haven't pushed it much. I see I can add
 stuff but I'm not sure what it's for. I expected the system to
 integrate all data offered, but maybe I need to set the expectations
 on the server side?
>>>
>>> Yes, exactly, that's what the schema does. Easiest way to get started is
>>> probably to just import the orwell example schema there, that contains all
>>> existing data sources, or you just create sources from their corresponding
>>> templates.
>>>
>>> That is, in the schema view chose schema -> import schema... or schema ->
>>> source template >  When you are done, select schema -> save schema to
>>> write the changes to the server. Afterwards you should see a lot more 
>>> columns
>>> and more charts in the analytics view.
>>>
>>> User documentation is still fairly limited on this, but there is a start of 
>>> a
>>> user manual describing the data model, that should help to explain most of 
>>> the
>>> options you have in the schema view.
>>>
 Either way, this is the information being sent at the moment (I copied
 your orwell.qml example sources so far).
 {
 "applicationVersion": { "value": "5.10.90" },
 "compiler": { "type": "Clang", "version": "4.0" },
 "platform": { "os": "linux", "version": "arch-unknown" },
 "qtVersion": { "value": 

Re: Application usage statistics and targeted user surveys

2017-06-15 Thread Ben Cooksley
On Fri, Jun 16, 2017 at 1:42 AM, Aleix Pol  wrote:
> On Tue, Jun 13, 2017 at 6:56 PM, Volker Krause  wrote:
>> On Monday, 12 June 2017 01:56:21 CEST Aleix Pol wrote:
>>> On Sat, Jun 10, 2017 at 10:22 AM, Volker Krause  wrote:
>>> > On Tuesday, 6 June 2017 15:01:57 CEST Aleix Pol wrote:
>>> >> On Thu, May 25, 2017 at 4:42 PM, Volker Krause  wrote:
>>> >> > On Wednesday, 24 May 2017 17:38:22 CEST Aleix Pol wrote:
>>> >> >> On Tue, May 23, 2017 at 6:31 PM, Aleix Pol  wrote:
>>> >> >> Hey Volker, I figured out this one. Never mind.
>>> >> >>
>>> >> >> I've done a proof of concept integrating it in Discover, here's 2
>>> >> >> patches:
>>> >> >> https://phabricator.kde.org/D5960
>>> >> >> https://phabricator.kde.org/D5961
>>> >> >
>>> >> > There's still two aspects missing in the integration:
>>> >> > - configure Provider to actually submit (see productIdentifier,
>>> >> > feedbackServer and submissionInterval properties)
>>> >> > - probably add some data sources (in the current form you only get an
>>> >> > indication on how many users you have, and untargeted surveys, nothing
>>> >> > more)
>>> >> >
>>> >> > The second point will need some more QML wrapper API. I'll look into
>>> >> > adding a QML plugin to KUserFeedback directly for this.
>>> >> >
>>> >> >> Now to proceed I'd like to give a try to whole system including the
>>> >> >> server. Do you have documented how to set it up anywhere? Would make
>>> >> >> it easier.
>>> >> >
>>> >> > INSTALL contains the deployment documentation, both for the full setup
>>> >> > with
>>> >> > authentication on an Apache server, and locally for unsecured testing
>>> >> > using
>>> >> > the built-in PHP server.
>>> >> >
>>> >> > I've also got a playground server on my own infrastructure now that I
>>> >> > can
>>> >> > provide accounts for. And Jan has published his ongoing work on
>>> >> > creating a
>>> >> > Docker image for the server here:
>>> >> > https://github.com/KDAB/kuserfeedbackdocker
>>> >> >
>>> >> > Regards,
>>> >> > Volker
>>> >>
>>> >> Hi Volker,
>>> >> More noob feedback:
>>> >> I set up a local system I could tinkle with using your colleague's
>>> >> docker. Worked quite well. But, I was getting an issue, possibly fixed
>>> >> by this patch:
>>> >> https://phabricator.kde.org/D6117
>>> >
>>> > This looks good, I'll try to get that path unit-tested to make sure this
>>> > works with sqlite too. However, you should not actually hit this path in
>>> > the first place, which is probably also why you are not seeing any data.
>>> >
>>> >> Now I get to see things being sent on the UserFeedbackConsole
>>> >> application, but I only see timestamps. I added debug information to
>>> >> see what is being sent and (after updating the discover patch above)
>>> >> and I see all sort of data, being delivered. Is it being lost in the
>>> >> internets? Or am I not looking into it correctly? If I export the
>>> >> product using UserFeedbackConsole I also only get timestamps :(.
>>> >
>>> > Do you see the empty columns for the other data in UserFeedbackConsole, or
>>> > do you only see the Timestamp column? In the former case the data is
>>> > either not transmitted, or rejected by the server for some reason, we'd
>>> > need to look at the JSON payload sent to the server in that case. In the
>>> > other case, you probably need to set up a product schema first with
>>> > UserFeedbackConsole (easiest via Schema -> Source Templates in the Schema
>>> > view).
>>>
>>> Here's what I'm seeing: https://imgur.com/a/BmH2B
>>> I've seen the schema view, I haven't pushed it much. I see I can add
>>> stuff but I'm not sure what it's for. I expected the system to
>>> integrate all data offered, but maybe I need to set the expectations
>>> on the server side?
>>
>> Yes, exactly, that's what the schema does. Easiest way to get started is
>> probably to just import the orwell example schema there, that contains all
>> existing data sources, or you just create sources from their corresponding
>> templates.
>>
>> That is, in the schema view chose schema -> import schema... or schema ->
>> source template >  When you are done, select schema -> save schema to
>> write the changes to the server. Afterwards you should see a lot more columns
>> and more charts in the analytics view.
>>
>> User documentation is still fairly limited on this, but there is a start of a
>> user manual describing the data model, that should help to explain most of 
>> the
>> options you have in the schema view.
>>
>>> Either way, this is the information being sent at the moment (I copied
>>> your orwell.qml example sources so far).
>>> {
>>> "applicationVersion": { "value": "5.10.90" },
>>> "compiler": { "type": "Clang", "version": "4.0" },
>>> "platform": { "os": "linux", "version": "arch-unknown" },
>>> "qtVersion": { "value": "5.9.0" },
>>> "startCount": { "value": 76 },
>>> "usageTime": { "value": 34132 }
>>> }
>>
>> That looks sane and shouldn't be the problem indeed.
>>
>> Regards,
>> 

Re: Application usage statistics and targeted user surveys

2017-06-15 Thread Aleix Pol
On Tue, Jun 13, 2017 at 6:56 PM, Volker Krause  wrote:
> On Monday, 12 June 2017 01:56:21 CEST Aleix Pol wrote:
>> On Sat, Jun 10, 2017 at 10:22 AM, Volker Krause  wrote:
>> > On Tuesday, 6 June 2017 15:01:57 CEST Aleix Pol wrote:
>> >> On Thu, May 25, 2017 at 4:42 PM, Volker Krause  wrote:
>> >> > On Wednesday, 24 May 2017 17:38:22 CEST Aleix Pol wrote:
>> >> >> On Tue, May 23, 2017 at 6:31 PM, Aleix Pol  wrote:
>> >> >> Hey Volker, I figured out this one. Never mind.
>> >> >>
>> >> >> I've done a proof of concept integrating it in Discover, here's 2
>> >> >> patches:
>> >> >> https://phabricator.kde.org/D5960
>> >> >> https://phabricator.kde.org/D5961
>> >> >
>> >> > There's still two aspects missing in the integration:
>> >> > - configure Provider to actually submit (see productIdentifier,
>> >> > feedbackServer and submissionInterval properties)
>> >> > - probably add some data sources (in the current form you only get an
>> >> > indication on how many users you have, and untargeted surveys, nothing
>> >> > more)
>> >> >
>> >> > The second point will need some more QML wrapper API. I'll look into
>> >> > adding a QML plugin to KUserFeedback directly for this.
>> >> >
>> >> >> Now to proceed I'd like to give a try to whole system including the
>> >> >> server. Do you have documented how to set it up anywhere? Would make
>> >> >> it easier.
>> >> >
>> >> > INSTALL contains the deployment documentation, both for the full setup
>> >> > with
>> >> > authentication on an Apache server, and locally for unsecured testing
>> >> > using
>> >> > the built-in PHP server.
>> >> >
>> >> > I've also got a playground server on my own infrastructure now that I
>> >> > can
>> >> > provide accounts for. And Jan has published his ongoing work on
>> >> > creating a
>> >> > Docker image for the server here:
>> >> > https://github.com/KDAB/kuserfeedbackdocker
>> >> >
>> >> > Regards,
>> >> > Volker
>> >>
>> >> Hi Volker,
>> >> More noob feedback:
>> >> I set up a local system I could tinkle with using your colleague's
>> >> docker. Worked quite well. But, I was getting an issue, possibly fixed
>> >> by this patch:
>> >> https://phabricator.kde.org/D6117
>> >
>> > This looks good, I'll try to get that path unit-tested to make sure this
>> > works with sqlite too. However, you should not actually hit this path in
>> > the first place, which is probably also why you are not seeing any data.
>> >
>> >> Now I get to see things being sent on the UserFeedbackConsole
>> >> application, but I only see timestamps. I added debug information to
>> >> see what is being sent and (after updating the discover patch above)
>> >> and I see all sort of data, being delivered. Is it being lost in the
>> >> internets? Or am I not looking into it correctly? If I export the
>> >> product using UserFeedbackConsole I also only get timestamps :(.
>> >
>> > Do you see the empty columns for the other data in UserFeedbackConsole, or
>> > do you only see the Timestamp column? In the former case the data is
>> > either not transmitted, or rejected by the server for some reason, we'd
>> > need to look at the JSON payload sent to the server in that case. In the
>> > other case, you probably need to set up a product schema first with
>> > UserFeedbackConsole (easiest via Schema -> Source Templates in the Schema
>> > view).
>>
>> Here's what I'm seeing: https://imgur.com/a/BmH2B
>> I've seen the schema view, I haven't pushed it much. I see I can add
>> stuff but I'm not sure what it's for. I expected the system to
>> integrate all data offered, but maybe I need to set the expectations
>> on the server side?
>
> Yes, exactly, that's what the schema does. Easiest way to get started is
> probably to just import the orwell example schema there, that contains all
> existing data sources, or you just create sources from their corresponding
> templates.
>
> That is, in the schema view chose schema -> import schema... or schema ->
> source template >  When you are done, select schema -> save schema to
> write the changes to the server. Afterwards you should see a lot more columns
> and more charts in the analytics view.
>
> User documentation is still fairly limited on this, but there is a start of a
> user manual describing the data model, that should help to explain most of the
> options you have in the schema view.
>
>> Either way, this is the information being sent at the moment (I copied
>> your orwell.qml example sources so far).
>> {
>> "applicationVersion": { "value": "5.10.90" },
>> "compiler": { "type": "Clang", "version": "4.0" },
>> "platform": { "os": "linux", "version": "arch-unknown" },
>> "qtVersion": { "value": "5.9.0" },
>> "startCount": { "value": 76 },
>> "usageTime": { "value": 34132 }
>> }
>
> That looks sane and shouldn't be the problem indeed.
>
> Regards,
> Volker
>
>> > I'll also try your Discover patches here to see if I can reproduce this,
>> > the QML bindings haven't gotten any real use yet, quite possible some

Re: [sysadmin/repo-metadata] projects/kdereview/qtcurve: Move QtCurve to KDE Review at request of it's maintainer

2017-06-15 Thread Ben Cooksley
On Wed, Jun 14, 2017 at 5:46 AM, Albert Astals Cid  wrote:
> Can you please tell whoever asked for that to send an email here, because i've
> seen nothing.

I'll do so shortly.

>
> Cheers,
>   Albert

Regards,
Ben

>
> El dissabte, 10 de juny de 2017, a les 3:36:46 CEST, Ben Cooksley va escriure:
>> Git commit 8464153d3e7b76c37a3114a9c639c17fc07f6e8e by Ben Cooksley.
>> Committed on 10/06/2017 at 03:36.
>> Pushed by bcooksley into branch 'master'.
>>
>> Move QtCurve to KDE Review at request of it's maintainer
>> CCMAIL: kde-core-devel@kde.org
>> Fixes T6306
>>
>> R  +0-0projects/kdereview/qtcurve/i18n.json [from:
>> projects/playground/base/qtcurve/i18n.json - 100% similarity] R  +0-0
>>  projects/kdereview/qtcurve/metadata.yaml [from:
>> projects/playground/base/qtcurve/metadata.yaml - 100% similarity]
>>
>> https://commits.kde.org/sysadmin/repo-metadata/8464153d3e7b76c37a3114a9c639c
>> 17fc07f6e8e
>>
>> diff --git a/projects/playground/base/qtcurve/i18n.json
>> b/projects/kdereview/qtcurve/i18n.json similarity index 100%
>> rename from projects/playground/base/qtcurve/i18n.json
>> rename to projects/kdereview/qtcurve/i18n.json
>> diff --git a/projects/playground/base/qtcurve/metadata.yaml
>> b/projects/kdereview/qtcurve/metadata.yaml similarity index 100%
>> rename from projects/playground/base/qtcurve/metadata.yaml
>> rename to projects/kdereview/qtcurve/metadata.yaml
>
>


Re: kio-stash is in KDE Review

2017-06-15 Thread Ben Cooksley
On Thu, Jun 15, 2017 at 9:04 AM, Albert Astals Cid  wrote:
> El dimecres, 14 de juny de 2017, a les 21:42:58 CEST, Arnav Dhamija va
> escriure:
>> Just to check I setup a brand new virtualbox with KDE Neon 5.8 LTS and
>> ran the following commands after cloning the repo and creating a build
>> directory:
>>
>> cmake -DCMAKE_INSTALL_PREFIX=/usr -DKDE_INSTALL_USE_QT_SYS_PATHS=TRUE ..
>> make
>> sudo make install
>> kdeinit5
>>
>> ..and then I ran the tests using 'ctest -v'. It passed slavetest with
>> no issues (18 out of 18 tests passed). My guess why it doesn't work
>> you is because you haven't run kdeinit5 after installing the ioslave.
>> If not that, the testdaemon process might not have been successfully
>> registered on the system D-Bus when thes test is run.
>>
>> Is there a way I can see if my test cases pass on KDE's CI
>> infrastructure to narrow down the problem? If so, I will a sysadmin to
>> do so.
>
> You said you were asking for kio-stash to be added to CI? What happened with
> that? Or am i misremembering?

I actioned the request this morning (my time).

>
> Cheers,
>   Albert

Regards,
Ben

>
>>
>> On Tue, Jun 13, 2017 at 4:16 AM, Albert Astals Cid  wrote:
>> > El divendres, 9 de juny de 2017, a les 11:45:14 CEST, Arnav Dhamija va
>> >
>> > escriure:
>> >> > Do you mean i have to manually start a process for the tests to
>> >> > succeed?
>> >>
>> >> If installed correctly with kdeinit restarted and the Stash Daemon is
>> >> running in kded5, it is not required. However, I cannot recall what
>> >> steps are needed for this to happen as I think it requires a system
>> >> restart or logout to do so.
>> >>
>> >> Hence, I have created a fallback testdaemon program which creates a
>> >> daemon process for the Stash Daemon to run. This is launched
>> >> automatically by the test suite if the test suite cannot find the
>> >> Stash Daemon running in kded. I just patched it so that it finds the
>> >> path to the testdaemon program correctly (it had the wrong path when
>> >> you tested it). It should pass the test cases now with no manual
>> >> invocation of the testdaemon process.
>> >
>> > Doesn't seem to work for me.
>> >
>> > https://paste.kde.org/ptnn5hhkt
>> >
>> > Cheers,
>> >
>> >   Albert
>> >>
>> >> On Fri, Jun 9, 2017 at 1:47 AM, Albert Astals Cid  wrote:
>> >> > El dijous, 8 de juny de 2017, a les 16:25:02 CEST, Arnav Dhamija va
>> >
>> > escriure:
>> >> >> Yes, I will file a sysadmin ticket for the same. Until I do so, could
>> >> >> you send me the output of the test suite in a screenshot or as plain
>> >> >> text?
>> >> >>
>> >> >> The ioslave works by storing a list of virtual files and folders in a
>> >> >> process running in the KDED, communicating with it over D-Bus. Hence,
>> >> >> some of the tests won't work unless a) the testdaemon process is
>> >> >> started
>> >> >
>> >> > Do you mean i have to manually start a process for the tests to
>> >> > succeed?
>> >> >
>> >> > If that is the case, that's not acceptable.
>> >> >
>> >> > Cheers,
>> >> >
>> >> >   Albert
>> >> >>
>> >> >> or b) the Stash KIO slave watcher is running in KDED. Usually
>> >> >> it requires a restart of KDED and a kdeinit after installing the
>> >> >> ioslave to have the Stash daemon running in KDED.
>> >> >>
>> >> >> On Thu, Jun 8, 2017 at 3:42 AM, Albert Astals Cid 
> wrote:
>> >> >> > El divendres, 26 de maig de 2017, a les 22:55:11 CEST, Arnav Dhamija
>> >> >> > va
>> >> >> >
>> >> >> > escriure:
>> >> >> >> Hi!
>> >> >> >>
>> >> >> >> I had made the kio-stash ioslave last year as part of my GSoC 2016
>> >> >> >> Project. Now that most of the changes which I wished to make in
>> >> >> >> Dolphin relevant to the ioslave are part of master, I wish to ship
>> >> >> >> the
>> >> >> >> ioslave soon.
>> >> >> >>
>> >> >> >> The project is now in KDE review and is awaiting feedback. The link
>> >> >> >> for the same can be found here:
>> >> >> >> https://phabricator.kde.org/R247:0f4dc333ac8469b36d1b3a1cedd0a6672a
>> >> >> >> c90
>> >> >> >> 7b8
>> >> >> >>
>> >> >> >> The source of the project can be found here:
>> >> >> >> https://cgit.kde.org/kio-stash.git/
>> >> >> >
>> >> >> > Can you please get it covered by the CI?
>> >> >> >
>> >> >> > I have some of the tests failing but don't know if it is because my
>> >> >> > setup
>> >> >> > is a bit broken at this moment, so wanted to check in CI if the
>> >> >> > tests
>> >> >> > were file but I have not been able to find it there.
>> >> >> >
>> >> >> > Cheers,
>> >> >> >
>> >> >> >   Ablert
>> >> >> >>
>> >> >> >> Thanks.
>
>