Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

We are planning to include Ecom services in named releases and devstack, starting with Dogwood.

 

 Notes from 7-20-15 Meeting

Ecom in Named Releases

Attendees: David Baumgold (Deactivated) Feanil Patel ClintonB (Deactivated) Renzo Lucioni (Deactivated) Sarina Canelake (Unlicensed)

  • Possible to include as part of full stack
    • pretty small compared to other apps
  • Documentation would be required
    • current documentation sucks
  • biggest challenge is documentation
    • Need two halves of documentation:
      • Open edx oriented - enabling otto &  running your instance w otto
      • Developing on Otto (developer's guide)
  • integration is a few settings & oauth
  • some integration work needed on ops side - Ecom team can handle
    • ansible
  • course administration tool needed in dogwood
    • expected to land in q1 (so no worry)
  • Goal for service is to be available but turned off by default (dogwood)
    • goal: by Eucalyptus turn on by default
      • makes path to deprecate / remove shopping cart, other code, much more clear

 

TODOs and due dates

TODO / JIRA ticketAssigneeDue date

Ecom: get otto into devstack & fullstack (put ecom in devstack - ansible changes)


JIRA ticket TBA		Renzo Lucioni (Deactivated)?
Coordinate documentation work (talk with docs team, generate JIRA tasks)Sarina Canelake (Unlicensed) 
   
  • No labels