Hi again,
Aleix Pol just added some documentation to KDE Connect, so we should now
meet the criteria to move it into extragear.
Is there anything else you guys think we should review, or is the package
ready to be moved?
Albert
2015-09-15 12:01 GMT-03:00 Albert Vaca :
> To put an example of a similar case, Windows 10 completely removed the "Help
> Center" and now it sends you online to the MS site if you need help.
"Windows 8 is truly the first Windows version made for the Internet
era... I had to
"I've let it there as a testimony of the dark side of wikis." <-- me
adds that to his quote book.
As a brand new user of KDE Connect if we had a user manual I would
look in it to see why for some reason the connection between KDE
Connect and my android phone who's name is "Jeremy's LG Phone" is
I see your points and actually agree. I'm completely ok with having
help go to some online documentation on userbase. I see the
requirement for offline/included help documentation to be going down
lately as you say and completely moot for kdeconnect since it
technically requires an internet
On Tuesday 15 of September 2015 08:01:44 Albert Vaca wrote:
> I don't think that having "descriptive documentation" (more about this
> later) is that important nowadays, and IMO users will likely google for
> help way before they use the help button when they find issues. Since most
> people I
I don't think that having "descriptive documentation" (more about this
later) is that important nowadays, and IMO users will likely google for
help way before they use the help button when they find issues. Since most
people I talked to in Randa agreed with me on this, I'm a bit surprised to
find
On Tuesday 15 of September 2015 09:06:40 Jeremy Whiting wrote:
> I see your points and actually agree. I'm completely ok with having
> help go to some online documentation on userbase. I see the
> requirement for offline/included help documentation to be going down
> lately as you say and
El Dimarts, 15 de setembre de 2015, a les 08:01:44, Albert Vaca va escriure:
> I don't think that having "descriptive documentation" (more about this
> later) is that important nowadays, and IMO users will likely google for
> help way before they use the help button when they find issues. Since
On Tuesday 15 September 2015 02:13:17 Aleix Pol wrote:
> Regarding the documentation, we discussed it briefly during the
> sprint and we have the feeling that the documentation for such a
> project would look more like a simple placeholder or something
> easily outdated than anything. Furthermore,
On Mon, Sep 14, 2015 at 12:52 AM, Jeremy Whiting wrote:
> As shown here: http://developer.kde.org/~cfeck/portingstatus.html
> (under Extragear base) It is missing a manual. Needs a Feature_summary
> added to CMakeLists.txt and some .desktop files should be renamed to
>
Aleix,
I disagree. I see the colors kcm has a manual, the icons kcm has a
manual, both accessible from the big "Help" button on the kcm in
systemsettings. kdeconnect's kcm has a Help button disabled because
there's no manual. While the ui is pretty intuitive, it would be good
to have something to
As shown here: http://developer.kde.org/~cfeck/portingstatus.html
(under Extragear base) It is missing a manual. Needs a Feature_summary
added to CMakeLists.txt and some .desktop files should be renamed to
org.kde.foo.desktop.
I just tried it out and it seems to work here, though I'm not seeing
On Sat, Sep 12, 2015 at 1:03 AM, Albert Astals Cid wrote:
> El Divendres, 11 de setembre de 2015, a les 07:52:34, Albert Vaca va escriure:
>> Our awesome sysadmins already moved the two repos (kdeconnect-android and
>> kdeconnect-kde) to Review.
>
> In
>
> I moved the translations for both repositories. Please update the
> translations
> branches for kdeconnect-android so that trunk_kf5 is master and trunk is
> none;
> yes, it's android and it does not matter, but it's easier for us.
>
Done.
> Translation branches for kdeconnect-kde are fine
Albert Vaca ha scritto:
> Our awesome sysadmins already moved the two repos (kdeconnect-android and
> kdeconnect-kde) to Review.
>
I moved the translations for both repositories. Please update the translations
branches for kdeconnect-android so that trunk_kf5 is master and trunk is none;
yes,
El Divendres, 11 de setembre de 2015, a les 07:52:34, Albert Vaca va escriure:
> Our awesome sysadmins already moved the two repos (kdeconnect-android and
> kdeconnect-kde) to Review.
In LoopbackDeviceLink::sendPackageEncrypted and
LoopbackDeviceLink::sendPackage you probably want to return
Our awesome sysadmins already moved the two repos (kdeconnect-android and
kdeconnect-kde) to Review.
+1 here too.
On Thu, Sep 10, 2015 at 3:39 AM, Albert Vaca wrote:
> +kde-core-devel
>
> Hi,
>
> With the latest changes we are making to KDE Connect as part of the sprint
> in Randa, I think that the project is becoming mature enough to be moved out
> of playground. Not only
On Thursday 10 of September 2015 02:33:55 Albert Vaca wrote:
> +kde-core-devel
>
> Hi,
>
> With the latest changes we are making to KDE Connect as part of the sprint
> in Randa, I think that the project is becoming mature enough to be moved
> out of playground. Not only that, but Kubuntu and
+kde-core-devel
Hi,
With the latest changes we are making to KDE Connect as part of the sprint
in Randa, I think that the project is becoming mature enough to be moved
out of playground. Not only that, but Kubuntu and other distros are already
installing KDE Connect by default, regardless of it
On Thu, Sep 10, 2015 at 2:20 PM, Luigi Toscano wrote:
> On Thursday 10 of September 2015 02:33:55 Albert Vaca wrote:
>> +kde-core-devel
>>
>> Hi,
>>
>> With the latest changes we are making to KDE Connect as part of the sprint
>> in Randa, I think that the project is
21 matches
Mail list logo