lueck created this revision.
lueck added reviewers: Documentation, pali.
Restricted Application added a project: Kopete.
Restricted Application added a subscriber: Kopete.
lueck requested review of this revision.
REVISION SUMMARY
remove or replace entities already defined in kdoctools
remove
lueck updated this revision to Diff 25657.
lueck added a comment.
add mising context
REPOSITORY
R434 Kopete
CHANGES SINCE LAST UPDATE
https://phabricator.kde.org/D9981?vs=25641=25657
REVISION DETAIL
https://phabricator.kde.org/D9981
AFFECTED FILES
doc/index.docbook
First off,
Hi!
I really enjoy using kopete! I was wondering if I would be able to continue
doing so in the brave new KF5 Era (IE, would somebody port it? Please,
please,
please)?
Second, I found a bug in MUC handling with jabber. Where would the best
place
to report it be?
Third, Are you accepting
I'm very discouraged to see so little movement on this. After skipping GCi
this past fall, are we now also considering skipping GSoC? Or downsizing
the number of students we are mentoring?
Without Ideas we will not get students. More important, we must complete
the Org application soon, and the
On 16.01.2018 00:45, Pali Rohár wrote:
Because it does not work.
remote: Push declined - excessive notifications would be sent
remote: Please file a KDE Sysadmin bug to continue
Therefore I opened sysadmin ticket T7642 and I was told that I should
discuss about it on kde-core-devel.
If I
On Mon, Jan 15, 2018 at 8:15 PM, Nate Graham wrote:
> I've submitted an idea for System Settings: Improve handling for touchpads
> and mice with Libinput
Speaking of systemsettings, would be a good fit porting to qml some
medium-to-big kcm?
--
Marco Martin
On 16.01.2018 09:20, Pali Rohár wrote:
Did you try already
1. merge the current master to master-kf5 and finish all the porting stuff
If you by "merge" means only git merge without git push, then this
operation does nothing.
Of course you have to push after the merge. But you can try to do
I've submitted an idea for System Settings: Improve handling for
touchpads and mice with Libinput
https://community.kde.org/GSoC/2018/Ideas#Improve_handling_for_touchpads_and_mice_with_Libinput
This is pretty important going forward since most distros are shipping
with Libinput now, but our
Hello GSoC mentors, and teams supporting mentors,
TL;DR: Fill out https://community.kde.org/GSoC/2018/Ideas; read
https://community.kde.org/GSoC. Now.
Every year, we've asked for more time to get ramped up for GSoC, and so now
is the time for organizations to apply[1]. We have begun to write our
Hi,
on GCompris side, we hope/plan to mentor 2 students like last year. I
updated the page to add one more task.
Regarding the events: this year, we were planning to skip SoK to focus more
on GCi and GSoC, having the 3 events is too consuming and do not allow us
to progress on our main tasks.
Hi, Valorie!
I have just edited the list of Krita ideas, now we have 8 ideas, 4 of
which are low-hanging fruits with localized optimizations of the code. I
hope that will help people who do not want to learn all half-million
lines of Krita code.
Speaking truly, I think I understand why
Hi all,
Would it be possible for sysadmins to just rename master ->
master-kde4, and master-kf5 -> master?
Cheers,
Ivan
On Tue, Jan 16, 2018 at 9:20 AM, Pali Rohár wrote:
> On Tuesday 16 January 2018 09:05:41 Alexander Semke wrote:
>>
>> On 16.01.2018 00:45, Pali Rohár
Hi all,
I have now completed the merge from Pali's clone repository into the
'master' branch of the main Kopete repository.
Phabricator processing of all the commits has been completed without incident.
Pali, please revise the metadata accordingly in sysadmin/repo-metadata
(for i18n) and
On Fri, Jan 19, 2018 at 12:06 PM, Pali Rohár wrote:
> On Thursday 18 January 2018 20:50:35 Ben Cooksley wrote:
>> Hi all,
>>
>> I have now completed the merge from Pali's clone repository into the
>> 'master' branch of the main Kopete repository.
>> Phabricator processing of
On Tue, Jan 16, 2018 at 9:24 PM, Ivan Čukić wrote:
> Hi all,
Hi Ivan (and others),
>
> Would it be possible for sysadmins to just rename master ->
> master-kde4, and master-kf5 -> master?
If master were merged into frameworks we could of course do such a
rename without too
Hi all,
Given that we are in essentially a intractable stalemate here and i'd
rather spend energy elsewhere, i'm going to go ahead and allow this.
It's going to be fairly messy however and will have consequences which
impact all KDE projects when it happens.
Phabricator will have to process all
16 matches
Mail list logo