Hi, The Spring/Servlet demos are still down on the vm. Will catch up on the JIRA ticket over the weekend if nobody else has time right now.
For a slightly more important goal of crowd-sourcing device updates, allowing users to test their device/UA against DeviceMap data, I asked what Portlet 3 experts think about using Pluto for that. Device Atlas UA Tester https://deviceatlas.com/device-data/user-agent-tester probably closest to what we need in a similar way requires users to register and log in first. https://deviceatlas.com/user/register is nothing but a scaled-down Portal if you want. Thus why reinvent the wheel if every major Portlet container like Pluto offers all that already. Combining registration with the necessary disclaimer (I trust Bertrand could help with that similar to what we wrote for the W3C DDR implementation) should be enough from a legal point of view. Maybe some sort of captcha to avoid bots and other scripting solutions, but that is also part of nearly every portal these days or easy to integrate. With a bit of help from the Portlet 3 EG/Pluto team, I am more than happy to drive this. Given the tagline of DeviceMap is "Apache DeviceMap is a project to create a data repository containing device information, images and other relevant information for all sorts of mobile devices, e.g. smartphones and tablets." I'd say maintaining that data or helping others to do so should be our main goal to keep the project active enough and alive. Whether the format may change some day in the future, we can still think about it but without contributors none of that makes sense, just look at Reza's fork that nobody cares about or contributed to since he put it on GitHub. Werner
