[Kde-scm-interest] Moving rekonq..

Eike Hein hein at kde.org
Wed Mar 17 02:08:57 CET 2010


On 03/17/2010 01:55 AM, Andrea Diamantini wrote:
> I did (or they did) quite all.
> I also created this page 
> (http://techbase.kde.org/Development/Tutorials/Git/KdeOnGit#Setting_up_your_KDE_project_to_start_developing_in_Gitorious)
> Hope it should work.

Thanks :).


> Now that things are "ready", what should I do to start being "kde-reviewed"?

First of please have a look at the "Unsolved i18n issue"
thread on this list since it was about Rekonq. In the end
the result is that you have to do nothing about the docs
right now, but just so that you're informed (please also
relay that to shadeslayer, he mentioned on IRC that he
was responsible for docs I think).

Next up, read this: http://techbase.kde.org/Policies/SVN_Guidelines

Basically, you have to move your app to kdereview and
then mail a review request to kde-core-devel.

Now since Rekonq is in Git, we can't/shouldn't remove it
to kdereview in SVN, of course, as we discussed. When all
of KDE moves to Git we have to morph kdereview into a
page on the Techbase wiki I think that has links to every-
thing under review etc.

However since it's just Rekonq right now I think the
best way to make sure that Rekonq actually gets reviewed
right now is not to shake things up too much.

I suggest you create a "rekonq" folder in the kdereview
folder in trunk and place a README file in it that ex-
plains where the code can be found and how it can be re-
trieved, i.e. the URL to the Gitorious web interface and
the clone command.

You should also mention in the README that people with an
SVN account who don't have access to KDE's Gitorious re-
positories (like Rekonq's) yet should sign up for a Gito-
rious account and then file a sysadmin request against
the gitorious component (making sure they mention both
their SVN and Gitorious account names) at:
https://bugs.kde.org/enter_sysadmin_request.cgi

So in short the README should tell people where to browse
the Rekonq code, how to get it, and how to get access to
commit to it. Doesn't need to be long at all, just the
bare essentials.

Once you've placed that folder and the README, write
the mail to kde-core-devel and there you go.


> Cheers,


-- 
Best regards,
Eike Hein


More information about the Kde-scm-interest mailing list