Hi,
I think I can handle it with no problem. Thanks,
________________________________
From: nvda-translations-bounce@xxxxxxxxxxxxx
<nvda-translations-bounce@xxxxxxxxxxxxx> on behalf of James Teh
<jamie@xxxxxxxxxxxx>
Sent: Wednesday, March 22, 2017 11:23 AM
To: nvda-translations@xxxxxxxxxxxxx
Subject: Re: [nvda-translations] Proposal to switch from Assembla to GitHub
Hi all,
Thanks to all who have provided feeback so far. Here are a few clarifications
and answers to questions.
Despite GitHub primarily using git, you can also use svn to access simple
GitHub repositories. I mentioned this in my initial email, but perhaps it was
unclear. So, you will still be able to use svn or TortoiseSvn if you wish. In
fact, I think svn/TortoiseSvn should still be the recommended, documented way,
not least because translators are already familiar with it.
Joseph asked:
Can we come up with a directory of translator names, GitHub account names,
email addresses, and languages they translate? That way a member of a language
community can look up account names for translators and mention them directly.
I think that would be ideal, though it may be something we need to build over
time rather than something that blocks the migration. Note that in the absence
of this, we will be able to look at the latest commits for a language to see
the GitHub usernames who have been committing to it.
What about people we lost contact with? Should we attempt to send an email to
them about the upcoming transition?
I think that will be fairly difficult. Also, if they have been absent for quite
some time, it's reasonable to assume they might check the documentation again
or at least ask on the list before attempting to contribute again.
zvonimir wrote:
One question: wich wiki you are yoing to use for the website
If you mean for documentation for translators, that is all currently on the
NVDA wiki, which is already GitHub. If you mean for
addons.nvda-project.org<http://addons.nvda-project.org>, I'm not planning on
making any changes to that as part of this migration. That will still be
Ikiwiki. We do want to move away from Ikiwiki to a more tailored system at some
point, but if we do that, it will be handled separately.
the switch can be done, among with the structure differences turning off,
because of hebrew.
The move to GitHub will not fix the issue regarding structure differences and
locale specific t2t code such as for RTL. That requires the structure
differences code to be significantly refactored and must be handled separately.
Thanks.
Jamie
