Do we have new device data? These updates are supposed to come monthly...
________________________________ From: Werner Keil <[email protected]> To: "[email protected]" <[email protected]> Cc: Gopal Kris <[email protected]> Sent: Wednesday, June 25, 2014 10:33 AM Subject: Re: DeviceMap Community - Incubator PMC/Board report Gopal/all, This is the June report for DeviceMap. We skipped a month or two before that, ideally we'd like to contribute to the next report, but the question is, can we say anything substantial about the Device Data Service prototype you said you have in the pipeline yet? I'll talk about DeviceMap this weekend (Sun) at a Web Developer MeetUp. That was already mentioned, but if attendees or the organizer of this meeting have clear intentions to contribute based on their dealing with the project I'd add this before July 1 or 2. Nothing new from me other than that. --------------------DeviceMapApache DeviceMap is a data repository containing device information, imagesand other relevant information for all sorts of mobile devices, e.g.smartphones and tablets. While the focus is initially on that data, APIswill also be created to use and manage it.DeviceMap has been incubating since 2012-01-03.Three most important issues to address in the move towards graduation: 1. Grow community. 2. Generate a release. 3. Explore options to allow contributions through a Web based interface/API to add new device specs. 4. Improved support for additional languages/platform (.NET, PHP,...)Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to beaware of? (None)How has the community developed since the last report? Tangentially, there have been presentations at conferences like JavaLand raised awareness. A Mobile Development MeetUp group in Germany is looking into the code, and where they might contribute.How has the project developed since the last report? Syncing device data with OpenDDR in regular intervals when relevant changes occur. Update of the Java DDR Simple API and other libraries.Date of last release: N/AWhen were the last committers or PMC members elected? N/A Cheers, Werner On Tue, Jun 3, 2014 at 6:20 AM, Gopal Kris <[email protected]> wrote: > Web based interface to verify and add new device specs is what iam working > on. > > Sent from my iPhone > > > On 02-Jun-2014, at 10:40 pm, Werner Keil <[email protected]> wrote: > > > > Spreading the word (as one of the few at the moment) is the best thing > to do at the moment. > > If contribution via a solid Web Service or Web Based interface can't be > established here for DeviceMap, then I'm afraid, it's likely t fail. > > And for that there's always a fall-back option to OpenDDR > > > > See attempts by Stephen Colebourne to create "Apache Commons Money" > which failed quite miserably. So did his follow-up "JodaMoney", but he at > least occasionally helped a bit with a new Java Standard in this area, > JavaMoney.org (JSR 354). Sometimes it takes time and also exploring > multiple options. Let's see which one is right here > > > > Werner > > > >> On Mon, Jun 2, 2014 at 6:58 PM, Kevan Miller <[email protected]> > wrote: > >> Thanks for the info. > >> > >> There may be lots of technical reasons justifying DeviceMap as project. > >> >From an ASF perspective, these are secondary. Primarily, the ASF will > need > >> to see a viable DeviceMap *community*. > >> > >> http://incubator.apache.org/guides/graduation.html is worth reading > from > >> time to time. And measuring where we think we are in meeting these > criteria. > >> > >> --kevan > >> > >> > >> On Mon, Jun 2, 2014 at 3:35 AM, Werner Keil <[email protected]> > wrote: > >> > >> > I'd say these are only 2 very good arguments for the existence (and > >> > eventual graduation) of DeviceMap: > >> > > >> > > http://www.telegraph.co.uk/technology/samsung/10869294/Samsung-launches-first-open-source-Tizen-smartphone.html?bcsi-ac-95bb4efa6a1646c8=229BB80200000503pehAqDaU4KXwMGaXAhZZ60bGqOWhAAAAAwUAADJVUQAIBwAAIQAAAON6AwA= > >> > and > >> > > >> > > http://dashburst.com/mobile-devices-insanely-large-screens/?utm_content=bufferfa4e6&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer > >> > > >> > Werner > >> > > >> > On Thu, May 29, 2014 at 2:08 AM, eberhard speer jr. <[email protected] > > > >> > wrote: > >> > > >> > > -----BEGIN PGP SIGNED MESSAGE----- > >> > > Hash: SHA1 > >> > > > >> > > Hi, > >> > > > >> > > my 2 cents regarding growing the community : > >> > > > >> > > In short : > >> > > > >> > > This community is small and we see it getting smaller. > >> > > There some very good reasons for this (see below). > >> > > This will by it's nature always be a rather small specialized > community. > >> > > But the ability to identify a user-agent/device will remain a > >> > > fundamental thing. > >> > > > >> > > Bit Longer : > >> > > > >> > > 1) The 'Frameworks' always had the edge : much closer to the > >> > > web-developer. DDR is HTTP-headers, back-end-y, further...far away > >> > > stuff and never really reached them. > >> > > > >> > > 2) "Device" is shifting. What is currently understood as a "device", > >> > > the smart-and not so-smart phones, tables, pads, phablets,... are > >> > > becoming more generic. Instead of long lists of esoteric properties, > >> > > it's basically back to : OS/browser/rendering-engine. > >> > > DDR was 'sexy' because 'mobile' was 'device'. > >> > > > >> > > 3) HTML5 : following what goes on on the WhatWg list and 'out there' > >> > > you see it becoming easier and easier to 'do mobile' -- the sexy > >> > > stuff, no frameworks etc. > >> > > > >> > > *But* the need for other uses stays [traffic analyses] and much more > >> > > importantly : 'device' will shift : "the Internet of > Things"...sounds > >> > > very much like "devices" to me. > >> > > > >> > > Maybe the community should congratulate 'mobile' as it graduates > from > >> > > 'device', and be ready to welcome in the next 'devices'. > >> > > > >> > > > >> > > esjr > >> > > -----BEGIN PGP SIGNATURE----- > >> > > Version: GnuPG v1.4.8 (MingW32) > >> > > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > >> > > > >> > > iQEcBAEBAgAGBQJThnqJAAoJEOxywXcFLKYcRlkH/irsBE8rnMWdu2Lfqrh31IDx > >> > > WH7xSTdUf6i3ZJeimcig7MaLQy1G/3FR/QrmSjjwNCGo73Gq5sss6YnRLuDxwB3m > >> > > ZMphxb3EAV2SUsT037fnSiM+I6BFC86nWs78S6FTD9etySlT2TCjW9OUp3wwXcIB > >> > > //hmfmCuQT2TueOouN/Hk+RCiV3WuFW0JJ0l+MmBlMX9YgHp5Q2IxtuWegVae/Bn > >> > > 1jF0zKewHAgrk90K5zH6gS4S1wS1h8QFTRcfHgxhUPEkMVg+c8X8aTS9QkYFNVmY > >> > > VX4PC4UshrsStHVOve9lbic948qTLxBbIw5PPOapl55BXJJ/lLvfcs3ODHulLW0= > >> > > =qjoV > >> > > -----END PGP SIGNATURE----- > >> > > > >> > > > >
