Amarok/Development/RoadMap: Difference between revisions

From KDE Community Wiki
m (Mamarok moved page Amarok/Development/Randa2012/Roadmap to Amarok/Development/RoadMap: move to current)
 
(8 intermediate revisions by 2 users not shown)
Line 23: Line 23:
These changes are to improve likeback as a team tool. The alternative is complete removal, but we feel it can be very useful.
These changes are to improve likeback as a team tool. The alternative is complete removal, but we feel it can be very useful.
=== Fix dialog layout ===
=== Fix dialog layout ===
It's not properly resizing. This is usually fixed by using the UI file more/properly.
<strike>It's not properly resizing. This is usually fixed by using the UI file more/properly.</strike>
''Should be fairly trivial but tedious, likely just playing with QBoxLayout margins, size policies and stretch factors.''
<strike>''Should be fairly trivial but tedious, likely just playing with QBoxLayout margins, size policies and stretch factors.''</strike>
 
Done.


=== Send comments to forums ===
=== Send comments to forums ===
The user forums is a much better place to handle these. They are properly monitored and admined.
The user forums is a much better place to handle these. They are properly monitored and admined.
''What's easy enough is have the "Feature request" button open the forums in the browser. Anything else, involving posting messages to the forums directly from Amarok, would require considerably more time.''
=== Remove comment fields from like and dislike ===
=== Remove comment fields from like and dislike ===
People keep using it for support request, remove the temptation. Could be replaced by radio button group with fixed choises
People keep using it for support request, remove the temptation. Could be replaced by radio button group with fixed choises
''As soon as we know which choices, this is quite easy and quick to do, a day or two tops.''
=== Generate statistics for amarok-devel ===
=== Generate statistics for amarok-devel ===
Since we mention it's only to be used for statistical purposes, let's use it that way. There should be summery mail send to [email protected] every week.
Since we mention it's only to be used for statistical purposes, let's use it that way. There should be summery mail send to [email protected] every week.
''Someone who knows a bit of PHP should do this.''


== Organize Dialog ==
== Organize Dialog ==
Line 62: Line 73:
== Git user test team organization ==
== Git user test team organization ==
''Myriam'': ? days
''Myriam'': ? days
Blogged about already: [http://blogs.fsfe.org/myriam/2012/09/25/more-randa-2012-goodness/ More Randa 2012 goodness]


== Directory Structure & CMake targets ==
== Directory Structure & CMake targets ==

Latest revision as of 17:20, 14 January 2013

TODO

Meta System Rewrite

Step 1: prevent circular dependencies

Matêj: 5 days

Step 2: Simplify Compilation: Genre, Label, ...

Matêj: ? days

Step 3: Multi-label, -genre, -trackArtist

Matêj: ? days

Playback::{Queue, Controller}

Basic functionality and simple QML based UI

Bart: 15 days

Dynamic Playlist refactor to Meta::Playlist and Queue

Ralf: ? days

Feature compatible with 2.6 The::Playlist

Team: ? days

KPlugin -> QPlugin

Mark: 2 days

Likeback improvements

These changes are to improve likeback as a team tool. The alternative is complete removal, but we feel it can be very useful.

Fix dialog layout

It's not properly resizing. This is usually fixed by using the UI file more/properly.

Should be fairly trivial but tedious, likely just playing with QBoxLayout margins, size policies and stretch factors.

Done.

Send comments to forums

The user forums is a much better place to handle these. They are properly monitored and admined.

What's easy enough is have the "Feature request" button open the forums in the browser. Anything else, involving posting messages to the forums directly from Amarok, would require considerably more time.

Remove comment fields from like and dislike

People keep using it for support request, remove the temptation. Could be replaced by radio button group with fixed choises

As soon as we know which choices, this is quite easy and quick to do, a day or two tops.

Generate statistics for amarok-devel

Since we mention it's only to be used for statistical purposes, let's use it that way. There should be summery mail send to [email protected] every week.

Someone who knows a bit of PHP should do this.

Organize Dialog

Refactor

Ralf: ? days

With extra preset dialog

Ralf: 2 days

Export playlist from PlaylistFileProvider

Ralf: 3 days

Services

Basics, desktop UI

Bart: ? days

Cool stream refactor as simple test case

Mark: ? days

GPodder refactor as complex test case

Lucas: 2 weeks

Ampache & ownCloud Service

Lucas: 3 weeks

CollectionManager Refactor

Slim Down (- ServiceCollection and assoc. mess)

Matêj: ? days

Move into core

Matêj: ? days

Individual Services/Collections

Matêj: ? days

Git user test team organization

Myriam: ? days

Blogged about already: More Randa 2012 goodness

Directory Structure & CMake targets

Team (lead by Mark and Matêj: ? days

PopUpDropper simplification & UI tweaks

Mark: ? days

Release Planning

2.7: GSoC projects

Statistics is ready to go in, Spotify and Nepomuk need some polish, tomahawk is unknown, QML is not supposed for immediate inclusion.

2.8: MTP, core code improvements & bugfixes

2.9: Last feature release of 2.x series

2.95: Amarok 3 tech preview: PlaybackQueue

2.96: Amarok 3 tech preview: QMLified browsers

2.97: alpha of Amarok 3

2.98: Beta 1 of Amarok 3

2.99: Beta 2 of Amarok 3

Amarok 3

Bugfixes to Amarok 2 continue