On 9 Apr 2013, at 12:12, Bertrand Delacretaz wrote:

> Hi Werner,
> 
> On Tue, Apr 9, 2013 at 12:10 PM, Werner Keil <[email protected]> wrote:
>> ...While I haven't claimed my actual committer user, I
>> remained active sometimes by helping others in the mailing list to add
>> their ideas...
> 
> Absolutely, thanks for that - I think that makes you and me the only
> initial committers (http://incubator.apache.org/devicemap/team.html)
> who have been recently active.
> 
> I'm not blaming people, life happens...but it's good if we can find a
> way to go forward by inviting others.

Indeed. And on that note... I must admit haven't really contributed much to 
date, but I'm definitely up for performing due diligence when the project is 
ready to make its first releases. 

> 
>> ....Some of them if they are happy to contribute really should
>> consider joining, also with code commit rights....
> 
> Yes - we're currently discussing this on the private list (as is usual
> for discussions about people), hoping to have some announcements very
> soon.
> 
>> 
>> ... OpenDDR released a 1.16 release also of the resources definition, so 
>> except
>> for the C# "balloon" that has not seen much activity over the last months,
>> both device definitions and where necessary the Java API are maintained in
>> almost monthly intervals...
> 
> My understanding was that this maintenance would happen here, after
> the DMAP-11 donation, but as you say:
> 
>> ...Unless we succeed to define a working way of
>> updating these kinds of things here, too, ideally in a semi- or fully
>> automated way, these changes may not always be applicable to DeviceMap, not
>> to mention possible IP or licensing requirements....
> 
> Ok, so we need to work towards that.
> 
>> ...If other OpenDDR committers here are too busy, I'd be happy to help trying
>> to sync device definitions, but there may be still one or two basic things
>> we should get in place first. Those offering to help may speed things up a
>> bit...
> 
> sounds good!
> 
> -Bertrand

Attachment: PGP.sig
Description: This is a digitally signed message part

Reply via email to