Strange pleasures are known to him who flaunts the immarcescible purple of poetry before the color-blind.
In a massive Cathy Theys double-header this week, hear parts rescued from our conversation at SyfonyCon Warsaw, which was plagued by technical difficulties and check out Cathy's insightful session, "Patch Reviews: Get good reviews, give good reviews. Faster." It is full of practical advice to take your contribution to Drupal and open source software to the next level. In the podcast interview, we talk about the opportunities Drupal has given Cathy; some of the benefits of the refactoring that has gone into Drupal 8; joining up with the Symfony community: mutual learning, different styles of contribution, Drupal's new relevance; and the business case for open source contribution and sustainability.
The Drupal Media team will be sprinting all week at DrupalCon Austin!
- Saturday May 31 to Monday June 2: Large Scale Drupal event and general community sprints.
- Tuesday June 3 to Thursday June 5th: Coders lounge
- Friday June 6th: The official contribution sprint day, where all people are encouraged to attend, no matter the skill level.
All of the sprint tasks are visible in our DrupalCon Austin Trello board which we and all the sprinters will be using to coordinate efforts and progress all week. If you would like access to this board, see Dave Reid (and make sure to sign up for an account on Trello).Sprint Areas Drupal core issues
This team will be working on any Drupal core issues tagged with "Media Initiative".
Some specific issues we'd like to tackle in Austin:
- #1399846: Backport the make unused file cleanup configurable to Drupal 7.
- #2128791, #2148353, #2078473: Ensure that file entities use a proper access controller and is used for hook_file_download().
- #1308152: Add module://, theme:// and profile:// stream wrappers to access system files
The modules we are working on:
This team will be working on the following in the hopes to be able to release 7.x-2.0-beta1 versions of the primary Media and File entity modules.
- Media module issues tagged with "7.x-2.0 beta blocker"
- File entity module issues tagged with "7.x-2.0 beta blocker"
We use a Trello board to organize the tasks for DrupalMedia.org.Sign up!
Make sure to sign up on the Sprint attendance availability Google spreadsheet under the 'Drupal Media Initiative' section, if you plan on attending any of the days.Not going to be in Austin?
No problem! There are still several ways to participate. We will all be in the #drupal-media IRC channel during the sprints and would be more than happy to help assign issues to work on or point people in the right direction.
We also will gladly accept your Drupal Media user story submissions as we start to finalize our plans and development for Drupal 8.Tags:
The ORCID API module aims to act a library to provide integration with the ORCID repository using the public and private apis (for claiming and provisioning purposes).Features
- Claim existing ORCID.
- Search and claim ORCID based on search criteria (such as email).
- Provision and claim new ORCID (if you have access to Member API).
Configuration functions for the module allow an ORCID member with a Creator membership to enter ORCID credentials. (Please note: this will not be useful for a Trusted Party ORCID membership.)
Next week, ten members of the ThinkShout crew will ship out to Austin, Texas for DrupalCon 2014. This is our largest delegation yet and we couldn’t be more excited about it! We’ve got Drupal 8 on the brain and we’re sure you do, too.
If you plan on attending DrupalCon in Austin, we’re always down to talk shop - or not shop. We’ll be all over the place during those four days, but here’s where you can find us:Exhibit Hall
We’ll be sharing booth 508 with our partner and preferred nonprofit payment processor, iATS Payments. Stop by! We’d love to talk to you about the exciting work we’re doing with the iATS Drupal Module. Dan Ruscoe himself will be available to discuss his work.Official Sessions
“Student, Counselor, Advocate: The Many Hats of Content Strategists ”
Room: 16 - Pantheon, 4th Floor
Brett Heckman and Brett Meyer will will provide you with some valuable techniques to help you facilitate a great discovery process.Birds of a Feather (BoF)
The ThinkShout team will be leading a great variety of BoF sessions next week. Join in the conversations - we want to hear from you!TUESDAY:
Title: Leveraging Salesforce with Drupal with Tauno Hogue
Room: 8A - JustDigital | 3rd floor
Time: Tuesday, 2:15-3:15pm
Title: Unmoderated Small Sample User Testing with Brett Meyer (@brett_meyer) & Sean Larkin (@sean_larkin)
Room: 10A - Ashday | 3rd floor
Time: Tuesday, 2:15-3:15pm
Title: Static Site Generators & Wireframes with Eric Paxton & Brett Heckman
Room: 8A - JustDigital | 3rd floor
Time: Tuesday, 3:45-4:45pm
Title: Building Your Drupal-Based Business: What Keeps You Up at Night? with Sean Larkin (@sean_larkin) w/Chris Wolz (@cwolz) of Forum One (@forumone)
Room: 8B - Unicon | 3rd floor
Time slot: Wednesday, 10:45-11:45
Title: Email Marketing with Drupal with Lev Tsypin (@levelos)
Room: 10A - Ashday | 3rd floor
Time: Wednesday, 3:45-4:45pm
Title: Nonprofit Fundraising with Drupal with Lev Tsypin (@levelos)
Room: 8C - VLM | 3rd floor
Time: Thursday, 10:45-11:45am
Title: Leveraging Drupal Commerce for a Nonprofit Payment Provider with Dan Ruscoe (@danruscoe) and Stephen Bestbier of iATS Payments
Room: 8A - JustDigital | 3rd floor
Time slot: Thursday, 1:00-2:00pm
Title: Discovery Workshop with Brett Heckman & Brett Meyer (@brett_meyer)
Room: 10A - Ashday | 3rd floor
Time: Thursday, 1:00-2:00pm
If you can’t make it, no worries. Get in touch with us and we’ll be happy to fill you in one what you missed. Twitter, email, carrier pigeon, whatever works for you. To those of you Austin-bound, we’ll see you there. Bring on the breakfast tacos!
The new rideshare platform Lyft is offering a special deal for DrupalCon Austin attendees. Conference attendees can download the Lyft app and get 2 weeks of free rides up to $25 per ride. If you enter the code "DRUPALCON" before your first ride, you will receive an additional free ride up to $25 (which can be used in any of Lyft's 60 other existing cities).
VAT can be nasty. Think you have a cart full of products with different tax rates.
Now what about tax rate for discount or shipping? One solution is to have tax rates proportional to tax rates in the cart.
This module makes this possible but currently needs some patches from #2276227: [META] Use order discount with VAT.
It was made for order discounts. Feel free to submit patches for other use cases.
DrupalCon is an international gathering of the most influential developers, designers, business owners, and decision makers in the Drupal world. This year, the US event is bringing the Drupal community to Austin, Texas. It’s going to be a hot one, but there will be plenty to do, see, and learn during the days in the air-conditioned Austin Convention Center.
We’re proud to be a Gold Sponsor of DrupalCon Austin, and will be setting up shop at Booth 310 for the week. So, drop on by to enter a contest, pick up some freebies, chat with our Drupal experts, learn about what we have to offer, and participate in the Propeople BoFs.Propeople BoFs
This year, the Propeople booth will feature an area dedicated to our own BoFs. We invite everyone to stop by and take part in discussions about Drupal with Propeople’s Drupal experts, who will be representing our offices from around the US and Europe. BoF topics are listed below. Be sure to stay tuned for additional topics that come up during the conference by checking back here or following us on Twitter.
Regression Testing with Drupal/PhantomJS
Tuesday, June 3 | 2pm to 2:30pm
A discussion on how to use Drupal/PhantomJS to perform automated regression testing, demonstrating a quick proof of concept (POC). Led by Chang Xiao, Propeople’s East Coast Director.
The City of Copenhagen
Tuesday, June 3 | 3pm to 3:30pm (Tech focus)
Wednesday, June 4 | 3pm to 3:30pm (Business focus)
The City of Copenhagen and Propeople are working together on the biggest Drupal setup in northern Europe. Martin Kristensen (from The City of Copenhagen) and Jens Beltofte (CTO, Propeople Denmark) will be discussing the unique challenges and opportunities presented by the use of Drupal on a large scale - particularly as it relates to a municipal government application.
Drupal UX Improvements with the PP Profile
Wednesday, June 4 | 2pm to 2:30pm
Yuriy Gerasimov, Senior Drupal Architect, will lead a discussion about PP Profile (https://drupal.org/project/pp) and the ways that improves the user experience for Drupal site adminsitrators and editors.
Tags: DrupalConCheck this option to include this post in Planet Drupal aggregator: planetTopics: Community & Events
We recently celebrated the launch of San Mateo County‘s new and improved web platform using Drupal and OpenPublic. The San Mateo County digital team had a vision of a new web platform that would accommodate all departments with intuitive administrative functions as well as a well designed end user interface to efficiently deliver information to the County’s citizens. We new we could deliver this with our Drupal distribution OpenPublic. OpenPublic is an open source distribution built with Drupal, developed to address commonly recurring challenges faced by Government agencies when managing their web content. With the successful launch of the San Mateo County platform, I finally got the chance to sit down with Beverly Thames, Content and Collaboration Manager at San Mateo County to chat about the web platform redesign and OpenPublic, here is out Q&A:
Q: What was is the goal or mission of the San Mateo County digital presence and why did you need a redesign?
A: Between departments and central IT, the website was a multi-million dollar per year enterprise, and yet, County leaders were dissatisfied. The site failed to meet their needs or the needs of the public. Two goals of the redesign were to lower costs and provide better service to our departments and site visitors. We wanted to improve communications and to reduce or streamline in-person office visits.
We had major challenges with our old proprietary content management system’s inflexibility and highly technical nature. This made it difficult for departments to produce content and to organize that content in a meaningful way. The result was that much of the content grew stale while vital “evergreen” and fresh content was difficult for visitors to find via search or the site’s menus. Beyond these functional shortcomings, the frustrating user experience on the CMS was made worse by the outdated visual design, which displayed poorly in most modern browsers–especially when viewed on mobile devices. Overall, the sites did not communicate the San Mateo County or department brand very well, a situation compounded by the sites’ outdated content features. It was time for a change.
Q: What were the challenges and needs for San Mateo County’s digital presence and how did OpenPublic address them?
A: We chose to build our site on OpenPublic because it is tailored to the needs of government. County leadership could only be convinced to adopt open source if they were assured the system was secure and accessible. OpenPublic delivered both.
Each department’s identity and requirements are tied to their lines of business and the communities they serve. The County departments wanted to maintain their unique identities within the overall County brand. OpenPublic allowed the County to maintain a strong central brand while meeting user demand for autonomy and flexibility.
Q: Was using an open source platform an important factor in choosing a new content management system? If so, why?
A: San Mateo County was spending too much on annual licensing fees for a proprietary content management system that no one liked. There was little user support, and few developers knew the CMS, so when you could find one, their rates were high. Open source comes with a global community of support and many talented developers.
Open source is a natural solution for the government sector because we are constantly sharing our work with our peers and the public. Adopting an open source CMS allows the County to benefit from and contribute to the continuous improvement of the platform within the context of a larger user community.Q: What is next for San Mateo’s digital presence?
A: Now that the site has been up for a few months, we will start digging into the analytics to see where we need to tweak search and to help us identify topics for curated pages. We’re also excited about exploring potential integrations with our Open Data portal, GIS mapping and enterprise content management.
Learn more about San Mateo County’s new Drupal platform in our Portfolio, and get a deep dive look at how we developed an improved search functionality to better serve the County’s constituents. If you are heading to DrupalCon Austin next week, don’t miss our session “Drupal For Gov- Raising The Bar With OpenPublic.”
In the past 8 years, we've had the privilege of working on some amazing high-profile projects. We helped extend the reach of Drupal, building some of the earliest household name Drupal websites including projects for MTV, Sony Music, FastCompany, WWE, Martha Stewart, Harvard University, and many more. Late in 2012 we were approached about what would become one of the most ambitious projects we've ever launched.
Today, I am ecstatic to announce the launch of our new, Drupal 7 Mediacurrent.com site. It has been a long time coming, and I am incredibly proud of the team for building a website that reflects our strengths and new direction.Buyer Personas Influenced our Strategy
To start the process, we reviewed our buyer personas. Frankly, some of our messaging and positioning had become outdated. Once we updated our personas, we built our content strategy, wireframes, and visual design around the needs of our target audience.
Similar to "This Week in Drupal Core", the relatively new Documentation Working Group (DocWG) is trying out a new communication strategy: an approximately monthly post on what is happening in Drupal Documentation. We'll be posting this both to the Core and Documentation groups on groups.drupal.org, and because it is posted to Core, comments will be disabled by policy.
If you have comments or suggestions, please see the DocWG home page for how to contact us. Thanks!Notable Documentation Updates
- Numerous people worked on updating Drupal 8 API tutorials: https://drupal.org/developing/api/8
- hatuhay and others wrote documentation for the "League" contributed module: https://drupal.org/node/2217333
- Darren Oh and others wrote and updated documentation for the "Salsify" contributed module: https://drupal.org/node/2235183
- dnsopek and others wrote and update contributor documentation for the "Panoply" contributed module: https://drupal.org/node/2271003
See note above on Suggestions if you'd like to be listed here in our next post!Thanks for contributing!
Since May 1st, 206 contributors have made 783 total revisions to Drupal documentation pages on Drupal.org. Wow, thanks everyone! 7 people made at least 30 page edits each:
- Darren Oh (49 revisions)
- tvn (44 revisions)
- jhodgdon (44 revisions)
- lolandese (34 revisions)
- xjm (34 revisions)
- danylevskyi (31 revisions)
- drupalshrek (30 revisions)
In addition, there were many many commits to Drupal Core and contributed projects that improved documentation -- these are hard to count, because many commits combine code and documentation -- but they are greatly appreciated too!Documentation Priorities
The Current documentation priorities page is always a good place to look to figure out what to work on, and has been updated recently.
If you're new to contributing to documentation, these projects may seem a bit overwhelming -- so why not try out a New contributor task to get started?Upcoming Events
- https://austin2014.drupal.org - DrupalCon Austin - June 2-6, 2014
- http://openhelpconference.com/ - Open Help, Cincinnatti - June 14-15, 2014
- http://conf.writethedocs.org/eu/2014/unconf-berlin.html - Write The Docs, Berlin - July 19-20, 2014
The DocWG was formed in April, and has been having meetings every two weeks to define how we'll work, and our Goals, Priorities, and Policies. In our first two months of meetings:
- We decided to meet for an hour every two weeks, for the time being.
- We set up communications procedures, which are listed on our DocWG home page.
- We made a definitive list of Goals, which are posted on https://drupal.org/governance/docwg-goals
- We're looking carefully through all of the suggestions and ideas the community has had in the past for how to improve documentation policies, procedures, and tools (and achieve our goals). We will eventually make a list of priorities. This is in progress.
- We've been talking to other individuals and working groups where our goals and responsibilities overlap, such as talking to representatives of the International Drupal community to figure out what our goals and priorities should be in the area of translating documentation.
- We've been updating the section on how to contribute to documentation at: https://drupal.org/contribute/documentation (there is more to be done there)
- We decided not to have a single "documentation team leader", and instead let the DocWG provide leadership
- We are deemphasizing the concept of the "documentation team" (which sounds like you have to be a docs expert or special team member to help out), and are instead trying to promote the concept of having the Drupal community as a whole take ownership of the documentation, and individuals take "maintainership" of parts of the documentation (more coming on that in the future).
- And... We decided to make these monthly TMIDD posts, which I'm putting into action today!
I’ve always loved Open Source. As a college student, studying philosophy and reading Emma Goldman and Mikhail Bakunin, discovering the Debian/Linux community was an affirmation of the ideal collaboration possible between humans. I made Debian my chosen distribution of Linux and ran off of the Sid repository because I had newer hardware which needed experimental drivers at the time. Sid is the codename for the unstable distribution of Debian where the initial heavy development happens, where packages are released first. I watched with every apt-get dist-upgrade as a tireless open source community labored to make it all work. New features every day, new fixes and sometimes new bugs, only to be followed again by new fixes.
Nobody had to be doing it. They just did. They just wanted to. They were making it work for them and it was working for me. It was beautiful.
There is something about solving problems that is really enjoyable. Solving them in collaboration with other people is even better. It is a mode of being that is truly rewarding and intrinsically valuable. In software development, there is a solvable problem at every turn and instant gratification when the 1s and 0s align. Doing this in collaboration with others is more than just gratifying. As if the strategy of collaborating to survive and thrive is innate to us; it triggers a sense of belonging to something greater than ourselves.
As I later fell into a career as an IT consultant, I stayed very close to open source. There was no doubt in my mind that whatever the answer was going to be, it was going to have open source in it. This was when Drupal started taking off like a wild fire. As if designed for collaboration, it seemed the entire open source community was looking to Drupal as its solution to the world’s content management problems. Drupal code was easy to share, fix and contribute back. As the community grew, so did the collaboration. My company started doing projects in Drupal and contributing our work back to the community. Not only was this rewarding to everyone involved, it also rewarded my company with new incoming billable projects. It was basically a “Pipeline for the Soul.”***
Running a business can be hard. There is no promise that anyone will need your help ever and you only stay in business as long as you are needed. The upcoming batch of work is your “pipeline.” While waiting for people to call for help leaves too much to chance, keeping that pipeline full while doing your current work can often seem an impossible task. In the web development business, one option is to respond to as many formal Requests for Proposals as possible. You win a few here and there and hopefully stay in business. It is a well known fact that responding to Requests for Proposals is time consuming, demoralizing, and it basically completely sucks to do. With Open Source, there is another beautiful dynamic that makes for a truly healthy pipeline of upcoming work.
A healthy pipeline is not only one that is full. A healthy pipeline is one that fills in naturally.
Consider the current state of Drupal as an open source community. There are community organized elements within it that create the kind of pipeline I am describing. These are Camps, Conferences and Community Involvement.
Rob and I are starting to prepare for our trip down to Austin, Texas for the 2014 North American DrupalCon. It is here we will be looking forward to getting some face time with people we’ve been collaborating with, solving Drupal problems with, over the internet on a regular basis. For us, the primary goal of conferences is not lead generation. That’s not how this works for us. We go to the conferences for the community and for the in-person collaboration and community presentations (sometimes given by us). We know from experience that our involvement here will help take care of our lead generation on its own.
Here is the path we've watched our clients follow on their way to engaging their first project with us:
- Seeing us at Camps and Conferences
- Seeing our Community involvement
- Finding our Drupal Marketplace page
- Visiting our Website
- Downloading our Sales-y brochure thingy
- Contacting us by phone, form, or email
We’ve realized that the first two stops on that list are who we really are. We love the collaboration and the learning and sharing of knowledge at the Camps and Conferences. We love the involvement of contributing back work to the same community pool of code we benefit from. It simply just feels good. While the next three are a presentation of who we are (with the last one being engagement), the beautiful part to us here is the experience that we stay in business to the degree in which we stay authentic to who we are. Doing the things we love and being ourselves fills our pipeline.
We’ve also realized that these first two steps to engagement are not only self-sustaining but have a strong positive impact on the health of our team. This is due to the personal motives in play in the type of participation involved. Open Source software is inherently inclusive and collaborative. The vast majority of participation is driven by intrinsic motives for personal growth, relationships, and helping others. It is an endeavor that creates actual happiness, dedication, and community. To do this as a team is invaluable. Doing this as a society is our best work.
Welcome to the 4th instalment of an 8-part blog series we're calling "The Ultimate Guide to Drupal 8." Whether you're a site builder, module or theme developer, or simply an end-user of a Drupal website, Drupal 8 has tons in store for you! This blog series will attempt to enumerate the major changes in Drupal 8. Successive posts will gradually get more technical, so feel free to skip to later parts (once they're published) if you're more on the geeky side.
Jonathan Sims is Assistant Professor of Strategy at Babson College. A 2013 PhD graduate from the University of Texas at Austin, he wrote his dissertation on entrepreneurship within Drupal.
Over four years ago, as a 3rd year PhD student at the University of Texas at Austin, I made a risky move. I asked my advisors, all hard-core researchers, to foot the bill to send me to SXSW Interactive. I told them that “Interactive” was the future of SXSW, a conference that at the time was known far more for music and film. I needed a dissertation topic, and argued that the conference that birthed Foursquare and Twitter was a great place to look. They took the bait.
At the conference, I attended a session entitled, “Selling the Milk when the Cow is Free.” Several of you were there. It was my first introduction to open source business models. The panel spoke eloquently about the business benefits of “giving back” and “riding the community wave.” For a student of strategy, these were almost heretical ideas. Dominant strategy theories emphasized the “resource based view,” arguing that companies should protect, even at great cost, whatever resources they had that were valuable, rare, or difficult to imitate or substitute.
Here was a room full of entrepreneurs succeeding by doing the opposite. I’d found my dissertation topic, and a new friend – for on that panel was Palatir’s Tiffany Ferris, who told me I “must go” to my first DrupalCon in San Francisco. Four DrupalCons and a Drupal-themed dissertation now behind me, I continue to research the novel business ideas that make Drupal firms so successful.
Over the next several weeks, I’ll be sharing those research findings in a series of posts.
In the next post, I’ll reflect the main findings of my dissertation, which was made possible thanks to the support of the Drupal Association and the 250 organizations that completed the Drupal Business Survey. If you’re interested in reading more about the results of that survey, I’ve worked with a talented team at Palantir to make a formal report available for download.
Later this year, I will be launching another Drupal Business Survey in partnership with the DA. We’re still putting on the finishing touches… and in the spirit of Drupal, we’re asking what you would like to know. What research questions do you have for entrepreneurs in the Drupal community? Send you suggestions to me at email@example.com or tweet me @jonsims.
Next Up: Four “So What” Research Findings about the Drupal Community
The Acquia Cloud API is a web service and CLI that allows developers to build powerful tools, automate repetitive tasks, and create custom development and testing workflows for sites on the Acquia Cloud platform. Released two years ago, our customers and partners have been building amazing things on Acquia Cloud API and we figured it was time to share some of them.
This module allows you to add a proportion to taxonomy terms when attached to an entity (node, user, ...). This helps you to weight the term used on a single basis without loosing the power of taxonomy and its core integration with vocabulary or term page, views, ...
2 widgets are available : autocomplete (with term creation) and radio/checkboxes
field prefix (like € or $) or suffix (like %) can be used
a formatter that allows you to display the term after or before the proportion.
the module has been designed to work with views