Not entirely sure why you posted it there first, so I'm not sure where to reply... I see brainstorming things in there but no real project proposals, so I don't know how helpful that post is going to be. Did you read my response above and have any feedback on the points raised?

For example, we need to be sure a task we create is good for a whole summer of code. Dependent attributes could be done in a week. If a task is to be made out of that, I think it should be lumped into a broader dynamic attributes system that also handles things like image replacement and incorporates cYu's price update. Then it needs identifiable benchmarks and achievable goals.

Further, a task like the conditional actions thing is much to essential to core Ubercart and the D6 update to be farmed out to a student who may have no familiarity with Ubercart who won't start until late May.

I like the idea of someone spending a summer working out a way to have inline form editing/saving. This can have a broader Drupal application, and the test implementation can be specifically Ubercart. I think it's a little misleading to say the existing screen is feature incomplete, though. At least if it is, can you post up issues for how features aren't working as expected?

I do think that the product XML building module can rock the socks off of several needs for e-commerce... specifically general product exporting, but particularly exporting for upload into feeds/shopping sites and for download into external applications like QuickBooks. That one could be fleshed out further.

Summary thought: Let's dialog about the tasks with the most potential here in the forums and put up detailed proposals over the next couple of days.

Also, count me in as a mentor.