[Ovmsdev] How can I help

[Robert Sharpe (Electric Vehicle Consultant)]

Hi Mark/All, Sometime ago I did lots of obvious updates of the User Manual to help readability, etc as a first stab. Now doing a second stab, there is one thing that has come to light and that is the definition of a user. In order to check the documentation I need to know what the user is capable of off.  I appreciate that the definition of user has probably changed over the development of the project and the product has matured enough that it can be operated by non-technical users opening up its usefulness.   Assuming that what were the original users would how fall into the category of Developers, does the following draft specification accurately reflect the minimum capabilities of a current/future User? User Definition a general household DIY capable person. can mount and plug things into the vehicle cant create connectors/leads modify the OVMS hardware don't know about internal or technical terms, such as Nissan Leaf GIDs, WiFi SSID, etc User Expectations the unit fully supports the listed features under all reasonable conditions reliable in operation error messages are non-technical and help the user solve the problem should be plug-n-play where possible, eg automatically detects vehicle type and year automatically detects battery capacity, etc Please let me know if this is accurate or what changes/clarifications need to be made. Rob --- On Tue, 07 Aug 2018 03:30:33 +0100 Mark Webb-Johnson <mark at webb-johnson.net> wrote ---- Robert, Thanks for the offer to help out. Perhaps you can look at it from the user’s point of view, and try to improve our documentation and approach for that? Regards, Mark. On 3 Aug 2018, at 4:01 PM, Robert Sharpe (Electric Vehicle Consultant) <robert.sharpe at evergreen-consulting.co.uk> wrote: Hi All, I like where OVMS project is going and would like to help if I can. Where I can possibly add value is make things easy for people to use (eg documentation, etc) experienced on UI/UX design, etc. as an ex developer, good at testing and finding problems. Some initial thoughts on activities are to make it easier for non technical people to use OVMS, help doc author pull out user only specific content to a user manual and make it non-technical (renaming current user manual to developers manual) to help people see roadmap, provide a mechanism to see who wants what and who is working on it. to allow developers and users to display problems with their vehicle only, add Labels to the github issues list or group by project (I am not an expert on GITHUB so please be patient) update GITHUB readmes to better direct people that find GITHUB first. Please let me know if anyone is dealing with any of these areas add and/or vote for what things you think I can help with by putting a comment next to the activity above. Regards, Robert Sharpe Electric Vehicle Consultant 07711 252971 <1.gif> <2.gif> <3.gif> <4.gif> <5.gif> <6.png>  Your Plugged-in Partner Evergreen Consulting is the trading name of Sharpe Consultants Ltd _______________________________________________ OvmsDev mailing list OvmsDev at lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev at lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20190103/b52dd10c/attachment-0001.html>