New York city Drupal camp happened last weekend in United Nations HQ and there was, among numerous other things, Media sprint going on. Organizers did their best to bring some of the most active Drupal Media contributors on-site. We are very happy and thankful that they made this possible, as we managed to achieve some very important steps forward.Plans for Drupal 8
Main part of our efforts at the camp was roadmap for Media in Drupal 8 as part of which we achieved few very important conclusions:
- Storage components: there are still different opinions about the storage part (AKA "File entity" approach vs. "Media entity" approach - for more info check https://groups.drupal.org/node/384813). We decided that this is fine. We will continue to work on both solutions, while trying to find as many sticking points as possible and share as much code as possible. Entire ecosystem will be split into several sub-components in order for this to be possible.
- Decoupled components architecture: as already mentioned we're dividing Media ecosystem into smaller pieces, which will be easier to develop and maintain. We will make sure to make every component as generally usable as possible. This will allow us to use them with both storage solutions and also, when applicable, in more general contexts (not necessary related to media itself). "Full featured" media solutions will still exist, but will mostly provide glue that will make individual components able to work together.
- Media browser/selector/creator: this part of the system will be responsible for browsing media collections, picking and/or creating individual or multiple media items. It will be used in different contexts as fields (entity reference, file, image, ...), WYSIWYG, global, etc. This component will not be related to media by it's nature. It should be possible to use it also in other similar use-cases (browsing and picking nodes for an entity reference field for example). Existing tools/systems should be used where possible (Views for entity browsing, existing field widgets for entity creation, ...).
- WYSIWYG integration: core now supports image embeds by default, but we still want to be able to embed other types of media. WYSIWYG entity embed framework will be responsible for that. It will be able to embed any entity using techniques that were already tested in D7. Entity-specific solutions that we know from D7 world (node_embed, ...) will become obsolete as a result of that.
- Display configuration: we will create two levels of display configuration. Field formatter level will provide more basic functionality, while ensuring simpler interface for site builders and administrators. This approach is expected to be used on simpler sites. Media/File entity render will, on the other hand, provide more powerful display configuration system with more complexity. Both storage solutions will share some parts of display configuration components, but it will not be possible to re-use everything.
- 3Rd party providers: both storage solutions will need own 3Rd party integrations due to fundamental differences in storage implementation.
- Sprint at DrupalCamp Alpe-Adria (May 17th - 20th)
- Week-long sprint at DrupalCon Austin (June 1st - 7th)
- Week-long sprint at DrupalCOn Amsterdam (September 28th - October 4th)
- Week-long sprint at BADCamp (approx. October 21st - 26th)
In order for Media to really rock in D8 we need a lot of help (by this I mean A LOT!). Are you personally interested in media on Drupal or you run a Drupal company/shop and have to deal with funky media problems and desperately need a powerful and extensible solution for that? Are you able to dedicate some of your (or one or your employees) time to achieve that goal?
We need you! No matter which skills you have! We need help with back-end and front-end development. We also need design/UX skills to create good editorial experience. Are you not a coder, but have good ideas? We need those!
You can reach us on #drupal-media or on groups.drupal.org/media. There will be weekly "scrums" held in Google Hangout onAir every Tuesday at 3:30PM GMT (follow groups.drupal.org/media for announcements).We need your user stories
There are as many possible media use-cases as there are Drupal websites. In order to be able to design the system in a way that will work for most possible situations we need your feedback - your user stories. Please take few minutes to think about your past project that dealt with Media and try to remember interesting problems that you'be been facing. Then use our form and send them our way in a form of a user story.Google Summer of Code 2014
We have two quite strong media related project proposals for this year's Summer of code. We are hoping for both of them to be accepted. We will be able to publish more informations about that in the second part of April.Please help Aaron Winborn
Aaron is a long time Drupal contributor, author of many media-related modules and a great and inspiring person. He is fighting ALS and he needs our help. Please consider contributing to his fund to help them make his and his families life just a little bit easier. Thank you!
We would like to thank camp organizers one more time. They prepared an unforgettable event for us. We would definitely not be able to achieve this progress without their support!
For some time we've had a bit of unfinished business around the Drupal Code of Conduct around how we manage and respond to conflict.
The Community Working Group has drafted a policy and is now looking for community feedback over the next 2 weeks. Please check out the draft in the drupal-cwg issue queue.
Seven years ago this month, Dries presented the State of Drupal in front of a few dozen developers at the Open Source Content Management System Summit on the Yahoo! campus in Sunnyvale, California. Drupal 5 had just come out, PHPTemplate was all the rage, and everyone was abuzz about the news that the Nigerian Prime Minister was using Drupal for his blog.
Today, Drupal is used by the President of the United States and nearly every other government on the planet, DrupalCons are attended by thousands of people, and PHPTemplate will soon be replaced by Twig in Drupal 8. The Drupal project and community have grown rapidly in a very short amount of time.
With this growth has come a lot of change, and while our community as a whole has done a great job of embracing that change, our website has struggled to keep up. Drupal.org is full of outdated content, it is difficult to navigate, and it does not accurately or adequately reflect the Drupal project or community to the rest of the world.
In order to address this, the Drupal.org Content Working Group (DCWG) has drafted a roadmap to overhaul the content and design of Drupal.org and to launch a redesigned and improved version of the site in 2015.Who?
DCWG is one of three working groups chartered by the Drupal Association that serve as the collective product owner for Drupal.org. DCWG is responsible for managing the content strategy for Drupal.org, including the overall look-and-feel and voice of the website. The group does not have jurisdiction over the issue queues or project documentation.
For the past 10 months, DCWG has been working quietly behind the scenes to help make Drupal.org a better home for the community, and a better resource for people who want to learn more about the project.Why?
Drupal.org has grown organically since its launch in 2001, relying primarily on content provided by volunteers, with minimal editorial resources or oversight. Even browsing or searching Drupal.org today regularly surfaces posts written back when Justin Timberlake was still a member of N’Sync.
The site’s growing pains were already apparent by 2007, and in his Sunnyvale keynote, Dries challenged the community to improve the experience of using Drupal.org. The result was a redesign that began in 2008, launched in 2010, and is still in place today. This redesign project was a huge step forward for the project and the community, but was limited in scope due to budget and resourcing constraints.
Drupal.org has always been a de facto “hub” for our community, and it should be a truly shining example of everything the project and community has to offer, empowering, connecting, and engage people who work with Drupal or want to learn more about it. Drupal as both a software project and as a community has come a long way in the past few years, and we are better situated than ever before to take Drupal.org to the next level.How?
The plan is to first conduct user research to identify and understand our existing and target audiences, so that we can serve them better. Then we will audit the content on Drupal.org and develop a comprehensive content strategy for the site. After that foundational work is done, we will then have what we need to begin the redesign process in earnest.
This will be a lot of work, and even with the full participation of volunteers from the community and Drupal Association staff, we will need assistance from professional consultants who will help provide us with the perspective and focus we need to make Drupal.org a resource that will continue to grow with our community.When?
In the coming days, the Drupal Association will be releasing a Request for Quote (RFQ) for the user research and persona development component of this project. Our hope is that we will have the opportunity to conduct in-person interviews with a broad range of Drupal users, developers, and evaluators at DrupalCon Austin, in addition to remote interviews with other Drupal users around the world. We also plan to share the results of this research with the community, both online and in person at DrupalCon Amsterdam.
As always, we welcome any questions, concerns, or feedback you might have. The Drupal community is the ultimate product owner for Drupal.org, and it’s important that the work done on the site reflect the values that we share as developers and users of open source software.
Have comments or questions? Join the conversation at https://association.drupal.org/content/reinventing-drupalorg
In early 2013 our fearless and benevolent leader, Dries Buytaert, formalised a governance structure and started a number of working groups for the Drupal project as a whole, and for our home on the Web, Drupal.org.
In 2012 Randy Fay, a longtime and significant contributor to the Drupal project, wrote a series of blog posts articulating some of the challenges of informal governance structures like ours. If you really want to know the full story behind the creation of the community working group, you should start with Randy’s blog, as well as this proposal that came out of a governance sprint held in July that year.
The aim of putting this governance structure in place is to help the Drupal community deal with the challenges of scale. Formalising roles and teams that already exist in the project supports the work of contributors "doing" in the do-ocracy, and provides more support to those people already actively engaged in community issues.
Dries asked Angela Byron, Roel de Meester, George DeMet and myself to form the first Community Working Group.
Angela is a long-time "cat herder" in the Drupal community who frequently gets drawn into a conflict resolver role and has helped the community through some "meaty" topics such as the CVS to Git migration, and five major Drupal core releases.
Once upon a time, Dries asked him to look after Drupal.be, The Belgium community website. Nowadays, he's interested in connecting people and ensuring that new members find their way in the community. He's known for his no-nonsense approach and collaborative nature.
George is a Drupal Association Advisory Board Member, chair of the Drupal.org Content Working Group, co-chair of DrupalCon Chicago, and one of the folks who helped develop the DrupalCon Code of Conduct.
and Me? I was one of the first people elected to the board of the rebooted Drupal Association and I'm really passionate about the non-code aspects of maintaining an open source community.
DrupalCon Prague was a milestone for the group. Lisa Welchman gave a keynote address on the importance of governance for communities like ours. Some people came away from her talk scratching their heads and asking questions.
Why is this relevant to a software project like ours?
In essence Lisa Welchman reminded us that there is no code without people. It is the people, and not the code that define the Drupal community. We have good processes for managing the development and quality of our code. We still don’t have great processes for how we support and acknowledge people and their contributions.
Lisa spoke about a giant fungus as a good analogy for web governance, but also for an open source community like ours. She asked "How do you grow something to be big, that maintains its integrity and maintains its identity?" Lisa suggests that standards and a stable environment are key.
For our code we have coding standards. For our community, we have a code of conduct. That code of conduct represents the foundation of our social standards.
[Photo: Amazee Labs]
In Prague we also held the first Drupal Community Summit. A group gathered to focus on how we might tackle building a conflict resolution policies and processes for the Drupal community. Could we create something flexible enough to apply to all the kinds of conflict we see in our community? How can we acknowledge that conflict itself can be a good thing? We explored questions like these and listed the sorts of conflicts we might need to handle. https://drupal.org/node/2116441
The community summit was a great success, so we'll be doing it again at DrupalCon Austin. https://austin2014.drupal.org/community-summit
[Photo: Amazee Labs]
I'll write a series of follow up articles about our ongoing efforts to define, refine and field-test policies and processes on how the community can deal with conflict and complaints.
We can't do this work alone. We need a team of people willing to help. Many people are already doing this kind of "work" in our community, if you are, please let us know! Or maybe you're doing it and don't realise you are.
If you are someone people look to to smooth things over when things get heated, or someone with experience in conflict resolution outside open source communities, then please get in touch with the Community Working Group. Tell us
- What are you doing?
- How can we support you?
- How can we amplify your effort and successes?
- How can we improve?
This is Drupal, so of course we have an issue queue!
We also have a discrete incident report form only seen by members of the community working group.
Please look through our issue backlog. We’re looking for people willing to help us mediate disputes, formulate and refine community policies, and look for ways to build a community culture we can all be proud of.
Our awesome community recently became a bit more awesome. Drupal was accepted into Google's Summer of Code 2014! Student applications started March 10th and are open until March 21st. It's not too late to become a student, mentor, or submit a project idea. Not available to join the GSoC fun...maybe you can send an email to your alumni university mailing list?
Did you know Drupal recently participated in Google's Code-In contest for high school students aged 13-17 and they contributed over a hundred tasks? For example, did you see the Drupal 8 Theme Cheat Sheet @ https://drupal.org/node/2145023 (desktop background version @ http://goo.gl/zsQOf1) or the Drupal 8 Hello World module video @ http://youtu.be/N0IFTFQ9VTI ? Maybe you recently utilized DrupalLadder.org to find content updated for Drupal 8 by GCI students and watched the video on how to contribute back to the ladder @ http://drupalladder.org/content/get-involved ? Most importantly it is exciting to note that Drupal gained several Drupal 8 core contributors under the age of 18.
This is a special year as it is the 10th anniversary of Summer of Code and our community is excited to engage in the fun. In an initiative to spark participation, we contacted every single one of Drupal's alumni students along with the mentors of past GSoCs to contribute in the 2014 festivities. As a result Drupal organized almost fifty project ideas from mentors and companies around the world. We filtered the list into just under thirty compelling ideas and submitted a solid application. We're still welcoming project ideas, but we need dedicated mentors to help write applications with students and of course work with them all summer.
How to be a Drupal GSoC student in 10 Steps
- Register an account @ https://drupal.org
- Join Drupal's group for Summer of Code @ https://groups.drupal.org/google-summer-code
- Find a project on our ideas page @ https://groups.drupal.org/node/407793
- Add your name as an interested student to project idea
- Add your name as an interested student to project idea
- Contact mentors listed on project idea via drupal.org contact page
- If you don't hear back after 48 hours, try creating an issue in issue queue for project and contact org/mentor https://groups.drupal.org/node/411293
admins (Slurpee, Slashrsm, Varunity)
- Office hours are listed below if you still can’t contact a mentor or admin
- If you don't hear back after 48 hours, try creating an issue in issue queue for project and contact org/mentor https://groups.drupal.org/node/411293
- Complete "Drupal Ladder for GSoC Students" @ http://drupalladder.org/ladders
- Completing additional ladders will help your application!
- Completing additional ladders will help your application!
- Utilize drupalmentoring.org to find issues to work on with mentors willing to help
- Test and reroll patches in issue queue
- Write a patch that is contributed into Drupal 8 (making you a “core contributor”)
- Become a maintainer of the project you're planning to work on by contributing code/patches/tests/documentation
- Hangout in #drupal-google @Freenode helping other students
10 tips for writing student applications
- Treat this as a real job, would any software company actually pay you to work on this project all summer?
- Demonstrate your ability to contribute to Drupal and that you can immediately start producing code from day one of GSoC
- Create a complete project plan broken down by every week of GSoC
- Document and diagram the workflow of user experience
- Create wireframes/mockups of UI and UX (http://codecondo.com/free-wireframe-tools/)
- Research and contact initiatives looking to accomplish related tasks
- Plan out your “support contract”, do you plan to stay in the Drupal community after GSoC (example, how long will you support/update your code for the community after GSoC?)
- Explain your workflow for project, time, and task management (a tool such a Basecamp or Trello?)
- Describe your methods, tools, and frequency of communication with mentor for collaboration in a virtual environment (g+ hangout twice per week?)
- Request mentors and helpers in #drupal-google to review application via Google Drive with comments enabled
10 tips for mentors to help students write applications
- List a project on our ideas page @ https://groups.drupal.org/node/407793
- Review the “Drupal Ladder for GSoC Students” to learn student prerequisites
- Update any of the Drupal Ladders to help students learn faster
- Respond to interested students that contact you via drupal.org contact page
- Please respond within 48 hours
- Please respond within 48 hours
- Test and review patches from students
- Facilitate contact with discussion between student and module maintainer of projects of interested student
- Create a project plan and timeline that student agrees on with specific deliverables, understanding you may need to fail student at midterm or final
- Review Google/Melange’s guide on being a mentor (non-Drupal stuff) @ http://en.flossmanuals.net/gsocmentoring/
- Contact Drupal’s org admins (Slurpee, Slashrsm, Varunity) if you have any questions
- Hangout in #drupal-google answering student questions
Drupal’s GSoC Office Hours (help in real time!)
Mentors are available on IRC in #drupal-google @Freenode thrice each weekday for one hour from March 10th until March 21st. Join us in real time at scheduled times below to chat with mentors in real time to ask questions, request application reviews, or simply hangout.
- Asia/Australia 04:00 - 05:00 UTC (IST 09:30-10:30)
- Europe 13:00 - 14:00 UTC (CET 14:00-15:00)
- Americas 18:00 - 19:00 UTC (PDT 11:00-12:00)
Contributing to Drupal
Did you know many successful students started with zero Drupal experience prior to GSoC? If new to Drupal and willing to contribute, come to participate in core contribution mentoring. It helps anyone without any experience to get started with Drupal contribution development. Google wants to see students contributing to organizations prior to the starting of their GSoC project and this is a chance to demonstrate your skills. Office hours provide a chance for students that have problems with their patches or can't find issues to work on to seek guidance. Create an account at http://drupalmentoring.org before you participate in core mentoring. Drupal core contribution office hours are Tuesdays, 02:00 - 04:00 UTC AND Wednesdays, 16:00 - 18:00 UTC. If you need help outside of office hours, join #drupal-contribute to chat with the community members willing to assist 24/7.
Details about core mentoring office hours @
https://drupal.org/core-office-hours and http://drupalmentoring.org. More information about contributing to Drupal @ http://drupal.org/new-contributors and http://drupal.org/novice.
Final notes from Google to Students
We are pleased to announce that we are now accepting applications from students to participate in Google Summer of Code 2014. Please check out the FAQs , timeline , and student manual  if you are unfamiliar with the process. You can also read the Melange manual if you need help with Melange . The deadline to apply is 21 March at 19:00 UTC . Late proposals will not be accepted for any reason.
 - http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gso...
 - http://www.google-melange.com/gsoc/events/google/gsoc2014
 - http://en.flossmanuals.net/GSoCstudentguide/
 - http://en.flossmanuals.net/melange/students-students-application-phase/
 - http://goo.gl/1ZefN4
Recently, the Association posted a discussion here in groups (https://groups.drupal.org/node/398548) which resulted in the Association registering Drupal.org to participate in TheDayWeFightBack (https://drupal.org/node/2188053). As we have discussed, there were technical issues we could have addressed differently (see the discussion: https://groups.drupal.org/node/407283), but we also heard from many community members who felt that Drupal.org should never be involved in any kind of political campaign at all. An in this case, I'll use "political" with a small "p" to indicate the very broadest definition - from political candidate campaigns to "political" stances.
In fact, as an example of politics with a small "p," we were recently asked to participate in the Open Innovation Network (http://www.openinventionnetwork.com/) by signing on as a supporter (though the patent work obviously does not directly affect us).
I promised to address this question specifically in a follow up post - so here it is! We want to hear from you, but we ask that you please help make the conversation as constructive as possible. These discussions get heated quickly, so here are some ground rules:
- Critique the idea with logic, not emotion
- Don't critique the messenger, just the idea
- Try not to take criticism of your idea personally
- No swearing
Finally - help us have a broad conversation. Share this post widely.
A couple months ago, at the BADCamp devops summit, we held a workshop to discuss the architecture and operation of the current Drupal.org Automated Testing infrastructure, as well as to review a proposed future state architecture for the platform.
This post is an attempt to summarize the discussion, outline the proposed architecture as presented, and discuss some next steps.Existing Infrastructure
To begin, I provided an overview of the existing PIFT/PIFR architecture and operation. Rather than re-hash those details here, I'll refer readers to the existing drupal.org documentation on the topic, located at https://drupal.org/node/1222652.Current Gaps
One of the items which came out of this discussion was a request to explain the existing gaps with our current infrastructure. At a high level, but without getting into too much detail, these include:
- i) Multiple environments
- need to support multiple testing environments (different PHP/Database versions)
- need to distinguish (i.e. decouple) testing environments from new testing plugins
- faster per-environment results (currently, all environments must complete before any one result is returned)
- ii) Quicker response times
- We have an ever-growing test run duration, having exceeded 2 hours in the recent past
- To meet developer expectations, we need to move to support parallel batch processing
- iii) Realtime feedback for in progress tests
- Allowing developers to monitor their tests, and better understand when they can expect a result.
- iv) New features
- 'Fast fail' option, which exits on the first failure
- Test prioritization ('Run x, y, and z first' testing option)
- Patch Conflict Detection
- Blacklisting tests
- Support private tests for security team
- Historical test results (instead of current 'last build only' capabilities)
- Associating tests with a specific core commit id
- Ability to write settings into settings.php
- Drush and Composer support
- v) Move away from a single purpose stack
- Move towards a generic job dispatcher instead of ‘simpletest-only’
- Support PHPUnit testing
- Add future flexibility as our toolsets change and evolve in the future
- vi) Separate environment setup from testing phase
- Currently, testbot environmental failures show up as failed tests
- vii) Cancel/Requeue capabilities to address false/random failures
The above list outlines the motivations behind a desire to modernize the current infrastructure ... the rest of this post outlines the proposed solution which was presented as a potential end-state for this evolution.Proposed Architecture
Key to the proposal is a move away from a single-purpose testing stack towards more of a flexible generic job dispatcher which supports a wide range of automation functions, and is able to evolve with the future changing needs of the community.
The proposal leverages the use of a Jenkins distributed build implementation as the primary job router/dispatcher. A master/slave architecture is used to support scalability of the platform over the long term, as well as the ability to meet the temporary short-term test capacity requirements of DrupalCons, conferences, and other sprint events.
Each of the jenkins slaves is also configured as a Docker host, capable of spinning up individual on-demand containers to provide the actual testbot/job workers. Each Docker host stores multiple container snapshots, and spins up the appropriate snapshot based on the testing type and desired environmental attributes (such as PHP/DB versions) specified within a test request.
Because we'd also like to support historical test results for every job run, it is anticipated that the storage requirements for the jenkins environment will be quite high. To help ensure that this doesn't affect operation of the jenkins master, the proposal suggests the use of a 'build publisher' server to host the results and job artifacts off of the main dispatcher. This may be another jenkins machine, or a purpose-built database server.
This approach also allows the hosting of the jenkins master on a private network segment, while providing the test results on a public server (increasing security of the testing backend while potentially exposing API-based access or hooks to the greater community on the front-end).
This 'build publisher' server becomes the canonical storage for job results, serving as the back-end for qa.drupal.org, which becomes little more than a presentation layer for the results data. As with the current environment, drupal.org would still provide summarized test results, with qa.drupal.org being the public interface for detailed results.Next Steps
With support for this proposal, it was decided that we would make use of the “Drupal.org Testing Infrastructure” group on groups.drupal.org as a collection point for self-organization and sharing our findings. The first phase will focus on ‘research’, as we investigate individual pieces of the architecture at a ‘proof of concept’ level, validating the smaller components of the proposal before coming together in a larger, more coordinated assembly. I will be following up this post with a planned roadmap for these activities, looking for feedback and volunteers.
To get involved, please take a moment to join the g.d.o group at https://groups.drupal.org/drupal-org-testing-infrastructure, and add your name to the ‘Volunteers and Roles’ contact list, add a comment below, or email me via my drupal.org contact form (https://drupal.org/user/148199/contact).
DrupalCampChina 2014 is a one day event that focuses on many aspects of Drupal in one location. Its focus is knowledge sharing among the community. Essentially, you’re getting the community together to do some community training. The term "Camp" comes from Barcamp, like an informal non-conference that happens at a bar.
Generally speaking, DrupalCampaChina is an extension of a meetup (e.g. the meetups in Shanghai).
10AM, Saturday, March. 22nd, 2014.
The Nest (Gongyi Xintiandi), 105 Puyu West Road
Near Lujiabang Road subway station (line 8, 9)
Walk east for 10 minutes, Make a right turn on Puyu West Road
Near Nanpu Bridge subway station (line 4)
Sessions and agenda:
There will be 6 sessions. 2 in the morning and 4 in the afternoon.
10AM-10:50AM: Pre-DrupalCamp training & announcement
11AM-12PM: DrupalCampChina 2014 Keynote ---- Rob Loach (Rob Loach is senior engineer at Myplanet Digital, Canada. He also worked as Drupal Ninja at Acuqia and Fast Company. Loach has been Drupal Core contributor since D6, and he also contributes to hundreds of modules on Drupal.org. More details coming...)
12PM-12:30PM: Group photo, please follow the instruction during the Pre-DrupalCamp training & announcement session
1:30PM-2:20PM: Want to present? Please propose a session
2:30PM-3:20PM: Want to present? Please propose a session
3:30PM-4:20PM: Want to present? Please propose a session
4:30PM-5:20PM: Want to present? Please propose a session
Sessions proposed by community members
Please visit https://groups.drupal.org/taxonomy/term/128103
DrupalCampChina 2014 is a free event. The conference will also provide you with free food, drinks, WIFI and T-shirt. Please use the "sign up" feature below.
Drupal中国营广义上也是Drupal Meetup的扩展，比如在上海就有本城市的DrupalSH Meetup。
11AM-12PM: 2014年Drupal中国营主题演讲 ---- Rob Loach (Rob Loach 是加拿大Myplanet Digital高级工程师。他也曾是Acquia和Fast Company的Drupalg高级工程师。Rob Loach自从Drupal 6开始已经成为Drupal核心的开发人员，并且他对超过100个Drupal.org上的开放模块都有贡献。主题演讲详细信息很快会更新...)
On April 25 - 27, join us for the second DrupalCamp Donetsk (Ukraine)!
The event will include two days of sessions and BoFs (in English and Russian), trivia night, Drupal Party, and full day code sprint. It is a great opportunity to meet East European Drupal community.
Come and share your Drupal knowledge and ideas, sessions in English are welcome. And if all the sprints during Dev Days Szeged just weren't enough, you can work on Drupal 8 some more at our Sunday code sprint!
Registrations are already open: http://camp2014.drupal.dn.ua/en/conference/tickets
Call for content will open in the next few days.
If you'd like to sponsor the event, please check proposal for sponsors.
Major announcement! The 10th annual Google Summer of Code application period kicked off Monday, February 3rd (GSoC 2014 announcement from Google).
Google Summer of Code (GSoC) - an annual contest for university students organized by Google with projects managed by open source organization mentors such as us (Drupal!). Are you or any colleagues available to be a mentor and/or provide a project idea? Please share project ideas even if you're not available to be a mentor. Did you know each accepted organization sends two of the top mentors to Mountain View, California on an all expense paid trip to visit GooglePlex for the "Mentor Summit"? This year will be special as it is the GSoC 10 Year Reunion Mentor Summit inviting all alumni.
Current need is adding project ideas into the 2014 GSoC Drupal Idea Wiki to finalize Drupal's GSoC 2014 Application. The 2014 deadline to submit project ideas to our core Drupal/GSoC group for review is Wednesday, February 12th at 23:00 UTC. Deadline's only requirement is an organized idea documented in wiki. Our goal is to submit an application with at least 30 quality ideas. If Drupal is accepted, another timeline will be setup to define the project scope (see 2014 GSoC schedule for details).
Links about GSoC:
- Google Summer of Code Official Website
- Drupal's GSoC 2014 Project Idea Wiki
- Drupal's GSoC Collaboration Group (important to note that each GSoC year had it's own group on gdo, but starting this year please join our new group moving forward for all GSoC years)
- Mon Feb 03 - Application period starts
- Fri Feb 14 - Application period ends
- Mon Feb 24 - Accepted organizations announced
- Mon Mar 10 - Student application period opens
- Mon Apr 21 - Accepted student proposals announced
- Mon May 19 - Students begin coding
- Mon Jun 23 - Midterm
- Mon Aug 18 - Firm 'pencils down' date
- Mon Oct 25-26 - Mentor Summit at Google
How can I help? Create Project Ideas!
- Anyone with a drupal.org account is allowed to add ideas (student, mentor, outsider, whoever)
- Submit project ideas @ Drupal's GSoC 2014 Idea Wiki
- Help add at least 30 project ideas
- The goal is focusing on Drupal 8 and as of today, many popular modules have not started ports to Drupal 8 (login_destination, flag, seo_checklist, faq, securepages, boost, getid3(), linkchecker, mailchimp, xmlsitemap, menu_block, lightbox2, poormanscron, node_clone, diff, site_verify)
- Example project idea: Port Quiz Module into Drupal 8
- Projects from previous Drupal GSoC: 2012, 2011, 2010, 2009, 2008, 2007, 2006, 2005
- Example of KDE whom is accepted into GSoC yearly @ http://community.kde.org/GSoC/2014/Ideas and http://community.kde.org/GSoC/2013/Ideas
 "GSoC 2014 announcement from Google" http://google-opensource.blogspot.com/2014/02/mentoring-organization-app...
 "Google Summer of Code (GSoC) @Melange" http://www.google-melange.com/gsoc/homepage/google/gsoc2014
 "GSoC 10 Year Reunion Mentor Summit" http://google-opensource.blogspot.com/2013/10/google-code-in-2013-and-go...
 "2014 GSoC Drupal Idea Wiki" https://groups.drupal.org/node/404778
 "Drupal's GSoC 2014 Application" https://groups.drupal.org/node/404768
 "2014 GSoC schedule" https://groups.drupal.org/node/404758
 "Google Summer of Code Official Website" http://www.google-melange.com/gsoc/homepage/google/gsoc2014
 "Drupal's GSoC Collaboration Group" https://groups.drupal.org/google-summer-code
 "Previous Drupal GSoC 2012" http://www.google-melange.com/gsoc/org2/google/gsoc2012/drupal
 "Previous Drupal GSoC 2011" http://www.google-melange.com/gsoc/org2/google/gsoc2011/drupal
 "Previous Drupal GSoC 2010" http://www.google-melange.com/gsoc/org2/google/gsoc2010/drupal
 "Previous Drupal GSoC 2009" http://www.google-melange.com/gsoc/org2/google/gsoc2009/drupal
 "Previous Drupal GSoC 2008" https://developers.google.com/open-source/soc/2008/?csw=1#drupal
 "Previous Drupal GSoC 2007" https://developers.google.com/open-source/soc/2007/?csw=1#drupal
 "Previous Drupal GSoC 2006" https://developers.google.com/open-source/soc/2006/?csw=1#drupal
 "Previous Drupal GSoC 2005" https://developers.google.com/open-source/soc/2005/?csw=1#drupal
 "Contact GSoC Drupal Admin Slashsrm" https://drupal.org/user/744628
 "Contact GSoC Drupal Admin Varunity" https://drupal.org/user/273530
