Bertrand,

Thanks for the update. While I haven't claimed my actual committer user, I
remained active sometimes by helping others in the mailing list to add
their ideas. Some of them if they are happy to contribute really should
consider joining, also with code commit rights.

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. 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.

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.

Regards,
Werner

On Tue, Apr 9, 2013 at 11:51 AM, Bertrand Delacretaz <[email protected]
> wrote:

> Hi,
>
> On Mon, Apr 8, 2013 at 4:56 PM, Andrew Savory <[email protected]> wrote:
> > ...The report is (over)due but I don't have time – would one of the
> other devs
> > care to take a shot at it?...
>
> I've added the below report at
> http://wiki.apache.org/incubator/April2013 - if someone wants changes
> please say so soon!
>
> -Bertrand
>
>
> It looks like DeviceMap needs to be rebooted - there's almost zero
> activity from the initial committers, but a few people have proposed
> contributions that could help restart with a mostly new set of
> committers (without kicking existing ones out of course - they're
> welcome to be more active if they're willing and able).
>
> Two committer/PPMC elections are pending, and with two active mentors
> this can provide the embryo of a new community.
>
> The podling could be considered a failure at this point, but giving it
> another chance does no harm, so we recommend trying that.
>

Reply via email to