Hi folks,
I have invited all non-SourceForge emails on record who have committed
to Apertium on SourceForge to the GitHub Apertium organization as members.
Please note that until we really migrate, repository creation is *disabled*.
For some technical reasons, this process needs to be done prior to an
actual migration.
If you are already in the organization and received an invitation, my
apologies.
It's a technical limitation of the platform and I figured it would not
bother too many
people if I did not clean up the list by hand.
If you are a member of Apertium on SF, would like to continue being a member
of Apertium on GitHub and *did not receive the invitation*, send me or any
member
of the PMC your GitHub username and we can add you (probably the former is
simpler).
Thanks for bearing with this necessary step. To reiterate, *no data has
been moved yet*.
*Keep using SF/SVN. *The only difference is that now the GitHub Apertium
organization
has more members.
--
Sushain K. Cherivirala
On Mon, Feb 19, 2018 at 8:32 AM, Sushain Cherivirala <sush...@skc.name>
wrote:
> Hi Hector (and any others who would like to continue using SVN commands),
>
> I've touched on this previously on this list but I think it's quite
> important so I'll mention it again.
>
> GitHub's SVN bridge (which neither GitLab nor Bitbucket have a free
> equivalent for),
> lets you continue using SVN for working with any of the language
> pairs/modules/tools (not
> the GitHub equivalents of /languages, /incubator, /trunk though).
>
> For example:
>
> $ svn co https://github.com/mock-apertium/apertium-cat.git/trunk
> apertium-cat
> A apertium-cat/.gitattributes
> A apertium-cat/AUTHORS
> A apertium-cat/COPYING
> A apertium-cat/ChangeLog
> A apertium-cat/Jenkinsfile
> A apertium-cat/Makefile.am
> [...]
> Checked out revision 598.
> $ cd apertium-cat/
> $ ls
> AUTHORS Makefile.am apertium-cat.cat.dix
> apertium-cat.post-cat.dix genvdix.py
> COPYING NEWS apertium-cat.cat.rlx
> autogen.sh modes.xml
> ChangeLog README apertium-cat.cat.tsx
> cat.prob texts
> Jenkinsfile apertium-cat.cat.acx apertium-cat.pc.in
> configure.ac
> $ echo 'who needs a dictionary' > apertium-cat.cat.dix
> $ svn status
> M apertium-cat.cat.dix
> $ svn ci -m "We don't need this file"
> Sending apertium-cat.cat.dix
> Transmitting file data .done
> Committing transaction...
> Committed revision 599.
>
> Tada: https://github.com/mock-apertium/apertium-cat/blob/mas
> ter/apertium-cat.cat.dix
>
> In this light, fully "deprecating" the Using SVN page isn't necessary.
> Just a big warning
> describing the limitation I mentioned above and what's actually happening
> should suffice.
> Specifically, the SVN bridge does not support Git submodules.
>
> Of course, there will also be a Git for SVN users guide, probably
> borrowing something
> someone has already made that works well.
>
> So, your daily workflow does not need to change. You will need a GitHub
> account which
> I hope isn't too much to ask :-)
>
> Happy to answer any further questions.
>
> --
> Sushain K. Cherivirala
>
> On Sun, Feb 18, 2018 at 4:11 AM, Hèctor Alòs i Font <h.a...@esperanto.cat>
> wrote:
>
>> 2018-02-16 9:13 GMT+03:00 Francis Tyers <fty...@prompsit.com>:
>>
>>> El 2018-02-14 01:38, Shardul Chiplunkar escribió:
>>>
>>>> Thanks for your comments.
>>>>
>>>> Felipe, I have tried to respond to your comment on the proposal page.
>>>> Please let us know if you have further questions.
>>>>
>>>> It seems that making the repository read-only and later deleting it is
>>>> the best option then. As Fran and Xavi said, we would go through the
>>>> wiki pages, READMEs, Virtualbox/Docker configs, etc. to replace
>>>> SourceForge links with GitHub links in the meantime.
>>>>
>>>> Shardul C.
>>>>
>>>
>>> Note, this will not just be replacing links, but also commands. It's no
>>> good
>>> replacing a link "svn co http://"; with the github one, and then leave a
>>> "svn commit". The documentation should be updated wholesale as a result of
>>> the move.
>>>
>>> This includes rewriting the contents of the Using_SVN page and
>>> deprecating it.
>>
>>
>> Yes, indeed. As a simple user of svn, and knowing nothing about git, I'll
>> be glad to have a "git for dummies" similar to the Using_SVN page, so
>> that I'll be able to continue the work with my usual language pairs.
>>
>> Hèctor
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Apertium-stuff mailing list
>> Apertium-stuff@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>>
>>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
