Mailing-List: contact dev-help@devicemap.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@devicemap.apache.org
Received-SPF: pass (nike.apache.org: domain of rezmang@yahoo.com designates
 216.109.115.223 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.com;
	b=ZwL9LYUQAnWmup3St563Rhfsj5YELT56Vd2wduPL3XPmHKWCwPIs9fDxSgJYXNxQZssxfy4z+MSk0z73IFax3h0ygRD73x1e1wD9dRgEqD06rmzgI+VS05F80VQ7JcXhzjQrcPB/8S8baqgGJ/M7NUzscDneIvFomRaOudmUz1Xg5FvaS5EE2qIED9GiR85hOC4UKrk+2Pyz916dtq8ZivBkP4hL/kQqyzW/9na3VIS1RXiFZIO/jeAIjTcey1DYBx1z+oqF3m40idSpgq/07vmWE/qctK0Kq0GBjkpbMfFuKuboAwnf5Aeh6aAkC6oD3/0WLOAU+lM5L6/Efp+vzA==;
Date: Fri, 2 Jan 2015 16:00:16 +0000 (UTC)
From: Reza Naghibi <reza.naghibi@yahoo.com.INVALID>
Reply-To: Reza Naghibi <reza.naghibi@yahoo.com>
To: "dev@devicemap.apache.org" <dev@devicemap.apache.org>
Message-ID: 
 <791090846.3697201.1420214416476.JavaMail.yahoo@jws106107.mail.bf1.yahoo.com>
In-Reply-To: 
 <CAP7pH7teJ2hNiSM9+B1nsMa3UgZGNQpZ0nud+WMnU-V2LyV6=Q@mail.gmail.com>
References: 
 <CAP7pH7teJ2hNiSM9+B1nsMa3UgZGNQpZ0nud+WMnU-V2LyV6=Q@mail.gmail.com>
Subject: Re: Collecting Specs for UAs
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_3697200_887286088.1420214416470"

------=_Part_3697200_887286088.1420214416470
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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 a=
t 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 s=
pecs

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 divi=
de and conquer. Just send me a message and I should be able to assign a ser=
ies to you so no one else takes it. And then we just have to work our way t=
hru the lists.

      From: Volkan Yaz=C4=B1c=C4=B1 <volkan.yazici@gmail.com>
 To: "dev@devicemap.apache.org" <dev@devicemap.apache.org>=20
 Sent: Friday, January 2, 2015 4:23 AM
 Subject: Collecting Specs for UAs
  =20
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:

=C2=A0 - id
=C2=A0 - vendor
=C2=A0 - model
=C2=A0 - marketing name
=C2=A0 - resolution-x
=C2=A0 - resolution-y
=C2=A0 - pixel-density-ppi
=C2=A0 - release-year
=C2=A0 - default-os
=C2=A0 - hardware

I have some questions regarding these properties:

=C2=A0 - How other people collect this sort of information? Is there a cert=
ain
=C2=A0 set of steps that I can follow? I was considering writing a crawler =
on top
=C2=A0 of a web-based proprietary UA resolver, would that be ok considering=
 the
=C2=A0 licensing issues?
=C2=A0 - Is there scheme am I supposed to follow for the *id* attribute? Or
=C2=A0 something descriptive would be just fine?
=C2=A0 - *resolution-x/y* means the width and height of the screen in pixel=
s,
=C2=A0 right?
=C2=A0 - How do we calculate *pixel-density-ppi*?

Best.


------=_Part_3697200_887286088.1420214416470--