Don’t Believe Everything You Think.
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.
In a world where innovation is only accelerating, shackling employees with non-competes doesn't make sense anymore. At Acquia, we believe that innovation is about openness and collaboration, and that working together is based on trust and loyalty, something that was born out of our Open Source background. It's been a long time coming but we decided to kill our non-competes. It is the right thing to do. Here is what we just sent to all Acquia employees:From: Tom Erickson <firstname.lastname@example.org> To: Everybody at Acquia Date: Friday, May 2, 2014 Acquians, We have an amazing team, it's the thing I am personally proudest about. When asked by others what's the best thing about our company, I don't hesitate to answer "our team". There are many things to value in each of you, from your commitment, your integrity and certainly your passion! The goal that Dries and I have always set was to have a company where everyone is challenged, has the opportunity to grow and has some fun along the way. Most of the time we're successful at that as a company, though sometimes we fail. Yet even when we fail, we want everyone to continue to do the right thing and sustain mutual respect. To this end, the exec team has decided to eliminate non-competes from our employment agreements. We believe its the right thing for our team members, for the company and for the industry. There are many reasons why companies have used non-competes in the past, but we believe that times have changed and individuals today value the companies who value them. This may seem contradictory .. "value me, but let me go to a competitor" .. but we believe that a company who respects our team members in this way will actually be a better magnet for talent. While we are getting rid of non-competes, we are not eliminating other terms, notably the non-disclosure. So while we do not want to restrict free movement of talent, it's important that company confidential information remains just that, confidential. We do not plan to change existing employment agreements, as that would be an administrative burden, and we have many other issues to deal with. This email should suffice as an assurance that existing non competes below the executive leadership level will not be enforced. All new hires, with certain exceptions at the executive level, will not have non-competes. Viva Acquia! Tom