At GDC 2015, game dev (and former architectural historian) Demetri Detsaridis examines why devs should think deeply about their workspace, and how they can improve it in order to improve their games. ...
After fifteen years of going from strength to strength, it’s a great time to look back on the Drupal that was and how it became a powerhouse of the open source content management world.
Way back in May 2000 the Drupal GitHub repository was started. In December 2000 Drupal 1.0 was named and since then it has taken over 33,000 commits to build Drupal as we know it today. Thanks to a dedicated community backing and flexible technology, Drupal is now a stable modular platform that is used by over 1.18 million websites. Did you ever think how Drupal got so big? We’re going to take you through this journey right now.
Drupal 1 (Drop)
Drupal 1.0 contained a mere 18 core modules, each driven by a php file. The system relied heavily on SQL to manage and modify content, themes, layout and more. Pre-loaded themes gave web developers a jumping off point, and Drupal allowed developers to hook into existing code and tweak colours, layouts and functionality to their liking. The original system came with some nice basics like a search function, comment fields and a diary/blog functionality.
Drupal 2.0 was released shortly after and come packed with translation features. Developers could now build or translate their sites by altering the database, a feature which opened up Drupal to a global community. 2.0 also brought in improvements to user ratings, stories and a whole host of additional fine tuning to the user access groups, allowing greater control over site development and stakeholder interactions.
Drupal 3.0 saw the introduction of the concept of ‘nodes’, taking over the common idea of web pages. Nodes increase flexible for creating and displaying content. All kinds of content, whether a web page, blog article or news item were managed by the node module. Comments and actions were attached directly to the node which increased flexibility in site building and later changes. The use of nodes instead of pages has become commonplace in mobile development, ten years after Drupal embraced the concept.
At this stage, six months had passed, and Drupal had grown to 26 core modules. In June 2002 Drupal 4.0 was released. Almost 100 major sites were built with Drupal, and a wide community of developers were contributing to the project across Europe and the United States.
Drupal 4.0 introduced the Taxonomy module, taking over from the meta module and giving site builders an entire new toolset for categorising, sorting and marketing their content. With a friendly user interface and a strong community of contributors Drupal 4.0 had moved away from its humble origins and taken a place as an enterprise quality Content Management System.
At this stage Drupal moved to a slower release schedule, with Drupal 4.1 not being released until February 2003, eight months later. Drupal 4 lasted until January 2007, with seven minor releases over four years.
Drupal 4’s minor releases saw a massive expansion of capability, including its first e-commerce module in 4.4. It also introduced its first WYSIWYG (What You See Is What You Get) editor, opening doors for web-writers without a coding background, and offered much more flexible theming options. Drupal saw a massive surge in usage when presidential candidate Howard Dean launched a multitude of interlinked campaign sites using Drupal.
Drupal 5.0 also came neatly packaged in a web based installer saving users from manual database manipulation and allowing the creating of custom packages pre-filled with contributed modules and themes. The backend was tidied up with a whole new file structure, and css files were automatically compiled and compressed, greatly reducing site loading times. Site builders were given the ability to control caching and create custom content types leading to greater performance and customisation.
Drupal 6.0 was released in February 2008 and supported until just last year. At the time that support ended there was an estimated 120,000+ websites still using Drupal 6.0. With 34 core modules, over 7000 contributed modules and 600 custom themes the modular genius of Drupal was undeniable. This new release contained a completely new menu structure that had been written from the ground up, and a friendlier installation process. The community also increased security, brought in more user friendly elements to the User Interface (such as drag and drop administration) and upgraded the language support to handle right-to-left languages.
Drupal 6.0 remained for three years. During this time it was used to host Whitehouse.gov, one of the largest profile websites at the time. Whitehouse.gov is still using Drupal to this day, although they have updated to Drupal 7.0
In 2011 Drupal 7.0 was released and by this stage it is being used by web developers from all walks of life. Small business owners, large corporations, bloggers and government agencies are all using Drupal for its flexibility and ease of use. At this stage there are over 11,000 contributed modules and 200 distributions available, though Drupal Core is kept slim with just over 40 core modules.
Drupal 7.0 saw even greater flexibility with interaction between nodes and modules, allowing any module to call, alter and display any node. Every item in Drupal 7.0 became an individual entity capable of being manipulated and displayed to the user to create a vast flexible website.
Drupal 8.0 was officially released on the 19th of November 2015. It has since been running on a six-month update cycle, meaning we already have access to Drupal 8.3. It comes bundled with over 60 core modules, and one of the most popular contributed modules ‘Views’ is now part of that core module set. Drupal 8.0 users over 60 database tables, but includes smarter tech like BigPipe to keep site load times to a minimum.
Drupal has been running ahead of the curve since the beginning, and with a strong community backing it won’t be stopping any time soon. Drupal’s evolution has always emphasised ease of use, quick site adjustments and a brilliant modular design that means no two Drupal sites are alike. It’s been a long ride to get here, but you can be sure that Drupal will be leading the way for years to come.Drupal Planet Drupal Title: The evolution of Drupal: Drop 1.0 to Drupal 8
The investment management firm Morgan Stanley estimates that Blizzard's competitive Overwatch eSports league could make more than $100 million yearly. ...
Search API revisions module is datasource provider for Search API.
It allows to create indexes based on revisions of any revisionable content entities (for example Nodes, Media, Paragraphs …).
It has same settings and options as content entities datasource (exclude or include languages and bundles).
The staff and board of the Drupal Association would like to congratulate our newest board member:Ryan Szrama.
Thank you, Ryan, for stepping forward to serve the Drupal community. On behalf of the community I also want to thank the 13 candidates who put themselves out there in service of Drupal and nominated themselves. We are grateful that our community has so many brave and generous people willing to contribute this way.
Ryan's election to the board represents the sixth year of elections to a community-at-large seat on the Drupal Association board. Each year we've focused on improving the elections process, and this year was no different. We focused on two goals:
- Improve the user experience of participating in the elections process.
- We added more in-line help materials throughout the elections process.
- For candidates, we added information about the responsibilities of a board member to the nomination form, as well as a video message from the Executive Director.
- For voters we improved the elections navigation, and provided more educational materials about the IRV voting process.
- We implemented a drag and drop ballot, to make it easier for voters to rank candidates.
- We added more in-line help materials throughout the elections process.
- Make it easier to get to know the candidates.
- We updated the candidate profile form, to ask more detailed questions to help voters get to know the candidates.
- Based on feedback from previous years, we eliminated the three virtual meet-the-candidates sessions, in favor of giving each candidate the option to post a statement-of-candidacy video. In conjunction with the question and answer section on each candidate profile, we felt this gave the electorate the opportunity to get to know their candidates at their own pace and on their own terms.
Our next steps will be to reach out to the candidates for their evaluation of the elections experience.
We also want to hear from the voters. Please tell us about your experience with the elections process in the comments below. Your feedback is important to us so that we can make the 2018 elections process even better.About the Elections Methodology: Instant Run-off Voting(IRV)
Elections for the Community-at-large positions on the Drupal Association board are conducted through Instant Run-off Voting. This means that voters can rank candidates according to their preference. When tabulating ballots, the voters' top-ranked choices are considered first. If no candidate has more than 50% of the vote, the candidate with the lowest votes is eliminated. Then the ballots are tabulated again, with all the ballots that had the eliminated candidate as their first rank now recalculated with their second rank choices. This process is repeated until only two candidates remain and a clear winner can be determined. This voting method helps to ensure that the candidate who is most preferred by the most number of voters is ultimately elected. You can learn more about IRV (also known as Alternative Vote) in this video.Voting Results
There were 13 candidates in contention for the single vacancy among the two community-at-large seats on the Board. 1,240 voters cast their ballots out of a pool of 94,499 eligible voters (1.3%). Voters ranked an average of 3.6 candidates on their ballots.
The bar charts below show the vote counts for each candidate in each round.
Place the mouse over a bar to see the number of votes.
- Yellow — Votes carried over from the previous round.
- Green — Votes received in this round.
- Red — Votes transferred away in this round.
A candidate's votes in a round is the sum of the yellow and green bars.
Since the green and red bars represent votes being transferred, the sum of the
green and red bars is the same.
The exhausted bar represents votes where the voter did not indicate a next
preference and thus there were no candidates to transfer the vote to.
Count of first choices.Round 2
Count after eliminating gurubryan and transferring votes.Round 3
Count after eliminating mehuls and transferring votes.Round 4
Count after eliminating zet and transferring votes.Round 5
Count after eliminating Rahul Seth and transferring votes.Round 6
Count after eliminating redacted and transferring votes.Round 7
Count after eliminating MatthewS and transferring votes.Round 8
Count after eliminating Riaan Burger and transferring votes.Round 9
Count after eliminating johnkennedy and transferring votes.Round 10
Count after eliminating jackniu and transferring votes.Round 11
Count after eliminating ok_lyndsey and transferring votes.Round 12
Count after eliminating Prasad Shir and transferring votes. Candidate rszrama is elected.Winners
Winner is rszrama.
I did make one comment on Dries’ blog in the immediate aftermath of learning about the situation which is roiling the Drupal community, but since then have taken some time to listen and ponder. The community is in deep pain now, and many of us are reacting to that pain with anger. Trust is in short supply. Healing seems nearly impossible.
We need to start from compassion for all involved. The pain is deepest for those in the middle. Larry has already expressed his pain eloquently - I know losing the Drupal community would cut me deeply, and pragmatically this is a major blow to his career as well. But, let’s also consider Drupal leadership - Dries, the Drupal Association, the Community Working Group. Regardless of whether we agree with their decision, I see no reason to believe it was done arbitrarily or with malice. Reaching such a decision against someone who has given so much to the community over the years must have been extraordinarily difficult, and the fact that this decision seems to have eroded much of the community’s trust in them is surely agonizing.
We need to recognize and address the asymmetries in this situation. The power in the relationship is unbalanced - Drupal leadership has an ability to affect Larry’s life profoundly that is not reflected. On the other hand, the information is also unbalanced - Larry is able to say what he chooses publicly, but the Drupal leadership has a responsibility to maintain confidentiality. Yes, “confidentiality” can be used as a smokescreen - but there really is a legitimate need to respect it - to protect those who gave evidence to the CWG, and to protect Larry himself from public accusations without public evidence. Transparency and confidentiality are at odds, and it is exceedingly difficult to find a “perfect” balance between them.
That all being said, and recognizing that the information I have is incomplete, my main thoughts on the three parties involved:
The impression Larry’s blog post leaves is that his dismissal was primarily due to BDSM/Gorean practices in individual personal relationships (that certainly appears to be the main takeaway in much of the criticism online). On the other hand, statements from the other side suggest it may have had more to do with broader statements of belief (and commitment to living that belief totally) which seem in conflict with the Drupal community’s values (although it’s difficult for me to be sure of whether they were meant to be taken literally in the real world, or as a form of cosplay - as portrayal of a Gorean character). Just to be clear - although I strongly disagree with some statements I saw, as long as they were not reflected in Larry’s behavior within the Drupal community I don’t see standing to dismiss him (except, perhaps, from representation to the PHP community if it seemed like it might diminish his effectiveness in that role). But, if this was indeed the main issue presented to Larry, I would have liked to see him address it head-on. He does deal with it somewhat in the section “Larry is a proponent for the enslavement of women!”, but the section title itself looks like an exaggeration of the actual accusation, and it is down at the bottom of the accusations he addresses, de-emphasizing it.
I think Drupal leadership needs to tilt the balance at least a little more towards transparency. The community does need to better understand broadly why Larry was dismissed. Dries’ post stated “I did this because it came to my attention that he holds views that are in opposition with the values of the Drupal project”. This suggests that the primary reason for the dismissal was those statements outside of Drupal - I (and many others) feel that what happens outside of the Drupal community, should stay outside of the Drupal community. Then, the DA stated “We want to be clear that the decision to remove Larry's DrupalCon session and track chair role was not because of his private life or personal beliefs... Our decision was based on confidential information conveyed in private by many sources.” This contradicts Dries’ original statement, which is concerning. It also fails to address the central concern many people have - did Larry do or say anything within the Drupal community?
I don’t think the Drupal community has acquitted itself well here. The immediate outpouring has been based on one point of view - admittedly, there is little hard information otherwise, but we should all be slower to react when we know we don’t have all the facts, and lead off with questions rather than diatribes. One thing to be concerned about is that the one-sided onslaught is likely to discourage expressions that disagree with the crowd - anyone who might agree with the Drupal leadership’s decision, or who might know of some concrete reasons they may have made that decision, has reason to fear speaking up. I’m thinking here of GamerGate. No, I’m not saying the people criticizing the decision are like the GamerGaters - but what I am saying is that, given that the center of this controversy is around beliefs and statements that look an awful lot like misogyny, and that much of the rhetoric has carried a whiff of torches and pitchforks, I would not be at all surprised if women (and feminists of all gender identities) felt good reason to fear a GamerGate-like backlash if they did speak up. We need to leave more room for all voices and not flood the space unilaterally.
So, where do we go from here? In reverse order,
The Drupal community is certainly Internet-savvy - we’ve all seen so many cases where based on one piece of information the flamers descend without waiting for fact-checking, the other side of the story, etc. We need to jerk our knees a little more slowly. We need to recognize we don’t have (and will never have) all the information, and the fact that we won’t have it is not in and of itself proof that the decisions of Dries/DA/CWG were wrong.
Drupal leadership does need to tell us more, and I think it can be done without violating confidentiality. Simply put - did Larry’s dismissal involve anything he did within the Drupal community? If they say it did, I for one, am willing to accept it and move on - I’m not in a position to know the specifics (nor should I be), but I recognize this as a legitimate exercise of authority, even if I don’t know if I would have voted the same way if I had seen the evidence. If, on the other hand, this is based purely on statements and actions outside of the Drupal community, it’s important for all of us in the Drupal community to understand that - we all need to know if the DA and CWG will hold us accountable for our online presence outside of Drupal. On that score, I’ve created a separate Twitter account for my Drupal and professional communications under my DBA, Virtuoso Performance. To be fair, I’ve considered doing this anyway just in terms of work/life balance, but now it seems all the more important to keep things separate.
I know it’s a lot to ask - actually, I know that it’s too much to ask and don’t actually expect it, but in the interests of symmetry I’m putting it out there… It would be great if Larry could share (without violating the confidentiality of anyone involved - redacting names and details) precisely what he was told were the specific charges that led to his dismissal. We’re not going to get any specifics from the Drupal leadership side - he’s the only person who can provide us with any hard information. Again, I don’t expect this - Larry has suffered more than anyone here, and has already really put himself out there. Edit: Larry has now responded with more information, which I will take some time to review before making further comment.
Ultimately, while this is a painful episode in Drupal’s history, I hope we can find a way to get through it and come out the other side with a better understanding of each other, and rebuild trust within the community.mikeryan Monday, March 27, 2017 - 10:47am Tags Planet Drupal Drupal Add new comment
Sooper Drupal Themes: New: Customize Glazed Builder With Glazed Theme 2.6.4 and Glazed Builder 1.1.3!
Today I'm excited to announce a new Glazed Builder and Theme release... Imagine having a meeting with your client tomorrow. You've promised your client the ability to update landing pages without needing any help. The client imagines he'll just be changing images and simple text blocks. Then you show him the Glazed Builder Sidebar and it's filled with your custom designed icon boxes, testimonial block, and even custom branded sliders. All accessible and editable without needing even basic HTML skills.Custom HTML Drag and Drop Elements in the Glazed Builder Sidebar!
Adding elements to the sidebar is now extremely easy, you don't need to have a custom module or even any PHP code. You just drop a folder with your custom elements in your theme or subtheme folder and your custom elements will magically appear as editable drag and drop elements. You just to add a class or two to indicate editable portions of your HTML elements and that's it. Of course, you can find all the details and an example zip file in the sidebar elements documentation.Various Fixes
We made various improvements to the Glazed Builder and Theme user experience, details of which you can read in the Glazed Builder Changelog and Glazed Theme changelog. We're ironing out as many little issues as possible while working on the Drupal 8 theme releases!
Need any help with sidebar elements? Just create a ticket in the support forum and we'll try to help you out and simultaneously improve our product to match any expectations you have that we did not think of.
This module extends Simple Hierarchical Select to add more functionalities through the UI. I've created this module because there is an understanding that SHS should be kept simple. However, features that are added by SHS will be removed from this module.
Currently, this module adds the following features to SHS:
Xeno Media: Xeno Media's Michael Porter to present "The Butler Did It: Putting Jenkins To Work For You" at Drupal MidCamp Saturday, April 1
Xeno Media Lead Developer Michael Porter was selected to present The Butler Did It: Putting Jenkins To Work For You at Drupal MidCamp on April 1 in Chicago.
Michael's presentation shows how use the power of Continuous Integration (CI) servers for offloading some of the repetitive tasks developers and software maintainers need to do on a daily basis.
The session will demonstrate how to use Jenkins, the leading open source automation server to:
- Run Drupal core and module updates
- Run and report on behat tests
- Run and report on Coding Standards
- Trigger Offsite backup of production sites
- Use Jenkins Pipeline workflows to build branch/feature based servers.
- Triggering jobs with webhooks
- Report progress, and results to Slack
MidCamp participation is part of Xeno Media's strategic dedication to Drupal and the Open Source community. We have been a MidCamp sponsor for two years and Web Strategist Jim Birch is an active organizer.
MidCamp is imminent, and I'm proud to announce that Virtuoso Performance (i.e., me!) is sponsoring a "Drupal Expert Is In" session Saturday April 1 at 1pm. I'll be in the main room (120) to answer your Drupal 8 migration questions, help you get through any tricky plugin issues, and demonstrate how to approach migration problems. The plan is to make this an open session - to allow anyone interested in Drupal 8 migration to sit around the campfire and learn from each other's issues.
Migrate all the things!mikeryan Monday, March 27, 2017 - 09:55am Tags Planet Drupal Drupal