Jun 01 2017
Jun 01
chuta's picture

Woa..."with over 100 years of experience on drupal.org"!
Will like to meet some of them in my life time!

ranjithraj's picture

Wow, 7 out of 8 students are Indians!
Drupal has a large student base in India, seems it's popularity among students would increase even more in near future.

Slurpee's picture

IMPORTANT DEADLINE for ALL MENTORS: First Evaluations open June 26 and are DUE before June 30, 16:00 UTC

Starting at 16:00 UTC on June 26th you can go to your dashboard on the GSoC program site to complete the first evaluation. Just click on the "Complete Evaluation" button and fill out the form. You must complete the entire evaluation form at once — you can not submit a partially completed evaluation and you can not edit the evaluation once it has been submitted. You must submit your first evaluation by June 30th at 16:00 UTC.

stevjackson011's picture

Indian are extremely talented when its come to IT. They are very good in this field.
p.s hard luck for them in ICC Champions Trophy.

There should be one thing in your life for which you can say that i have given my 100% to it.

Slurpee's picture

IMPORTANT DEADLINE for ALL MENTORS. Second evaluations opened today and are due by July 28th at 16:00 UTC.

One mentor for each student project must complete an evaluation of their student before Friday, July 28th at 16:00 UTC. If you haven't done so already, go to your dashboard on the GSoC program site and complete your evaluation of your student before July 28th at 16:00 UTC. We encourage you to complete the evaluations ASAP so you don't forget to do it - it should take you less than 10 minutes to complete.

Students, this week's check-in meeting is not complete until evaluations are finished.


noortina's picture

It sounds great and proud to see our people grow. I wish to achieve such competition one day.I have been working on Drupal for some time now and i am still learning a lot.

Slurpee's picture

Attention GSoC mentors, please fill out final evaluations ASAP.

Be sure to submit the Evaluation before Tuesday, September 5th at 16:00 UTC.

If you're unable to process evaluation, please contact me.

diegocastro's picture

Excelent!! I hope that everything works fine.

FrankSpang's picture

Seems like an amazing opportunity. I myself is a freelance webdesigner not only for drupal projects but others as well. Latest i began experiencing with the new AMP platform (developed by Google in fact) and among other websites, created this one https://moneybanker.dk as my first project with the coding platform. Will try to apply for joining this event myself next time around.

hantanviet's picture

I want use code drupal cho my sites in future, about print and design
Trade shows can be a great source of sales leads and can introduce a large number of potential new customers to your business. They can also take a lot of your time, effort and often money printing business cards https://kprint.vn/printing-business-cards/. However, there are ways to make the very most of your trade show appearance and by following our trade show tips your investment should really pay off

AlexKorv's picture

https://www.bestadvisers.co.uk/rotisserie-ovens I`m interested if it is possible to improve the location of buttons or images for search engines and the user. Subjects as you see varied, but I care about this moment only this - dedicated to the kitchen, and specifically rotisserie ovens.

Apr 25 2016
Apr 25

Did you know Drupal was accepted into Google Summer of Code 2016 and that 11 Drupal projects were accepted? In other words, Google is funding 11 people to contribute to Drupal for 10 weeks worth a total of $60,500 USD (thank you Google!). Congratulations to selected students who are collectively credited on more than 100 issues fixed in the past 3 months on drupal.org. Coding starts May 23rd and ends August 23rd.

Majority of projects are focused on work related to Drupal 8 contributed modules. Drupal's students are from 4 different continents and we currently have 26 mentors from 12 countries with over 150 years of experience on drupal.org. As always, we're excited about this summer and we hope community members will provide an extra helping hand if you see students in queues. Learn more about our projects below.

Project: Social API
Student: Getulio Sánchez "gvso" (Paraguay).
Mentors dahacouk (UK), e0ipso (Spain), pcambra (Spain).

Project: Solving content conflicts with merge algorithms in Drupal 8
Student: Rakesh Verma "rakesh_verma" (India).
Mentors: dixon (Sweden), timmillwood (UK), jeqq (Moldova).

Project: Port Mailhandler to Drupal 8
Student: Milos Bovan "mbovan" (Serbia).
Mentors: miro_dietiker (Switzerland), Primsi (Slovenia).

