Yes to all of that. However, one concern is that AlluraImportApiClient is based on the old token/ticket model. The ticket import functionality (documented at docs/migration.rst) is probably something that could be removed since the newer ForgeImporter framework supports uploading ticket data in allura format. But the AlluraImportApiClient class is referenced in a few places and will have to be removed - I took a quick look at it seems like probably not too hard. I was afraid that the ForgeImporter classes were calling it somehow, but it seems not.
--- ** [tickets:#1687] Remove pre-oauth stuff** **Status:** in-progress **Milestone:** forge-backlog **Labels:** cleanup 42cc **Created:** Wed Mar 09, 2011 07:33 PM UTC by Dave Brondsema **Last Updated:** Mon Apr 28, 2014 09:48 AM UTC **Owner:** nobody Remove the user preference for the key & secret key, and integration therein. Remove RestClient, remove server-side validation, etc. --- 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.
