The `project_unixname` variable name isn't a great name. Unix name is a SF-specific thing (and includes the nbhd suffix). Better to call it `shortname`
`GoogleCodeProjectImporter` only works for `/p/` nbhd. Shouldn't it be able to work with any neighborhood? "SourceForge" is used in a flash message, which isn't appropriate for other sites using Allura. I know we have the same text during regular project registration (site note: are we copying too much from that logic? will we have to copy it all again for other importers?) Lets not further the SourceForge hard-coding here. Perhaps we need a .ini setting for site name? `!important` in css isn't a good thing. Validation of the google code project name has an error message that says "Usernames must include only..." Functionality works well. --- ** [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 04:57 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_p8...@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 [email protected] 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.