Project: CKEditor plugins for TMGMT
Student: Saša Nikolič "sasanikolic" (Slovenia)
Mentors: miro_dietiker (Switzerland), Berdir (Switzerland).

Project: Port search configuration module to Drupal 8
Student: Joyce George "joyceg" (India)
Mentors: naveenvalech (India), heykarthikwithu (India), neetu (India).

Project: Integrate Google Cloud Vision API to Drupal 8
Student: Arpit Jalan "ajalan065" (India)
Mentors: naveenvalech (India), penyaskito (Spain), eugene_ilyin (Russia).

Project: Port Google Login Authenticator To Drupal 8
Student: Mehul Gupta "therealssj" (India)
Mentors: nerdstein (USA), attiks (Belgium).

Project: Media Solution Module
Student: Vijay Nandwani "royal121" (India)
Mentors: slashrsm (Slovenia), paranojik (Slovenia).

Project: Web Component-ize Drupal 8
Student: Tianlei Zheng "ztl8702" (Australia)
Mentors: skyredwang (China), Wimleers (Belgium).

Project: Add Password-based Public-key Encryption to Drupal 8
Student: Talha Paracha "talhaparacha" (Pakistan)
Mentors: nerdstein (USA), colan (Canada), jibran (Pakistan).

Project: Porting Comment alter module to Drupal 8
Student: Anchal Pandey "anchal29" (India)
Mentors: Boobaa (Hungary), czigor (Hungary).

Final call for mentors. Are you interested in helping any of the projects above? Contact Slurpee on drupal.org, find us in #drupal-google on Freenode, and join us at https://groups.drupal.org/google-summer-code.

A special "Thank you" goes out to Drupalize.me for providing all of our students a free account.

Feb 12 2015
Feb 12
pukarthapa53's picture

There is a lot of money in it, and the best part is that you don’t need any qualifications, prior experience or specialised skills. All you need is a few spare hours per day, a computer with an internet connection.click here if u want globalwebworkers.com

Randalltbartel's picture

Buying an essay from online is very difficult process due to having some scamming service in the online. So first of all we have to understand the service properly for ordering our essay in the online service. The education essay writing task is bit difficult to complete from the students side. Even the evaluation is very different in the academics. The essay writing evaluation on academy must be well organized, and student’s thoughts must circulation rationally from one point to the next. So students should be mentioned properly according to their self-discipline in writing. So these things should be followed by the service writers. Present language and opinions on the subject in an impartial and extensive way. Writing a self essay requires the huge amount of knowledge and skill sets. The top and best essay writing service will always keep good format and high-quality essay for the students. Therefore you can get a tension free essay from this best online writing service. Their professional writers are good enough to complete any type of educational essay for students. So struggling students can make use of this service for completing their academical essay writing tasks. This website is giving quality essay in a low cost.

Sep 16 2014
Sep 16
penyaskito's picture

Congratulations to all participants :))

Christian López Espínola (@penyaskito)

surcap's picture

Congratulations to you

shorelinegtx's picture

Congrats to all the participants. Must have been a fantastic experience.

arya88bimo's picture

Congratulations to all of you..

varunity's picture

Hey congrats! Good job everyone!

rachit_gupta's picture

Congratulations to all of you..

Nov 20 2013
Nov 20

Big news! The annual Google Code-In contest kicked off Monday, November 18th. The contest's purpose for pre-university students (ages 13 - 17) is learning how to contribute to open-source software projects and offers them a chance to win a once in a life time grand prize of an all expense paid trip to Google HQ in California. The bigger news...Drupal was chosen as one of the ten participating organizations to create tasks for the students to complete during the 2013 contest! This is a huge honor for Drupal and gives us an amazing opportunity to grow our community. Details @ https://www.google-melange.com/gci/homepage/google/gci2013

