Advertise with Googlier.com http://www.bluedropshop.com/tags/contributing en http://www.bluedropshop.com/blog/contributing-irl <span property="schema:name" class="field field--name-title field--type-string field--label-hidden">Contributing IRL</span> <span rel="schema:author" class="field field--name-uid field--type-entity-reference field--label-hidden"><span lang="" about="http://www.bluedropshop.com/user/8" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">kthull</span></span> <span property="schema:dateCreated" content="2014-10-06T11:29:40+00:00" class="field field--name-created field--type-created field--label-hidden">Mon, 10/06/2014 - 06:29</span> <div property="schema:text" class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>Let’s face facts: I am not a coder. With a lot of caffeine, much googling and more time than is reasonable, I *can* code my way out of a paper bag, but that’s about it.</p> <p>So it is highly unlikely you will ever see my username tied to a module or on a list of contributors. Sure, I create the occasional new issue on a module’s issue queue or provided feedback for a patch I needed, which in itself is a form of contributing. But messing around with core? Funny. Me writing a patch? Nope. Sprinting? I only run when being chased.</p> <p>According to d.o then, I am not a contributor. </p> <p>The outward problem with this is that the language around contributing back to Drupal is code-centric. The current system places emphasis on how many commits you have and how many projects you maintain. But there is hope for those of you who, like me, won't be contributing back code anytime soon. </p> <p>I am a co-organizer for the Fox Valley Drupal Meetup Group in the western suburbs of Chicago. We held our first camp in 2013 and I was part of the team that helped pull it off, and we recently wrapped our 2014 camp.</p></div> Mon, 06 Oct 2014 11:29:40 +0000 kthull 6 at http://www.bluedropshop.com