>> Reza, would you like to do the structural organization? I believe all outstanding tasks are done.
As for tasks, the only task that need attention right now is data. Im not aware of any priority client tasks at the moment. Also, given that 2.0 is on the horizon, time spent on clients is better spent on 2.0 than 1.0. If there is something substantial that can be added in 1.0, then im all for it, especially in the performance or accuracy area. Back to the data, I am still planning on more data release, 1.0.3, hopefully in May. So take a look at these tickets: https://issues.apache.org/jira/browse/DMAP-96 https://issues.apache.org/jira/browse/DMAP-154 Between these 2 tickets, there are about 30 relevant devices which can be added which would complete the 1.0.3 release. The steps for adding devices: 1) Create a JIRA ticket for the device, assign it to yourself, and add as much info to the device as possible. There are numerous examples of this on JIRA that you can use as a guide. Most importantly, make sure the model, specs, and user-agent are in the ticket. This is important because Google (and other engines) will index the JIRA ticket and future searches for the device and its attributes will return the ticket as a top result. This is a great way to expose our data to future users. 2) Add the pattern and device attributes to the ODDR xml. Once again, use previous devices as a guide or just ask the list if you have a question. 3) Add a unit test for the device to the Java client. Just add 1 line at the bottom with the user agent and the device id to this file: https://svn.apache.org/viewvc/devicemap/trunk/clients/1.0/java/src/test/resources/uas.data?view=markup Make sure that the client is using the data snapshot dependency that you are working on. On Thu, Apr 30, 2015 at 7:05 AM, Volkan Yazıcı <[email protected]> wrote: > I will have some time at the weekend to check this out. > > Reza, would you like to do the structural organization? > Or do you prefer me to do it? If so, I will be appreciated > if you can share a couple of steps that I need to take. > Such as, > > - remove X dependency from POM, > - move modules X to directory Y, > - etc. > > Best. > > On Thu, Apr 30, 2015 at 11:33 AM, Werner Keil <[email protected]> > wrote: > > > Hi, > > > > After the hackathon last weekend and a busy week in local projects, I > > should have a little more time this weekend, also due to May 1st holiday > > tomorrow. > > > > I have not set up any Jenkins job or requested one, but > > got /trunk/clients/w3c-ddr/ consistent by fixing old names or POM > > references like "java". This module is now self-contained and also builds > > properly in Maven. I trust Reza or other committers can help doing the > same > > on the /clients/java side. Ideally also with separate /examples building > on > > top of a particular client. > > > > How about .NET? It was pretty unaffected by the actual change, but > Log4Net > > shows clearly, there is a Jenkins node and possibly plugins allowing to > > build C# or VB.net projects, too. > > > > @Eberhard, would you be able and willing to drive that, or do you > currently > > have no time for that? > > > > Also on the long run, it seems Microsoft plans to replace Visual Studio > > Community Edition with something called "Visual Studio Code", see > > https://code.visualstudio.com/Docs > > > > I downloaded it, probably give it a try here or on my laptop if it > doesn't > > take too much HD space over the weekend. It looks like it does the basic > > stuff for all of these languages: > > https://code.visualstudio.com/Docs/languages so more or less an answer > to > > Eclipse, NetBeans or free versions of IntelliJ from Microsoft. > > Thus trying to edit and compile the .NET codebase with this new "Open > > Source friendly" IDE from Microsoft and maybe offer some level or README > > (VS Code also supports MarkDown;-) seems like a good idea. Not to > mention a > > lot of other languages, including Java also are supported. > > > > Werner > > >