Drupal Community, we're about 48 hours into the 2013 Code-In contest, students have already finished several tasks, and we need YOUR help. In this busy day and age, finding mentors can prove challenging and after months of "cat herding", we realized a simple solution for participation: "Just 1 Task". Even if you submit one task and mentor that task, everyone wins. We currently have 14 mentors in Google's system with tasks, but there is no limit on mentors or number of tasks we can accomplish. Ironically, after mentors add one task, they usually add a few more tasks. With Drupal 8 on the horizon, we have plenty of easy tasks that anyone at any age can accomplish, and it is the perfect opportunity to find new long time contributors. This is your chance to be a part of the global phenomenon that is open-source software! Join us in #drupal-gci or see information below on becoming a mentor.

After being selected to participate in the 2013 Code-In contest, our goal is to keep this momentum moving forward and plan to have a solid application with an elevated level of participation in Summer of Code 2014. Plus, Google has big plans in 2014 for Summer of Code's 10 year anniversary ( http://google-opensource.blogspot.com/2013/10/google-code-in-2013-and-go... ).

Thank You!
A big thank you to our core team of mentors that organized tasks, worked on the application, and set up everything for student participation (Janez Urevc in Slovenia, Varun Baker in Jamaica, and Matthew Lechleider in USA). Plus, we can't forget all the current mentors who jumped at the chance to contribute (Aaron Dudehofer, Abdul Qadir, Andrew Shemo, Ben Carlson, Patrick Elward, Cody Carlson, Doug Vann, Jason Daniels, Kevin Reynen, Martin Martinov, Matt V).

How to Become a Mentor
*Login with Google account @ https://www.google-melange.com/gci/homepage/google/gci2013
*Click "Register to be a Mentor"
*Connect with Drupal
*(wait for approval)
**Contact slurpee on d.o if issues

How to Add Tasks
*Login @ https://www.google-melange.com/gci/homepage/google/gci2013
*Click "My Dashboard"
*Click "Create Tasks..."

How to be a Mentor
*Add at least one task @ https://www.google-melange.com/gci/task/create/google/gci2013/drupal
*Notification of task will be sent to Drupal admins for approval
*Approval of task by admin publishes tasks publicly to students
*Request to be assigned task by student notifies mentor
*Mentor logs into Melange to click "Assign Task"
*Notification that task has started is sent to Student/Mentor/Admins
*Hangout in #drupal-irc on freenode to answer questions in real time if needed
*Comment task in Melange for feedback and help with student on task
*Review students work when completed
*Complete task to finish process

Questions? Contact Drupal's GCI 2013 Admin (Matthew Lechleider) @ https://drupal.org/user/91767

Sep 08 2012
Sep 08

I felt like working in a niche until November 2011. I did not believe there was anyone else beyond me in my local area who's seriously using Drupal. But — it was on my walk to the grocery store when two strangers suddenly crossed the street, bumped into me and said "Dude, are you sun from drupal.org?"

How wrong I was. I started my local user group shortly after, in November 2011. Out of fucking nowhere, 12+ people attended the first meeting! With a huge interest in Drupal and fostering a local user group.

Meanwhile, the Drupal User Group Karlsruhe is close to its 1st anniversary. And, we've adopted the DrupalCon spirit recently: We are meeting once a month. We're meeting in a different location each time. The location is different, just like our members are. We want to learn about new things. And the location shouldn't be excluded.

We want to share and exchange knowledge, about Drupal and the world. But how?

The cause.

We originally started to organize our meetings in a Facebook group, via Doodle events, and groups.drupal.org. Plenty of organizational overhead and problems with that:

  • Facebook groups, even though "public", are only public within Facebook, but cannot be accessed nor found from the outside world. Many people understandably do not want to sign up due to data privacy concerns, and have other good reasons to stay away from it. Inaccessible, in terms of accessibility.
  • Doodle events are not found anywhere to begin with.
  • groups.drupal.org has groups and events. But not even long-term users are able to figure out how to use the site in a way that allows to locate and distill the events of actual interest. How are new users supposed to do that then? But nevermind, ~80% of my group members didn't have a drupal.org user account in the first place! (geez, what? — Effin' register now if you're using Drupal but don't have one yet!)

Conclusion: We need our own web site.

We need to be found on the net. And in search results. We need to make it trivial for interested people to join. We need our own mechanisms to figure out the next meeting location. We are our own local Drupal sub-community. We need to feel home, and we need a way to communicate with each other. This matters.

