Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: allura-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net
 designates 216.34.181.60 as permitted sender)
Content-Type: multipart/related;
 boundary="===============5044722861722692304=="
MIME-Version: 1.0
To: "[allura:tickets] " <6456@tickets.allura.p.re.sf.net>
From: "Cory Johns" <masterbunnyfu@users.sf.net>
Reply-To: "[allura:tickets] " <6456@tickets.allura.p.re.sf.net>
Subject: [allura:tickets] #6456 Create project importer for Google Code
Message-ID: 
 </p/allura/tickets/6456/186f23cfc39cf6c51e7b010956d8783b22e22fbf.tickets@allura.p.sourceforge.net>
Date: Fri, 19 Jul 2013 20:11:57 +0000

--===============5044722861722692304==
Content-Type: multipart/alternative;
 boundary="===============2883364536302047766=="
MIME-Version: 1.0

--===============2883364536302047766==
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

`allura:cj/6456`
`sftheme:cj/6456`


---

** [tickets:#6456] Create project importer for Google Code**

**Status:** code-review
**Labels:** import google-code 
**Created:** Fri Jul 12, 2013 09:09 PM UTC by Cory Johns
**Last Updated:** Tue Jul 16, 2013 07:53 PM UTC
**Owner:** Cory Johns

Create a controller that provides a landing page to import a project from Google Code hosting.  The landing page should ask for a project name and provide a list of all the tools (wiki, downloads, tracker, etc) supported for import, with a checkbox for each.  When submitted, it should pull the basic project info (description, icon, license) from the summary page (e.g., https://code.google.com/p/modwsgi/) and create a stub project with that data.

The description and icon values have `itemprop` attributes of "description" and "image", respectively, but the license will take a little bit of processing to extract.

The importers for the tools will be done in separate tickets.  The list of supported tools should be discovered by iterating the entry-points in the group `allura.importers` looking for importers with a `source` attribute equal to "Google Code".  Use the importer's `target_app` attribute to get the `tool_label` (and possibly icon?) for display.  See [the mailing list](http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201307.mbox/%3CCAEMb8zUg7Kem2aDxVzAqF3U4aKEj7jL3UO=UpX=2+NfY_P8kXQ@mail.gmail.com%3E) for more information.

The project importer should register itself as an entry point under the `allura.project_importers` group, and should expose a `source` attribute with the value of "Google Code".  I'm thinking the controller should be under an app-less tool called `ForgeImporters`, e.g. `ForgeImporters/forgeimporters/google/project.py` or such.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.
--===============2883364536302047766==
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<div class="markdown_content"><p><code>allura:cj/6456</code><br />
<code>sftheme:cj/6456</code></p>
<hr />
<p><strong> <a class="alink" href="http://sourceforge.net/p/allura/tickets/6456/">[tickets:#6456]</a> Create project importer for Google Code</strong></p>
<p><strong>Status:</strong> code-review<br />
<strong>Labels:</strong> import google-code <br />
<strong>Created:</strong> Fri Jul 12, 2013 09:09 PM UTC by Cory Johns<br />
<strong>Last Updated:</strong> Tue Jul 16, 2013 07:53 PM UTC<br />
<strong>Owner:</strong> Cory Johns</p>
<p>Create a controller that provides a landing page to import a project from Google Code hosting.  The landing page should ask for a project name and provide a list of all the tools (wiki, downloads, tracker, etc) supported for import, with a checkbox for each.  When submitted, it should pull the basic project info (description, icon, license) from the summary page (e.g., <a href="https://code.google.com/p/modwsgi/" rel="nofollow">https://code.google.com/p/modwsgi/</a>) and create a stub project with that data.</p>
<p>The description and icon values have <code>itemprop</code> attributes of "description" and "image", respectively, but the license will take a little bit of processing to extract.</p>
<p>The importers for the tools will be done in separate tickets.  The list of supported tools should be discovered by iterating the entry-points in the group <code>allura.importers</code> looking for importers with a <code>source</code> attribute equal to "Google Code".  Use the importer's <code>target_app</code> attribute to get the <code>tool_label</code> (and possibly icon?) for display.  See <a class="" href="http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201307.mbox/%3CCAEMb8zUg7Kem2aDxVzAqF3U4aKEj7jL3UO=UpX=2+NfY_P8kXQ@mail.gmail.com%3E" rel="nofollow">the mailing list</a> for more information.</p>
<p>The project importer should register itself as an entry point under the <code>allura.project_importers</code> group, and should expose a <code>source</code> attribute with the value of "Google Code".  I'm thinking the controller should be under an app-less tool called <code>ForgeImporters</code>, e.g. <code>ForgeImporters/forgeimporters/google/project.py</code> or such.</p>
<hr />
<p>Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to <a href="https://sourceforge.net/p/allura/tickets/">https://sourceforge.net/p/allura/tickets/</a></p>
<p>To unsubscribe from further messages, a project admin can change settings at <a href="https://sourceforge.net/p/allura/admin/tickets/options.">https://sourceforge.net/p/allura/admin/tickets/options.</a>  Or, if this is a mailing list, you can unsubscribe from the mailing list.</p></div>
--===============2883364536302047766==--

--===============5044722861722692304==--