[Ovmsdev] Zoe Compatibility PR #160?
Wolfgang Jenne
wolfi at spider.li
Mon Sep 16 05:46:12 HKT 2019
Hi,
I have to apologize. I might be able to pick up the work this fall. As it looks now, It could happen in 2 months or so, currently no chance. Therefore, I am happy if you take what is best and include it into the release. When ever someone (me or anyone else) has time it can be continued.
thanks,
Wolfgang
========================
Wolfgang Jenne
Spider Webmanufaktur GmbH
Rotenbodenstrasse 60
9497 Triesenberg
+41 78 672 00 14
http://www.spider.li
> Am 15.09.2019 um 22:59 schrieb Michael Balzer <dexter at expeedo.de>:
>
> It seems both Zoe developers have abandoned working on this and there's no change in sight.
>
> Both had signaled cooperating on merging the features, then Marco went offline. Some months later Wolfgang said he may take on the work some day, but he didn't
> come back on this.
>
> I second merging Marcos PR. Having some support is better than none. It seems few developers actually buy Zoes, but maybe adding the basic support motivates
> someone to improve on it.
>
> Any objections to including this in the 3.2.003 release?
>
> Regards,
> Michael
>
>
> Am 15.09.19 um 19:42 schrieb Glyn Hudson:
>> Hi,
>>
>> Does anyone know the latest status of Zoe compatibility, in particular
>> this PR by mmezog
>> https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/160
>>
>> I gather reading the PR comments that Michael was keen to wait for
>> Wolfgang to create a PR with more advanced Zoe support. However, this
>> was almost a year ago and Wolfgang has not responded. If mmezog code
>> is functional would it not be a good idea to merge this PR then at
>> least basic Zoe functionality would be available? It doesn't look like
>> Wolfgang is activity developing, his V3 repo fork has not been updated
>> since Jan 2018.
>>
>
> --
> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20190915/7207e1f2/attachment.htm>
More information about the OvmsDev
mailing list