There's excellent shit for that. — But wait.


What's the problem?


How many things can we attack by asking the right questions?

  1. A concrete use-case.

    Jeff Eaton preached it all over again at DrupalCons and camps all over the world. Dries Buytaert repetitively stated it in keynotes. And even Drupal usability team leads Roy Scholten and Bojhan Somers want it: Installation profiles and distributions.

    Tailored to a specific use-case.

    Since Drupal 5 in 2007, the installation profile functionality in Drupal core was heavily improved. Given these improvements, the community tried hard to reach consensus on the fact that profiles and distros are a good thing.

    Years of discussions later. Under the working title Snowman [also: "Onramp"], a concrete scope and use-case for an installation profile to be shipped with Drupal core was developed:

    Small groups collaborating on a project who want to tell the world about it... and convince others to join in.

    A solid and focused use-case.

    Given that, the Drupal community dived into shitloads of discussions on which functionality would be required in core that doesn't exist yet. And we looked into potential consumers and adopters for that use-case. For example, the global Occupy movement.

    Missing the obvious. Not realizing that we have the identical and perfect match of a use-case within the Drupal community ourselves:

    Hundreds of local Drupal User Groups all around the world have a SHARED INTEREST!

    We want to communicate with each other and the world about Drupal, and our interest is to on-board new people into our local groups. Transferring and sharing knowledge. Taking Drupal to the next level.

    Is there any better incentive to work on Drupal?

  2. Missing Drupal resources.

    You hear the same story. Shuffle. Repeat: Some contributors find their way to contributed projects, but have no idea and are scared of Drupal core. People are not able to find skilled Drupal service providers — they're swamped with work already. And companies that are relying on Drupal and employing people don't manage to increase their skills.

    Dries depicted the Drupal Learning Curve in 2007. I revised that into the Real Drupal Learning Curve later — showing the giant gap between people who stay in custom code forever and those who make the massive leap of contributing to Drupal core.

    Once you take that path, your skills drastically improve. On all levels.

    Hundreds of local Drupal User Groups all around the world have PLENTY OF PEOPLE.

    Did you know that even a single Drupal core patch makes a significant difference on your resume?

  3. Mentor Drupal talent.

    Did you ever consider to contribute to Drupal? Did you ever consider to help someone to contribute to Drupal? Did you know that there are thousands of people who are only seeking for some minimal guidance?

    Have you been inspired, influenced, or brought into Drupal by someone else? People who explained stuff to you, but actually didn't have any reason to waste their time with you? And did you learn something new?

    As of today, you are able to give credit your mentors in your drupal.org user profile. Use it!

    Truth is: You weren't in the position you are today, if there wouldn't have been others from who you've learned. That applies to you, me, and everyone else.

    It only takes the effect of a fucking dead pixel on your screen to understand the impact of a single link in the chain. Let's pretend the one who taught you about Drupal was that pixel — you'd be excited about his/her exceptional behavior compared to all others, but would you give a shit?

    But what if you were that dead pixel, the dead link in the chain?

    You are.

    And you can give a shit. But you can also start to make a difference. Whatever know-how you gained and have, you can truly pay it forward. You can ask yourself where to start. But did you know?

    Hundreds of local Drupal User Groups all around the world have a SHITLOAD OF TALENT!

    Stop fucking ask yourself where to start. Go to your local user group (or initiate one). Grab yourself some attendees and mentor them in contributing to Drupal. Pay it forward.

    They'll be excited to learn about what's going on with Drupal and how they can contribute to Drupal. Bridging the gap? Totally no better way to do that.

    If you need more support, there's an entire Drupal Core Mentoring effort to support you. A true guide for new contributors to find appropriate tasks for their skill level, with a shittonne of stunning results!

    Help them to contribute to Drupal. So they are going to educate, help, and train others to become better, in turn!

  4. Sanity testing.

    Drupal 5 was the last release that was deployed on drupal.org during development. Gone are the times in which we ate our own dog food before releasing the fancy new shit — determining bugs and revealing nonsense early — when things can still be changed, before publicly releasing to the masses.

    Today, drupal.org is driven by 100+ contributed modules. There's no way to keep that code in sync with the daily API changes that are happening for Drupal core.

    But real world testing is important. Most of us don't have an incentive to use the latest and greatest code. We're missing an essential feedback mechanism to learn about mistakes early. We need qualified feedback from people. Before it is too late. Guess what?

    Hundreds of local Drupal User Groups all around the world can TEST!

    We can restore true production site testing and the lack of that feedback mechanism.

    Whose sites would be better suited than those of local Drupal User Groups? What kind of fancy functionality do you have on there that couldn't be restored within minutes on a fresh site? All we need and all we should need for that use-case is Drupal core... [rewind and circle back into the above]

    (And if all fails, what other data than the user accounts do you really need?)

    Rumors are, some Drupal hosting providers will happily hand your local user group one of their managed full stack environments if you decide to contribute to Drupal core in this way, so your group doesn't have to deal with infrastructure/devops shit and can focus on contributing!
    [Providers: Feel free to state your offer and how to apply in comments!]

  5. Focus on user needs.

    Some initiatives are driving some major architectural changes for Drupal 8 in dedicated working groups. Exciting! Everyone of us is on fucking steroids to get those done! But.

    There are almost no new features that make a difference for users.

    Check. A Wysiwyg editor in core, native inline/in-place editing, user profiles, E-mail fields, Link fields, Date fields, a Token UI, a post-module installation guide, native SMTP support, and whatsoeverfucking nonsense, check.

    There's a lot that needs to be done. And for the most part, there's even agreement that it should be done. But everyone's swamped already!

    This is where you and your local Drupal User Group come in. You have the real needs. You are able to shift the focus, onto features that none of the usual suspects has time to work on.

    Hundreds of local Drupal User Groups all around the world can MAKE THAT SHIT HAPPEN.

