The following bugs are blocking the next Amarok release:
This search was scheduled by bcooks...@kde.org.
(1 bugs)
Bug 338541:
https://bugs.kde.org/show_bug.cgi?id=338541
Severity: crash
Priority: NOR
Platform: Other
Assignee: amarok-bugs-d...@kde.org
Status: UNCONFIRM
Hello Nitul,
Seems like you forgot to "reply to all" (as amarok-devel was not in your
recipients).
On Tue, Oct 28, 2014 at 12:37 AM, Nitul Datt wrote:
> On 10/27/14, vedant agarwala wrote:
> > Hello Nitul,
> >
> > I agree with all that Myriam has said. I should've waited for a go-ahead
> > for
Hello Harshal,
I am already mentoring one student for SoK this year.
I have cc'ed this mail to the Amarok-devel mailing list so if you are
lucky, someone else might be willing to mentor.
Also, please adhere to the general guidelines of posting in public mailing
lists and start hanging out on the
Hello Nitul,
I agree with all that Myriam has said. I should've waited for a go-ahead
for a senior Amarok member; if you remember I had mentioned that I was
unable to get in touch with them. Sorry for rushing in and making you do
some extra work.
Take your time and pick a new project from the 2 m
Hi Nitul,
Thanks for your proposal, but I have some doubts about this.
On Mon, Oct 27, 2014 at 8:47 AM, Nitul Datt wrote:
> Hi!
One thing which springs to mind is, suppose a user
> wants to store a custom cover. Should that also be stored in the
> filesystem mentioned in the specification or sho
Hi!
Please have a look at the first draft of my proposal for SoK [1]. I'd
like your comments and pointers on how it con be improved, especially
the timeline. I'd also like to know if I've missed anything from the
technical aspect. One thing which springs to mind is, suppose a user
wants to store a