DrupalPicchu: "celebrating the freedom and cultural diversity of the Drupal Community"
In the photo above, on the left: Victor Kane, a gentleman, British/American, currently living in Buenos Aires, Drupal pioneer in Latin America. On the right: Veronica Nerak, a young lady from Bolivia, interested in learning more about Drupal.
DrupalPicchu happened on January 20-24th in Cusco, Peru. We had about 300 participants, of which almost 50 were from abroad. We had community members from all corners of Latin America, including Peru, Bolivia, Brazil, Colombia, Ecuador, Chile, Argentina, Uruguay, Mexico, Guatemala, and Costa Rica. We also had guests from the United States, Finland, and Belgium. From Peru, we've received participants from Cusco, Lima, Arequipa, and Puno.
In the first day of the event, about 20 Drupal experts dedicated their time to teach over 150 participants a little more about Drupal. Victor Kane also ministered an advanced workshop called "Drupal Lean Process". The workshop program contemplated 6 parallel tracks.
In the second and third days of the event, we had 6 Summits covering the following areas: Community, Business, Education, Media, Non-profit, and Government. In total there were 40 talks, including a forum for each Summit where a group of experts shared their experiences.
Aligned with the mission of celebrating the cultural diversity of our community, we also had a keynote about Women in Drupal. From left to right: Nancy Contreras (Peru), Griselda Tastaca (Bolivia), Holly Ross (USA), Molly Byrnes (USA), Veronica Nerak (Bolivia), Karen Da Cruz (Peru), and Nibeth Mamani (Bolivia).
On the fourth and fifth days, some developers gathered for code sprinting. They also helped participants by giving advice on good development practices.
The most memorable moments of DrupalPicchu were the social gatherings and cultural activities. We had a dinner sponsored by Andrew Kucharski (from Promet Source), another by Holly Ross (from the Drupal Association), and a third one by Molly Byrnes (from Phase2).
Perhaps the biggest Drupal adventure ever was the trip to Machu Picchu! In the photo above we have 32 Drupaleros who made it. The majority of these went on to climb Huayna Picchu (the mountain in the background, overseen Machu Picchu).
DrupalPicchu was a great opportunity to bring together people from multiple cultures to help progress both the software and the community itself. This cultural diversity may present some challenges, but with the right attitude it may present many benefits as well.
This cultural diversity is important for several reasons:
- Technical: many talented individuals can contribute to the Drupal project.
- Organizational: a more balanced governance can foster a stronger community.
- Financial: international partnerships can create attractive business opportunities.
- Social: these opportunities can have a huge impact on people's lives everywhere.
The Drupal Latino community has been working hard to spread Drupal in Latin America and to create bridges with other communities around the world.
We believe that it's a matter of social responsibility promoting Drupal participation everywhere, specially in regions where Drupal has the biggest potential for truly changing people's lives and making the world a better place.
Additionally, it's well known that innovation requires a high dose of creativity, the type that emerges "in the edges" of the network. So by spreading Drupal in regions like Latin America, not only are we helping those in the edges of the community, but we might be actually helping those in the very core of the community itself.
Drupal, the software, is as powerful as it is today because of its healthy ecosystem where most innovation comes from the edges. Think about every great thing in the Drupal world: Fields, Views, Rules, Entities, etc. Every single one of them started either by an individual or a very small team in the edge of the network, "scratching their own itch". Now these innovations are part of Drupal's core (or very close).
People "in the edges" can provide a different (and potentially revolutionary) perspective. For example, while constellations in traditional cultures were observed by connecting stars, in the Incan culture the constellations were observed by visualizing the whole (not only stars, but also the "dark clouds"). In the above photo we see the Llama Constellation, with the alpha and beta Centauri stars representing the llama's eyes.
This cultural diversity and openness to different perspectives are key to innovation and very much part of the open source philosophy. Open source represents the freedom to study, to learn, to adapt, to collaborate, and to contribute back, no matter who you are or where you are from.
With that, DrupalPicchu invites the whole community to expand Drupal to new horizons and to foster new opportunities in places where it's most needed! Let us nurture a healthy ecosystem with no boundaries or frontiers! Let us work the edges of the network, because the future of the Drupal community might very well be there!
We would like to thank the DrupalPicchu Sponsors:
- Domo (represented by Iván Campaña, from Ecuador),
- Axai (represented by Joaquin Bravo Contreras, from Mexico),
- SeeD (represented by Aldibier Morales, from Colombia),
- Just Digital (represented by João Paulo Seregatte, from Brazil),
- Taller (represented by Renato Vasconcellos and Sebastian Ferrari, from Brazil), and
- Agaric (represented by Benjamin Melançon, from USA).
Also, a very big thank you to the DrupalPicchu Patrons:
Join us for 2-days of Drupal goodness! Pre-trainings, sessions for all levels, code sprint and, of course, evening mixers! Join the fun as we Drupal in the desert.
Drupal Camp PHX is a 2-day conference organized by Drupal professionals and the Phoenix Drupal User Group (PHX DUG) to promote and advance the Drupal community in Arizona and the Southwest region. Drupal Camp PHX brings together a variety of people interested in learning and growing skills in open-source, web content management and web development. This year's camp will consist of trainings, sessions for various levels of experience, social events, and a chance to contribute to Drupal core.
- Explore best practices for web developers and marketers alike
- Learn or accelerate skills in web development
- Connect with like-minded individuals, aspiring entrepreneurs, and talented industry experts
- Mingle at social mixers on both Friday and Saturday nights
Register today...for FREE!
For Camp Questions, contact email@example.com
A leadership team responsible for decision-making about the Drupal.org community sections (Forums, Planet, User Groups, User Profiles) will be appointed by the Software Working Group by the end of February 2014. Read this post carefully if you wish to participate in shaping this leadership team.Overview
The Drupal.org Software Working Group (drumm, eliza411, tvn, webchick) was chartered to provide vision and direction for Drupal.org by working with the community on Drupal.org software in a number of ways. The first duty on our list is establishing team leadership.
From the charter:
(DSWG) Creates and removes teams for each major area of the Drupal.org websites, which have authority to make software and feature decisions within their scope. The DSWG defines and appoints the leadership roles within each team, such as a technical lead, product owner, QA lead, etc.
Full charter: https://drupal.org/node/1929526
The first team we set out to appoint was Developer Tools Team. That process is at the finish line right now. We are getting ready to announce team members on January 30.
Therefore, it’s time for us to start working on the next team.Proposal
Community Tools Team Scope
Proposed scope of functionality for the Community Tools Team includes:
- User profiles
- User groups (groups.drupal.org)
We feel that, outside of the issue queue, these are the sections of the site where community interaction happens. Therefore it makes sense to group them under one leadership team, which will take a high-level look at the current tools and work with the community to find out what kind of tools are needed for they things our community does outside of code development, e.g. for discussions, collaboration on initiatives, events and local groups organization, job search etc.
- Product Owner
- Project Manager
- UX Lead
- Lead Architect for forums?
- Lead Architect for Planet?
- Lead Architect for user profiles?
- Lead Architect for user groups
January 23 - February 2 — Online Discussion
Process Facilitator: tvn
Responsibilities, Authority and Conflict Resolution will largely follow the ones we defined for Developer Tools Team. The discussion template below contains some of the questions for consideration for this team specifically.
- Scope: Are the areas proposed related enough to group them and under one team? Is there something else, which should be listed?
- Roles: What roles are needed for this area (technical lead, product owner, QA lead, etc)?
February 3 - DSWG to summarize community discussion, publish the final proposal and publish the call for candidates
By February 28, Drupal.org Software Working Group to appoint leadership team
Join us for the inaugural Drupalcamp New Orleans on Saturday, March 29, 2014. Featuring keynote speaker Chris Shattuck of buildamodule.com, the event will include a full day of presentations in tracks for Beginners, Development and Theming and Case Studies. Visit www.drupalcampnola.com for more information, to register and to submit a session.
Drupalcamp New Orleans
Saturday, March 29, 2014 - 9 am - 5 pm
643 Magazine St
New Orleans, LA
Drupal Developer Days 2014 is coming up quick in Szeged, Hungary from March 24th (Mon) to the 30th (Sun) 2014. Szeged, Hungary may sound like it is the middle of nowhere but what do you need to get together with a bunch of Drupal developer friends and learn about and advance the platform together? As those who have been to DrupalCon Europe 2008 in the same city know, Szeged is the ideal place for just that. Check out our interviews about those experiences.
Here are some quick facts about Drupal Dev Days 2014:
- A whole week of sprints with two core committers (Alex Pott and Nathaniel Catchpole) as well as the testbot system maintainer (Jeremy Thorson) on location! Could we help more to make progress? Oh, most top European Drupal developers are already signed up to come as well!
- Three days of sessions and workshops (50 topics providing 56 hours of content). Get lots of readily applicable know-how including website monitoring, e-commerce, practical scrum, Vagrant, product development in real life, Heisencache, IDE tricks and so on. Look into how Drupal is made, see the life of a core maintainer, get gamification tips or discuss a new type of money: Druplicoins!
- Want to work on upgrading your modules to Drupal 8 but don't know how? No problem! Additionally to learning about all the new Drupal 8 subsystems, there is a bring-your-own-module workshop as well, where mentors will help you upgrade your module!
- Want to get into Drupal development? Attend the community tools workshop and learn all the tools we use to communicate and work on solutions and learn and enjoy how the Drupal mentoring program works.
A truly fantastic opportunity isn't it? Last but not least its also very cheap. The ticket is only 30 Euros for the whole week! If you want to get to know Drupal 8 or even help make it happen, this is the place to be in March. Note that some cheap hotel deals expire this week. Don't miss out!
Florida DrupalCamp is now taking registrations and session submissions! Register at http://fldrupalcamp.org! The event will be taking place at the beautiful campus of Florida Technical College in Orlando, Florida on Saturday, March 8th.
This year, we’re doing away with the traditional keynote speaker, and bringing in four (yes four!) amazing featured speakers from around the country! We’ll be announcing a new featured speaker every week - starting with the illustrious Jen Lampton! Read more about Jen at https://fldrupalcamp.org/featured-speaker/jen-lampton
Early-bird registration is only $25 and includes lunch and an awesome tshirt! Register today (before we raise the price on you)!
We're planning a conference that's packed with 3 full days of pre- and post-camp activities, including trainings, topic-based summits, a job fair, a barn raising to benefit a local non-profit, parties, and more!
Here's our tentative schedule for the next couple of months:
Session submissions start on January 13, 2014
GLADCamp is 3 days dedicated to all things Drupal, and we're looking for session proposals on everything including site building, coding, development, e-commerce, theming, design, performance, security, site showcases and case studies.
Training submissions start on February 3, 2014
Training companies and individual trainers are welcome to propose a training to be scheduled on Friday, March 7, 2014. We currently have two training spaces, but we might have more depending on demand.
Barn raising applications start on February 10, 2014
Continuing our tradition of holding "barn raisings" for non-profit organizations, we'll be reviewing applications from non-profits who would like to participate in a code sprint dedicated to building their website or adding much-needed features.
1st round of selected sessions will be announced on February 17, 2014
We're combining some elements of barcamp-style organizing with traditional conference planning, and will announce a preliminary schedule on February 17th. This is also when folks coming from out of town should start getting their travel arrangements together.
Final schedule will be posted on February 24, 2014
2 weeks before the conference, we'll have a finalized schedule so everyone will know which sessions to look forward to!