I accidentally dropped devicemap-dev@ off of an email exchange with Werner. Reposting (with Werner's permission):
On Sun, Jun 8, 2014 at 9:17 PM, Werner Keil <[email protected]> wrote: > Kevan, > > Thanks for the reply. > > We're looking forward to require Gopal's approach as a PoC for a > web-based interface to update device signatures, but it's good to hear, it > should be possible to update "content" (in addition to executable code) > that way, too. > > If "release" only refers to a graduation or 1.0 that is not the case, but > I assume there is a "Milestone" practice somewhat similar to e.g. Eclipse > or other communities with 0.x milestone builes. The tag of most artifacts > got a rather unlucky "0.9.9-SNAPSHOT" initial version, Except for the data > artifact, see below, tags for other libraries are at slightly more > realistic values leaving room for improvement. > > Information in "device-data" until a web-based API is in place relies on > OpenDDR contributions. Those don't stop, and currently the data of OpenDDR > reached a version of 1.27. The latest sync happened with 1.26. As the > version information contains a distinct version number, that matches the > one by OpenDDR, thus for the time being it is also naturally to have > matching SVN tags for the data project. Putting "0.9.9-SNAPAHOT" there > would make little sense. At the moment the results don't even go to the > Apache Snapshot repo, but that's another isssue I hope Bertrand can help > resolve. > > > Here the text based on the information I sent earlier, plus update on > committers. I believe Gopal works at Adobe with Bertrand, please confirm > with him, because Gopal isn't yet updated on the DeviceMap team page, but > should be a committer since March 2014, maybe sooner. > > > -------------------- > DeviceMap > > Apache DeviceMap is a data repository containing device information, images > and other relevant information for all sorts of mobile devices, e.g. > smartphones and tablets. While the focus is initially on that data, APIs > will > 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. Does Appache support contribution throgh a Web based interface/API to > add new device specs (similar to e.g. Eclipse Babel) > 2. Improved support for additional languages/platform (.NET, PHP,...) > 3. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > > > How has the community developed since the last report? > 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: > 2014-03-24 > > When were the last committers or PMC members elected? > Mar 2014 > (please confirm with Bertrand) > > -------------------- > > Thanks and Regards, > Werner > > On Sun, Jun 8, 2014 at 11:59 PM, Kevan Miller <[email protected]> > wrote: > >> >> On Thu, Jun 5, 2014 at 11:43 AM, Werner Keil <[email protected]> >> wrote: >> >>> I trust you must have missed the full text I sent here a bit earlier, >>> thus here is the complete content. >>> >> >> I've been reading emails and responding, as I felt was needed / >> appropriate. If someone wants to create a board report, I'll copy it into >> the wiki. The only consumable version of a board report was your previous >> email, which I responded to. If you want other content. Please put it in a >> format that you'd like relayed to the board. >> >> >>> >>> And the first and most important issue rephrased. It is one thing to >>> demonstrate such a web based interface works, the other more important one >>> crucial to growing the community is "Can this work at Apache?" >>> Unfortunately the mindset is very code-driven, but this is not the case >>> here. A large majority of people contributing new device information to the >>> "data" project are unlikely to do this via "Git Pull-requests" though that >>> could be an improvement over XML, if we really want to >>> >>> Does foundation bureaucracy allow a "contributor" to provide such >>> information just the way it works e.g. in a JIRA bug ticket (IMHO >>> attachment to JIRA may not work properly here, I don't think Gopal's >>> approach works like that, but I have not seen much of it yet) >>> >> >> I believe the answer to this would be yes. If there is a concrete >> proposal for this, then we can discuss and request approval (or communicate >> intentions with the rest of the ASF) as necessary... >> >> >>> The last code release happened on March 24, both to the "data" and >>> "client" code. >>> >> >> What release? OK, I now see that some tags were created. However, as far >> as I know, there have not been any release votes or discussions. So, there >> has not been a *release*. And the fact that we might be referring to the >> tags as a release (and even the existence of the tags) is a sign of my poor >> mentorship of the project. >> >> >>> There is regular sync with OpenDDR and until we know the data/resource >>> gathering can be done at DeviceMap in a consistent and approved way that >>> helps grow the community, it is good to be backward compatible with >>> OpenDDR. Should it be necessary to use it as "fall-back"... >>> >> >> Can you explain "regular sync"? >> >> >>> >>> For the bottom parts including last time (code) committers were added, >>> please refer to earlier Wiki or ask Bertrand. >>> >> >> >> >
