[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-release-team
Subject: Re: Exception for Dolphin - KFileMetadataWidget
From: Vishesh Handa <me () vhanda ! in>
Date: 2012-12-22 9:56:24
Message-ID: CAOPTMKADsk9UcoGyFwNQOebfun0DUtxMDftM5_NDaL5YWU6h+g () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Sat, Dec 22, 2012 at 3:07 PM, Frank Reininghaus <frank78ac@googlemail.com
> wrote:
> If many people thought that the benefits of the new widget outweigh
> the risks, I would say "let's merge it" - I don't want to be blamed by
> future users of KDE 4.10 for holding back useful things if there is no
> good reason for it. But at the moment, it seems that there are more
> people who are worried about the risks, so I feel that it should
> better wait until KDE 4.11.
>
From what I have noticed most people just don't respond, and that is taken
as a sign of acceptance. So one cannot really infer that there are more
people who are worried about the risks. Just that 2 people who disagree
have raised their voice.
Is there something I can do to reduce these risks?
From what I see there are 3 use cases -
1. Using it when Nepomuk enabled
2.1. Using it when Nepomuk is disabled
2.2. Using it when Nepomuk is enabled but the file has no meta-data
So, the concern of using the widget in unknown ways doesn't really come
into play.
I hope I'm not being rude. I just really really want to get this widget
into 4.10. Otherwise I'm going to have to spend 2-3 days (maybe even more?)
fixing up the old deprecated Nepomuk code and the KFileMetadataWidget. I
rather focus on other things.
--
Vishesh Handa
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Dec \
22, 2012 at 3:07 PM, Frank Reininghaus <span dir="ltr"><<a \
href="mailto:frank78ac@googlemail.com" \
target="_blank">frank78ac@googlemail.com</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div id=":wl">If many people thought that the benefits of the \
new widget outweigh<br> the risks, I would say "let's merge it" - I \
don't want to be blamed by<br> future users of KDE 4.10 for holding back useful \
things if there is no<br> good reason for it. But at the moment, it seems that there \
are more<br> people who are worried about the risks, so I feel that it should<br>
better wait until KDE 4.11.</div></blockquote><div><br></div><div>From what I have \
noticed most people just don't respond, and that is taken as a sign of \
acceptance. So one cannot really infer that there are more people who are worried \
about the risks. Just that 2 people who disagree have raised their voice. <br> \
</div></div><br></div><div class="gmail_extra">Is there something I can do to reduce \
these risks?<br><br></div><div class="gmail_extra">From what I see there are 3 use \
cases -<br><br></div><div class="gmail_extra">1. Using it when Nepomuk enabled<br> \
</div><div class="gmail_extra">2.1. Using it when Nepomuk is disabled<br></div><div \
class="gmail_extra">2.2. Using it when Nepomuk is enabled but the file has no \
meta-data<br></div><div class="gmail_extra"><br></div><div class="gmail_extra"> So, \
the concern of using the widget in unknown ways doesn't really come into \
play.<br><br></div><div class="gmail_extra">I hope I'm not being rude. I just \
really really want to get this widget into 4.10. Otherwise I'm going to have to \
spend 2-3 days (maybe even more?) fixing up the old deprecated Nepomuk code and the \
KFileMetadataWidget. I rather focus on other things.<br> <br></div><div \
class="gmail_extra">-- <br><span style="color:rgb(192,192,192)">Vishesh \
Handa</span><br> </div></div>
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic