Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YWWMA-0005uU-JV for pgsql-advocacy@arkaria.postgresql.org; Fri, 13 Mar 2015 20:38:54 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YWWMA-00022D-1E for pgsql-advocacy@arkaria.postgresql.org; Fri, 13 Mar 2015 20:38:54 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YWWM8-0001zT-Cb for pgsql-advocacy@postgresql.org; Fri, 13 Mar 2015 20:38:52 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YWWM5-00036I-3q for pgsql-advocacy@postgresql.org; Fri, 13 Mar 2015 20:38:50 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 44D972019A for ; Fri, 13 Mar 2015 16:38:46 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 13 Mar 2015 16:38:48 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= x-sasl-enc:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=mesmtp; bh=lkj/z+ZeOUJZ9ch/x9yseRsNdJU=; b=UFaBh8tVQiJJH2052f XDbvbaK7SZG+LxWZqm0Fdo2wcg3qxvD3kYPstECoKGB9EAzi41jxXzWi4aYxgV5M PS3Vd7JqRjQN/MuKfJDofIsSkWE4dhw05UCkTHETMrl6PQONVmDce4T15Lf9rH9q vYLNTUGdL58sJ9HWSBT/kHWxk= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:message-id:date:from :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=lkj/z+ZeOUJZ9ch/x9yseR sNdJU=; b=qWXNhoLna0EdC7U1f2JGtuXNOpWWBsc3dWTnGbauLYAhpgOLISmh/c D0g+goLGOepuJ+ONJ1gHlT6/S+P872WbUQHq5CSDODO5Yr6swlAua8jRKdYeCqPN 2SMYcg2dTTFxFjRAhvYWfOJ01c/swyLwDHOH+/9J2SgEE19mJO12k= X-Sasl-enc: 78x9FelvMCrLkM0ywaA3R9lvkg3eJNT0O+HGqyIP0SyA 1426279127 Received: from [192.168.1.4] (unknown [174.21.191.40]) by mail.messagingengine.com (Postfix) with ESMTPA id 8C43EC002A2; Fri, 13 Mar 2015 16:38:47 -0400 (EDT) Message-ID: <55034AD6.8070800@aklaver.com> Date: Fri, 13 Mar 2015 13:38:46 -0700 From: Adrian Klaver User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Josh Berkus , pgsql-advocacy@postgresql.org Subject: Re: Need help migrating old student projects off of Google Code References: <55031546.7080209@postgresql.org> <55031E65.1090508@agliodbs.com> <550349C5.8080405@aklaver.com> <550349FA.8070808@agliodbs.com> In-Reply-To: <550349FA.8070808@agliodbs.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-advocacy Precedence: bulk Sender: pgsql-advocacy-owner@postgresql.org On 03/13/2015 01:35 PM, Josh Berkus wrote: > On 03/13/2015 01:34 PM, Adrian Klaver wrote: >> On 03/13/2015 10:29 AM, Josh Berkus wrote: >>> On 03/13/2015 10:03 AM, Gurjeet Singh wrote: >>>> I can help in migration to GitHub. We can create a new org (or, if >>>> acceptable, move them under github.com/postgres). >>>> >>>> Just an FYI, since Google-code is currently overwhelmed by migration >>>> requests, they are not accepting any moves right now; "come back >>>> later" as the message says. >>> >>> Like I said, I need to push the button for moving the actual projects >>> because I'm the only one who has been an admin or assistant admin the >>> whole time. >>> >>> However, pushing the "migrate" button is the easy part. The hard part >>> is figuring out all of the projects which: >>> >>> a) have substantial code saved to google code; >> >> Well looking at: >> >> code.google.com/p/google-summer-of-code-YYYY-postgres/ >> >> for 2006-2014 I get either page not found(2006,2009,2012,2013,2014) or >> just a repo skeleton with no code(2007, 2008, 2010, 2011). >> >> Still working through the Wiki pages to see where the projects are >> actually hosted, though that information seems to be hidden in many cases. > > Thanks! > > Note that we *do* have 3 months to do this. Yea, it may take some time to ferret out where the projects actually are. I figured this was a 'as time permits' chore. I just tackled the low hanging fruit first. > > -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-advocacy mailing list (pgsql-advocacy@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-advocacy