(Disclaimer: I was with Mike chatting about this stuff, but I'm repeating some thoughts here for others' benefit, too.)

I love the idea of bringing Ubercart to the SoC. Thanks for taking point on this, and let me know where I can lend a hand. Gonna go sign up to the SoC mentor's group on g.d.o.

Looking at the list, I think any would be awesome, though I don't know if a couple there would provide enough development time for the students. I think the order input page would be definitely worth it and a great addition to Ubercart 2.0. I'm assuming you're considering a single view/edit page where the whole form is constructed and you click on a field to edit it inline? Something like this should take enough time and core involvement that a student could really benefit and stay busy the whole summer.

The framework for product exporting would be great. Thoughts tossed around over lunch included being able to specify a format submitted with a structured array that would be parsed to build out the export. For example, specifying XML and then passing in an array with key/value combinations that are used to build elements and fill them w/ data. This, too, could be a boon to the project and a good experience for the student.

I think the dynamic attributes item may be a little thin on material for the whole summer. It would be great to have dependent attributes and options affecting product images, but this one seems like it would be the most difficult to spec and stretch out over a summer. Definitely open to discussion here.

I'm not sure all your thoughts on the store interface and help system, so I won't directly comment here.

Lastly, I think one possibility we mentioned that didn't get listed was a robust discount system that could be shipped with core. This would be dependent on the conditional engine which I didn't get the chance to sketch out on the plane. Spent my first flight chatting w/ a businessman and gleaning some of his wisdom and my second flight falling asleep while trying to wait for a glass of water.