Most people think that the things they experience are real... But they are wrong... This can be seen as an illusion if we go to a different culture, or if we enter a different reality by going insane.
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!
If you are of a mind to put the party in danger, how about suggesting a stroll across one of the deadliest regions of Mars, the TITAN Quarantine Zone?
Beginning with an explanation of what the Zone is and how it came to be, there are details of the terrain and major features as well as of the measures taken to ensure that the curious stay well out of it. This is intermingled with suggestions as to how these measures might be counteracted, although it will be up to you how you choose to pass on any ideas to your players if they are struggling to come up with their own - this is a book decidedly for the GM!
The hazards of the TQZ are extreme, even without the Patrol ready to pounce on intruders. Extensive jamming of all communication links render not just keeping in touch (or yelling for help) but navigation difficult. The terrain is rugged in the extreme, and prone to dust storms. All sorts of malevolent critters live there and even the artefacts that are the usual reason for anyone wanting to go there are dangerous if improperly handled (in many cases, if handled at all). A random encounter table and full notes on what you might encounter are provided to liven things up a bit.
Various locations are described, as are some of the TITAN artefacts that remain to be found - including quite an array of different drugs and addictive substances. Finally, there's a collection of plot hooks to get the party's interest in an expedition whetted enough for you to get to use all of this on them.
If you like adventures in which the environment is as much an enemy as the monsters, this is one to consider.
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 firstname.lastname@example.org or tweet me @jonsims.
Next Up: Four “So What” Research Findings about the Drupal Community
"The best thing that ever happened to me professionally was being laid off... Here are my guidelines on how you can produce your way out of a layoff." ...
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
Why does a particular type of game start to dominate? "All art is shaped by the economics of a specific time and place. All standardized forms of art are but niches within a socioeconomic ecosystem." ...