From kde-frameworks-devel Tue Apr 28 09:44:39 2020 From: Ian Wadham Date: Tue, 28 Apr 2020 09:44:39 +0000 To: kde-frameworks-devel Subject: Re: Information regarding upcoming Gitlab Migration Message-Id: <3992BFBF-73BA-4060-A854-17C1A9803B22 () gmail ! com> X-MARC-Message: https://marc.info/?l=kde-frameworks-devel&m=158808535908507 Um, guys=E2=80=A6 Google is your friend... I am a former KDE Games developer. I play KPatience quite a lot, as well = as other games to keep my brain active, especially during COVID-19 = lockdown. Recently I thought I could see where the answer lay to three = bugs in the solver(s), two in the Forty Eight variant and one, very = recently reported, in the Klondike variant. So I thought I would have a = look at the source code to see if my hypotheses might be correct and = maybe work out a patch. My first problem was to track down where the repos that I need are and = how to clone read-only copies. I didn=E2=80=99t even know what websites = they are on any more and KPatience is actually called kpat in the code = (which I remembered). However I can google =E2=80=9Csource code KDE = KPatience=E2=80=9D and the pat repository comes up as the first hit, = presumably because =E2=80=9CKPatience=E2=80=9D is used in the = repository=E2=80=99s description. Again =E2=80=9C=E2=80=A6 card games=E2=80= =9D got the repo as hit 2 and =E2=80=9C=E2=80=A6 solitaire=E2=80=9D (the = American term for such games) got it as the first hit. I have also found that several of the tricky cases mentioned earlier in = this thread can be resolved with Google search terms beginning =E2=80=9Cso= urce code KDE xxx=E2=80=9D. For example, seeing xxx as =E2=80=9CPlasma = Mobile=E2=80=9D get the repo as hit 2. And just using =E2=80=9Cgo=E2=80=9D= as xxx finds the Kigo repository as hit 3. Even a search with xxx =3D = =E2=80=9Cloderunner=E2=80=9D finds the KGoldRunner repository as hit 1, = even though Loderunner is not mentioned in the repository=E2=80=99s = description. I wonder how far down repositories Google indexing goes. = Even using xxx =3D =E2=80=9Clode runner=E2=80=9D (2 words), as suggested = by Google, finds the KGoldrunner Handbook, though not the repository. = Still, a smart newbie might guess the name used for that type of game in = KDE and refine his source code search accordingly. Even after I found the kpat repository, I could not understand where the = souce code was getting the card decks it uses. I knew from memory that = they are in some library somewhere, but there is no libkdecards. = Googling with xxx =3D something like =E2=80=9Clibrary cards=E2=80=9D = found the cards as a sub-directory of the libkdegames repository. So my suggestion is to keep whatever categories you like, including = multiple categories as required, as long as the category names are in = plain English, not KDE jargon. In addition, please continue to pepper = repository descriptions with search terms (words) that are easy for = laymen and non-core KDE developers to find. Another possibility is to construct (automatically) a text-file = =E2=80=9Ccatalog=E2=80=9D with one line for each of the 1000+ = repositories, containing (at least) the repo name and description, but = maybe other keywords. Then people could just =E2=80=9Cgrep=E2=80=9D and = =E2=80=9Csort=E2=80=9D it to find what they wanted.=20 My 2 cents, Ian Wadham. > On 28 Apr 2020, at 2:46 pm, Bhushan Shah wrote: >=20 > Hi Olivier, >=20 > On Mon, Apr 27, 2020 at 10:49:46PM +0200, Olivier Churlaud wrote: >>> Because in order to search for something, you need to know it = exists. >>>=20 >>> If you are just casually browsing, then the search can't help you. >>=20 >> I don't think people casually browse our repos. What use case is more = likely to happen and do we want to support?=20 >=20 > We don't really want to discard use-cases just because it does not = suit > our workflow. That is not how we are going to gain new contributors, = we > should value each contribution, be it drive-by contribution, or = focused > contribution towards one single project. >=20 >> Use case 1 : Jerry learns about KDE and go in their forge in the = Multimedia section. After carefully reading the code of two applications = and three libs he starts contributing to Elisa.=20 >>=20 >> Use case 2 : While using her Ubuntu installation of Elisa / while = reading on reddit about Elisa, Jerry decides to try to contribute to = this project/fix this bug that itches her and searches for it in KDE's = forge.=20 >=20 > Let me add a some more usecases, some of which I've been dealing with = in > project I maintain. >=20 > Use case 3 : Tom comes in Plasma Mobile channel and asks for Plasma > Mobile applications source code >=20 > Use case 4 : Tom is a student in Germany and is interested in > contributing to wikitolearn, and he asks where can I find code of the > wikitolearn? >=20 > Suggestion offered by sysadmin team does not cater to one single > use-case, but offers a way to provide a solution to all 4 usecases. = For > Plasma Mobile team or Wikitolearn team it would be much easier to = refer > contributors to the https://invent.kde.org/plasma-mobile or > https://invent.kde.org/wikitolearn then tell them to go to > https://invent.kde.org/KDE and search for the tag wikitolearn or = Plasma > Mobile. >=20 >> On the other hand, I think the discussion about spotting open merge = requests (in a derived thread from this one) should be answered, being = by relevant tags, subgroups or whatever.=20 >=20 > (super personal note) >=20 > Ironically, Usecase 1 is how I started contributing to KDE 7 years = back. > While I was inspired by battery monitor re-design in 4.11 release, I > wanted to work on "something" so I did literally browse through = various > repositories to find something where my technical capabilities were > enough to work on [1]. Back then it was projects.kde.org (chiliproject > installation). >=20 > [1] https://blog.bshah.in/2013/09/01/hello-planet/ >=20 > --=20 > Bhushan Shah > http://blog.bshah.in > IRC Nick : bshah on Freenode > GPG key fingerprint : 0AAC 775B B643 7A8D 9AF7 A3AC FE07 8411 7FBC = E11D