Hi everyone,

Thanks for your inputs.

Sergio:

> move all the existing user base with minimal impact (how to announce, how
> to contact

users, how to switch off the old repos, etc.)

This is a very valid concern. We have updated the wiki page for the
proposal with a brief
outline of how we would handle this.

Regarding Gitlab, I also believe that it is theoretically superior to
GitHub (because the
interface does not use proprietary JS, among other things) but the reason
for choosing
GitHub is the visibility of a very popular hosting service, and the ease of
use for newcomers
who are often already familiar with GitHub. These and other reasons are
detailed in the
proposal.

Tommi:

> all the continuous integrations, continuous deployment and github pages
> (generated
>
from dixes via xslt and bahs hacks!) experimented out a bit

Thanks! We'll surely take a look and see what can be generalized to other
packages.

Fran: Thanks for pointing out the GSoC schedule. If all goes well, I
believe March 12
is not an unreasonable deadline to finish the technical parts of the
migration.

Thanks,

Shardul C.

On Tue, Feb 6, 2018 at 3:34 AM, Benedikt Freisen <b.frei...@gmx.net> wrote:

> Alright.  Thanks for pointing me at it.  I must have scrolled right past
> that "authors.txt", assuming that it was the AUTHORS file of the
> repository.
>
> My suggestion for added clarity would be:
> - create an AUTHORS file with your names in it
> - rename authors.txt to apertium_svn_authors.txt or something like that
>
> The ...@users.sourceforge.net addresses do indeed make more sense than
> pure dummy addresses, since they are at least theoretically valid
> addresses of the respective authors.
>
> Regards
> Benedikt
>
> Am 06.02.2018 um 03:38 schrieb Sushain Cherivirala:
> > Hi Benedikt,
> >
> > Thank you for your reply. You raise a good question regarding the
> > preservation
> > of emails in a transition to Git.
> >
> > Fortunately, in managing the Apertium packages for various platforms,
> > Tino has also
> > has put together a correspondence between SVN users and emails. The
> import
> > scripts that I have written use this correspondence. The current version
> > can be
> > found here:
> > https://github.com/sushain97/apertium-on-github/blob/master/authors.txt
> > <https://github.com/sushain97/apertium-on-github/blob/master/authors.txt
> >.
> >
> > Here is some documentation for the scripts I mention:
> > https://github.com/sushain97/apertium-on-github#scripts
> > <https://github.com/sushain97/apertium-on-github#scripts>.
> >
> > If your proper email is missing, you could email Tino and I. If your
> > email in the file
> > does not correspond to the email you use from GitHub, it can be changed.
> > However, it might be easiest to just add the email to your GitHub
> > account (you
> > can ensure that it is private). Of course, a repo's authors can always
> > be modified
> > after the fact with a re-import or filter-branch operation if necessary.
> >
> > I will leave you with an example of what the import script does when
> used on
> > apertium-cat: https://github.com/mock-apertium/apertium-
> cat/graphs/contributors
> > <https://github.com/mock-apertium/apertium-cat/graphs/contributors>.
> >
> > I am happy to answer any further questions.
> >
> > --
> > Sushain K. Cherivirala
> >
> > On Mon, Feb 5, 2018 at 5:06 AM, Benedikt Freisen <b.frei...@gmx.net
> > <mailto:b.frei...@gmx.net>> wrote:
> >
> >     One not so unimportant issue that I do not see mentioned anywhere is
> >     E-mail addresses.
> >     While svn only maintains a simple user name, git requires user name +
> >     E-mail address.  Tools like git-svn will only create a dummy address
> >     (user@repository-hash or something like that).
> >
> >     When reactos moved to github in October, a list of svn committer
> names
> >     plus full (real) names and E-mail addresses was compiled and
> supplied to
> >     the conversion tool, with more meaningful dummy addresses for
> previous
> >     committers without a known valid E-mail address.
> >     Apertium could use something like
> >     svnnameofcommitterwhol...@svn.apertium.org
> >     <mailto:svnnameofcommitterwhol...@svn.apertium.org> in that case.
> >
> >     My suggestion is therefore to scan all AUTHORS files for E-mail
> >     addresses and names corresponding to the respective committers.
> >     This has the additional benefit, that if those authors have a github
> >     account and use the same name+address combination with their github
> >     repositories, github will automatically recognize their commits as
> >     theirs.
> >
> >     Regards
> >     Benedikt
> >
> >     Am 04.02.2018 um 01:03 schrieb Shardul Chiplunkar:
> >     > To the President and members of the PMC and Apertium contributors,
> >     >
> >     > There is a new proposal to the PMC to move Apertium to Github:
> >     >
> >     http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
> >     <http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
> >
> >     >
> >     > Both previous proposals of a similar topic had shortcomings which
> this
> >     > proposal tries to address.
> >     >
> >     > If you are not a member of the PMC but would like to express your
> >     > support for this proposal, please add your name to the "Non-PMC
> >     > signatories" section at the bottom of the page.
> >     >
> >     > Thank you,
> >     > Shardul C.
> >     >
> >     >
> >     >
> >     ------------------------------------------------------------
> ------------------
> >     > 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
> >     <mailto:Apertium-stuff@lists.sourceforge.net>
> >     > https://lists.sourceforge.net/lists/listinfo/apertium-stuff
> >     <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
> >     <mailto:Apertium-stuff@lists.sourceforge.net>
> >     https://lists.sourceforge.net/lists/listinfo/apertium-stuff
> >     <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
> >
>
> ------------------------------------------------------------
> ------------------
> 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

Reply via email to