Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reorganize technical reports #7227

Closed
sgiehl opened this issue Feb 16, 2015 · 8 comments
Closed

Reorganize technical reports #7227

sgiehl opened this issue Feb 16, 2015 · 8 comments
Assignees
@sgiehl
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone
2.13.0

Comments

@sgiehl
Copy link
Member

sgiehl commented Feb 16, 2015

we should reorganize the technical reports. (follow up to #3962)

We currently have:

  • Devices
    • Device type
    • Device brand
    • Device model
    • Browser (Versions)
    • OS (Versions)
    • Browser engine
  • Visitor settings
    • Resolution
    • Configurations (OS / Browser / Resolution)
    • Browser plugins
    • Browser language

I don't think that this splitting makes much sense. Maybe something like that would fit more:

  • Devices
    • Device type
    • Device brand
    • Device model
    • Resolution
  • Something like "Browser & Operating System"
    • Browser (Versions)
    • OS (Versions)
    • Browser engine
    • Browser plugins
    • Configurations (OS / Browser / Resolution)

Browser language report will be move to location reports in #7226
Devices reports should also be improved, which will be done in #6933

Maybe we could also link the resolution and the configurations reports as related?
@sgiehl sgiehl added the RFC Indicates the issue is a request for comments where the author is looking for feedback. label Feb 16, 2015
@mattab mattab added this to the Piwik 2.12.0 milestone Feb 16, 2015
@tsteur
Copy link
Member

tsteur commented Feb 19, 2015

👍 for reorganizing it like this. I was always confused by that. Would be nice to have something shorter than "Browser & Operating System" but I like that it's clear. Maybe "Software"? or something else...

@gaumondp
Copy link

"Browser & Operating System" => Browser & OS ?
"Browser & Operating System" => Client software ?

"Software" alone could be misleading IMHO.

@sgiehl
Copy link
Member Author

sgiehl commented Feb 21, 2015

I think "Client Software" would fit best, as we might add more reports there in #5413

@sgiehl sgiehl self-assigned this Feb 22, 2015
@sgiehl sgiehl removed the RFC Indicates the issue is a request for comments where the author is looking for feedback. label Feb 22, 2015
@mattab
Copy link
Member

mattab commented Feb 23, 2015

+1 for Client software

@tsteur
Copy link
Member

tsteur commented Feb 23, 2015

"Client Software" would be only browser but not Operating System right?

"Client Software" from http://techterms.com/definition/client :

The term "client software" is used to refer to the software that acts as the interface between the client computer and the server. For example, if you use Microsoft Outlook to check your e-mail, Outlook is your "e-mail client software"

As this report is under "Visitor" I would have preferred just "Software". Maybe some people would be even confused by this rather technical name (Client Software)? Software would be a bit broader / universal since we also want to allow to track other things than websites.

@sgiehl
Copy link
Member Author

sgiehl commented Feb 23, 2015

@tsteur good point. So "software" only?

@sgiehl sgiehl mentioned this issue Feb 24, 2015
Merged
@mattab mattab modified the milestones: Piwik 2.12.0, Piwik 2.13.0 Mar 11, 2015
@mattab
Copy link
Member

mattab commented Apr 1, 2015

see comment in: #7292 (comment)

After this little one, maybe we close the issue 👍

@mattab mattab added Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. c: Usability For issues that let users achieve a defined goal more effectively or efficiently. labels Apr 1, 2015
sgiehl added a commit that referenced this issue Apr 1, 2015
@sgiehl
refs #7227 #7292 - added fallback for index action
d9f89ad
sgiehl added a commit that referenced this issue Apr 1, 2015
@sgiehl
refs #7227 #7292 - updated UI test to check software page instead of …
a118f7d 
…old visitor settings
@sgiehl
Copy link
Member Author

sgiehl commented Apr 1, 2015

UI tests should be fixed now

@sgiehl sgiehl closed this as completed Apr 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sgiehl sgiehl

Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Milestone
2.13.0
Development

No branches or pull requests
4 participants
@tsteur @mattab @sgiehl @gaumondp