Development timeline + milestone update/reorganisation

@david-sabata I think we could use issue milestones to better effect, as they’ve been under-employed so far.

I’m sure you have precise feature ideas, and more abstract ambitions about how you see the extension developing in the coming months and years; I’m sure those of us who contribute also have thoughts in the same vein.

There are loads of awesome things we could do with this project, and it’d be great to see everyone’s thoughts and ideas shared with the world in writing.

With them assigned to milestones, they could give a focus and direction to feature development; recently we’ve seen contributors binge-fixing open issues, but I’m sure they’d equally be up to the challenge of building out new features that have been discussed and planned.

If nothing else, I think updating the milestones could galvanise discussion about how to improve the extension.

Proposed Project Timeline:

We should start using Semantic Versioning - the extension offers a few key APIs for contributors to work with (e.g. BaseConnector, Song, BaseScrobbler coming soon…)

• v2.0.0 - _Operation CONSOLIDATE: Standardised. Documented. Tested._
  • Port all connectors to ‘v2’ Connector API ( #781 )
  • Full implementation of v2 API methods, where available:
    • Check album (#576) [50 of 97]
    • Check current time [20 of 97]
    • Check art (#778) [49 of 97]
    • Check duration [15 of 97]
    • Check uniqueid [13 of 97]
  • Build testing suite:
    • /core/ unit tests ( #235 )
    • /connectors/ browser testing ( #779 )
  • Update dev dependencies:
  • Fully document code in /core/
  • Update Github wiki ( #102 )
• v2.1.0+ - _Operation INFORM: Transparent. Intuitive. Convenient._
  • Improve UX for errors:
    • authorisation errors - catch errors, suggest reauth’ing, make it more reliable, etc. ( #758, #796 )
    • connector errors - catch errors, suggest refreshes, etc. ( #757 )
  • Notify users of site-native scrobble functionality
  • Implement chrome.storage ( #647 )
    • Sync extension settings/authorisation
    • View/edit scrobble history ( #211, #265, #291 )
  • More granular options/config
    • Move popup to browserAction, leave pageAction for connector-specific options UI (#776)
    • Clear out notifications ( #467 )
    • Options for notification info & buttons ( #776 )

[janbaykara]

I don’t know if we need to worry too much about the way we manage discussion - I think what we really need is to actually do the discussing. I’m definitely a fan of keeping things simple…

[galeksandrp]

looks like v2 discussion in #781. It not be early merged without any test.