<table><tr><td style="">nmel added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D23309">View Revision</a></tr></table><br /><div><div><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D23309#516339" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D23309#516339</a>, <a href="https://phabricator.kde.org/p/pino/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@pino</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D23309#516337" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D23309#516337</a>, <a href="https://phabricator.kde.org/p/yurchor/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@yurchor</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>The only problem with <a href="https://krusader.org/get-involved/" class="remarkup-link" target="_blank" rel="noreferrer">https://krusader.org/get-involved/</a> is that it is even more conservative than our user docs</p></div>
</blockquote>
<p><a href="https://cgit.kde.org/websites/krusader-org.git/" class="remarkup-link" target="_blank" rel="noreferrer">https://cgit.kde.org/websites/krusader-org.git/</a><br />
Just open a review request for that repository (or commit directly), it is not complicated...</p></div>
</blockquote>
<p><strong>Please always open a review! </strong>Committed and pushed changes are deployed directly to live site. People make mistakes, it's normal, and reviews reduce the likelihood of a mistake.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;">
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>(no translations, etc.).</p></blockquote>
<p>You need to known English to contribute anyway, almost all the tasks added by this patch require that. Hence I do not see how making them translatable helps anyway: even if the users read them in the translated documentation, as soon as they get to the "get involved" page the translation factor becomes useless.</p>
<p>So better be honest upfront: have only a small Help paragraph pointing to <a href="https://krusader.org/get-involved/" class="remarkup-link" target="_blank" rel="noreferrer">https://krusader.org/get-involved/</a>, mentioning that the page is in English.</p></blockquote>
<p>I agree with this point. If potential devs have problems with English and are curious enough, they'll use their favorite Page Translate service. It won't be ideal but at least it will be the most up-to-date translation.</p>
<blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D23309#515743" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D23309#515743</a>, <a href="https://phabricator.kde.org/p/pino/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@pino</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>As I said, IMHO the best is to point the installed documentation to <a href="https://krusader.org/get-involved/" class="remarkup-link" target="_blank" rel="noreferrer">https://krusader.org/get-involved/</a>. <strong>Getting involved into krusader IMHO is not something that depends on the krusader version, which is something the user documentation reflects.</strong><br />
Let's take an actual example: currently this documentation chapter mentions phabricator, which soon will be gitlab (where KDE is heading to). Now the user installs krusader from a stable distro (the latest Debian/Fedora/openSUSE/etc), then they read to use phabricator, and they try to reach it... which won't exist anymore.</p></div>
</blockquote>
<p>And I agree even more with this. I believe the majority of people just use what their distro suggests and this info will be outdated inevitably. Current dev affairs don't depend on the app version.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><ul class="remarkup-list">
<li class="remarkup-list-item">remove almost all the content of the Help chapter, leaving only a paragraph saying that help is welcome, you can do lots of things, etc etc, pointing to <a href="https://krusader.org/get-involved/" class="remarkup-link" target="_blank" rel="noreferrer">https://krusader.org/get-involved/</a></li>
<li class="remarkup-list-item">have the <em>up-to-date</em> instructions for help in <a href="https://krusader.org/get-involved/" class="remarkup-link" target="_blank" rel="noreferrer">https://krusader.org/get-involved/</a> only</li>
</ul></blockquote>
<p>+1. Toni, what you propose is a good change, however I think we should direct our efforts on keeping the online page as much detailed and updated as possible. It will be great to have starting steps for each type of work (for example, want to do Bug Triaging - go to the specific bugzilla link showing the list of not triaged bugs and try to repro bugs one by one, and then post your comments in the bugs).</p>
<p><a href="https://phabricator.kde.org/p/yurchor/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@yurchor</a>, in any case, the changes to the docs shall be made only in <tt style="background: #ebebeb; font-size: 13px;">master</tt>, since <tt style="background: #ebebeb; font-size: 13px;">stable</tt> is in the doc-freeze mode, correct?</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R167 Krusader</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D23309">https://phabricator.kde.org/D23309</a></div></div><br /><div><strong>To: </strong>asensi, Krusader, yurchor<br /><strong>Cc: </strong>nmel, yurchor, pino, kde-doc-english, Krusader, gennad, fbampaloukas, mjanczara, miroslavm, skadinna, janlepper, abika, martinkostolny, asensi, gengisdave, andreaska<br /></div>