RFC: Amarok 2.0 deadline September, 1

[Dan Meltzer]

On 6/12/08, Alejandro Wainzinger <aikawarazuni at gmail.com> wrote:
> On Thu, Jun 12, 2008 at 7:46 AM, Maximilian Kossick
>
> <maximilian.kossick at googlemail.com> wrote:
>
> > way to many crucial tasks imo.
>  > tasks that can be downgraded:
>  > -all other media devices - unlikely that we'll have support for all
>  > media devices again, but we'll be take all we can get
>
>
> I'll be doing mtp devices, not just ipods.
>
>
>  > -service framework
>  > -service - both are the most polished part of A2 at the moment.
>  >
>  > new tasks:
>  > -generic media device : crucial
>
>
> Agreed, but from what I hear this is going to be hell.  I'm confident
>  I can get something reasonably usable, but generics are currently at
>  the end of my todo list.  I can work on that instead of MTP in light
>  of this release schedule idea though, to make it on time.

I think the simplest way to handle generic media devices as
collections would be to genericify the sqlcollection code and use
amarokcollectionscanner + a prefixed set of tables in the database to
show data.  The trick would be translating that properly into an
on-disk layout when music gets synced.
>
>
>  >
>  > please note that these priorities only apply to core developers imo.
>  > All SoC students are (obviously) completely free to work on their
>  > projects.
>
>
> I guess in my case being that the things my project has to do are
>  _critical_ I think it's safe to say this doesn't apply to me?  =p
>
>
>  >
>  > btw, organize to collection is done, could somebody adjust the status?
>  >
>  > max
>  >
>  > On Thu, Jun 12, 2008 at 4:21 PM, Harald Sitter <sitter.harald at gmail.com> wrote:
>  >> On Thu, Jun 12, 2008 at 3:49 PM, Leo Franchi <lfranchi at gmail.com> wrote:
>  >>> We do already have the wiki page with ranked features etc, but maybe
>  >>> if we just clean it up and define EXACTLY what we want working before
>  >>> release, we can make some more progress.
>  >>
>  >> http://amarok.kde.org/wiki/Amarok2_Progress
>  >>
>  >> new status crucial: needs to be done for 2.0
>  >>
>  >> please update/add/propose for delay until 2.0.1/2.1
>  >> _______________________________________________
>  >> Amarok-devel mailing list
>  >> Amarok-devel at kde.org
>  >> https://mail.kde.org/mailman/listinfo/amarok-devel
>  >>
>  > _______________________________________________
>  > Amarok-devel mailing list
>  > Amarok-devel at kde.org
>  > https://mail.kde.org/mailman/listinfo/amarok-devel
>  >
>  _______________________________________________
>  Amarok-devel mailing list
>  Amarok-devel at kde.org
>  https://mail.kde.org/mailman/listinfo/amarok-devel
>