Return-Path: X-Original-To: apmail-incubator-allura-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D7412D3FD for ; Tue, 4 Dec 2012 23:17:52 +0000 (UTC) Received: (qmail 45534 invoked by uid 500); 4 Dec 2012 23:17:52 -0000 Delivered-To: apmail-incubator-allura-users-archive@incubator.apache.org Received: (qmail 45490 invoked by uid 500); 4 Dec 2012 23:17:52 -0000 Mailing-List: contact allura-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-users@incubator.apache.org Delivered-To: mailing list allura-users@incubator.apache.org Received: (qmail 45478 invoked by uid 99); 4 Dec 2012 23:17:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 23:17:52 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jpschewe@gmail.com designates 209.85.212.48 as permitted sender) Received: from [209.85.212.48] (HELO mail-vb0-f48.google.com) (209.85.212.48) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 23:17:46 +0000 Received: by mail-vb0-f48.google.com with SMTP id fc21so3856831vbb.7 for ; Tue, 04 Dec 2012 15:17:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=KxOj1hgABSnZX69C8CwCrAGrTtw7KBGjz7GKiFYQ+pc=; b=Ec2caVuba7DF0IwGGYuB+KO0LQ6BbGmurlhAW497DV7LWng9sntTgsrqr2bU4PCdYG Kir4a1LkZ7i6+txJ2dVV6gLixy0UbvSDdC58Kwuc0zgL75DgHFZEOMqKaLA//55+McoK nv3GwNg+qfhFnL9dXFTimjmVCi7ZUK4Lg8+Oe4C8NTyVxVKJLD5i1qijb1E2kNJ6jolN no0NjNpxSBNXmAweK/ZED9C3Dt7/h6zDE7xqoebqc/HZK51eqxQlSLcsgdm5tXlBSYER ON+zgMLd9fjrKp4KfaROwcFRD2onE4nsL2TMgrxDVWV93zjkFuj+5Ja9n+ZzUrzXc//9 xeig== MIME-Version: 1.0 Received: by 10.52.100.40 with SMTP id ev8mr11409846vdb.114.1354663045385; Tue, 04 Dec 2012 15:17:25 -0800 (PST) Sender: jpschewe@gmail.com Received: by 10.58.31.194 with HTTP; Tue, 4 Dec 2012 15:17:25 -0800 (PST) Date: Tue, 4 Dec 2012 17:17:25 -0600 X-Google-Sender-Auth: MMnmOXg-AMIQS-Esw-D6TEAz_zs Message-ID: Subject: Status of allura import From: Jon Schewe To: allura-users@incubator.apache.org Content-Type: multipart/alternative; boundary=bcaec50163859c4d1d04d00f1164 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec50163859c4d1d04d00f1164 Content-Type: text/plain; charset=ISO-8859-1 What is the status of importing data into Allura? I found documentation at http://allura.sourceforge.net/migration.html and eventually found allura_import.py in the source tree, but the python script wasn't really working when I first started using it. I've fixed a couple of things and put in merge requests for them. I'm looking to migrate from my SourceForge Hosted App Trac (which I'm told will go away soon) to the new Allura platform on SourceForge. I've managed to get the trac_export.py script to create a JSON file that appears looks to have all of the important information in it. I notice that it doesn't grab attachments, but I'm not sure how it could and I don't have many, so that's not a big deal. Now I'm looking at trying to validate my JSON file and have some confidence that an import into SourceForge will work. Can I validate without an API key? If so, how? If I get an API key and the validation passes, is the import likely to work? Has someone else tried this or am I on the bleeding edge of things? -- http://mtu.net/~jpschewe --bcaec50163859c4d1d04d00f1164 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable What is the status of importing data into Allura?=A0 I found documentation = at http://allura.s= ourceforge.net/migration.html and eventually found allura_import.py in = the source tree, but the python script wasn't really working when I fir= st started using it. I've fixed a couple of things and put in merge req= uests for them. I'm looking to migrate from my SourceForge Hosted App T= rac (which I'm told will go away soon) to the new Allura platform on So= urceForge. I've managed to get the trac_export.py script to create a JS= ON file that appears looks to have all of the important information in it. = I notice that it doesn't grab attachments, but I'm not sure how it = could and I don't have many, so that's not a big deal. Now I'm = looking at trying to validate my JSON file and have some confidence that an= import into SourceForge will work.

Can I validate without an API key? If so, how?

If I get an API k= ey and the validation passes, is the import likely to work? Has someone els= e tried this or am I on the bleeding edge of things?


--
http://mt= u.net/~jpschewe


--bcaec50163859c4d1d04d00f1164--