You can find me around as tosky.
- User Since
- Apr 18 2015, 1:18 PM (157 w, 3 d)
Mon, Apr 23
Sun, Apr 22
Sat, Apr 21
Fri, Apr 20
Do you really want to remove the proper source of information in security dialog that asks you some additional credentials?
Please keep it there.
Thu, Apr 19
Wed, Apr 18
Tue, Apr 17
Don't you need to raise the requirement to a new Frameworks version, or #ifdefs if it's not possible (as it should probably be coordinated with the rest of the Plasma team)?
Mon, Apr 16
Sun, Apr 15
Thu, Apr 12
Talking about "the tool provide something, but it may not be the best idea": the more we discuss the more I found absurd to link the release date information in the appstream file: while we have a good process, releases can slip for whatever reason and adding the information ahead of the timesounds just backward; you will always run after the releases to update them.
Also, how does it work with the other big software center?
Just to add more details:
- some care should be taken when when a stable branch with changes is merged into master, and that may be complicated
- the size of this file will explode easily.
- the appstream spec talks about a short description, not those long contents.
As mentioned in the task, I'm not sure that this the way to go. It's even more relevant because this may set a precedent and going back could be complicated.
It does seem fine, thanks, with one caveat: you did not use arcanist apparently, so there are no author metadata in the review.
Do you have commit access?
Can you please update the commit message too?
The problem with release tags should be solved in a more global way by the release scripts IMHO.
@mak the context is in the previous messages, but tl;dr: are the releases.release tags supposed to
- contain release notes in addition to few metadata
- be translatable?
A quick read of https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html seems to point to "no" for both.
To be honest
Wed, Apr 11
Tue, Apr 10
Mon, Apr 9
As a user, I don't think that this has much sense. PlanetKDE works because you get only KDE related content (when some non-KDE content is visible, the author explicitly choose to do so).
As twitter does not allow to filter anymore by tag, you would get all the tweets. I'm not sure that it makes sense. It does not for my account (which can be remove from the list), where the amount of KDE-related stuff is not so high (well, in general I don't use it too much), and it's mostly re-twitting. I guess this is the common scenario.
Sun, Apr 8
See the past thread on kde-www:
Sat, Apr 7
The doc team was automatically added as subscriber.
Regarding the entity, just expand it inline, or define the entity in this file: we add it for people who have more contributions (and it would introduce a dependency on a new version of Frameworks, so you would need to keep the expanded version here anyway).
Fri, Apr 6
Thu, Apr 5
Wed, Apr 4
Tue, Apr 3
Mon, Apr 2
Sun, Apr 1
This should really be in the 2.1.0 version, as it makes CMakeLists.txt follow the same structure of CMakeLists.txt files in other projects.
+1 for me, waiting for @sars
Sat, Mar 31
I was not sure about the question: when you compile krusader, the documentation is compiled too. If you install it in the usual locations, khelpcenter will show it as usual.