So I think this is a great place to start. Can we go ahead and spend a little bit of time making sure the JIRA system is properly configured and useable for reporting devicemap issues, and in particular, data related issues? So an important workflow is going to be device defects and new device additions. So the only issues I see is that we need to customize the 'component' and 'issue type' fields so they match our product(s). Any idea how we can configure this? Can guests submit issues?
Once we have this system in place, we can go ahead and start patching and updating the device map DDR...! Im going to put the whole git thing on ice for now. Its not too critical at the moment. Svn will work. Im also going to go ahead and try and finalize the Java api in the next week, we still have a few lingering cleanup tasks. ________________________________ From: Werner Keil <[email protected]> To: "[email protected]" <[email protected]> Sent: Monday, June 30, 2014 9:59 AM Subject: Re: OpenDDR switch to Apache DeviceMap Adam/all, Thanks a lot for the input and interest in helping maintain device data. As of now, the repository files are structurally compatible, and where W3C DDR specified that also major client API. A "How to contribute" guide, similar to e.g. the Agorava project ( http://agorava.org/contributing/) is probably a good idea. If you are not an Apache committer to any other project, it's probably best to start by filing change requests for device data in JIRA https://issues.apache.org/jira/browse/DMAP. Interesting to hear about the BrowserCap project. Especially maintaining device data was not so different at OpenDDR recently, and a monthly launch cycle got slower in Q1, so we may have a similar situation here. Which is why we hope to have a decent number of people maintain this kind of information at DeviceMap rather than have several small projects do this side by side at a slower pace. Regards, Werner Werner Keil | JCP Executive Committee Member, JSR 363 Co Spec Lead | Eclipse UOMo Lead, Babel Language Champion | Apache Committer Twitter @wernerkeil | @UnitAPI | @JSR354 | #EclipseUOMo | #Java_Social | #DevOps Skype werner.keil | Google+ gplus.to/wernerkeil * Developer Week: 14/15 Jul 2014, Nürnberg, Germany. Werner Keil, JCP EC Member, JSR 363 Spec Lead, DevOps Guy will present "Triple-E' class Continuous Delivery", "JSR 363 and IoT" (GER) * JavaZone 2014: 9-11 Sep 2014, Oslo, Norway. Werner Keil, JCP EC Member, JSR 363 Spec Lead will present "JSR 363 - The Answer to Life Science and the Internet of Everything" * JavaOne 2014: Sep 28-Oct 2 2014, San Francisco, USA, Werner Keil, JCP EC Member, JSR 354 EG Member will host "Java and Digital Currencies, Friend or FOE" * JMaghreb 3.0: 4-6 Nov 2014, Casablanca, Morocco. Werner Keil, JCP EC Member, JSR 363 Spec Lead, DevOps Guy will present "Triple-E' class DevOps", "JSR 363" * Mobile Developer Conference kompakt: 18 Nov 2014, Hamburg, Germany. Werner Keil, JCP EC Member, Apache DeviceMap Committer will present "Apache DeviceMap" (GER) On Mon, Jun 30, 2014 at 2:45 PM, Adam <[email protected]> wrote: > Hi, > > I'm currently using the OpenDDR resources files with a Varnish dClass > component (https://github.com/TheWeatherChannel/dClass) to do browser > detection for a number of sites. > > Is there any difference between your data and the OpenDDR resource > files, or are they both compatible? > > Going forward I am able to help maintain these device databases. Is > there any documentation/advice on updating the files? > > I've previously used the Browser Capabilities Project > (http://browscap.org/), however the person responsible for the project > changed a year ago and since then the files have gone through > exponential growth and becoming unusable. OpenDDR & Apache DeviceMap > look like idea replacements. > > Regards > > Adam >
