incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cory Johns" <>
Subject [allura:tickets] Re: #6456 Create project importer for Google Code
Date Mon, 22 Jul 2013 18:35:02 GMT
I used `project_unixname` to match the `add_project` form.  I can change it, though; I do like
`shortname` better.  I think was originally going to use the same form and `check_names` AJAX
call, but didn't anyway.

Right about the neighborhood, and there's no reason for it to have been hard-coded.  I'll

+1 to .ini setting for site name.

Copy/paste error.  I really wanted to re-use `add_project.css` but could figure out how to
reference the file since I'm not using EW.  Help is appreciated there.

That's a standard FormEncode validation message.  What should it say instead?

Upon further discussion with Tim, I also need to change how the tool importers are dispatched
to not assume that `import_tool` will manage tasking.


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

**Status:** in-progress
**Labels:** import google-code 
**Created:** Fri Jul 12, 2013 09:09 PM UTC by Cory Johns
**Last Updated:** Mon Jul 22, 2013 06:31 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., 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](
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/`
or such.


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message