[Ovmsdev] How can I help

[Michael Balzer]

Robert,

thanks for joining and offering help on the documentation & support side.

Before beginning to work on improvements please first make sure you're up to date on existing features, documents and issues. These are the channels to know:

  * this mailing list: http://lists.openvehicles.com/pipermail/ovmsdev/
  * the github issues/todo list: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues (+ iOS & Android app repositories)
      o + https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/knownissues.txt
      o + https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/todo.txt
  * the git log: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commits/master
      o + https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/changes.txt
  * the openvehicles.com site:
      o Forum: https://www.openvehicles.com/forum
      o Support area: https://www.openvehicles.com/support/openvehicles
  * the user guide: https://docs.google.com/document/d/16JrXR7rybp-18DrEoeh1rg6GqQT_jVBvhaXh2oEWRHw/edit
  * the developer guide: https://docs.google.com/document/d/1q5M9Lb5jzQhJzPMnkMKwy4Es5YK12ACQejX_NWEixr0/edit


Noone I know of is currently focused on documentation / public presentation, and we can use some help there. The repository readme certainly could have an
update, it's still the v1 readme. There is no "formal" roadmap, as there is noone keeping books of ideas and todos. We're also rather building a city than a road.

Some beginner tutorial would be nice. That should come from real beginner questions & issues using the current version -- note most issues in the support area
were related to earlier versions. It seems the current version is already quite easy to use, first questions tend to become more specific now.

Regards,
Michael


Am 03.08.2018 um 10:01 schrieb Robert Sharpe (Electric Vehicle Consultant):
> 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
>
> <http://www.linkedin.com/in/arsharpe> <http://www.twitter.com/EgcTechnical> <https://www.facebook.com/EvergreenConsultingLtd> <http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html> <http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
>
>   <http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
>
> /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

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180805/8cdfefde/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.gif
Type: image/gif
Size: 1452 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180805/8cdfefde/attachment-0010.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2.gif
Type: image/gif
Size: 1441 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180805/8cdfefde/attachment-0011.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3.gif
Type: image/gif
Size: 1421 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180805/8cdfefde/attachment-0012.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 4.gif
Type: image/gif
Size: 1457 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180805/8cdfefde/attachment-0013.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 5.gif
Type: image/gif
Size: 1191 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180805/8cdfefde/attachment-0014.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 6.png
Type: image/png
Size: 10590 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180805/8cdfefde/attachment-0002.png>