The solution.

Attend your local Drupal User Group meetings. Don't tell me you can't. Don't tell me you're above that level. Don't fucking tell me anything. Attend them! :)

Explain to everyone how awesome it is to change the system while we can. Tell them how adjusting it for their needs makes their lives so much fucking easier.

Build your local Drupal User Group web site on Drupal 8. Don't be scared. Take the challenge, learn and help to create something new with others!

  1. Help to build the Snowman installation profile for Drupal 8, for your very own user group.
  2. Attract new Drupal people by just appearing in your local user group.
  3. Solve the Drupal talent problem by mentoring someone (or two)!
  4. Ensure Drupal 8 works, by testing it live.
  5. Make Drupal awesome by solving actual user problems.

You can contribute on so many levels. Don't make the mistake that it was about coding only. There's usability, design, project management/coordination (pushing shit forward), front-end/JS/CSS, manual testing, performance testing, and tons of other areas!

What you get. For free:

  • Native HTML5 output.
    (a.k.a. html5 and html5_tools in core)
  • A new configuration system.
    (a.k.a. Configuration staging [and a bit of Features] in core)
  • A new RESTful HTTP router system?
    (a.k.a. Services in core)
  • A fully multilingual and translatable system?
    (a.k.a. i18n and Entity translation in core)
  • A native layout, page building, and blocks system?
    (a.k.a. Beans, Panels and Page manager in core)
  • Views in core?
    (a.k.a. Views in core)

And after explaining all that fancy new shit to others ;) ...you'll notice how you're suddenly right in the middle of mentoring someone in how to contribute to Drupal.

Do it. Pay it forward.

"You", in all of the above, means you.

May 11 2012
May 11

Drupalcon MunichHere we go again! Drupalcon Munich is just around the corner - August 20 - 24th. That may seem like a long time, but for a veteran of organizing one of these events, I can tell you that the work is ramping up rapidly. All my best to our friends and colleagues over the pond who are, undoubtably, working like crazy. I'm looking forward to enjoying the next convention not being behind the scenes.

Over the last few months I've presented on Agile Scrum twice. Once, as one of the Drupalcamp Austin Keynotes and a second time at Drupalcon Denver with my good friend Stacey Harrison. The presentation evolved from one of the events to the next. I've continued to wear my presenter hat and am ready to do Mark III on the topic of Hybrid Agile Project Management.

