Migrating Web parts from Subversion to GitHub

[Pascal Chevrel]

Hi,


We are in the process of migrating all repositories used for Web parts
from SVN to GitHub.

We already started with a first repository [1]. We are going to move
them all under this GitHub account [2]. If you already have a GitHub
account, you'll be given write permissions for the l10n repos. If you do
not have a GitHub account and are a regular committer on SVN, please
create one and contact us so hat we can add you to the @localizers group
on Github.


*Will the migration to GitHub change the way I work on Pontoon or
Locamotion?*

No. The change will be transparent for you, Pontoon and Locamotion are
fully compatible with Git and will make the switch as the migration is done.

This migration is only about providing new tools to people willing to
use them.

*What is the scope of the migration?*

We are only migrating web l10n projects hosted on Subversion (SVN).
Firefox for iOS l10n, which is done on Subversion, is not in the scope
of this migration, at least for now. Products hosted on Mercurial are
not concerned by this migration at all.


*What is the schedule of this migration?*

We already migrated our first repository fully (Google Play content for
Firefox https://github.com/mozilla-l10n/appstores) and actually a few of
you already started translating there either via pull requests or via
Pontoon. We intend to migrate all significant projects from SVN to
GitHub before the end of the year. The mozilla.org repository is likely
to be migrated last because of the infrastructure changes needed for
deployment.

*What's the impact on the Web Dashboard, Langchecker, Transvision,
committer accounts…?*

The Web Dashboard and its associated tools (langchecker, web stats…) are
updated with each new migrated repository so there is nothing changing
there for you, they will work as usual.

Transvision which indexes mozilla.org will also be updated when we
migrate the repository to GitHub.

Mozilla LDAP accounts are no longer needed to translate on GitHub and
l10n-drivers will grant access to the repositories by adding your GitHub
account to the localizers team on GitHub. That also means that we can
create accounts faster. We already sent invites to about 50 web
localizers for which we already knew their GitHub Account. If you were
not contacted yet that just means that we don't know your account or you
don't have a GitHub account, just send us an email or ping us on IRC to
get your account added to the localizers team.

*What's new with GitHub?*

If you're already familiar with GitHub, you probably already know all
this, but let's take a quick tour of what's now possible to do with the
GitHub platform.

- Pull Requests: People can now propose changes, and you'll have the
opportunity to review the changes and accept them, ask for additional
changes with the author or discard the Pull Request.

- Anyone can propose a little change to one file with the online editor,
even without any Git knowledge [3].

- You can review the changes [4] and discuss the changes [5] with the
author before accepting the Pull Request.

This is also a great platform to involve new people, since they can
easily access the content and submit changes. This will also allow us to
reach people already familiar with Git/GitHub and make it easier for
them to get involved.

On the technical side:
You have commit access to the repository. You can clone the main
repository and work directly on master (similarly to SVN). If you
prefer, you can also fork the repository and work with pull requests
(you’ll be able to merge them directly).
You won’t be able to create new branches in the main repository, squash
your commits (combining multiple commits into one), amend your commits
(change the last commit), and in general perform a “forced push”. In
this sense the workflow is very similar to the one you’re already
familiar with for SVN: which means you can commit directly to a clone of
the repository, or merge pull requests from a clone, you will work by
committing directly on the master branch (the default one), you won’t be
able to create new branches or squash your commits (e.g. combining
several commits into a single one, for those familiar with that). So
that’s a workflow very similar to SVN.


*What can I do from now?*

You can ask us to be added to the localizers team on GitHub if you are
not already part of it.

You can start committing to the repositories we already migrated as
explained above.

If you have troubles to update your tools or have questions about the
migration, please reach out to us, we can help and answer questions :)

We have also set up a short FAQ about the migration that we will update
regularly based on issues you guys may encounter. A good starting point
if you are not familiar with git is to look at the workflow examples we
documented in the FAQ which compares the git and svn workflows:
https://github.com/mozilla-l10n/git-migration-faq#workflow-examples

[1]
http://viewvc.svn.mozilla.org/vc/projects/l10n-misc/trunk/obsolete/README?view=co
[2] https://github.com/mozilla-l10n/
[3]
https://help.github.com/articles/editing-files-in-another-user-s-repository/
[4]
https://help.github.com/articles/using-pull-requests/#reviewing-proposed-changes
[5]
https://help.github.com/articles/using-pull-requests/#pull-request-discussion
[6]
https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion#git-svn


Pascal, Francesco and Théo for the L10N team

[Michal Stanke]

Thank you Pascal for all the info. I was just going through all the
e-mails from GitHub and wondering what is their impact. Just to make
sure, after the migration only Firefox for iOS l10n will stay SVN?

Cheers,
Michal Stanke

Dne 26.8.2015 v 17:54 Pascal Chevrel napsal(a):

> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n

[Pascal Chevrel]

Le 26/08/2015 20:52, Michal Stanke a écrit :
> Thank you Pascal for all the info. I was just going through all the
> e-mails from GitHub and wondering what is their impact. Just to make
> sure, after the migration only Firefox for iOS l10n will stay SVN?
>
> Cheers,
> Michal Stanke
>

Yes, only Firefox for iOS l10n stays on svn.

Of course, if in the years to come IT decides to pull the plug on our
old svn server, we will probably have to move that one either to github
or to mercurial.

Cheers,

Pascal

[Khaled Hosny]

Hi,

I havn’t done any web parts translation in a while, but I’m just letting
you know that I didn’t get any GitHub related emails, just in case I was
supposed to get one. My account is khaledhosny.

Regards,
Khaled

[droid...@gmail.com]

> > committer accounts...?*
> >
> > The Web Dashboard and its associated tools (langchecker, web stats...) are

would be neat if you could add https://github.com/bittin to the right group/groups aswell :) as i do some Firefox OS Fireplace stuff :)

[Pascal Chevrel]

Le 28/08/2015 10:57, droid...@gmail.com a écrit :

>
> would be neat if you could add https://github.com/bittin to the right group/groups aswell :) as i do some Firefox OS Fireplace stuff :)
>

Done :)

Pascal

[Enrique Estévez Fernández]

Hi Pascal.

Can you add me, please?

Regards.

[Alexander L. Slovesnik]

Hi Pascal.

Please add https://github.com/unghost to the right group/groups.


Pascal Chevrel пишет 26.08.2015 18:54:

> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
>

--
Sincerely yours,
Alexander L. Slovesnik a.k.a. Unghost
==>Jabber ID: ung...@mozilla-russia.org
==>Gmail Talk ID: ung...@gmail.com
==>Skype: alexander.slovesnik
==>Twitter: http://twitter.com/unghost

[Alexander L. Slovesnik]

Hi Pascal.

Please add https://github.com/unghost to the right group/groups.


Pascal Chevrel пишет 26.08.2015 18:54: