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

List:       kde-i18n-doc
Subject:    Re: Downtime for SVN - Action Required
From:       Agron Selimaj <as9902613 () gmail ! com>
Date:       2020-04-20 22:54:58
Message-ID: CA+_PYyvEa24hQidFCO7znOE9YkromROprU7bKkcdgs+aKLyO1Q () mail ! gmail ! com
[Download RAW message or body]

Guys I just need a little clarification for submitting translated file to
the gitlab repository.

My first question is - is the migration over and can I submit translated
files?

Second, with SVN all I did was commit (of course after compiling and other
tests). Now with Git, I fork + clone, translate and then send a merge
request? Right? Is there a guide for submitting po files?

Third, I need a little git/kde geography. What path do I clone from, from
git? Is there an efficient path that concerns translations only or more
specifically albanian translations.

Thanks,
//Agron




On Sat, Apr 18, 2020 at 6:36 AM Nicol=C3=A1s Alvarez <nalvarez@kde.org> wro=
te:

> El dom., 12 de abr. de 2020 a la(s) 05:57, Ben Cooksley
> (bcooksley@kde.org) escribi=C3=B3:
> >
> > Hi all,
> >
> > As you may be aware, KDE is currently undertaking a migration to Gitlab=
.
> >
> > As part of this, we also need to migrate our Subversion repository
> > from the server it currently resides on to the new system that also
> > hosts Gitlab. To simplify our systems we will also transition
> > management of SSH keys to Gitlab when we do this.
> >
> > It is intended at this time that we perform the migration of the
> > Subversion repository next weekend.
> >
> > We therefore need all holders of a Developer account, even if they
> > only use our Subversion repository, to login to Gitlab and upload
> > their SSH keys there.
> >
> > Our Gitlab instance can be found at https://invent.kde.org/ and you
> > should be able to login there using your KDE Identity
> > (identity.kde.org) details.
> >
> > Additionally, following this migration we will begin limiting access
> > to the Subversion repository to those actively using it. The list of
> > people whose access will be continued can be found at
> > https://cgit.kde.org/repo-management.git/tree/svn-ssh-keys/users-list
> >
> > Should you still need access to the repository, but are not on the
> > above list, please let us know by emailing sysadmin@kde.org.
> >
> > If anyone has any questions on the above, please let us know.
>
> Hi all,
>
> I wanted to add that this server migration will also change the SSH
> host keys for "svn.kde.org". After we switch servers, you will get the
> nasty "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" message from
> ssh when you use SVN. To avoid this, you should add the new keys to
> your ~/.ssh/known_hosts. You don't need to wait for the server switch,
> you can add it now (keeping both old and new keys in the file) and it
> will Just Work.
>
> I have added instructions for all these changes and the new ssh host
> keys to the wiki:
> https://community.kde.org/Infrastructure/Subversion/2020_Changes
>
> --
> Nicol=C3=A1s
> KDE Sysadmin Team
>

[Attachment #3 (text/html)]

<div dir="ltr">Guys I just need a little clarification for submitting translated file \
to the gitlab repository.<div><br></div><div>My first question is - is the migration \
over and can I submit translated files?</div><div><br></div><div>Second, with SVN all \
I did was commit (of course after compiling and other tests). Now with Git, I fork  + \
clone, translate and then send a merge request? Right? Is there a guide for \
submitting po files?</div><div><br></div><div>Third, I need a little git/kde \
geography. What path do I clone from, from git? Is there an efficient path that \
concerns translations only or more specifically albanian translations.  \
</div><div><br></div><div>Thanks,</div><div>//Agron</div><div><br></div><div><br></div><div><br></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Apr 18, 2020 at 6:36 AM \
Nicolás Alvarez &lt;<a href="mailto:nalvarez@kde.org">nalvarez@kde.org</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">El dom., 12 de abr. de \
2020 a la(s) 05:57, Ben Cooksley<br> (<a href="mailto:bcooksley@kde.org" \
target="_blank">bcooksley@kde.org</a>) escribió:<br> &gt;<br>
&gt; Hi all,<br>
&gt;<br>
&gt; As you may be aware, KDE is currently undertaking a migration to Gitlab.<br>
&gt;<br>
&gt; As part of this, we also need to migrate our Subversion repository<br>
&gt; from the server it currently resides on to the new system that also<br>
&gt; hosts Gitlab. To simplify our systems we will also transition<br>
&gt; management of SSH keys to Gitlab when we do this.<br>
&gt;<br>
&gt; It is intended at this time that we perform the migration of the<br>
&gt; Subversion repository next weekend.<br>
&gt;<br>
&gt; We therefore need all holders of a Developer account, even if they<br>
&gt; only use our Subversion repository, to login to Gitlab and upload<br>
&gt; their SSH keys there.<br>
&gt;<br>
&gt; Our Gitlab instance can be found at <a href="https://invent.kde.org/" \
rel="noreferrer" target="_blank">https://invent.kde.org/</a> and you<br> &gt; should \
be able to login there using your KDE Identity<br> &gt; (<a \
href="http://identity.kde.org" rel="noreferrer" target="_blank">identity.kde.org</a>) \
details.<br> &gt;<br>
&gt; Additionally, following this migration we will begin limiting access<br>
&gt; to the Subversion repository to those actively using it. The list of<br>
&gt; people whose access will be continued can be found at<br>
&gt; <a href="https://cgit.kde.org/repo-management.git/tree/svn-ssh-keys/users-list" \
rel="noreferrer" target="_blank">https://cgit.kde.org/repo-management.git/tree/svn-ssh-keys/users-list</a><br>
 &gt;<br>
&gt; Should you still need access to the repository, but are not on the<br>
&gt; above list, please let us know by emailing <a href="mailto:sysadmin@kde.org" \
target="_blank">sysadmin@kde.org</a>.<br> &gt;<br>
&gt; If anyone has any questions on the above, please let us know.<br>
<br>
Hi all,<br>
<br>
I wanted to add that this server migration will also change the SSH<br>
host keys for &quot;<a href="http://svn.kde.org" rel="noreferrer" \
target="_blank">svn.kde.org</a>&quot;. After we switch servers, you will get the<br> \
nasty &quot;WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!&quot; message from<br> \
ssh when you use SVN. To avoid this, you should add the new keys to<br> your \
~/.ssh/known_hosts. You don&#39;t need to wait for the server switch,<br> you can add \
it now (keeping both old and new keys in the file) and it<br> will Just Work.<br>
<br>
I have added instructions for all these changes and the new ssh host<br>
keys to the wiki:<br>
<a href="https://community.kde.org/Infrastructure/Subversion/2020_Changes" \
rel="noreferrer" target="_blank">https://community.kde.org/Infrastructure/Subversion/2020_Changes</a><br>
 <br>
-- <br>
Nicolás<br>
KDE Sysadmin Team<br>
</blockquote></div>



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

Configure | About | News | Add a list | Sponsored by KoreLogic