[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Revisiting the TechBase situation (2 proposals)
From:       Dominik Haumann <dhaumann () kde ! org>
Date:       2019-08-13 18:59:17
Message-ID: CALi_srCXVLrofZfzX0YY1uaOhqiA=CoLRUYLTb3-fB5CtG0_EA () mail ! gmail ! com
[Download RAW message or body]

Hi Alexander,

we have google and other excellent search engines. I don't think that the
way we search our content should result in many mediawiki instances. This
sounds to me like an attempt to solve a problem with a very wrong approach.
Besides that, the issue of broken cross-wiki links outweighs this by a
large factor.

Best regards
Dominik

On Thu, Aug 8, 2019 at 1:05 AM Alexander Potashev <aspotashev@gmail.com>
wrote:

> > On Tue, Apr 2, 2019 at 4:21 PM Juan Carlos Torres <jucato@kdemail.net>
> wrote:
> >> OPTION 1: Sunset TechBase, put everything in Community Wiki
> >>
> >> PROS:
> >> - All-inclusive, all-welcoming place for any kind and any level of
> developer
> >> - Everything is one place, easier to search, easier to see duplicates,
> no jumping back and forth
> >>
> >> CONS:
> >> - Could make the Community Wiki crowded
> >> - Lose search ranking, lose a catchy name
>
> Using one Wiki for everything has another little drawback: you can't
> limit search to a subsection of the wiki.
>
> Let's say a user searches for "kblocks". If it was a search on
> UserBase, it gives 0 results and that's it - there is no user
> documentation for it on UserBase. However if it was a single Wiki for
> everything, you would see about 20 results, all of them are technical,
> and the user would need to go through all of them just to find that
> none of those are relevant.
>
> On the other hand, I can't imagine a person who uses MediaWiki search
> function in 2019, other than me.
>
> --
> Alexander Potashev
>

[Attachment #3 (text/html)]

<div dir="ltr"><div>Hi Alexander,</div><div><br></div><div>we have google and other \
excellent search engines. I don&#39;t think that the way we search our content should \
result in many mediawiki instances. This sounds to me like an attempt to solve a \
problem with a very wrong approach. Besides that, the issue of broken cross-wiki \
links outweighs this by a large factor.<br></div><div><br></div><div>Best \
regards</div><div>Dominik<br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Thu, Aug 8, 2019 at 1:05 AM Alexander Potashev &lt;<a \
href="mailto:aspotashev@gmail.com">aspotashev@gmail.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">&gt; On Tue, Apr 2, \
2019 at 4:21 PM Juan Carlos Torres &lt;<a href="mailto:jucato@kdemail.net" \
target="_blank">jucato@kdemail.net</a>&gt; wrote:<br> &gt;&gt; OPTION 1: Sunset \
TechBase, put everything in Community Wiki<br> &gt;&gt;<br>
&gt;&gt; PROS:<br>
&gt;&gt; - All-inclusive, all-welcoming place for any kind and any level of \
developer<br> &gt;&gt; - Everything is one place, easier to search, easier to see \
duplicates, no jumping back and forth<br> &gt;&gt;<br>
&gt;&gt; CONS:<br>
&gt;&gt; - Could make the Community Wiki crowded<br>
&gt;&gt; - Lose search ranking, lose a catchy name<br>
<br>
Using one Wiki for everything has another little drawback: you can&#39;t<br>
limit search to a subsection of the wiki.<br>
<br>
Let&#39;s say a user searches for &quot;kblocks&quot;. If it was a search on<br>
UserBase, it gives 0 results and that&#39;s it - there is no user<br>
documentation for it on UserBase. However if it was a single Wiki for<br>
everything, you would see about 20 results, all of them are technical,<br>
and the user would need to go through all of them just to find that<br>
none of those are relevant.<br>
<br>
On the other hand, I can&#39;t imagine a person who uses MediaWiki search<br>
function in 2019, other than me.<br>
<br>
-- <br>
Alexander Potashev<br>
</blockquote></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]