(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.

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.

from what I've gotten from Angie and Gordon, the SoC proposal isn't supposed to be -that- detailed. All they want is a list of things you wanna work on. If accepted, and apparently 'drupal and ubercart is awesome' is about all you need to get accepted, then you spec out the details and examples for the students to work on.

However, I've added some examples of things that could be improved for uc_2.0 for the various sections. Yes some of these are very small, and would only take a week or two to complete. While other things like UI research and implementation could take up to a month to finish.

I striked out the rules engine for now because it looks like fago has something coming down the pike, and updated his blog today about it. Lets hope to see something come out soon!

I edited the UI to indicate that the orders admin is just one section example of where UI changes would be nice. Ubercart does the best job of doing inline editing, much better than ecommerce... however, there are a few places that definitely could use some improvement.

I didn't add quickbooks, ebay, etc to this project because I thought that might be a little to specific, but I can add it as an example.

The main point is that a project proposal is due in 24 hours (March 12 at noon PST), so we need summaries of ideas around the project. We can hash out the details later.

I dig... I have nothing against using g.d.o and check it every day as is. I was just trying to have the internal "what should we propose" from our side done out of their way and then just present to them fuller proposals that they could interact with. I'm not sure we'll be porting the whole community to g.d.o, but I'd be more than happy to have any discussion related to SoC take place over there.

My original thought was Mike would take point on this, as he seemed to raise the issue first. If he's not able to due to time, you'd be my second choice, and I'd be my last choice.

I just want to make sure that if we're asking for inclusion in the SoC, we're doing it well and conforming to their desires for project scope, specificity, and follow-through. Perhaps we can chat on #ubercart tomorrow to nail down a couple legit, full proposals and stick them up for review on g.d.o? Or is there a specific channel for Drupal SoC that we should hold the discussion in?

#drupal-ubercart sounds just as good to me. I'd hate to split folks over two channels, so we should probably stay on #ubercart until I can get a reply from gurpartap.

Folks needn't read into names too much... gurpartap setup #ubercart ages ago. I'm as committed to integration with Drupal and d.o as anyone else.

Rock on... well, you can hold onto ownership as far as I'm concerned. Thanks for registering it. I'll update the book page at Drupal and make sure I list #drupal-ubercart here on the community page.

I don't think that would meet the soc requirements. The ideal project is something that requires new engineering, and new functionality. I don't think site integration stuff would really apply. The only thing we might be able to work on is a way to share nodes & comments between separate drupal instances. So you could map ubercart forum threads to g.d.o groups.

webchick has accepted the updated ubercart proposal into d.o for the official list:

http://drupal.org/node/237902

Time to get ready for SoC!

As well as to bump the thread. Feedbacks and suggestions for my proposal will be much appreciated.