[PLEASE VOTE] so what should we be working on

[Jeroen Massar]

On 2016-05-28 23:37, Dirk Hohndel wrote:
[..]
> So what should we be working on...? Should we...
> 
> (1) just shut this down and move on?

Definite no.

> (2) move things to maintenance mode,

4.5 could be in maint IMHO.
With 4.6 being the 'fix dive site management' edition.

> abandon Subsurface-mobile,

While it definitely needs improvements, we just have to make the list
and attack the various problems, one at a time.

> fix bugs in Subsurface whenever we find time but otherwise declare
victory?

I think 4.5 is in a good state; but improvements likely should be called
4.6.

> It won't be too painful to track libdicecomputer and keep making 4.5.x
> releases for a while, I guess...

Tracking libdc for 4.x is a good way to go.

> (3) focus on Subsurface-mobile, release the iOS version,
> update the Android version and see if there is a single person
> besides me who is willing to invest time into that?

As I note below, I'll be heavily focusing on the bluetooth
libdc<->mobile downloader tool. Got iphone/ipad here, don't have android
ready, but one platform at a time is a good start.

> (4) focus on Subsurface 4.6, fix the dive site management and create a
list of
> prioritized features that we want to get in place?

Yes, sounds like a good plan. Depending on size of the feature, it might
go to 5.x.

> (5) focus on Subsurface 5.0, write a completely new UI and abandon
> what we have in 4.5?

4.5 should remain, it works from what I have been playing with now.
As you note for 4)

Planning possible improvements that might become 5.0 in for example
mspaint/gimp/powerpoint style diagramming/design of layouts etc would be
a good idea. A UI overhaul would definitely be a 5.x thing.

> If your vote is for 3, 4, or 5 I assume that you are volunteering to
> carry some of the work that is needed to get there. If you don't
> vote, I will count that as a vote for 1.

Definitely volunteering to commit code! :)
Will get to that when I am back from this trip and do not have 300ms+++
latency, or let alone, a full day of dives :)

Will be at first focusing on the bluetooth libdc<->mobile downloader
that we can then deploy on the CHIPs.

Greets from .mv,
 Jeroen