Hi all,
>To solve this I think three very central question need to be answered >very
>precisely before doing anything else. > >1. How many people will actively
>commit to working on this as their >*main* project? >2. What does the primary
>target audience of Plasma even need? >3. What do the contributors want to
>actually have in the end >understanding their own time constraints?I'm
>committed to work on this as main. I've been swimming in the bangarang
>codebase and so far we're almost rewriting the entire thing. From my
>perspective, porting is near rewrite, so it's better to have a good design and
>vision from the start. Might I suggest that we simply have a survey of what
>our users (plasma or general) want from a music player instead of relying on
>personas. It seems a bit naive to assume we only have casual users and power
>users. Feedback from actual users is more concrete than anything persona we
>can invent. FWIW I want a music player that plays music and supports playlists
>and media info, I'm not likely to use other features much.
------------------
_______________________________________________
Amarok-devel mailing list
Amarok-devel@kde.org
https://mail.kde.org/mailman/listinfo/amarok-devel