Art is a lie that enables us to realize the truth.
In our monthly training newsletter I’ll present you with news and helpful links to Drupal tutorials. I keep on finding great tutorials I want to share, and tell you about all that’s going on with the training program. So please do Sign up to our training newsletter for notifications about webinars, freebies and tutorials.
The monthly Drupal core bug fix release window is this Wednesday, and since it has been a while since the last one, I plan to release Drupal 7.28 on that date. However, in practice the release might not happen until Thursday, to give people a bit more time to test the latest code. Per our release policy, this will be a bug fix release only (no security fixes).
The final patches for 7.28 have been committed and the code is frozen (excluding documentation fixes and fixes for any regressions that may be found in the next couple days). So, now is a wonderful time to update your development/staging servers to the latest 7.x code and help us catch any regressions in advance.
Drupal 7.28 does not have any new features or API changes that are large enough to warrant an official change record, but there are numerous significant improvements, including:
- A change which should make the Update Manager module more reliable about reporting correct information about security updates to site administrators. This change has some possible performance implications though, so we're particularly interested in any testing and feedback on the drupal.org issue: "No available releases found" - fetching update information exceeds timeout.
If you do find any regressions, please report them in the issue queue. Thanks!
Upcoming release windows after this week include:
- Wednesday, May 21 (security release window)
- Wednesday, June 4 (bug fix release window)
Wow, what a couple of intense weeks for the Drupal 8 initiative for porting Search API. There were many improvements made lately and we hope to properly explain them all to you but for now I want to shout out a couple things. First and foremost I want to thank everyone in the community and especially Intracto because because of all of you we were able to reach our intended goal to help the funding of Search API for Drupal 8! We managed to raise 20% more than expected, which means we raised $2400!
As explained in the drupalfund.us project, this is intended to organize 2 sprints and to help drunkenmonkey to spend time during business hours on Search API without going bankrupt. This means that 60% of the raised money will go to Thomas (Approximately $1300) and the rest will be used (approx $1000-$900) for organizing 2 Sprints and help other community members to join these events.
The next sprint will be held at the Intracto offices during the 13th till the 15th of June. Intracto has been so kind to not only sponsor the project with money but also offer their location as a sprint location for 3 full days.Location
Intracto Group nv
13th till the 15th of June (Friday till Sunday)Accomodation
To be defined. We'll update this as soon as possible!Joining?
RESTful module is a new approach to providing a REST server in Drupal. Its concepts and philosophy appears in the module's README so I won't repeat it, but I'd like to go over some of the key points.<?php // Handler v1.0 $handler = restful_get_restful_handler('articles'); // GET method. $result = $handler->get(1); // Output: array( 'id' => 1, 'label' => 'example title', 'self' => 'https://example.com/node/1', ); // Handler v1.1 extends v1.0, and removes the "self" property from the // exposed properties. $handler = restful_get_restful_handler('articles', 1, 1); $result = $handler->get(1); // Output: array( 'id' => 1, 'label' => 'example title', ); ?>
In the past year almost every site we have is either completely decoupled from the server side where AngularJs serves the webapp, or AngularJS plays a smaller part, and we just embed web components inside a Drupal page to provide a slick UI.
Up until now our go to module was RestWs by the wonderful Klausi, which wraps around Entity API module's metadata wrapper. Basically, it hands over to the metadata wrapper the responsibility for the access and for the actual value it spits out.
It works fine, however the JSON it exposes has too much information.
I had a task. It seemed simple enough. It involved a link field with a title and a url (created by the Link module) and a single on/off checkbox field. The checkbox was a toggle for whether the link should open in a new browser tab/window.
Last summer, we created three Drupal.org working groups: one for content, one for software, and one for infrastructure. Since then, Working Group members have put countless hours of time and energy into making Drupal.org the best it can be! Now that we’re winding to the end of our first year with the working groups, we’d like to announce small changes in membership. We have two new members joining the Drupal.org Software Working Group!
Drupal gurus Cathy Theys (YesCT) and David Hernandez (davidhernandez) will be bringing a fantastic array of skills and experience to the DSWG. David has great perspective and a background that will help encourage strategic-level thinking within the Working Group; and, as many of us know firsthand, Cathy has tons of experience coordinating volunteers and directing volunteer energy on Drupal.org. Both Cathy and David are trusted members of the Drupal community, and will help us carry out our decisions and make Drupal.org better than ever.
The seats that Cathy and David are filling were recently vacated by Kim Pepper (kim.pepper) and Melissa Anderson (eliza411), who decided to step down and focus on other projects. We’d like to thank both of them for their time and effort, their participation in the Working Group all these months was invaluable. Though we’re sad to see Kim and Melissa go, we’re thrilled to welcome David and Cathy on board. Welcome to the Drupal.org Software Working Group!
This deck accompanied my talk at DrupalCamp Toronto on April 2, 2014 - which related experiences using Drupal as a framework for developing SaaS solutions.
The gist of the talk was that Drupal's flexibility for theming and interacting with other software (through its API and Services like JSON) in combination with its modular scalability really empower software designers to test hypothesis' through rapid prototyping using Drupal. Additionally, now that cloud hosting solutions like Pantheon exist, which is tailored for Drupal specifically, you don't have to worry too much about implications of growing userbases - prototypes can become actual customer-facing offerings from day 1.
As an example of how we've used Drupal at Design Guru to power SaaS offerings, I talked briefly about the architecture powering a project called GetFilmi (subscription video on demand service for South Asian cinema) which uses Drupal to act as a central content publishing hub which displays video assets from Kaltura and then pushes content to native mobile and tablet apps using Services. From the lessons learnt in developing GetFilmi's architecture we've created a white label SVOD service and I spoke to our vision for the future which would be a truly turn-key offering (taking some queues from another Drupal powered SaaS service called introduction.io we run for creatives around the world to host portfolios.)-->
OK, we finally did it! DrupalEasy Academy is now making our super high value training programs (and all the resources that go with them) available anywhere on the globe via our live online classroom. We are kicking things off on May 27 & 28 with Getting Your Stuff into Drupal, our 8-hour split session workshop delving into the Feeds module on Tuesday (May 27, 1-5pm EDT), and the Migrate module on Wednesday (May 28, 1-5pm EDT). Here’s the best news: the introductory price is just $99.-->
I had the privilege of attending Lonestar PHP 2014 in Addison, Texas a couple weekends ago. It was an amazing event full of amazing people and valuable sessions. For those of you who know me, I typically spend a lot of time in the hallways just talking with and meeting new people, however I did attempt to attend some sessions and the calibre of sessions being presented was ridiculously high. The PHP community that attends these events is really obviously close knit. It was a bit like going to a large regional Drupal event.
The title says it all. I love to travel, meet new people, experience local community and share my knowledge. This is edition 2014.
Pinpoint yourself onto the map if you are interested in any of the trainings, doesn't matter if you are an individual or a company.
If you can host me (couch), show me around your city, and find the venue for training, you will get discounts.
This post was written by Manuela Meier, a member of the organizational team of DrupalCamp Frankfurt 2014, and Senior Manager Software Development at Cocomore AG/Frankfurt.
DrupalCamp Frankfurt 2014 took place on the 12th & 13th of April atGoethe University in Frankfurt Bockenheim. Organized by volunteers of the Drupal community Rhein-Main and run under the roof of the Drupal e.V., it was the first Drupal camp in Frankfurt, which meant there was lots of work to do in advance. We, as the organizers, were really nervous and excited, and hoped that everything would run as planned.
We had about 200 visitors, and our plan to make it an international camp worked out quite well: The attendees came from 16 countries all over Europe and even from overseas. We had 35 sessions in 3 to 4 parallel tracks, and the majority of these sessions were held in English. The number of session proposals was really more than enough, and we had a hard time to decide which ones to use and which ones to drop.
We covered a wide variety of topics, so that everyone from devs to themers to project managers to devops could find a talk that was interesting for her or him most of the time. On Sunday, we even had a fourth room with a track for Drupal novices. There were two beginner sessions, handling basic topics like setting up a Drupal, choosing modules etc. These sessions were visited really well, so thanks to Ronald and Mark for bringing new people closer to Drupal!
We also had keynotes on Saturday and on Sunday. Saturday started with MortenDK presenting “Twig - all the new awesome” and as expected it was a success. People liked it and we're really happy that Morten followed our invitation to our camp. The keynote on Sunday was by Nils Adermann, founder of Composer, and he talked about "PHP Reinvented – How Composer helped shape the new way of writing PHP." This session also was a great choice and a good example that Drupal Camps are not only about Drupal, but also about interesting or innovative topics that are related and relevant. In this context, many thanks to the Drupal Association whose funding also made it possible to invite these great speakers!
Sprinting took place throughout the weekend. On Friday we had a code sprint in the rooms of the Cocomore AG. Quite a number of people that arrived earlier in Frankfurt dropped by and discussed about how to contribute best to Drupal and its modules and it was explained how contributing to Drupal works. Some people were given their first issues on drupal.org to train contributing on real examples. On Saturday and Sunday we had a room reserved in the university for sprinting, and most of the time you could find some people there, discussing, coding and working on Drupal8.
Well, and of course, there were the socializing events. Friday evening we met with other Drupalistas at an Irish Pub for a warmup. It was a really nice evening with many well known faces as well as some new ones. Saturday evening we met for 100L of free beer at the Depot 1899 in Frankfurt, and afterwards we conquered the Clubkeller with 20-30 people. It was a long evening, with many many great people and lots of fun.
In conclusion: The weekend was awesome! As mentioned above, we were really nervous in advance, there were so many things that could have gone wrong. And in the end, we had great sponsors and supporters, 200 guests, so many sessions that we had to choose which we wanted to have, coffee machines, recording, tshirts, badges, everything in time, we had great speakers, the best weather you could imagine and everyone had fun. It's really not too much to say that we all were relieved, happy and excited. The work paid off, and if the attendees liked it as much as we did we'd love to do it again sometime in the future. And probably the 2nd time will be easier.
As already said at other places: Thank you all a lot, you're the best!
On May 2, 2014 the Drupal Core Gittip Team was somewhat quietly launched. There was a helpful quick round of questions on twitter and in IRC, and more details were added to the Drupal Core Gittip Team profile page and the @DrupalCoreGT twitter account. This post is a follow-up with even more details. We hope this answers more questions people have, and continues the discussion.
We are just getting started, so some of this information will probably change as we gain experience and more feedback.
We recognize that the most significant contribution to Drupal has always been and will continue to be the unfunded voluntary contributions of the many. Our hope is that the Team can play a part in making Drupal core development sustainable.
Thanks, Cathy and AlexWho are you?
We are making the world better by working on Drupal Core.
Drupal Core contributors need consistent, reliable sponsorship without having to be experts in fundraising, and would-be sponsors need a central place to contribute that they can have confidence in. The Drupal Core Gittip Team hopes to be part of meeting these needs.
This team is run by Drupal Core mentor and contributor @YesCT and Drupal Core committer @alexpott. Contact us to join the team. We are looking for people who reliably work on Drupal Core and want help meeting their funding goals.
The team is for funding people who are reliably working on Drupal Core. If you are listed in MAINTAINERS.txt or have more than ten core commit mentions within the past six months, then you should be automatically eligible. If you do not meet those criteria but feel you have been contributing reliably to Drupal core, then give more detail about your contributions and the admins will review this. (If an admin rejects membership, an applicant can ask it to be put to all members for discussion and a ballot, with a simple majority needed.)
Over time, members of the Gittip team will be periodically reviewed. Team members who have stopped contributing to core for a significant period of time, or are suspected of abusing the criteria for membership (for example a shared Drupal.org/gittip account) may have their team membership revoked.How much money do members get?
Gittip Teams are set up by Gittip such that each member chooses how much money they claim, starting at max US$1, which they are able to double each week, with new members getting priority. Who receives money and the amount each member receives is publicly available on the members tab on Gittip.
We have set some additional guidelines and will review these over time.What other agreement is there among Team members for deciding who gets how much money?
If your company pays you for all of your time contributing to Drupal Core, please do not also ask to be funded through the Drupal Core Gittip Team. The Gittip team is a way for companies and individuals to support people who are contributing their own time, without compensation, to Drupal Core development.Preliminary claim guidelines:
- (After May 8, 2014) Members when they join are asked to set their claim to US$1/week, when they meet the criteria for reliable Drupal Core work.
- It is ok to be a member of the group and claim less than US$1.
- An initial goal is for members, who have some of their hours working on Core not funded, and want to have it funded, to get at least one hour a week of funds.
- Until we have enough weekly contributions coming in to fund more than one hour for members (who want it, and meet the criteria), please do not set your claim higher than max (US$64, $total_funds/$number_people_wanting_funds).
- When we have enough money to give everyone who wants (and meets the criteria), we will announce letting people claim up to 4 hours a week.
- Members wanting to claim more than US$256 or 4 hours a week, should publish a summary (short: 140 characters) of what they worked on and share it with the team each week. People can up their claims, maxing out at 8 hours a week.
- Vacation? If the vacation is less than 2 weeks (per 20 weeks) there is no need to reduce your claim.
- Members should reduce their claim when they have gone more than 2 weeks with their work funded from some other source.
- Partial reducing is encouraged, if for example they picked up partial funding from other places, but still have some work unfunded.
Currently YesCT and alexpott can add members via the twitter account. Admins are selected by … them volunteering to take on admin responsibilities, and being a member of the group for at least 7 weeks. New admins will be appointed by the current/outgoing admins, when an open admin slot is available.Who are you to try and tackle the funding situation?
We are Drupal Core contributors that have tried to fund our work, have talked with others who have attempted to get their work funded, and are trying to move forward with something we think has potential.What Drupal Core work does this fund?
It funds people who meet the criteria. On receipt of funds people are free to do what they want. This is tip - the work is already done.Why a Gittip Team?
- Gittip because: Gittip can maximise fundraising efforts using a fundraising platform well known to the community - over 500 Drupal people are already there.
- A team because: donors will not have to move their sponsorship as the funding needs change for the people who work on Drupal Core. And people who work on Drupal Core do not have to do new fundraising as their sponsors change.
- We hope the team provides a central, consistent, and trusted space to raise funds for Core development.
- We hope through the community controlled membership the funds are targeted in the best way possible, to those that deserve and need it.
- Core development is driven primarily by individuals working across a large number of different patches/subsystems, as opposed to specific fixed-scope projects. Funds with no specific development targets attached support this.
- Core is bigger and more complex than ever. This is one solution to help individuals continue to contribute time, especially if they are not supported by the company they work for.
- There are individuals and companies who can not donate development time to core this provides a way for them support core development.
Current charter says the DA must not direct Core. This is felt by many to preclude the Drupal Association from fundraising for core development. The Drupal Core Gittip Team plans to work with the Drupal Association on the issue of Core sustainability and funding.What is your funding goal?
US$5000 per week.Why so much?
Depending on cost of living assumptions, that is the equivalent of 2 full time people.Why so little?
Yeah, it will take a lot more than that to make Drupal Core funding more sustainable, but it is a start.Comments
Mon, 05/05/2014 - 14:24Notes about money [moved these comments out of the post and here] Note, since members start at US$1, and can only double every week, it would take 7 weeks before anyone could get to US$64. This gives us more time to think through the claim agreement.
Note, we do not, as yet, have enough money to worry about the following, but this documents some ideas.
Elijah Lynn (not verified)
Mon, 05/05/2014 - 23:00Woohoo! Just pitched in $5/month!
This is great news, I just pitched in $5/month! I will start spreading the word!
Tue, 05/06/2014 - 11:17
In reply to Woohoo! Just pitched in $5/month! by Elijah Lynn (not verified)week ... careful, Gittip is per week. :) Add new comment Your name Subject Comment* More information about text formatsRestricted HTML
- Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd> <h4> <h5> <h6> <p> <br>
- Lines and paragraphs break automatically.
- Web page addresses and e-mail addresses turn into links automatically.