[Ovmsdev] Roadmap and team info

[Mark Webb-Johnson]

Robert,

I think that the roadmap part of this duplicates the github issues.

https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues>
https://github.com/openvehicles/Open-Vehicle-Android/issues <https://github.com/openvehicles/Open-Vehicle-Android/issues>
https://github.com/openvehicles/Open-Vehicle-iOS/issues <https://github.com/openvehicles/Open-Vehicle-iOS/issues>

By properly labelling, we can see enhancement request there and separate them from bugs.

There is also a todo

https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/todo.txt <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/todo.txt>

and knownissues

https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/knownissues.txt <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/knownissues.txt>

which at this point could all probably be merged into that.

I realise that github is not the most user friendly for novice users. Perhaps we can pull from it, to maintain a user-visible list? The primary issues with roadmaps / enhancements for a project like this is that there are far more people adding issues to the list, than doing the work to remove them, so it becomes kind of demoralising.

The ‘team’ tab is useful, and it would be good to publicly credit contributors in a better way. Perhaps for vehicle module contributors that can be in the individual vehicle sections of the user guide, and for main code contributors, it an be in the main intro section of the user guide?

Regards, Mark.

> On 13 Aug 2018, at 3:56 PM, Robert Sharpe (Electric Vehicle Consultant) <robert.sharpe at evergreen-consulting.co.uk> wrote:
> 
> Hi,
> 
> In response to a request for a road map there is now an easy to use Google Sheet <http://bit.ly/2B5yCwf> where people can see the current road map, share what you are doing and what future features you would like to see.
> 
> While doing that it's also a good opportunity to help new comers by pulling together a summary of the team and any (non feature) tasks people might be working on.
> 
> Can you please therefore take a few minutes of your time in the next few days to fill in all three sheets below 
> 
> <1.png> <http://bit.ly/2B5yCwf>
> 
> 
> Thanks,
> Robert Sharpe
> Electric Vehicle Consultant
> 07711 252971
> 
> <2.gif> <http://www.linkedin.com/in/arsharpe> <3.gif> <http://www.twitter.com/EgcTechnical> <4.gif> <https://www.facebook.com/EvergreenConsultingLtd> <5.gif> <http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html> <6.gif> <http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
> <7.png>  <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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180814/6786aa83/attachment.htm>