paris commerce sprint

26
Paris Commerce Sprint January 17-21, 2011

Upload: ryan-szrama

Post on 22-Nov-2014

1.222 views

Category:

Technology


0 download

DESCRIPTION

The introductory presentation for the Paris Commerce Sprint, January 17-21, 2010.

TRANSCRIPT

Page 1: Paris Commerce Sprint

Paris Commerce SprintJanuary 17-21, 2011

Page 2: Paris Commerce Sprint

IntroductionsState of Drupal commerceRoadmapSprint objectivesInstallation partyFeature presentation and walkthroughBreak into teams

Page 3: Paris Commerce Sprint

5th SprintFeature completion and QA

UI and documentationMarketing

Page 4: Paris Commerce Sprint

Schedule

January 17 : Introductions, teams, getting started!

January 18 – 21 : Morning meeting per team, sprinting January 21 : Review work, communicate sprint results

We will have a Drupal meet-up on Thursday.

Page 5: Paris Commerce Sprint

IntroductionsState of Drupal commerceRoadmapSprint objectivesInstallation partyFeature presentation and walkthroughBreak into teams

Page 6: Paris Commerce Sprint

Current state  • Product

Product types, attributes, administration

• Line item Line item types, line item manager widget

• Order Creation and management, states and statuses

• Cart Add to Cart form, shopping cart orders, block

• CheckoutForm builder, stateful checkout, PCI-DSS aware

Page 7: Paris Commerce Sprint

Current state • Payment

Payment method definition, conditional availability, integrated redirected payment services

• Pricing Dynamic pricing, pre-calculation, basic UI

• Tax Tax rate definition, conditional display

• Currency Support for multiple currencies and conversion

Page 8: Paris Commerce Sprint

Current state

Systems that need to mature in contrib :

• Shipping quotes• Discounts• Coupons• File downloads• Membership / access• Marketplace functionality

Page 9: Paris Commerce Sprint

Current state

Heavy reliance on :

• Entity API - property definition and the metadata wrapper

• Rules 2 - payment, pricing, checkout• Views 3 - admin interfaces, shopping cart block and

form

• Chaos tool suite - unused at present, there for Views 3 • Token - core system, but we need better coverage

Page 10: Paris Commerce Sprint

Current state: Documentation

Current documentation efforts include:

• Inline / API documentation - roughly 28% comments• DrupalCommerce.org handbooks:

o Some system overviewso Info hook explanation / exampleso Using core forms and test classes

• Sparse user documentation

Page 11: Paris Commerce Sprint

Current state: Installation profiles

Major goal of Drupal Commerce has been to enable installation profiles and Feature to easily bundle e-commerce:

• Commerce Dev - developer oriented • Commerce Base - planned base profile

• Commerce Kickstart - planned beginner profile

Page 12: Paris Commerce Sprint

IntroductionsState of Drupal commerceRoadmapSprint objectivesInstallation partyFeature presentation and walkthroughBreak into teams

Page 13: Paris Commerce Sprint

Roadmap

March 20111.0 – Core systems, not feature complete

September 20112.0 - User experience, code refactoring

Page 14: Paris Commerce Sprint

What still needs to happen for 1.0?

Development- Feature completion

Documentation- User interface documentation

Communication- Making a splash at Drupalcon Chicago

Page 15: Paris Commerce Sprint

IntroductionsState of Drupal commerceRoadmapSprint objectivesInstallation partyFeature presentation and walkthroughBreak into teams

Page 16: Paris Commerce Sprint

Sprint: Development

• Entity revisions and log displays • Multilingual / multicurrency usage• Rules / Views / Token integration• SimpleTest coverage• UI design and customer / administrator usability

  *Some developers may be reserved for feature completion.

Page 17: Paris Commerce Sprint

Sprint: Documentation• Installation• Product management• Product pricing• Shopping cart / checkout• Payment method configuration and use (Paypal,

Authorize.Net, CyberSource, etc)• Tax configuration• Order management

Page 18: Paris Commerce Sprint

Sprint: Communication• What is the status and future of Drupal Commerce?

• How can people get involved now?

• What are our emphases at Drupal vs. non-Drupal events?

• Where can users go to find support? What should we do with DrupalCommerce.org? 

Page 19: Paris Commerce Sprint

A success if…..• Drupal Commerce 1.0-beta1

• Development log of issues to finish work

• Outlined user documentation

• Communication plans for before and after DrupalCon

Anything else...?

Page 20: Paris Commerce Sprint

IntroductionsState of Drupal commerceRoadmapSprint objectivesInstallation partyFeature presentation and walkthroughBreak into teams

Page 21: Paris Commerce Sprint

Installation partyAsk for help setting up a local development environment.

Drupal 7.0 + Drupal Commerce (7.x-1.0-dev)

Dependencies (dev versions):• Addressfield• Admin Menu• Chaos tool suite • Entity• Rules 2• Views 3

Commerce Dev - http://github.com/rszrama/commercedev• Install to drupal/profiles/commercedev.

Page 22: Paris Commerce Sprint

IntroductionsState of Drupal commerceRoadmapSprint objectivesInstallation partyFeature presentation and walkthroughBreak into teams

Page 23: Paris Commerce Sprint

Feature walkthrough

• Cart / Checkout customer experience

• Product type configuration and product administration

• Product display and the flexible Add to Cart form

• Checkout configuration

• Customer profile configuration and Checkout integration

• Cart / Checkout integration with Order

• Order administration

• Line item and Customer profile references

Page 24: Paris Commerce Sprint

Feature walkthrough

• Payment configuration and management

• Default Views overview

• Rules integration overview

• Pricing rule creation and pre-calculated prices

• Tax configuration and display options

• Currency support

Page 25: Paris Commerce Sprint

IntroductionsState of Drupal commerceRoadmapSprint objectivesInstallation partyFeature presentation and walkthroughBreak into teams

Page 26: Paris Commerce Sprint

Dividing into teams

Development teams• Entity revisions and log displays • Multilingual / multicurrency usage• Rules / Views / Token integration• SimpleTest coverage• UI design and customer / administrator usability

* Feature completion

Documentation team

Communication team