<div><div class="gmail_quote">On Tue, Feb 9, 2010 at 1:37 PM, Seb Ruiz <span dir="ltr"><<a href="mailto:ruiz@kde.org">ruiz@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 9 February 2010 23:16, Milot Shala <<a href="mailto:milot.shala@gmail.com">milot.shala@gmail.com</a>> wrote:<br>
> Hi there,<br>
> I would like to add something to this topic.<br>
> Amarok has great features inside I don't think that they should be removed,<br>
> but I suggest that the developers should be more concentrated on stabilizing<br>
> the code, fixing bugs and/or refactoring the code rather than adding new<br>
> features to it.<br>
> I am new to the community but long time Amarok user, from my software<br>
> engineering expertise for several years Amarok can be a feature-bloated<br>
> software that users will not know what's inside anymore and several of them<br>
> will even not bother using it anymore because with more features users will<br>
> pay the cost during the usage of Amarok.<br>
> Before adding a feature I think it is a good idea to think hard about a<br>
> specific feature and making some surveys.<br>
> Again, I am new to the community and I don't know how you guys handled this<br>
> part until now, but this is my opinion, if I am wrong feel free to correct<br>
> me.<br>
> Sincerely,<br>
> Milot<br>
<br>
<br>
</div>Hi Milot,<br>
In these situations it is not always a case of who is right and who is<br>
wrong :) Each development team assesses possible features differently<br>
to the next (some more than others of course). In Amarok, core<br>
developers are usually left to their discretion when implementing<br>
features, but will often be subject to discussions or criticism if<br>
there are thoughts of inappropriate features or potentially better<br>
implementation methods (as you might have seen around here). Of course<br>
stablising the code base is an important and noble goal for any<br>
software project, but it is also worth noting that as a volunteer<br>
project, it is hard to force someone to do the dirty ugly work.<br>
<br>
The only thing we know for certain is that top quoting emails is poor form :)<br>
<font color="#888888"><br>
Seb<br></font></blockquote><div><br></div><div>Dear Seb,<div><br></div><div>Yes you are right, but I wasn't telling anyone that is right or wrong, just gave my opinion regarding the nice article that Mark pointed here and what I feel that we should be aware of what was written there, but not removing any of the features because as we all know, Amarok is a great music player and I am happy for using for so many years and joined here to help developing it more :D</div>
<div><br></div><div>Sorry for top quoting my email, gmail automatically does that :)</div></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><font color="#888888">
</font><div><div></div><div class="h5"><br>
> On Tue, Feb 9, 2010 at 12:28 PM, Nikolaj Hald Nielsen<br>
> <<a href="mailto:nhnfreespirit@gmail.com">nhnfreespirit@gmail.com</a>> wrote:<br>
>><br>
>> Personally, I agree that here are quite a few features that could be<br>
>> removed from Amarok.<br>
>><br>
>> BUT, the thing is, my list of features that are "bloat" are likely<br>
>> different from everyones elses. So if we removed all that parts of<br>
>> Amarok that someone does not use, there likely would be very little<br>
>> left at all ;-)<br>
>><br>
>> This is not an argument for blindly adding everything that someone<br>
>> wants, but since the perfect music player is different for anyone,<br>
>> some common ground has to be found.<br>
>><br>
>> - Nikolaj<br>
>><br>
>> On Tue, Feb 9, 2010 at 12:13 PM, Nathan Sala <<a href="mailto:sala.nathan@gmail.com">sala.nathan@gmail.com</a>><br>
>> wrote:<br>
>> > In my user opinion, Amarok doesn't currently embed "useless" or "out of<br>
>> > the<br>
>> > pool" features. But I must admit I probably don't know everything.<br>
>> ><br>
>> > Could you please let us know what are these features you consider to be<br>
>> > overweight?<br>
>> > It could be interesting to know it for next moves.<br>
>> ><br>
>> ><br>
>> > 2010/2/9 Mark Kretschmann <<a href="mailto:kretschmann@kde.org">kretschmann@kde.org</a>><br>
>> >><br>
>> >> On Tue, Feb 9, 2010 at 11:39 AM, Nathan Sala <<a href="mailto:sala.nathan@gmail.com">sala.nathan@gmail.com</a>><br>
>> >> wrote:<br>
>> >> > Do you mean you would like to delete some features form Amarok? :=)<br>
>> >><br>
>> >> Not necessarily. Although, to be really honest: Yes.<br>
>> >><br>
>> >> What I find more important though: Watching out that we don't add even<br>
>> >> more obscure features to it. Once you have added them, it's difficult<br>
>> >> to remove them, due to user outrage (we've had that happen many<br>
>> >> times).<br>
>> >><br>
>> >> --<br>
>> >> Mark Kretschmann<br>
>> >> Amarok Developer, Software Engineer at Collabora Ltd<br>
>> >> Fellow of the Free Software Foundation Europe<br>
>> >> <a href="http://amarok.kde.org" target="_blank">http://amarok.kde.org</a> - <a href="http://www.fsfe.org" target="_blank">http://www.fsfe.org</a> - <a href="http://collabora.co.uk" target="_blank">http://collabora.co.uk</a><br>
>> >> _______________________________________________<br>
>> >> Amarok-devel mailing list<br>
>> >> <a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br>
>> >> <a href="https://mail.kde.org/mailman/listinfo/amarok-devel" target="_blank">https://mail.kde.org/mailman/listinfo/amarok-devel</a><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Amarok-devel mailing list<br>
>> > <a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br>
>> > <a href="https://mail.kde.org/mailman/listinfo/amarok-devel" target="_blank">https://mail.kde.org/mailman/listinfo/amarok-devel</a><br>
>> ><br>
>> ><br>
>> _______________________________________________<br>
>> Amarok-devel mailing list<br>
>> <a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br>
>> <a href="https://mail.kde.org/mailman/listinfo/amarok-devel" target="_blank">https://mail.kde.org/mailman/listinfo/amarok-devel</a><br>
><br>
><br>
><br>
> --<br>
> Milot Shala, Software Engineer<br>
> <a href="http://www.spartansoft.org" target="_blank">www.spartansoft.org</a> | <a href="mailto:m.shala@spartansoft.org">m.shala@spartansoft.org</a><br>
><br>
> _______________________________________________<br>
> Amarok-devel mailing list<br>
> <a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/amarok-devel" target="_blank">https://mail.kde.org/mailman/listinfo/amarok-devel</a><br>
><br>
><br>
<br>
<br>
<br>
</div></div><div class="im">--<br>
Seb Ruiz<br>
<br>
<a href="http://www.sebruiz.net/" target="_blank">http://www.sebruiz.net/</a><br>
<a href="http://amarok.kde.org/" target="_blank">http://amarok.kde.org/</a><br>
_______________________________________________<br>
</div><div><div></div><div class="h5">Amarok-devel mailing list<br>
<a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/amarok-devel" target="_blank">https://mail.kde.org/mailman/listinfo/amarok-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Milot Shala, Software Engineer<br><a href="http://www.spartansoft.org">www.spartansoft.org</a> | <a href="mailto:m.shala@spartansoft.org">m.shala@spartansoft.org</a><br>
</div>