Learn from the experiences of Examiner.com's team. We've done it all - cowboy, waterfall, extreme, and agile scrum.

Learn why...

  • Waterfall doesn't always work
  • Agile has a place, but isn't the holy grail
  • Cowboy can kill the relationships you have with your stakeholders
  • How "Fixed Scope" is a lie
  • That a combination of approaches is the answer
  • The Examiner team has carefully honed, updated, improved, and iterated its process for over two years. It continues to evolve, improve, and make development more consistent and predictable.

Project management requires a blend of techniques and tools to effectively shepherd projects from ideation to release. We'll explore and discuss different tools and methodologies that can help make your project successful.

I'd love the opportunity to continue to share my learnings over the last 16 years with a particular focus on the immediate previous 9-12 months. Examiner's process has changed, evolved, improved, and continues to become increasingly awesome. If you're interested in seeing me present, please pop onto my proposal and leave a supporting comment!

Over the last few years I have become great friends with Rick Nashleanas of Monarch Digital. On the last day of Drupalcon Denver, he and I spent quite a few hours chatting, eating, and drinking and ended up cooking up a plan to present together. We're hoping this first faure together might occur in Munich. Come chat with us about recruiting and retention, about active listening and communicating, and about being mentored and mentoring.

Drupal has been around for about a decade. Information Technology predates it about about 5000 years - the Premechanical, the Mechanical, and the Electromechanical segued into The Electronic Age in the 1940s. In the 1950s what we would recognize a Project Management began evolving. There have been Project Management truisms across time.

Sit with two veteran IT managers and leaders (who also predate Drupal) to discuss:

  • Recruiting - Where and HOW do you find people?
  • Retention - How do you keep and nurture those you have?
  • Zen and the art of listening... and hearing. How to hear your clients, your peers, your subordinates, and those you report to.
  • Mentorship - Designers, Coders, Project Managers - How to grow within and beyond your discipline.

Attendees should bring questions and ideas that can be explored by the entire group.

If you'd like to see Rick and me engage in entertaining, informational, and engaging buffoonery - please write a supportive comment on our proposal. Here's to our next community event! Sharing, contributing, and participating brings me joy. I hope I get the chance in Munich.

Dec 24 2010
Dec 24

UPDATE: Fixed formatting. Thanks, Brock!

Two developers recently joined our team. Johnny has worked with Drupal before, and needs a little help getting used to Drupal 6 and Views 2. Elena is an IT architect who is new to both IBM and Drupal. She needs a lot more help getting started, because she doesn’t know what things are called yet and she isn’t yet accustomed to the Drupal way of doing things. For my part, I work on Workflow, node access, and other requirements that require deep Drupal hacking.

I’m learning to check on Elena more frequently and to help her break down tasks. Otherwise, she might get lost or stuck, because she might not yet know where things are or whether she’s getting closer to an answer. I’ve made good progress on the things we’ve planned for this iteration, and I can invest the time into helping our new team members be more productive and learn more effectively.

Both Elena and Johnny have set up their debuggers in Eclipse, so they don’t have to figure out the right places to insert var_dumps. Instead, they can trace through the relevant pieces of code, learning more about the structures and the flow of Drupal websites along the way.

Although I occasionally struggle to explain things I take for granted, I enjoy helping someone who’s new to an area. It helps me remember the things people need to learn. For example, Elena’s work on surveys requires her to learn about nodes, getting values from the $_REQUEST, loading nodes, working with CCK, altering forms, adding new form fields using the Form API, and using Drupal functions for links and text. We broke down the task into the following steps:

  1. Create a CCK node type.
  2. Use hook_form_alter to add some text to the form.
  3. Load a node and fill the information in the form.
  4. Get the extra node ID from the URL.
  5. Adapt form_alter for the case where you’re editing the node.

We’ve managed our planning well, so I don’t feel overcommitted or stretched with the additional mentoring I’ve taken on. The time is an investment that will pay off both in the short-term as well as the long-term. If I can slow down and write more, then the investment can benefit to other people too.

I like this. It’s certainly much better than leaving developers to flounder and work things out on their own, and I learn a lot in the process of helping. Maybe that will be one of my specialties: projects where other people are learning a lot on the fly.

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web