Hello people
Random Idea: How about we close the k-c-d mailing list? It's main purpose used
to be to discuss kdelibs changes, but now since we have kde-frameworks, the
mailing list seems less useful. We already have kde-devel for other generic
kde stuff.
--
Vishesh Handa
I'll be closing all the Nepomuk bugs.
--
Vishesh Handa
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
the previews (still not ported to Plasma5)
It might be best for you to just written KRunner plugins, if you're
targeting Plasma 5. If you want to target KDE4, have a look at the milou
source code (milou/lib/sources/) and try copying and modifying any of the
existing sources to meet your needs.
--
Vishesh
Ping?
What's the status of this? I have a copy of Baloo on github, and I
have been thinking of creating a "KDE Baloo" organization (or KDE) so
that it is not under my name. I would obviously prefer an official
mirror instead of me updating it manually.
--
Vis
Hey
Do you think the "Semantic Desktop" forum could be removed? Unless,
I'm too late.
--
Vishesh Handa
On Sat, Sep 26, 2015 at 9:03 AM, Luca Beltrame <lbeltr...@kde.org> wrote:
> Hello,
>
> today we will start a forum structure reorganization that will hopefully
On Sat, Sep 26, 2015 at 4:01 PM, Luca Beltrame <lbeltr...@kde.org> wrote:
> Currently we're renaming it to "Desktop Search".
Perhaps "File Search"? Though I think I may have replied too late.
--
Vishesh Handa
___
k
owever, certain projects within the KDE
umberella can be willing to occasionally utilize non-free tools.
--
Vishesh Handa
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
anization. Using word such as "been fooled" seems to indicate some
kind of malice intent. If I didn't think this would help KDE I
certainly would not have sent over 30+ emails over the last 2 days.
How about you assume good intentions until proven otherwise?
--
Vishesh Handa
_
alarmed by how people are advocating their
principles for ALL kde projects without any scope for negotiations for
different projects. I fear that this will just drive people/projects
away from KDE.
--
Vishesh Handa
___
kde-community mailing list
kde-c
ovided.
It depends on our end goal: creating free software or creating free
software with only free tools? If it is the latter then I fear we have
already failed since many of us use additional tools to aid
development which are not free.
--
Vishesh Handa
___
d for the
next time. Ditto with bugs actually. I get reports via IRC, emails,
Google+ and even FB (once). If it is minor I act on it, if it isn't I
point the user towards bugzilla or just file a bug myself so that I
don't forget.
--
Vishesh Handa
___
kde
my use of gmail, please, I am deeply
> ashamed about it and apparently too lazy to change... but I will reuse
> Kmail again as soon as it stops eating my mail every time I filter
> something and when Akonadi stops filling up my hard disk and memory
> and... etc. etc. Promised!)
>
Ther
uct. They most
certainly are part of the "development process". Providing a Windows
version of Krita does force me to install these tools if I wish to
contribute to that part of Krita.
--
Vishesh Handa
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
; release.
Lets break this down -
* Consistency - It is still maintained, but there can be additional
sources as an exception. Just as some people could just directly email
you a patch. (It has certainly happened to me)
* Reporting Bugs in 2 places -
merge it, and not just
tell the person - here use this strange tool where you will need to
spend 10-15 extra minutes.
--
Vishesh Handa
[1] https://github.com/KDE/baloo
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
On Sat, Sep 19, 2015 at 11:44 AM, Luca Beltrame <lbeltr...@kde.org> wrote:
> Il Sat, 19 Sep 2015 11:30:39 +0200, Vishesh Handa ha scritto:
>
>
>> * There is nothing to do with selling your soul. Each of us has
>
> We have a Manifesto, and we should, ideally, strive to
his point in time, at least, I
> believe. I really hope that it will remain this way and KDE can be a
> good factor to challenge things with github with open alternatives.
And we should continue challenging them, however, just like we still
ship binar
correct.
I'm not advocating abandoning our own infrastructure or telling
contributors to use GitHub. Our documentation should always point
towards our own tools.
--
Vishesh Handa
___
kde-community mailing list
kde-community@kde.org
https://mail.
rt of your workflow. You should
> never ever look at it. It is simply an additional clone source, just
> like KDE's anongit servers. That's it.
This is the part of your email I really like. Though this is not what
you meant: If projectX choose to also use Github, it is not affecting
your pr
On Sat, Sep 19, 2015 at 4:37 PM, Boudhayan Gupta <bgu...@kde.org> wrote:
> On 19 September 2015 at 19:34, Vishesh Handa <m...@vhanda.in> wrote:
>> Please note that consistency isn't a requirement to be part of KDE. If
>> I decide to write an application in Rust
github.
> If the problem is somewhere in (a), where is it?
>
From what I understand, people are against some discussion or pull
requests being allowed at all. They should always be closed with a big
NO sign. I don't understand this or see the distinction betwe
d those through github.
We already use some other forms of code review -
* IRC
* Email
* IM
* Google+ Hangouts (Just discussed some things related to the Baloo
KCM a week ago)
* Knocking on David's door and screaming "I need you to look at some cod
control the direction of the project
and issues are discussed over there.
--
Vishesh Handa
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
to use a new service.
--
Vishesh Handa
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
de review discussions on IRC often lead
> to "please put this on ReviewBoard".
"often" but not always.
We have to be able to use our best judgement. If I get a patch on
gtihub and I think that should be discussed more, I'll probably send
t
, you can bring it up and then we can
deal with it. Dealing in extreme What-Ifs does not help this
discussion.
I can argue that KDE should not be hosting Windows binaries of
applications because that promotes Windows, and slowly it will be
impossible to contribute without Windows.
-
On Sat, Sep 19, 2015 at 7:03 PM, Luca Beltrame <lbeltr...@kde.org> wrote:
> Il Sat, 19 Sep 2015 18:49:48 +0200, Vishesh Handa ha scritto:
>
>> When/If that actually happens, you can bring it up and then we can deal
>> with it. Dealing in extreme What-Ifs does
On Sat, Sep 19, 2015 at 3:29 PM, Eike Hein <h...@kde.org> wrote:
> You're ignoring the position that says "the long-term
> negatives outweigh the short-term positives on this",
> though.
Well, I clearly think differently. I do not see any long term
negatives which cannot
On Sat, Sep 19, 2015 at 4:15 PM, Eike Hein <h...@kde.org> wrote:
>
>
> On 09/19/2015 04:04 PM, Vishesh Handa wrote:
>> This is the part of your email I really like. Though this is not what
>> you meant: If projectX choose to also use Github, it is not affecting
>
gle+.
Alright. Lets talk about Windows and Android then? You haven't
answered that part of my email.
--
Vishesh Handa
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
On Feb 8, 2016 11:51, "Jonathan Riddell" wrote:
>
> I also heard a suggestion from Vishesh that projects like Amarok
> shouldn't be allowed in GSoC because they are not very active. It
> seems nonsense to block projects from having activity on grounds that
> they are not very
31 matches
Mail list logo