Last time I installed Commerce Kickstart I saw a User Agreement but guys, what's up with you? This is not Magento, this is Drupal so please don't use ads in a Drupal distribution. Imagine every module would put ads into a Drupal site, holy shit.

Screen Shot 2013-07-04 at 16.15.26.png

CommentFileSizeAuthor
Screen Shot 2013-07-04 at 16.15.26.png287.95 KByannickoo
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

robertDouglass’s picture

Hi yannickoo,

thanks for bringing this up. The decision to include the content delivery network in the Kickstart distribution was one that Commerce Guys made very carefully, including even having an all-company meeting and getting feedback from many people outside of Commerce Guys.

There are a couple of problems we're trying to solve by including the content delivery network.

  • We want to be able to communicate with developers and merchants using the distribution about new things that come along after they've downloaded and installed Kickstart. For example, the newest version of the PayPal module - included in Kickstart - has some significant improvements and new features. It's good if we can tell people about these things when they're available.
  • We want to be able to provide the latest documentation, learning videos, and Module Tuesday blog posts at the right time and at the right place inside of Kickstart. For example you'll notice that we promote the online documentation for shipping configuration on the shipping screen inside of Kickstart.
  • We want to learn more about how people use Kickstart so that we can solve the actual problems and needs that developers and merchants actually have. The content delivery network is a good way for us to do this because we see aggregate numbers about what pages are the most visited inside of Kickstart, as well as the content topics that people are most interested in.

In deciding how to address these goals we wanted to make sure that we avoided two possible pitfalls that we were pretty sure would anger our community. We wanted to avoid collecting personally identifying or private information, and we wanted to avoid turning Kickstart into a billboard that distracted from the functional aspect of the software. We also wanted to be very forthright about the whole idea and make it clear what we're doing and why. Hopefully, between the carefully designed tips and the placement of the content, as well as the Privacy Policy, and my blog post series on Sustainable Drupal Distributions, we achieved as many of our goals as possible.

If you think we're still missing our mark, just turn off the Commerce Backoffice Content module and the whole thing goes away.

I'm happy to answer any questions or hear any feedback you have about our decisions, either here, or in private mail: robert@commerceguys.com

robertDouglass’s picture

Assigned: Unassigned » robertDouglass
Status: Active » Closed (won't fix)
robertDouglass’s picture

PS it was pointed out to me that the module to disable is Commerce Kickstart DFP (commerce_kickstart_dfp) and not Commerce Backoffice Content.

fizk’s picture

@yannickoo Check out Open Commerce Kickstart:

https://drupal.org/project/open_commerce_kickstart

duppy.ocio’s picture

Issue summary: View changes

#3 worked for me. Thanks!