Bertrand/all, Thanks for your support getting the project started and as you said mainly with infrastructure or board-related duties since.
Sorry to see you leave, but if out of 13 (14 or 15 max at times) committers only 1, 3 or no more than 3 ever really committed something, neither you nor others are to blame. A data-driven project like DeviceMap where the most important artifact is information, not executable code was probably never seen at Apache before. All the "Big Data" projects do not contribute data, they only help storing, processing or analyzing it. Especially that information was never maintained and released at the same pace as OpenDDR set standards between 2011 and 2014. With pretty much monthly releases, at the very least once a quarter. DeviceMap Data released approx. every 6 months and now it's been a year since 1.0.3. Following what some vendors do, a dual-format approach with XML or JSON was a fascinating idea, but neither Reza nor myself or others could have maintained that all by ourselves. And his "TextGlass" project forked out of the JSON idea shows no activity: https://github.com/TextGlass/device No forks, no issues, no pull requests, and the only one watching it is Reza. I was more active with DeviceMap data and clients, e.g. getting the VB.NET or C# clients released (something its original author never managed for a long time) DeviceMap Data contains further devices now, but the idea is not that a single person does this, especially if like Bertrand or others everybody has day jobs or sometimes multiple other projects to take care of. I mentioned the idea of archiving/retiring DeviceMap to the Portals team where at least device data should be of interest (possibly some of the Java code to read it) using the new User Agent feature of Portlet 3. Whether a project like Portlets could point to static content of an archived/retired DeviceMap similar to what e.g. it does with Jetspeed-1 for ages now, would be nice to clarify. To function after all a Portlet 3 demo would not even need a DeviceMap site. In its current form, the VM is of course required, also for the VB and C# clients btw. Not sure, if you resigned effective as of today, or plan to do so in the very near future? If a final release of Java and .NET clients taking device data also from a remote maven repository could be done, that would make both the site and VM irrelevant. And allow e.g. some GitHub or Pluto/Portlet 3 demo project to tap into the existing device data (not very recent but functioning, for a RI IMHO that could be more than enough) I asked the people behind OpenDDR what they think of the situation and if they were willing and able to pick up the relevant parts of the projects. Will have to see what they say. Regards, Werner >From >dev-return-2907-apmail-devicemap-dev-archive=devicemap.apache....@devicemap.apache.org Thu Aug 18 10:15:10 2016 Return-Path: <dev-return-2907-apmail-devicemap-dev-archive=devicemap.apache....@devicemap.apache.org> X-Original-To: apmail-devicemap-dev-arch...@www.apache.org Delivered-To: apmail-devicemap-dev-arch...@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 744BF19BF9 for <apmail-devicemap-dev-arch...@www.apache.org>; Thu, 18 Aug 2016 10:15:10 +0000 (UTC) Received: (qmail 33517 invoked by uid 500); 18 Aug 2016 10:15:10 -0000 Delivered-To: apmail-devicemap-dev-arch...@devicemap.apache.org Received: (qmail 33477 invoked by uid 500); 18 Aug 2016 10:15:10 -0000 Mailing-List: contact dev-h...@devicemap.apache.org; run by ezmlm Precedence: bulk List-Help: <mailto:dev-h...@devicemap.apache.org> List-Unsubscribe: <mailto:dev-unsubscr...@devicemap.apache.org> List-Post: <mailto:dev@devicemap.apache.org> List-Id: <dev.devicemap.apache.org> Reply-To: dev@devicemap.apache.org Delivered-To: mailing list dev@devicemap.apache.org Received: (qmail 33466 invoked by uid 99); 18 Aug 2016 10:15:10 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Aug 2016 10:15:10 +0000 Received: from mail-wm0-f51.google.com (mail-wm0-f51.google.com [74.125.82.51]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id C6FBA1A0118 for <dev@devicemap.apache.org>; Thu, 18 Aug 2016 10:15:09 +0000 (UTC) Received: by mail-wm0-f51.google.com with SMTP id i5so24748372wmg.0 for <dev@devicemap.apache.org>; Thu, 18 Aug 2016 03:15:09 -0700 (PDT) X-Gm-Message-State: AEkooutQJtTIlR1m4i/b0QktGVDyBlzgiAxxBYx72NOKPa9fi684i+MFCMylazgwkfJC339EWIlY5pdeJY+96Q== X-Received: by 10.194.114.135 with SMTP id jg7mr1459036wjb.166.1471515308244; Thu, 18 Aug 2016 03:15:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.152.146 with HTTP; Thu, 18 Aug 2016 03:15:07 -0700 (PDT) From: Bertrand Delacretaz <bdelacre...@apache.org> Date: Thu, 18 Aug 2016 12:15:07 +0200 X-Gmail-Original-Message-ID: <caewfvjm3mtsskpqk0m2c_j8fa4-hcruc9qsfenx6+mqpvga...@mail.gmail.com> Message-ID: <caewfvjm3mtsskpqk0m2c_j8fa4-hcruc9qsfenx6+mqpvga...@mail.gmail.com> Subject: Leaving the DeviceMap project and PMC To: dev@devicemap.apache.org Content-Type: text/plain; charset=UTF-8 Hi, I haven't done any coding in DeviceMap for a very long time, and I'm not planning to become active again - I stayed on the PMC mostly to help with community aspects when the project graduated, and there's not much happening in terms of community anyway. So I have decided to leave the PMC as well as resign from being a DeviceMap committer. This might mean having to shut down this project, as it currently has only 3 PMC members (including myself) which is the minimum for a viable ASF project. I don't think there's enough momentum anyway to have a successful ASF project, so it's probably better for whoever might want to do that to continue elsewhere. -Bertrand
