Snowman

Hey guys! I have a problem. I want to create a get all data REST resource in Drupal 8. I need a request that will display all the data from all the requests. This request will be executed when the mobile application starts . I found this module:
https://github.com/enzolutions/entity_rest_extra, but I don't know the methods to display all the views with content types that I created. Any solution?

At Drupalcon Prague, Jeff Eaton and me presented our 'Install Profiles for Core: We Can Do It!' core conversation.

Vision:

Model:

There's more to share soon, just wanted to let you all know that Snowman lives!

In his Pay it forward article, Sun came with a great idea : let's use the Snowman distribution to organize local groups and meetups.

Since some even say that snowman is dead, this could be a great way to bring it back to life :).

For the beginning, it could be really simple :

• public user listing
  • "fancy" with pictures, with some attributes hidden
• private user listing
  • visible only to members
  • some detail available
  • search

Hi All,

I am using paypal express checkout in D7 but after submitting the order, its redirecting to cart page and the product still available in the cart. The order status is still in checkout. But Payment is successful in my paypal sandbox. Is there any patch for this? Thanks in advance...!

Hi All,

I am using google checkout payment in my D7 site. But once the payment status is changed in my google sandbox, its not affecting the ubercart order status. Its still in the 'Chargeable' state. Can anybody help me to solve this issue. I want to change the ubercart status to 'Payment Received' once the order is charged in google.

Thanks in advance for all help....!

Please join us for our 1st bi-weekly meeting to discuss issues and progress related to the Drupal 8 Design initiative. The meeting will be held in #drupal-design in IRC.

PST: 11:00 AM
EST: 2:00 PM
UK: 7:00 PM
CET: 8:00 PM

Our first BOF was a last-minute affair at DrupalCon Chicago -- this year we're actually scheduling it in advance! Craziness!

We'll be meeting to talk about the findings from our Snowman 'Discovery period,' the progress of Snowman related core patches for Drupal 8, and the next steps for implementing a working first version of the Snowman profile. Our priorities for the BOF are:

• Bringing newcomers up to speed
• A first stab at the concrete feature list/scope
• Next steps for building against that feature list

If you're interested and will be in London, be sure to attend! If you can't make it, post your questions and/or input on this thread and we'll be sure to bring the issues up at the BOF.

Note: the BOF was rescheduled slightly to avoid several scheduling collisions with related UX conversations. It's now at 15:00-16:00, one hour later than originally scheduled. If you're interested in discussing more Installation Profile and Distribution related BOFs, the discussions about the Build Kit Specification, the Drupal For Churches distribution, and the Drupal and Online Advocacy BOFs are sure to be interesting as well...

Well, then.

It's been quiet for quite some time, in part because I vanished for a while after we started building the demo sites. I've been working on some non-Snowman related stuff for part of that time, but also trying to process some of the things that we've been learning as the different demo sites were built out.

Anyone spotted the demo for the Twenty Eleven theme for Wordpress 3.2 - http://twentyelevendemo.wordpress.com

I think its worth us tearing this apart and looking at the ideas they have bought in, I've only played with it briefly and its pretty nice actually. That said my initial impression was not so favorable (omg this is lame), however the more I play around with and uncover its various features the more I like it.

One thing that was raised at today's presentation/discussion at dcco2011 is: it'd be awesome to have a tutorial which explains stuff. The analogy used was, yes, Drupal is a box of legos but boxes of legos ship with instructions on how to put the little blocks together to build a spaceship.

To scope this discussion - this is about our new core theme for Drupal 8 and who it will serve, and how they will use it.

Its not possible to design and build something that will suit everyone, so we have been working on narrowing it down to identify who might use our new core theme and what their needs might be.

I have expanded on this and tried to think about skill-sets, constraints, features and what type of sites might they be building.

I’m worried that I’m bringing this input to the table much too late for it to be of any use, but what the hey. The Core Conversation session was great, but unfortunately, I was flying majestically through the air while the BOF was happening, and am just now finding time to catch up.

Firstly, I'd just like to bring up a few big picture concerns that kept running through my mind while listening to Eaton's awesome, passionate pitch.

Big picture

Re: Using only core modules

I'm currently working on an R&D site and starting to jot down issues in a google doc, just wondering how this is going to collected and collated and perhaps if there's a format we should follow, or is the plan just to hold the descriptions in the wiki and look over the sites once they are up and running?

What comes next for the Snowman project? At the Drupalcon BoF, we nailed down some clear goals for the project and resolved a number of outstanding questions about purpose and target audience. We could start having arguments and bikeshed discussions about specific features, layout, and so on. But because that's not awesome, we're not.

This page is a group-editable wiki containing descriptions of the Snowman test sites that are being built during the 1-month R&D phase. If you're working on one of these sites, edit this page and post information about it below. Include a descriptive title, your username, a summary of the specific 'User story' that you're building for, and the URL of a demo site if available.

At Drupalcon Chicago, I organized a 'core conversation' about the Snowman (nee Tsunami) project and many of us (including Leisa, Dmitri, Bojhan, Yoroy, and others) met up for a BoF the next day. A couple of really valuable insights emerged and we believe that it's solidified our path forward.

Those of us who've been working on the project for the past couple of weeks, and those who heard about it at Drupalcon Chicago, will notice that this group is no longer named Tsunami. We want to show our solidarity with (and sensitivity to) the victims of the tragic earthquakes and Tsunami that have ravaged Japan in recent days: aggressively promoting a project named after a natural disaster doesn't feel compatible with the spirit of community and care that characterizes Drupal.

If you're interested in helping victims of the disaster, check out this excellent article on Technorati about relief efforts and ways to donate. If you're interested in helping make an amazing core Drupal profile... keep reading!

With Drupalcon Chicago coming up, would it make sense to plan on a Tsunami BOF? If we put a bit of thought into it beforehand, we can go into it with an actual agenda and resolve some questions rather than just engaging in unstructured conversation about the idea, too...

Thanks to @rickvug for kicking off the personas discussion.

I feel pretty strongly that the community owner / site owner and community member / site user are the two most important personas from a priority perspective.

eaton's description of the overall target / use case is:

[tsunami] is currently meant for small groups of individuals who are collaborating on a project and want to communicate with each other, tell the world about their project, and attract other people who are interested in helping. Imagine a small open source project, a local community group seeking to renovate a park, or a club that needs to keep in touch between meetings and attract new members.

I think an addition to this should be some guiding principles:

• the primary usage of this site will be by users
• that is, when choosing between a site building use case and a user-centric use case, Tsunami will lean towards the user-centric use case

When writing these personas for the Tsunami profile I wanted to highlight a few key constituents of "Drupal the product" as it stands today. As much as Drupal is perceived a tool for developers the silent majority of Drupal users are end users. End users are those who consume Drupal: web editors, bloggers, some one creating an account on a Drupal site, the non-profit installing Drupal in a day and so on. When end users choose Drupal they do so because of its strong social features. They also know that Drupal is powerful and flexible, future proofing their site.

We need to look at how we are meeting the needs of these users to pinpoint where improvement is needed. A product should try and anticipate the needs of its audience. Thinking pragmatically, Drupal core already has module such as forum, blog, tracker and aggregator so meeting the needs of a typical community site is an achievable goal.

Other personas are also included. Test driving a pre-configured product should make a positive impression on a first time site builder, showcasing what Drupal can do. This would be a positive outcome but is mostly a byproduct of focusing on end users. We also need to take into account seasoned developers and the diverse use cases of "Drupal the framework". These users will not use Tsunami. The primary concern here will be ensuring that any changes to Drupal core to facilitate Tsunami does not negatively impact other use cases.