<div>The sense here is just that working on git(orious) allows us to have a lot of occasional contributors.</div><div>The docs as example has been mainly written by two-three guys with just a 2 days work (and 2 commits each).</div>
<div>And I cannot remember more than that from them.</div><div>Just to clarify: there are probably 20-30 people around the "so called rekonq project". But just 2-3 of them have a kde (git, svn) account.</div><div>
I can say to anyone (and I do) to ask for an account, but numbers are the ones I said.</div><div>So, I need a way to manage all contributions coming from them. This way is the "merge request". It works really well here.</div>
<div>What I proposed here is a place to collect these merge requests.</div><div>On the other side, I understand your needs to manage in the easiest way possible this sort of things. So, I really don't know what's the best thing to do.</div>
<div>Probably, leaving docs untranslated? :) </div><div>Helping Albert to improve the scripty kid for git? Syncing rekonq docs dir with the right place in svn?</div><div><br></div><div><br></div><div class="gmail_quote">2010/8/31 Burkhard Lück <span dir="ltr"><<a href="mailto:lueck@hube-lueck.de">lueck@hube-lueck.de</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Am Dienstag, 31. August 2010, um 19:28:49 schrieb Andrea Diamantini:<br>
<div class="im">> The right way should be working on docs in svn. The problem is that the 2<br>
> or 3 guys working on it don't have svn access for.<br>
<br>
</div>It is really easy to get an svn account in kde.<br>
<div class="im"><br>
> I guess the simplest<br>
> way should be creating a new repository on gitorious for "rekonq docs", to<br>
> git svn sync every time with svn docs.<br>
><br>
</div>Please not an additional repository for rekonq.<br>
And please do not "sync" two writable repositories, that does not make any<br>
sense to me.<br>
<div class="im"><br>
> If this sounds good to all the parts, I'll ask for it in a while.<br>
><br>
</div>Sorry to say, but as longs as there is no replacement for my current workflow<br>
regarding i18n and documentation (svn up k* e* p* l10n-kde4/*) everything<br>
switching to git simply gets out of my radar...<br>
<br>
--<br>
<font color="#888888">Burkhard Lück<br>
</font></blockquote></div><br>