infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Otto van der Schaaf (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-15735) Import PageSpeed git repositories
Date Mon, 08 Jan 2018 10:15:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-15735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316021#comment-16316021
] 

Otto van der Schaaf commented on INFRA-15735:
---------------------------------------------

Thanks Daniel! I have asked everyone to link their github IDs.
One question: I already had them linked, but I don't yet have write access to any of the incubator-pagespeed-*
repo's yet.
Is that expected?Is there anything I should do, like unlink/link to refresh?

Thanks! Otto

> Import PageSpeed git repositories
> ---------------------------------
>
>                 Key: INFRA-15735
>                 URL: https://issues.apache.org/jira/browse/INFRA-15735
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>            Reporter: Jukka Zitting
>            Assignee: Daniel Takamori
>
> PageSpeed is a new Incubator podling (https://s.apache.org/eGgS) with existing git repositories
at https://github.com/pagespeed. We'd like to migrate those repositories to the ASF.
> The software grant that covers the repositories is on file at the ASF as google-pagespeed.pdf.
> I already used https://reporeq.apache.org/ to create empty placeholder repositories for
the migration, but encountered problems when trying to migrate the existing version histories
with:
>     $ git clone --mirror https://github.com/pagespeed/$source
>     $ cd $source.git
>     $ git remote add apache https://git-wip-us.apache.org/repos/asf/incubator-pagespeed-$target.git
>     $ git push apache --mirror
> This worked for the small cpanel repository, but resulted in lots of notification spam
to commits@pagespeed.incubator.apache.org. An attempt to push the bigger mod_pagespeed repository
failed after a timeout (which was good, as it would have resulted in even more spam).
> What's the best way to migrate these repositories? The specific repositories we want
to migrate are ($source -> $target):
>     mod_pagespeed -> incubator-pagespeed-mod
>     ngx_pagespeed -> incubator-pagespeed-ngx
>     domain-registry-provider -> incubator-pagespeed-drp
>     zlib -> incubator-pagespeed-zlib
>     icu -> incubator-pagespeed-icu
>     mod_pagespeed_debian_packaging -> incubator-pagespeed-debian
>     fcgid -> incubator-pagespeed-fcgid
>     optipng -> incubator-pagespeed-optipng
>     cpanel -> incubator-pagespeed-cpanel
> If needed, I can attach these repositories as tarballs or retry pushing them myself if
the commit notifications are temporarily disabled and the timeout significantly increased.
> It's also OK to remove the incubator-pagespeed repositories I created with reporeq if
that makes the migration easier.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message