Sure. One more thing, if we feel that the series is extremely uniform, then we
can do a blanket pattern and capture the whole series as a single generic
series device. That might be best. Im not sure, I havent looked thru the models
in detail. So let me know.
From: Volkan Yazıcı <[email protected]>
To: "[email protected]" <[email protected]>; Reza Naghibi
<[email protected]>
Sent: Friday, January 2, 2015 11:12 AM
Subject: Re: Collecting Specs for UAs
Yes, please do so.
I will see what I can do...
On Fri, Jan 2, 2015 at 5:00 PM, Reza Naghibi <[email protected]
> wrote:
> Volkan, I probably should have taken a look earlier, but each device needs
> it own JIRA and entry. For example:
>
> https://issues.apache.org/jira/browse/DMAP-97
>
>
> You have this as Samsung SM-N series. But when I look at the user-agents,
> I see the following models:
>
> SM-N7502, SM-N7505, SM-N9007, SM-N900W8
>
>
> So what we can do is treat these tickets as parents. We then have to look
> at the all different models in the series and:
>
> 1) Check if they are already in the DDR
> 2) If not, create a sub task for the model, put in the user agent and the
> specs
>
> As for the specs, just search google. For example: 'SM-N7502 specs':
>
> http://www.gsmarena.com/samsung_galaxy_note_3_neo_duos-6015.php
>
>
> Once that is done, we can add them to the DDR.
>
> I can help with this. I think if we each take a series, we can kind of
> divide and conquer. Just send me a message and I should be able to assign a
> series to you so no one else takes it. And then we just have to work our
> way thru the lists.
>
> From: Volkan Yazıcı <[email protected]>
> To: "[email protected]" <[email protected]>
> Sent: Friday, January 2, 2015 4:23 AM
> Subject: Collecting Specs for UAs
>
> Hi all,
>
> The entire UA collection tickets (DMAP-94, 95, 96, 97, 98, 100, 102) I have
> submitted to JIRA are being marked as NeedsSpec, which is fine. In the
> explanation, I am being told that I need to collect the following
> properties for each UA:
>
> - id
> - vendor
> - model
> - marketing name
> - resolution-x
> - resolution-y
> - pixel-density-ppi
> - release-year
> - default-os
> - hardware
>
> I have some questions regarding these properties:
>
> - How other people collect this sort of information? Is there a certain
> set of steps that I can follow? I was considering writing a crawler on
> top
> of a web-based proprietary UA resolver, would that be ok considering the
> licensing issues?
> - Is there scheme am I supposed to follow for the *id* attribute? Or
> something descriptive would be just fine?
> - *resolution-x/y* means the width and height of the screen in pixels,
> right?
> - How do we calculate *pixel-density-ppi*?
>
> Best.
>
>
>
>
