Google Code-In - Coding tasks needed!
Hello folks, we have a bit less than one month to the end of GCi, January 25. We do have 71 claimable tasks, but very few coding tasks, and students are asking for these. If you have not yet mentored or created a task, and would like to dive in, please ask in #kde-soc on IRC if you need help, or on the KDE-Soc-Mentor list. All mentors with a bit of time, please add some more coding tasks. Mentors need 1. a google-connected email account and 2. to subscribe to the mentor list [1]. Ping one of us admins with your email to be invited to the webapp. Valorie 1. https://mail.kde.org/mailman/listinfo/kde-soc-mentor -- http://about.me/valoriez >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: robots.txt in quickgit.kde.org
On Montag, 28. Dezember 2015 18:09:32 CEST, Kevin Funk wrote: Are you aware that not even every KDE developer knows about LXR? I constantly have to tell people about it. Yes, and I'm as well aware of the "if it's not in google, it doesn't exist" phenomenon, BUT: that's not gonna work. If you search for QComplicatedClass, you'll find the Qt API docs, maybe some bug and most likely some stackoverflow entry - not a token in some thousand lines of code (leaving aside that mindless "i copy what I don't understand" is not the best of all approaches) - that will be on page [where no one has gone before] Now consider someone outside of KDE even, trying to figure out where KAwesomeClass is defined But you already know it exists? As mentioned I don't care, but for devs, one should ensure they get aware of lxr.kde.org - that's *far* better than having them enter "m_foo" into google and click until they find a result in KDE. The idea that someone finds a solution to his problem in the KDE sources is a bit far off to me. No idea what it would take, but ideally google would simply forward lxr.kde.org when you search for "kde" and something else. Stillshrug, Thomas Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: robots.txt in quickgit.kde.org
On Sun, Dec 27, 2015 at 12:35 PM, Ben Cooksley wrote: >> Is there some place where search engines can easily index our source >> code or are we shooting ourselves in the foot here? > > We could probably make it available by publishing the source trees > used by LXR / EBN. > This would only have the main branches obviously rather than everything > though. > > I haven't checked, but LXR may already make it's copy of the code > accessible... I think making our sourcecode available to search engines is pretty important for the reasons already mentioned by others. Do you need help for it? If you write down what's needed I can help find someone to do it. Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher KDE e.V. Board of Directors / KDE Community Working Group http://kde.org - http://open-advice.org >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: robots.txt in quickgit.kde.org
On Monday, December 28, 2015 04:37:47 PM Thomas Lübking wrote: > On Montag, 28. Dezember 2015 11:35:23 CEST, Albert Vaca wrote: > > Lxr can't search across every open source project in the world, so that's > > a > > point for Google. > > Presuming google could, why would I. Or anyone? > I dig for certain variables or strings in specific code, but why would I > look for m_foo or "SomeSetting" "across every open source project in the > world"? Lower STR? Search who copied "my" code? Are you aware that not even every KDE developer knows about LXR? I constantly have to tell people about it. Now consider someone outside of KDE even, trying to figure out where KAwesomeClass is defined, or how it is implemented quickly -> bummer. (right now there's api.kde.org, which at least gives results about signatures, but the content of the .cpp or .h files are not indexed afaics) So having KDE source code indexed by Google would be definitely a win for everyone. It being linked back to LXR even more (=> people learn LXR exists when googling for KDE source code) Cheers, Kevin > Don't get me wrong, I don't care if anyone can - fine. But the inability > doesn't exactly like shooting yourself. > > Shrug, > Thomas > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe > >> << -- Kevin Funk | kf...@kde.org | http://kfunk.org signature.asc Description: This is a digitally signed message part. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: kdesrc-build and include-dependencies
On Thu, Dec 24, 2015 at 10:57 PM, Michael Pyne wrote: > On Thu, December 24, 2015 00:11:10 Michael Pyne wrote: >> I'll be working over the next few days to try to expand out --include- >> dependencies to include any possible kde-projects modules (how it was >> originally intended to work), but until then hopefully this help. > > This /should/ now work. I still need to try to optimize it a bit (each missing > module results in re-parsing the XML for kde_projects.xml at this point...) > but now kdesrc-build should reach for any dependency expressible in kde-build- > metadata (though, these are only KDE git modules). > > Regards, > - Michael Pyne Hi Michael! Thanks a lot for looking into it! :D Aleix >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: robots.txt in quickgit.kde.org
On Monday, December 28, 2015 04:37:47 PM Thomas Lübking wrote: > On Montag, 28. Dezember 2015 11:35:23 CEST, Albert Vaca wrote: > > Lxr can't search across every open source project in the world, so that's > > a > > point for Google. > > Presuming google could, why would I. Or anyone? > I dig for certain variables or strings in specific code, but why would I > look for m_foo or "SomeSetting" "across every open source project in the > world"? Lower STR? Search who copied "my" code? > > Don't get me wrong, I don't care if anyone can - fine. But the inability > doesn't exactly like shooting yourself. Potential new contributors do not find our code as they do not know to search in LXR / EBN and when they don't find the code through Google it does not exist in their world and thus they will not contribute. But if it would be possible to find even only git master through LXR through Google it would be great :) /Kåre >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: robots.txt in quickgit.kde.org
El Monday 28 December 2015, a les 16:37:47, Thomas Lübking va escriure: > On Montag, 28. Dezember 2015 11:35:23 CEST, Albert Vaca wrote: > > Lxr can't search across every open source project in the world, so that's > > a > > point for Google. > > Presuming google could, why would I. Or anyone? You want to use QComplicatedClass, can't figure out how, go to google and search for it. You see KDE does use it and since you know KDE is an amazing group of developers you read their code and now understand how to use QComplicatedClass, you make your code and then realize the KDE people missed a subtle corner case, you sent a code review, everyone wins. Cheers, Albert > I dig for certain variables or strings in specific code, but why would I > look for m_foo or "SomeSetting" "across every open source project in the > world"? Lower STR? Search who copied "my" code? > > Don't get me wrong, I don't care if anyone can - fine. But the inability > doesn't exactly like shooting yourself. > > Shrug, > Thomas > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe > >> << >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: robots.txt in quickgit.kde.org
On Montag, 28. Dezember 2015 11:35:23 CEST, Albert Vaca wrote: Lxr can't search across every open source project in the world, so that's a point for Google. Presuming google could, why would I. Or anyone? I dig for certain variables or strings in specific code, but why would I look for m_foo or "SomeSetting" "across every open source project in the world"? Lower STR? Search who copied "my" code? Don't get me wrong, I don't care if anyone can - fine. But the inability doesn't exactly like shooting yourself. Shrug, Thomas Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: libkonq release? I'm missing the favicons interface
El Tuesday 22 December 2015, a les 21:22:15, Robby Stephenson va escriure: > On Tue, Dec 22, 2015 at 5:05 PM, Albert Astals Cid wrote: > > El Monday 21 December 2015, a les 22:17:05, Robby Stephenson va escriure: > > > Hi all, > > > > > > Tellico uses the org.kde.FavIcon DBus interface for showing some icons > > > for websites that provide data APIs. The same interface appears to be > > > used in KIO::favIconForUrl(). But unless I'm missing something, that > > > interface is part of libkonq which is (yet) unreleased for KF5 and > > > Konqueror itself is unmaintained. > > > > > > Please correct me if I'm wrong. Is there potentially a release planned > > > for libkonq? > > > > > > If not, I'm trying to figure out alternatives. I'd hate to write my own > > > component for downloading and caching favicons. I could grab the libkonq > > > code and put it in Tellico, but that would be a last resort. Any > > > suggestions? > > > > You step up and coordinate the release of libkonq for KF5 (which would be > > the > > same work as grabbing the code and putting it in Tellico but would > > benefit > > the wider world and not only you) > > Sure, I'm willing! How do I know if I have thick enough skin to be a > library maintainer? :) Anyone want to volunteer to be a mentor for me? I > disagree that it would be the same amount of work, but I'm willing to do > the extra... Great :) > A couple of items quickly come to mind: > * I barely know how to release an application. Library release and > maintenance brings additional needs (binary compatibility, soname > management, etc.) about which I barely know enough to know that I don't > know. I didn't know how to release stuff a while back either, now i release KDE Applications every month, it's not hard, just needs learning by doing and people answering your questions. > * Konqueror is unmaintained. Should libkonq even be a separate release? > Bringing in the small amount of code from libkonq/favicons to KIO seems > like a feasible approach. I'm willing to test and fix bugs there, too. This is a great question, having a quick look at the code, seems the libkonq/ favicons code is pretty isolated and doesn't depend at all on the rest of the libkonq code. Can you confirm? If that's correct and KIO indeed needs/uses this kded it may make sense to move it over there (i don't know much about frameworks/KIO either so may be wrong) > * Is this the appropriate mailing list for the discussion or should it go > to kde-frameworks-devel? Probably yes, it may make more sense to approach it as "libkonq release" but as "KIO::favIconForUrl doesn't work because the kded is unreleased". Cheers, Albert > > Robby >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: robots.txt in quickgit.kde.org
Lxr can't search across every open source project in the world, so that's a point for Google. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
